1 changed files with 80 additions and 8 deletions
@@ -46797,17 +46797,19 @@ The following table shows which Protocol each pipeline slot implements and what

 ## Milestone Plan

-This section defines the ordered milestone plan for CleverAgents v3.x, mapping architectural features to verifiable deliverables. Each milestone builds on the previous and is independently testable. Milestones v3.0.0 and v3.1.0 are **complete**. This plan covers v3.2.0 through v3.7.0 — the production-ready target.
+This section defines the ordered milestone plan for CleverAgents v3.x, mapping architectural features to verifiable deliverables. Each milestone builds on the previous and is independently testable. Milestones v3.0.0 and v3.1.0 are **complete**. This plan covers v3.2.0 through v3.9.0 — the production-ready target.

-!!! note "Milestone Status (as of 2026-04-08)"
+!!! note "Milestone Status (as of 2026-04-14)"
    - **v3.0.0** ✅ CLOSED — Minimal Local Source-Code Workflow
    - **v3.1.0** ✅ CLOSED — Actor Compiler + Full LLM Integration
-    - **v3.2.0** 🔄 IN PROGRESS — Decisions + Validations + Invariants (85 open / 235 closed)
-    - **v3.3.0** 🔄 IN PROGRESS — Corrections + Subplans + Checkpoints (65 open / 108 closed)
-    - **v3.4.0** 🔄 IN PROGRESS — ACMS v1 + Context Scaling (55 open / 130 closed)
-    - **v3.5.0** 🔄 IN PROGRESS — Autonomy Hardening (486 open / 188 closed)
-    - **v3.6.0** 🔄 IN PROGRESS — Advanced Concepts & Deferred Features (162 open / 150 closed)
-    - **v3.7.0** 🔄 IN PROGRESS — TUI Implementation (461 open / 403 closed)
+    - **v3.2.0** 🔄 IN PROGRESS — Decisions + Validations + Invariants (881 open / 269 closed)
+    - **v3.3.0** 🔄 IN PROGRESS — Corrections + Subplans + Checkpoints (187 open / 111 closed)
+    - **v3.4.0** 🔄 IN PROGRESS — ACMS v1 + Context Scaling (251 open / 140 closed)
+    - **v3.5.0** 🔄 IN PROGRESS — Autonomy Hardening (1104 open / 217 closed)
+    - **v3.6.0** 🔄 IN PROGRESS — Advanced Concepts & Deferred Features (337 open / 153 closed)
+    - **v3.7.0** 🔄 IN PROGRESS — TUI Implementation (602 open / 428 closed)
+    - **v3.8.0** 🔄 IN PROGRESS — Server Implementation (374 open / 133 closed)
+    - **v3.9.0** 🔄 IN PROGRESS — Documentation & Feature Updates (37 open / 4 closed)

 ---

@@ -47066,6 +47068,76 @@ This section defines the ordered milestone plan for CleverAgents v3.x, mapping a

 ---

