v0.9.0: complete versioned exec stream receipts and tool lifecycle metadata

[Hmbown]

Problem

Exec-stream JSON now has the foundation for typed terminal outcomes, but the terminal receipt and tool lifecycle are not yet complete enough for replay, support, or cost attribution. Consumers need an additive, versioned contract rather than inferring execution facts from prose.

Evidence

The current release lane distinguishes success, cancellation, model error, tool error, and infrastructure error. It still lacks a complete terminal receipt covering routing, timing, retries, usage/cost inputs, sandbox posture, and artifact/config identity. Tool lifecycle records also need uniform timing, side-effect, error, and truncation metadata.

Expected behavior

• Keep stdout JSONL-pure in stream mode.
• Add a schema/version discriminator and additive fields that old consumers may ignore.
• Emit one terminal receipt with provider/model route, termination reason, typed error category, duration, retry count, usage/cache facts when available, permission/sandbox posture, and relevant binary/config/prompt/tool hashes.
• Give tool lifecycle events a stable tool name/id, start/end timestamps or duration, side-effect status, typed error, and truncation/artifact metadata.
• Represent unavailable provider facts as absent/unknown, never fabricated values.

Likely files

• crates/tui/src/main.rs
• crates/tui/src/core/events.rs
• crates/tui/src/core/error_taxonomy.rs
• crates/tui/src/tools/truncate.rs

Acceptance criteria

• The stream schema is explicitly versioned and backward-compatible through additive fields.
• stdout remains valid JSONL with diagnostics confined to stderr/events.
• Success, model error, tool error, infrastructure error, cancellation, and approval denial each end with an unambiguous receipt.
• Tool completion events include duration, side-effect status, typed outcome, and truncation/artifact facts.
• Deterministic tests validate required fields and absence semantics.

Related

• v0.9.1 architecture: Fleet / Workflow / Lane / Runtime product model (canonical tracker) #4175 tracks the broader Fleet / Workflow / Lane / Runtime architecture.

[Hmbown]

Resolved by #4361 at merge commit 9bfa466. The versioned JSONL exec stream now records terminal/tool receipts, typed outcomes and termination reasons, and explicit absence semantics with regression coverage. Full hosted macOS and Windows suites, local TUI tests, and the merged dogfood build are green.