Specification Status

User-facing configuration pages describe the current source tree. Specifications also preserve proposals and design decisions; a draft is not an installed-binary configuration reference.

Specification	Status
Agent messaging	Implemented; governing contract for send_message agent-to-agent messaging
Subagent handles	Draft proposal; short tree-unique handles for model-facing session references
Tree-scoped session ownership lock	Implemented; one owner.lock per root session tree, no lock files for delegated children
Store lock retention	Implemented; bounded acquisition, commit-time CAS, lock-free OAuth reads, and per-run daemon token for ~/.cookie-agent secure stores
Tool output streams and artifact reads	Implemented; correctness and performance/code-quality reviews passed
Model configuration	Current root draft preserved; implemented in the current source tree and independently reviewed
Documentation overhaul	Preserved draft; this documentation reorganization was separately authorized
Refactor phase 1: test layout and build hygiene	Implemented; split test monoliths, collapse engine test hooks, dev-profile debuginfo
Refactor phase 2: dependencies, bindings, CI, syntect	Implemented; single reqwest via oven-sdk, dropped TypeScript bindings, CI diet, crates.io syntect
Refactor phase 3: module splits	Implemented; split Inner, App, transcript renderer, SessionStore, TUI reducer
Goal mode and producers	Implemented, approved product contract
Protocol	Implemented wire contract
Events	Implemented persistence and subscription contract
Schemas	Current compatibility contract
Tools	Implemented tool arguments, output, retention, and limits
System prompt	Implemented composition contract
Security boundaries	Current platform and local-execution guarantees and limitations

The two draft pages include the current repository source at every build, not copied snapshots. Their original status text is preserved, not silently promoted to an approved specification. Consult Providers for the implemented model schema.