+### v3.8.0 — Server Implementation
+
+**Goal**: Implement the CleverAgents server and all server-dependent capabilities using the A2A (Agent-to-Agent) protocol standard. This milestone delivers the full server stack — wire protocol, transports, authentication, entity sync, multi-device experience, and deployment — enabling teams to share resources and execute plans in the cloud.
+
+**Spec Coverage**: [Server and Client Architecture](#server-and-client-architecture), [Agent-to-Agent Protocol (A2A)](#agent-to-agent-protocol-a2a), [Authentication and Authorization](#authentication-and-authorization)
+
+**Key ADRs**: [ADR-047](adr/ADR-047-acp-standard-adoption.md) (A2A Standard Adoption), [ADR-048](adr/ADR-048-server-application-architecture.md) (Server Application Architecture)
+
+#### Deliverables
+
+| # | Deliverable | Spec Reference | Verifiable Check |
+|---|-------------|----------------|-----------------|
+| 1 | A2A JSON-RPC 2.0 wire format implemented with `_cleveragents/` extension method routing | §A2A Protocol — Wire Format | Extension methods (`_cleveragents/sync/*`, etc.) route correctly; unknown methods return JSON-RPC error |
+| 2 | A2A stdio transport (local mode — agent as subprocess) | §A2A Transport — stdio | `agents` CLI in local mode communicates with agent subprocess over stdio JSON-RPC |
+| 3 | A2A HTTP transport (server mode — single JSON-RPC endpoint) | §A2A Transport — HTTP | Server exposes single HTTP endpoint; clients connect and issue A2A operations |
+| 4 | LangGraph Platform RemoteGraph integration for server-side actor execution | §Server — Actor Execution | Plans execute on server via RemoteGraph; results streamed back to client |
+| 5 | Server application structure: FastAPI + A2A SDK | §Server Application Architecture | `agents server start` launches FastAPI application with A2A SDK integration |
+| 6 | Authentication: API token issuance and validation | §Authentication and Authorization — API Tokens | `agents server token create` issues token; requests without valid token rejected with 401 |
+| 7 | Authorization: team RBAC (roles: owner, admin, member, viewer) | §Authentication and Authorization — RBAC | Member cannot delete resources owned by another namespace; owner can |
+| 8 | Entity sync via `_cleveragents/sync/*` extension methods | §Entity Sync Protocol | `_cleveragents/sync/push` and `_cleveragents/sync/pull` synchronize entities between client and server |
+| 9 | Multi-device experience: shared namespaces across devices | §Multi-Device Experience | Two clients connecting to same server share namespace; entities visible from both |
+| 10 | PostgreSQL backend for server-side persistence | §Server — Storage Backend | Server stores plans, decisions, resources in PostgreSQL; SQLite used for local mode only |
+| 11 | Docker deployment: `docker-compose.yml` for local server setup | §Server Deployment — Docker | `docker compose up` starts server with PostgreSQL; `agents server connect` connects client |
+| 12 | Kubernetes + Helm deployment charts | §Server Deployment — Kubernetes | Helm chart deploys server to Kubernetes cluster; health checks pass |
+| 13 | `agents server` subcommands: `start`, `stop`, `status`, `connect`, `token` | §CLI Commands — server | All server management commands functional end-to-end |
+| 14 | Test coverage ≥ 97% | §Quality Gates | `nox -s coverage_report` passes |
+
+#### Key Architectural Constraints
+
+- **A2A exclusivity**: All client-server communication uses A2A JSON-RPC 2.0. No REST API endpoints exposed to clients.
+- **Transport abstraction**: `A2aLocalFacade` (stdio) and `A2aServerClient` (HTTP) implement the same interface; application layer is transport-agnostic.
+- **Extension method namespace**: All CleverAgents-specific methods use `_cleveragents/` prefix per A2A extension mechanism; standard A2A methods (`message/send`, `tasks/get`, etc.) are unmodified.
+- **PostgreSQL requirement**: Server mode requires PostgreSQL ≥ 14; SQLite is local-mode only and not supported for server deployments.
+- **RBAC enforcement**: Authorization checks occur in the Application layer before any Domain service is invoked; no Domain service performs authorization.
+- **No deadline assigned**: v3.8.0 has no fixed deadline. Focus on completing M1–M6 milestones (v3.2.0–v3.7.0) before beginning server work.
+
+#### Definition of Done
+
+- All 14 deliverables verified by automated tests
+- `nox` passes with coverage ≥ 97%
+- No open P0/P1 bugs in v3.8.0 milestone
+- Full server stack functional end-to-end: client connects to server, authenticates, executes a plan, and retrieves results
+- Docker and Kubernetes deployment verified in CI
+
+---
+
+### v3.9.0 — Documentation & Feature Updates
+
+**Goal**: Deliver documentation improvements and incremental feature updates that do not fit into earlier milestones. This milestone serves as a rolling catch-all for documentation gaps, minor feature additions, and quality-of-life improvements identified after v3.8.0 ships.
+
+**Scope**: v3.9.0 documentation and feature updates. Specific deliverables are tracked in the v3.9.0 milestone on the issue tracker and will be refined as earlier milestones complete.
+
+#### Planned Areas
+
+- Comprehensive user-facing documentation (guides, tutorials, how-tos) for all features delivered in v3.2.0–v3.8.0
+- API reference documentation generated from source
+- Deployment and operations guide for server mode
+- Migration guides for users upgrading from earlier versions
+- Feature updates and quality-of-life improvements identified post-v3.8.0
+- Example action and actor YAML library expanded with real-world use cases
+
+#### Definition of Done
+
+- All issues in the v3.9.0 milestone closed or explicitly deferred
+- `nox -s docs` passes with no warnings
+- No open P0/P1 bugs in v3.9.0 milestone
+- Documentation site builds and deploys successfully
+
+---
+
 ### Cross-Milestone Quality Gates

 These quality gates apply to **every milestone** and must pass before a milestone is considered complete: