Beagle SCM

BE-053: todo list-all links resolve as ///BE-021/ tree URIs — must run todo BE-021 in the CURRENT context

Reported by gritzko 2026-07-19. In the todo view's list-all board, a ticket link lands on e.g. ///BE-021/ — a (nonexistent) tree URI — instead of executing the spell todo BE-021 in the current context. The view emits hidden U word spells todo <KEY> by design (BE-038), and a spell is (context, verb, args) — the pager must hand it to the verb loop, never resolve it as a relative URI off ///. Somewhere on the emit or follow path the word spell degrades into URI resolution.

Input

Context

• views/todo/todo.js mints todo <KEY>/todo <TOPIC> U spells on every list row and body token (:222, :247, targetSpell :283, page splice :336-357) — no /// is composed in the view; the corruption is downstream (hunk uri slot, pager _uriAt/follow resolver, or the spell-vs-URI classifier).
• Design truth: verbs take (context, arg) and resolve via resolve(context,base,rel); the pager is arg-blind (BRO-024 context model) — a todo BE-021 spell runs in the CURRENT //WT/dir/ context.
• ALL URI/hash resolution goes through core/resolve_hash.js; a word spell must never enter it as a path-relative and climb to ///.
• be tip at filing: 82ef082f (WORK-007 posted).
• Second live variant (gritzko 2026-07-19, a WORK-010 [?] click, empty-context O //: todo STATUS-008): the arg welds onto the CURRENT //WT context — red bar //WORK-010/STATUS-008/: todo, expected //WORK-010/: todo STATUS-008; evidence in BRO-038 STALE. The staged fix predates //WORK/#36040cfb — needs a weave onto the moved tip + a pin for this variant.

Goals

• Repro first: a pty click on a list-all board row pins the wrong ///KEY/ navigation red, then flips green.
• A ticket-link click executes todo <KEY> with the pager's current context unchanged (BRO-024: context mutates only by navigation); the address bar shows (ctx): todo BE-021, not ///BE-021/.
• Whatever path degraded the spell (emit tag, follow resolver, spell classifier) is fixed at the ONE seam — no per-view patching.

Constraints

• Verify through the real UI path — a pty-click repro that flips, not TLV/unit probes alone.
• No reimplementation of URI resolution; the fix routes spells to the verb loop, URIs to resolve_hash — one classifier.
• Rulings in force: pager arg-blind; context only changes by navigation; errors in plain words.

WIP

Design decisions

• Root cause: pager _runSpell (views/bro/pager.js) treated a word-spell's ARG as a nav address — _fillAuth("BE-021") → ///BE-021 → _ctxFrom → context ///BE-021/; the page rendered right, the CONTEXT jumped wrong.
• Fix at the one seam: _isNavAddr(uri) — only a scheme, //authority, or absolute /path navigates; a bare relative arg leaves ctx unchanged and shows verbatim in the bar. ../?ref slot-edits untouched (_applySpell path).
• Noted for later: a relative-FILE click target (cat wiki/Page.mkd) now also keeps ctx at the meta root — consistent with BE-038's context-tree note; _isNavAddr is the seam if per-file descent is ever wanted.

TODOs

• pty repro: fixture board + click driver (scratchpad todopty.py/setup.sh); red pinned ///BE-021/: todo on the unfixed pager.
• seam located + minimal fix in _runSpell (views/bro/pager.js only, ~40 diff lines).
• green: bar shows //: todo BE-021, context unchanged; suite 302/303 == baseline (the one red is the known pre-existing work/getctx pty).

Blockers and bummers

• None.

Outcome

• Staged (put only, NOT posted) in //BE-053 on base //WORK/#82ef082f: views/bro/pager.js.
• Orchestrator re-verified 2026-07-19 by running the pty flip BOTH ways: unfixed pager (//WORK) red ///BE-021/: todo, fixed (//BE-053) green //: todo BE-021; work/view pty suite PASS on the fixed tree.
• Suggested commit: BE-053: keep pager context on a word-spell arg click