DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3_COVERAGE_AUDIT.md
Current Specs/DOC11/DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3_COVERAGE_AUDIT.md
# DOC11 R15 Amendment Proposal R3 — Coverage Audit **Date:** 2026-05-19 **Audited document:** `DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3.md` **Release ceiling:** stable OpenClaw through `2026.5.18`; `2026.5.19-beta.1` watch-only. ## Result The R3 proposal is complete enough to use as the source document for drafting the DOC11 R14 → R15 redline. It supersedes Proposal R2 before implementation. ## Coverage checklist | Area | Included in R3? | Notes | |---|---:|---| | Stable release basis through `2026.5.18` | Yes | Watch-only handling for `2026.5.19-beta.1` included. | | No-phantom-control / desired-effective discipline | Yes | Common primitives and acceptance tests require it. | | Unified OpenClaw feature dashboard | Yes | Section 3. | | `commands.list` / command catalog | Yes | Section 4. | | Externalized plugin lifecycle | Yes | Section 5. | | Plugin runtime deps / install repair / ClawHub metadata | Yes | Section 5. | | Plugin-owned Gateway method registry | Yes | Sections 4 and 5. | | Typed tool-plugin builder | Yes | Section 5. | | Active-run `/steer` | Yes | Section 6. | | `/btw` / `/side` side-result behavior | Yes | Section 6. | | Side-result memory policy correction | Yes | Section 6.3. | | Follow-up / collect / interrupt queue modes | Yes | Section 6. | | Branch metadata without fake branch UI | Yes | Section 7. | | Dual browser model | Yes | Section 8. | | Browser dialogs / `blockedByDialog` / dialog answer | Yes | Section 8. | | Browser evaluate timeout and URL allowlist | Yes | Section 8. | | Chrome extension observation bridge | Yes | Section 8. | | Browser artifacts / DOC20 obligations | Yes | Section 8.4. | | Provider-native and plugin-backed search policy | Yes | Section 9. | | SSRF/private-network/proxy controls | Yes | Section 9. | | Codex app-server/code-mode migration | Yes | Section 10. | | Codex Computer Use | Yes | Section 10. | | Voice/Talk/TTS/STT/realtime controls | Yes | Section 11. | | Google Meet deferred / inventory-only | Yes | Sections 11 and 25. | | Compaction owner/trigger/source refs/capture guard | Yes | Section 12. | | OpenClaw memory controls and ELNOR precedence | Yes | Section 13. | | Diagnostics/export/startup/restart/trajectory | Yes | Section 14. | | Config reloadability | Yes | Section 14. | | Provider quota usage | Yes | Sections 14 and 15. | | Model catalog source plan/auth/fallback | Yes | Section 15. | | Subagent readback / parent review / handoff | Yes | Section 16. | | Paired-node file-transfer controls | Yes | Section 17. | | Sender-scoped tool authority | Yes | Section 18. | | Streaming/progress/final delivery normalization | Yes | Section 19. | | ACP fallback backends | Yes | Section 20. | | Settings page implementation map | Yes | Section 21. | | Route/event closure | Yes | Section 22. | | Acceptance tests | Yes | Section 23. | | Deferrals/watch-only rows | Yes | Section 25. | ## Known issues remaining No blocking issue remains in the proposal. The actual DOC11 redline must still perform route appendix, event appendix, control matrix, and Appendix U closure against the compiled DOC11 R14 document. ## Follow-up before redline Review R3 for desired scope choices, especially: 1. whether to keep `2026.5.19-beta.1` watch-only; 2. whether to include any branch-chat UI commitments beyond readback hooks; 3. how aggressively to expose provider-native search in the default settings page; 4. whether paired-node file transfer should default to disabled or approval-required.