[jbeda]

Stage

Plan / Interface

Summary

• define transient tool.result.available for every effective tool-result path
• preserve canonical tool.result ordering, persistence, model history, and cancellation semantics
• require independent card settlement so operators can identify the long-running call in a concurrent batch
• record the public event, live-only persistence boundary, guardrail release boundary, and client replacement behavior in ADR 0370

Contract highlights

• availability follows PostToolUse processing, repair, inbound review, and any result-release decision
• clean siblings may become available around an unrelated serialized release prompt
• Converse, live HTTP/SSE, and StreamSessionLive carry availability
• event-log recording, replay/watch surfaces, snapshots, recorder output, counters, and model history omit availability
• Mecatui and ACP update one call-ID-correlated card; canonical result confirms or replaces the transient payload
• canonical read-batch results remain behind the complete ordered drain

Verification

• bash .claude/skills/to-acceptance-plan/scripts/check-acceptance-plan.sh docs/acceptance/tool-result-availability.md
• bash .claude/skills/to-acceptance-plan/scripts/check-acceptance-plan-test.sh
• task docs
• advisory design review completed; disconnect drain, exact live/replay surfaces, cancellation cases, and serialized event sequencing folded into the contract

Tracking: #1976