Files
orca/src
Brennan Benson 7c34a48529 fix(native-chat): show a prompt hook's block as its own row for every agent (#30898)
* fix(native-chat): show a prompt hook's block as its own row for every agent

When a prompt hook refused a message, Codex showed nothing, Claude showed
an unmarked warning the turn fold could hide (with a copy of the prompt),
and Grok read as the user stopping the turn.

Each adapter now writes one warning row, "Blocked by hook: <reason>" or
"Hook stopped: <reason>", marked with the hook-outcome presentation that
the turn fold never hides:
- Codex: a blocked or stopped UserPromptSubmit hook/completed frame
- Claude: a warning informational frame that halts the prompt, worded from
  its structured prompt_submit_outcome when present
- Grok: a HookDenied end, from either completion signal under one row
  identity; the turn ends completed instead of interrupted

Nothing new is saved and nothing changes on the wire beyond the new
presentation value.

* fix(native-chat): end a hook-denied Grok turn on its first signal, and clean older Claude block wording

Follow-ups from the size review of the hook-row change:
- Grok: a hook-denied turn_completed now ends the turn and writes the row
  straight away, instead of waiting for the prompt's answer; a later answer
  changes nothing.
- Claude: when an older Claude sends only its sentence, the row keeps the
  hook's reason and drops the hook path and the copy of the prompt. Whether
  the row shows still depends only on prevent_continuation.
- The turn-ending shape is declared once, the Codex hook payload is read
  once, and the Codex hook row returns early instead of threading through
  the generic frame row.

* test(native-chat): cover hook-block rows with real Grok frames and a preserved send

- Replace the source-derived Grok fixture with frames captured from Grok
  1.0.62 (session, prompt ids renamed to the test's).
- One whole-flow file, three parameterized cases (Codex, Claude current and
  older wording, Grok in every completion order), on the shared timeline
  rig with a per-agent journal identity.
- Each case starts with a send on record and checks it is unchanged after
  the reopen.

* fix(native-chat): word every Claude prompt-hook refusal, and draw the Codex hook row like the others

- Claude: a plugin module's dropped_by_hook / not_passed_on refusal reads "Blocked by hook" too.
- Older Claude sentence: an empty reason no longer turns the prompt copy into the reason; each hook's
  path label goes per line, while a hook's own [TAG]: stays.
- Codex: the prompt-hook row is read once, before classification, and carries no raw-frame
  disclosure, so it matches the Claude and Grok rows. The hook/completed table entry is back to main's.
- Comments the change had made wrong are corrected.

* fix(native-chat): strip only the older Claude sentence's first hook label, as before

Command labels without a slash were kept and labels inside a hook's own text were removed; the
first-line strip is back, with the empty-reason fix kept.

* refactor(native-chat): keep a hook's block row visible as a generic turn notice

The fold never hides a row presented as 'turn-notice', a host notice about the turn, instead of
a hook-specific value; the hook rows write it for every agent.

* fix(native-chat): report a Claude prompt hook's exit-2 block once

With hook events on, Claude also sends the blocking UserPromptSubmit hook's exit 2 as an error
hook_response; that is the block itself, already shown by the halting warning, so it writes no
red hook-failed row. Other hook events and exit codes are unchanged.

* docs(native-chat): say a prompt hook's exit 2 may also be a missing plugin script

* test(native-chat): type the Claude hook-outcome frame as a record

* fix(native-chat): keep a blocked Codex prompt's turn on its own message

Codex never echoes a prompt its hook refused, so its turn was anchored on the send only while
the send read in flight. Once the turn ended the host publishes the send as in doubt, the anchor
fell back to the turn record, and the block row moved to a second turn: live, the chat drew two
"Worked for" bars; after a reopen the bar sat on the row instead of the message. A send in doubt
now keeps anchoring the turn it opened (the first send in flight, else the newest in doubt).

* fix(native-chat): keep refused Codex hook notices outside turns

* revert(native-chat): keep Claude's exit-2 prompt hook_response as main's red row

A missing plugin script also reports exit 2 without blocking, so suppressing it hid a real failure main shows. With a user-added --include-hook-events an exit-2 block shows both rows (known limit).
2026-10-22 00:56:00 -07:00
..