--no-record is silently dropped by the press/fill/click readers — the documented state-repair flow doesn't work via CLI

[thymikee]

Summary

The state-repair divergence hint tells agents: "fix app state with --no-record actions, then replay --from N". That flag is silently dropped — the press / click / longpress / fill CLI readers never forward noRecord into the daemon request. The grammar accepts --no-record, the reader ignores it, and the action records anyway.

During an armed (--save-script) repair this means an agent's state-fix mutations are recorded into the healed script as spurious flow steps — e.g. a press "Back" used only to reset app state becomes a step in the heal, so replaying the healed script performs an unintended action. This is the documented repair flow not working.

Evidence

src/commands/interaction/interactions.ts:

• press reader (~line 45): spreads commonInputFromFlags / selectorSnapshotInputFromFlags / repeatedInputFromFlags / settleInputFromFlags, plus target and verify — no noRecord. Same for click, longpress, fill.
• get reader (~line 100): fix(replay): default-exclude observation-only reads from repair heals, add --record opt-in (#1271 stage 2) #1303 just fixed this one by explicitly adding noRecord: flags.noRecord on top of its existing ...commonInputFromFlags(flags) spread — which proves the common spread does not carry noRecord. Its comment states the flags were "silently dropped by this reader".

Only open (src/commands/management/app.ts) forwarded noRecord before #1303.

Relationship to #1271

• record-and-heal: armed --save-script repair records the agent's read-only diagnostics into the healed script (can introduce new divergences) #1271 stage 1 (fix: warn agents that armed-repair diagnostic reads are recorded too (#1271 stage 1) #1287, merged) shipped guidance telling agents to --no-record their diagnostic reads — that guidance was inert for the same reason, until fix(replay): default-exclude observation-only reads from repair heals, add --record opt-in (#1271 stage 2) #1303 fixed the read readers (get, find, snapshot).
• fix(replay): default-exclude observation-only reads from repair heals, add --record opt-in (#1271 stage 2) #1303 explicitly scoped mutations out (it's orthogonal to observation-only exclusion). This issue is that remainder: the same dropped-flag class, for mutating commands, where it breaks the state-repair flow.

Fix

Forward noRecord (and the new record) in the mutating readers, mirroring what #1303 did for get/find/snapshot. Audit every reader for the same omission rather than fixing case-by-case — the root shape is "each reader hand-forwards flags, so any reader can silently drop one."

Regression: a --no-record press performed inside an armed repair segment must NOT appear in the healed script; and the healed script must not contain state-fix mutations.

[thymikee]

Triage: confirmed CLI command-surface bug. The grammar accepts the flag but mutating interaction readers do not project it into the daemon request, so the documented repair workflow records state-reset mutations. Labeled bug + ready-for-agent. Implementation should either stack on #1303 (for the new --record half) or land after it; the existing --no-record forwarding fix and its healed-script regression are independently actionable.