//host still routes to cached remote — spec says worktree, periodRuling 2026-07-09 (URI, Invariants): a scheme-less //name is ALWAYS a worktree; a remote URI always carries its transport scheme. The code decides local-vs-remote by EXISTENCE, not shape: core/loop.js:197-201 (authorityRepo) lets a dotted //host or a _isCachedRemote hit fall through to the wire, NAVNONE only for dotless non-cached misses; verbs/get/get.js:111 classifies cached = !hasScheme && hasAuth and seedCached (get.js:248) resets from the remote-tracking tip. The get.js D7 comment still quotes the pre-ruling GET.mkd ("uses the cached tip if no scheme set") — amended in the wiki this same day.
- //X never reaches the wire or the remote-tracking cache: worktree hit or NAVNONE, for every verb.
- A worktree named like a remote (work/origin) resolves as the worktree, deterministically.
- Cached remote reads (old be head //origin, //origin?feat resets) need their NEW spelling — a ruling, not silent removal; kin of the landed DIS-060 verb/scheme conflation.
- Push/fetch forms are already scheme-ful in the wiki; only the cached-read spelling is open.
//X = wtdir hit or NAVNONE, every verb._isCachedRemote + dotted fall-through gone (loop.js), get.js D7 cached+seedCached gone, head.js peekCached gone, put.js scheme-less //host push form gone; scheme-ful push/fetch + bare be head cached counterpart kept. jab cat //nosuchtree/x → NAVNONE, no wire.test/wire/head-cached/ and test/get/cached/; nav-navnone part b FLIPPED to assert the new rule (dotted //host NAVNONEs too) instead of deleting, keeping part a's swallowed-authority coverage. Suite after: 1 fail = pre-existing bro-view only.