docs: architecture — add milestone navigation plan

Add acceptance criteria for v3.6.0, document milestone navigation coverage across v3.2.0–v3.8.0, and record the change in the changelog. ISSUES CLOSED: #7564
2026-04-14 15:39:46 +00:00
2 changed files with 18 additions and 0 deletions
@@ -110,6 +110,11 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
  `docs/development/automation-tracking.md` and the new
  `docs/development/docs-writer.md` reference.

+- **Docs — Milestone Plan navigation guide**: Added a Milestone Plan section to the
+  architecture specification that maps v3.2.0–v3.8.0 milestones to their spec
+  coverage, acceptance criteria, and architectural constraints. Includes explicit
+  acceptance criteria for v3.6.0 and documents the change for implementers.
+
 ### Changed

 - **Decision Tree Full ULID Display** (#5825): The `agents plan tree` command now
@@ -47000,6 +47000,19 @@ This section defines the ordered milestone plan for CleverAgents v3.x, mapping a
 | 16 | Code review tool examples in `examples/` directory | §Workflow Examples | `examples/code-review/` contains working action YAML and actor YAML |
 | 17 | Test coverage ≥ 97% | §Quality Gates | `nox -s coverage_report` passes |

+**Acceptance Criteria:**
+
+- [ ] ACMS exposes ARCE, temporal archaeology, and plan-decision-context strategies as selectable options via the `ContextStrategyRegistry`
+- [ ] ProviderRegistry auto-discovers third-party LLM providers through entry point registration (`langchain-*`, `cleveragents-*` packages)
+- [ ] Resource registry supports cloud, database, and virtual resource types with spec-defined schema validation and inheritance rules
+- [ ] Container tool execution provisions and tears down devcontainers on demand for tools flagged `execution: container`
+- [ ] Scope chain resolution extensions can be registered and invoked during strategize/execute phases through the ScopeChainResolver plugin API
+- [ ] Cost and session budget enforcement halts plan execution when limits are exceeded and records the safety profile decision trail
+- [ ] E2E workflow specification tests cover at least one advanced concept scenario (context strategy swap, provider override, or container tool)
+- [ ] Code review tooling example is published as a reference plugin and linked from the documentation
+- [ ] Plugin architecture extension points are documented in the specification and validated with at least one reference implementation
+- [ ] Test coverage ≥ 97%
+
 #### Key Architectural Constraints

 - **ACP deprecation**: The `acp` module is deprecated; all new code uses `a2a`. The `acp` module may remain as a compatibility shim but must not be used in new implementations.