Three proposal documents, numbered in dependency order: - RFC 009: an abstract, append-only, event-based SessionPersistence service over the existing SessionEvent log (no parallel persisted type), a JSONL impl, a SessionMeta header seam, and an async AgentLoop.resume path. Design informed by Codex/Claude Code/ opencode/pi. Core design point; unblocks resume + ACP session/load. - RFC 010: ACP (Agent Client Protocol) support as a dsh-acp client-driver plugin on @agentclientprotocol/sdk, mapping ACP onto the agent/* events and the tools/execute permission seam. Builds on 009 for session/load; single active session. - RFC 011: multiplex concurrent ACP sessions over one connection (bridge-layer change; downstream of 010).
1.6 KiB
1.6 KiB
RFCs
Proposals for substantial future work — reviewed before implementation, unlike ADRs (which record decisions already made). Each RFC groups a related set of ideas from the quality/robustness proposal (2026-06-11); statuses move proposed → accepted → implemented (then usually graduate to an ADR).
| # | Title | Status |
|---|---|---|
| 001 | Property-based testing for protocol-shaped code | implemented |
| 002 | Mutation testing as the coverage counterweight | proposed |
| 003 | Deterministic tests + replay invariant fixture + race stress | proposed |
| 004 | Architectural rules: dependency-cruiser, adapter conformance kit | proposed |
| 005 | Runtime arg validation, structured error taxonomy, dev-mode invariants | implemented |
| 006 | Doc-sync enforcement and API extractor reports | implemented (pts 1-2; pt 3 deferred) |
| 007 | Supply chain checks and vendor drift verification | proposed |
| 008 | Deep-readonly public surfaces | implemented (revised) |
| 009 | Durable session persistence — abstract, append-only, event-based store | proposed |
| 010 | Agent Client Protocol (ACP) support for external editors | proposed |
| 011 | Multiplex concurrent ACP sessions over one connection | proposed |