be get //name — wrong rev (branch tip) and wrong destination tree
Ruling 2026-07-09 (GET, Nav): be get //ABC-123 checks out, in the CURRENT context wt, the revision worktree ABC-123 is on — the authority arg supplies the rev, irrespective of context. The code does neither: authorityRepo (core/loop.js:181) re-anchors be.repo to //ABC-123 and strips the authority, so inRepoSeed (verbs/get/get.js:450) runs ON ABC-123 — it FFs ABC-123 itself; and D3' (get.js:524-532) takes tip = k.resolveRef(curBranch) — the BRANCH TIP — not curTip().sha (the rev the wt is actually on, read at get.js:455). The destination half is acknowledged as a follow-up in the get.js:331-338 comment (BE-030 adjacent); the tip-vs-curSha half is new.
//MAIN, be get //ABC-123 resets MAIN's wt to ABC-123's curTip().sha; ABC-123 untouched.: spell //ABC-123, no verb) must still hop the context; only GET-with-authority changes.be get //src from the other → today FFs src to tip.curTip() as the source REV; destination = the context wt.//peer-as-SOURCE follow-up (also referenced by BE-031 S3).