jab get ../../jab/dog / jab get ../TKT-123 has no code path; wiki spells the form file:../proj onlytrees example 5 (lines 199-210, post-2026-07-12 rewrite) pulls between worktrees with BARE relative paths: jab get ../../jab/dog (the main tree's sub as source) and jab get ../TKT-123 (a sibling wt as source). No code path: isRemoteSeed (get.js:261-267) admits a seed only with a scheme, an authority, or a .be-suffixed path; a bare relative path falls through to inRepoSeed (get.js:292-293) and parses as an in-repo path/branch — out-of-tree → NAVESCAPE/garbage. The wiki documents only the schemed spelling file:../proj?feat (GET.mkd:31). The Bro spells of the same example (get ///jab/dog, get //TKT-123/) are DIS-063's operand classifier; THIS ticket is the scheme-less fs-path SHELL form only.
.be suffix; dispatchRow get.js:284-293 routes everything else to inRepoSeed.file:../proj?feat is the only documented local-path source form; Verbs.mkd:27 routes a bare tracked-path token to restore, :29 any /-bearing token parses as a URI.jab post ../../jab, the deleted example) as optional sugar, not spec; the rewrite added these GET twins, making the form spec-ish — hence its own ticket.file: spellings (user edit) — pick one.jab get ../TKT-123 == jab get file:../TKT-123; precedence stays deterministic — an IN-tree path is an in-repo seed (restore/subtree), only an out-of-tree path holding a .be/wtlog anchor seeds from it, anything else NAVESCAPEs; no existence-probe ambiguity on tracked names.get ../TKT-123 FFs the caller from the sibling; a tracked sub/dir arg must stay a restore (precedence leg).file: spellings in the post