Beagle SCM

BRO-015: nav keys replay MUTATION verbs — back/R re-drive the tracked spell, with its rest args stripped

The pager's back key (-/BS → popView+_refresh, pager.js:471) and R refresh (pager.js:728-741) re-EXECUTE the view's tracked spell. Two compounding defects: (1) _driveApply (pager.js:713-722) tracks only (verb, arg0) and discards rest, so the re-driven spell loses the verb's real arguments; (2) _refresh re-drives ANY verb, including mutations. :post ?feat 'msg' then - re-drives post //WT/x?feat — post's DIS-054 bare-advance form (post.js:592-593, needs NO message) — a branch FF fired by a navigation key. Nav.mkd:33 wants an abandoned post … screen inert on back. Found in the 2026-07-07 pager nav audit, runtime-VERIFIED (headless Pager + driveSpell stub). Method Issues.

Input

Context

• _applySpell composes {verb, arg0, rest} (shared/spell.js compose) and drives buildSpell(c), but _driveApply stores only view.verb+view.uri (= arg0); rest is gone.
• VERIFIED trace: :grep "needle" drives grep("//WT/dir/file.c?br","needle"); pressing R re-drives grep //WT/dir/file.c?br — the pattern is lost, the view silently becomes a different query. Quoting is the ONLY way to pass a grep pattern in the pager (barewords become paths), so EVERY pager grep view has a broken refresh.
• VERIFIED trace: :post "hello world" tracks verb=post uri=//WT/dir; navigate away, press - → drives post //WT/dir (message-less → POSTNOMSG err); with a tracked ?ref the re-drive is the bare-advance REF MUTATION, no error, no confirmation.
• The same class hits the initial columnar view (bare verb re-fire) — that anchor loss is BRO-017.
• LIVE SIGHTING 2026-07-17 (gritzko, BRO-030 session): after a real post, pager nav around status //BRO-030[/test] surfaced err: \?` can not be fast-forwarded` — post.js:326's bare-trunk advance re-driven by the replay; the status verb itself never calls post (clean CLI repro).

Goals

• Back/R NEVER re-execute a mutation verb; a mutation-result view refreshes as an inert re-render (or refuses with a message).
• Refresh re-runs the EXACT call that produced the view: track the full {verb, arg0, rest} (or the built spell string) on the view object.
• Repro tests: grep-with-pattern refresh keeps the pattern; a post-result view's back/R fires no second post.

Constraints

• views/bro/pager.js (_driveApply/_runSpell/_refresh); a read-vs-mutation predicate may reuse loop.js SCHEME_ALLOW / the projector-vs-verb split (DIS-060).
• Repro-first; do not touch the working plain/tlv paths.

WIP

Design decisions

• (pending) mutation gate: projector allowlist vs a verb-declared readonly flag.

TODOs

• Repro: refresh drops rest args (grep pattern) — BRO-024 test/bro/context legs (g)-(j).
• Repro: back re-fires post bare-advance on a ?ref view — verified live in the BRO-024 iter-3 session (:put x then R re-ran the put).
• Track the full call on the view; gate _refresh to read views; suite green — view.call={verb,spell,context,disp} + the isMutation refresh refusal.

Blockers and bummers

• None known.

Outcome

• Fixed as part of BRO-024 iter 3 (recorded invocations + mutation-replay guard), commit 5ebf0c8d in work/BRO-024; flip to DONE when that branch merges to trunk.