Beagle SCM

DIS-062 DONT: be/ JS post cannot target another LOCAL worktree; trees.mkd example 5 post ///jab/dog has no code path

trees rules "all worktrees may get/post (push/pull) from/to each other directly" (lines 109-112) and example 5 (line 189/194, post-2026-07-12 rewrite; the former example 6) fast-forwards the main tree's jab/dog from the ticket worktree. The pull half exists (GET-038 resolveLocalSource, get.js:141-165). The push half does not: post.js knows exactly three targets — Host slot = wire push, ssh/https only, scheme-less //X explicitly excluded (post.js:127-136, 301-376, BE-033); Query slot = branch FF (post.js:259-292); Path slot = narrow commit scope (post.js:150-155, 216-220). post ///jab gets its authority eaten by authorityRepo (loop.js:189-217), rescopes the run to the main tree's jab and degrades to a bare post there → POSTNONE; post ../../jab parses as an out-of-tree NARROW → NAVESCAPE/garbage.

Input

Context

• post.js:127-136 if (u.host) wire-only gate; pushRemote post.js:301-376; BE-033 excludes scheme-less authorities from push.
• //X on arg0 is consumed as nav context by authorityRepo (loop.js:189-217) — correct per the verbs-resolve-args law, but it leaves post no way to say "target that tree".
• Path args are narrow slots (post.js:150-155, 216-220), so a filesystem path to another wt cannot be a target either.
• Prerequisite named in code: get.js:286-292 (BE-030 comment) — distinguishing an EXPLICIT //other operand from the injected context is "a SEPARATE follow-up"; shared prerequisite with DIS-063.
• /// from a ticket worktree currently names the LAUNCH tree, not the main tree, in the flat layout (rootTop discover.js:279-287, BE-045 fallback) — that mapping rides BRO-024:52, do not fix here.

Goals

• A post arm for a local worktree target: an explicit wt URI or path operand resolves (reuse get.parseRemote localish + GET-038 redirect) to the target's anchor; FF the target's tracked ref + wtlog row like a local receive; FF-only gate, no forced updates.
• post ///jab/dog works from the ticket wt (trees example 5); the fs-path spelling (jab post ../../jab, the deleted example 6) is optional sugar, not spec.
• Spec sweep: POST slot table + Verbs:18 gain the local-wt target form.

Constraints

• Depends on the DIS-061 ruling for WHAT gets fast-forwarded (ref vs wt row vs both) — land after or together.
• Explicit-operand-vs-context detection must not weaken NAVESCAPE/arg0-only (BE-039, memory law); the target is an operand, not a context move.
• Repro-first: a two-wt fixture, post from A targeting B, assert B's ref+row moved and A untouched.

WIP

Design decisions

• (none yet)

TODOs

• repro fixture: two local worktrees, FF-able divergence
• operand classifier: explicit wt URI/path target vs context authority (coordinate the BE-030 follow-up with DIS-063)
• local-receive FF: refs + wtlog + checkout of the target
• POSTNONE/NAVESCAPE errors for non-FF and out-of-scope targets
• POST.mkd + Verbs.mkd target forms

Blockers and bummers

Outcome

• FILED 2026-07-12 (trees.mkd audit); ref/row half landed as advanceWorktree (post.js), the checkout half never did.
• STALE 2026-07-16: superseded by POST-026, which owns the post-recursion rebuild + the wt-target get-style checkout.