3 people 76db418212 Address review: every answered agent target fences a late Go ...

Only targets answered with a session were fenced against a delayed
generate event. A request that timed out (or ended in another failure
verdict the CLI already reported) was simply forgotten, so a Go whose
capture outlasted the timeout still opened a session nobody was told
about.

`resolve_agent_target` now records every terminal resolution, with the
answering session when the verdict carried one, and
`agent_target_refusal` refuses a generate event for any answered
target unless it comes from the answering session itself. The
browser_timeout instructions no longer send the agent to live-status
for a session that can no longer start. The overlay's refusal toast
covers both causes.

Tests: a Rust integration case and a Node protocol case (claim, time
out, late Go refused with 409 and nothing journaled), a unit test for
the timeout instruction; contract doc updated.

Written with AI assistance (Claude).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-09-15 05:45:49 +05:00

..

agents

Use GPT Image 2.5 Flare and native transparent assets (#786)

2026-09-08 15:52:38 -07:00

reference

Port /impeccable generate to the engine crates

2026-09-15 05:45:49 +05:00

scripts

Address review: every answered agent target fences a late Go

2026-09-15 05:45:49 +05:00

SKILL.src.md

Add /impeccable generate: agent-initiated live variants (Node-era squash)

2026-09-15 05:45:49 +05:00