BRO-038: pager welds a verb's KEY arg into the context — //WT/KEY/: verb instead of //WT/: todo KEY

Now: DONT

Superseded by BE-053 — the SAME _runSpell weld, root-caused and fixed at the _isNavAddr seam, staged in //BE-053 on base #82ef082f. This page stays as evidence of the second live variant: the arg welded onto a //WT context (//WORK-010/STATUS-008/: todo, red bar), not just the ///KEY/ climb BE-053 pinned. Remaining work (weave onto the moved //WORK/ tip + pin this variant) runs under BE-053.

Input

Context

Reported by gritzko 2026-07-19, live: a WORK-010 [?] click (O-invite //: todo STATUS-008) shows the ticket fine, but the address bar goes RED: //WORK-010/STATUS-008/: todo. Expected //WORK-010/: todo STATUS-008 — context kept (empty O context = current), verb todo, arg STATUS-008.

Weld site: views/bro/pager.js _runSpell tail — _splitSpell(s) takes the whole arg as the view ADDRESS, _fillAuth grafts the previous //authority onto the bare KEY, then the BRO-024 "click IS navigation" leg this.ctx = this._ctxFrom(this.view.uri) reduces that non-path into the context.
RED = the welded context names no worktree dir; the ticket key rides the context as a phantom path segment.
Same weld on every todo KEY click (the todo board's own list links) — pre-dates WORK-010, [?] just surfaced it on wt rows; flagged in the WORK-010 worker report.
BRO-024 owns the address form: prompt-like //WT/dir/: verb args, context is $PWD-like, mutated ONLY by navigation. BRO-025 owns the three-part call (context · verb · args); view.call = {verb, spell, context} is already recorded at the weld site.

Goals

A ticket-link click keeps the pager context; the address bar reads //WT/: todo KEY (BRO-024 prompt form), not red.

A verb arg that is no path target must not reduce into the context; context changes by navigation only.
Red-first pty repro: todo (or work) view → click a ticket link → assert the address form, the unchanged context, and no red.

Constraints

Fix the pager's address recording (the _runSpell tail / _ctxFrom leg), not the link mints — the WORK-010 mint is correct and test-proven.
Rulings in force: context only by navigation (BRO-024); verbs resolve their own args, the pager is arg-blind; resolution via core/resolve_hash.js only; no manual URI parsing/composition.
Real nav clicks (dir/file targets) keep their reduce-to-context behavior — no cat/status navigation regression.
Overlaps unlanded //WORK-010 ([?] mint + view test); the generic todo-link repro must not depend on it.

WIP

Design decisions

TODOs

red: pty repro pins the post-click address — //WT/: todo KEY, context unchanged, no red
fix: non-path verb args stay out of _ctxFrom; nav targets still reduce
green: pty + todo/work view tests; cat/status click still recontexts