[AUTO-SPEC] Proposal: Add v3.8.0 milestone plan section to docs/specification.md #8877

Open
opened 2026-04-14 03:17:07 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit Message: docs(spec): add v3.8.0 Server Implementation milestone plan section
  • Branch: docs/spec-add-v3.8.0-milestone-plan

Background and Context

The docs/specification.md Milestone Plan section currently covers milestones v3.2.0 through v3.7.0 only. The v3.8.0 milestone (Server Implementation) exists in the repository with 373 open issues and 133 closed issues but has no corresponding Milestone Plan section in the specification.

The spec header at line 46800 explicitly states: "This plan covers v3.2.0 through v3.7.0 — the production-ready target." However, v3.8.0 is actively being worked on (373 open issues) and requires spec coverage per the spec-first development principle.

Note: PR #8846 (AUTO-ARCH-5) adds a v3.9.0 section but skips v3.8.0. Both sections are needed.

Expected Behavior

The docs/specification.md Milestone Plan section includes a ### v3.8.0 — Server Implementation subsection that accurately describes the goals, deliverables, and references for the v3.8.0 milestone, consistent with the format used for v3.2.0–v3.7.0 sections.

Acceptance Criteria

  • A ### v3.8.0 — Server Implementation section is added to the Milestone Plan in docs/specification.md
  • The section states the goal: Implement the CleverAgents server and all server-dependent capabilities using the A2A protocol standard
  • The section references existing spec sections: Server and Client Architecture, A2A Protocol
  • The section references key ADRs: ADR-047 (A2A Standard Adoption), ADR-048 (Server Application Architecture)
  • The section lists all key deliverables from the v3.8.0 milestone description
  • The milestone status note is updated to include v3.8.0 and v3.9.0
  • The section follows the same format as existing v3.2.0–v3.7.0 sections
  • A PR is created and passes review

Subtasks

  • Draft ### v3.8.0 — Server Implementation section content
  • Include goal statement referencing A2A protocol standard
  • Add cross-references to spec sections: Server and Client Architecture, A2A Protocol
  • Add ADR references: ADR-047, ADR-048
  • List all key deliverables:
    • A2A JSON-RPC 2.0 wire format and _cleveragents/ extension method routing
    • A2A stdio transport (local mode)
    • A2A HTTP transport (server mode)
    • Server application structure (FastAPI + A2A SDK)
    • Authentication and authorization (API tokens, team RBAC)
    • Entity sync via _cleveragents/sync/* extension methods
    • Multi-device experience, shared namespaces, PostgreSQL backend
    • Server deployment (Docker + Kubernetes + Helm)
  • Update the milestone status note to include v3.8.0 and v3.9.0
  • Open PR targeting main with the spec update
  • Obtain human approval and merge

Definition of Done

This issue should be closed when:

  1. A PR has been merged to main that adds the ### v3.8.0 — Server Implementation section to the Milestone Plan in docs/specification.md
  2. The milestone status note has been updated to include v3.8.0 and v3.9.0
  3. The section follows the established format of existing milestone plan sections

Proposal: Add v3.8.0 Milestone Plan Section

Type: Spec Update Proposal (Step 1 of 2)
Proposed by: AUTO-SPEC Supervisor (spec-update-pool-supervisor)
Priority: Medium


Discrepancy Detected

The docs/specification.md Milestone Plan section currently covers milestones v3.2.0 through v3.7.0 only. The v3.8.0 milestone (Server Implementation) exists in the repository with 373 open issues and 133 closed issues but has no corresponding Milestone Plan section in the specification.

The spec header at line 46800 explicitly states: "This plan covers v3.2.0 through v3.7.0 — the production-ready target." However, v3.8.0 is actively being worked on (373 open issues) and requires spec coverage per the spec-first development principle.

Note: PR #8846 (AUTO-ARCH-5) adds a v3.9.0 section but skips v3.8.0. Both sections are needed.


Classification

Implementation found a better approach → The v3.8.0 milestone is being actively developed without spec coverage in the Milestone Plan. The spec should be updated to reflect this.


Proposed Change

Add a ### v3.8.0 — Server Implementation section to the Milestone Plan in docs/specification.md, following the same format as v3.2.0–v3.7.0 sections. The section should:

  1. State the goal: Implement the CleverAgents server and all server-dependent capabilities using the A2A protocol standard
  2. Reference existing spec sections: Server and Client Architecture, A2A Protocol
  3. Reference key ADRs: ADR-047 (A2A Standard Adoption), ADR-048 (Server Application Architecture)
  4. List key deliverables from the v3.8.0 milestone description:
    • A2A JSON-RPC 2.0 wire format and _cleveragents/ extension method routing
    • A2A stdio transport (local mode)
    • A2A HTTP transport (server mode)
    • Server application structure (FastAPI + A2A SDK)
    • Authentication and authorization (API tokens, team RBAC)
    • Entity sync via _cleveragents/sync/* extension methods
    • Multi-device experience, shared namespaces, PostgreSQL backend
    • Server deployment (Docker + Kubernetes + Helm)
  5. Also update the milestone status note to include v3.8.0 and v3.9.0

Approval Required

This is a Step 1 Proposal. Human approval is required before a spec-update-worker will be dispatched to create the actual PR.

To approve: Add the needs feedback label or comment "APPROVED" on this issue.
To reject: Close this issue.


Automated by CleverAgents Bot
Agent: new-issue-creator
Supervisor: Spec Update | Agent: spec-update-pool-supervisor

## Metadata - **Commit Message**: `docs(spec): add v3.8.0 Server Implementation milestone plan section` - **Branch**: `docs/spec-add-v3.8.0-milestone-plan` ## Background and Context The `docs/specification.md` Milestone Plan section currently covers milestones v3.2.0 through v3.7.0 only. The v3.8.0 milestone (Server Implementation) exists in the repository with 373 open issues and 133 closed issues but has **no corresponding Milestone Plan section** in the specification. The spec header at line 46800 explicitly states: *"This plan covers v3.2.0 through v3.7.0 — the production-ready target."* However, v3.8.0 is actively being worked on (373 open issues) and requires spec coverage per the spec-first development principle. Note: PR #8846 (AUTO-ARCH-5) adds a v3.9.0 section but skips v3.8.0. Both sections are needed. ## Expected Behavior The `docs/specification.md` Milestone Plan section includes a `### v3.8.0 — Server Implementation` subsection that accurately describes the goals, deliverables, and references for the v3.8.0 milestone, consistent with the format used for v3.2.0–v3.7.0 sections. ## Acceptance Criteria - [ ] A `### v3.8.0 — Server Implementation` section is added to the Milestone Plan in `docs/specification.md` - [ ] The section states the goal: Implement the CleverAgents server and all server-dependent capabilities using the A2A protocol standard - [ ] The section references existing spec sections: [Server and Client Architecture](#server-and-client-architecture), [A2A Protocol](#agent-to-agent-protocol-a2a) - [ ] The section references key ADRs: ADR-047 (A2A Standard Adoption), ADR-048 (Server Application Architecture) - [ ] The section lists all key deliverables from the v3.8.0 milestone description - [ ] The milestone status note is updated to include v3.8.0 and v3.9.0 - [ ] The section follows the same format as existing v3.2.0–v3.7.0 sections - [ ] A PR is created and passes review ## Subtasks - [ ] Draft `### v3.8.0 — Server Implementation` section content - [ ] Include goal statement referencing A2A protocol standard - [ ] Add cross-references to spec sections: Server and Client Architecture, A2A Protocol - [ ] Add ADR references: ADR-047, ADR-048 - [ ] List all key deliverables: - [ ] A2A JSON-RPC 2.0 wire format and `_cleveragents/` extension method routing - [ ] A2A stdio transport (local mode) - [ ] A2A HTTP transport (server mode) - [ ] Server application structure (FastAPI + A2A SDK) - [ ] Authentication and authorization (API tokens, team RBAC) - [ ] Entity sync via `_cleveragents/sync/*` extension methods - [ ] Multi-device experience, shared namespaces, PostgreSQL backend - [ ] Server deployment (Docker + Kubernetes + Helm) - [ ] Update the milestone status note to include v3.8.0 and v3.9.0 - [ ] Open PR targeting `main` with the spec update - [ ] Obtain human approval and merge ## Definition of Done This issue should be closed when: 1. A PR has been merged to `main` that adds the `### v3.8.0 — Server Implementation` section to the Milestone Plan in `docs/specification.md` 2. The milestone status note has been updated to include v3.8.0 and v3.9.0 3. The section follows the established format of existing milestone plan sections --- ## Proposal: Add v3.8.0 Milestone Plan Section **Type**: Spec Update Proposal (Step 1 of 2) **Proposed by**: AUTO-SPEC Supervisor (spec-update-pool-supervisor) **Priority**: Medium --- ## Discrepancy Detected The `docs/specification.md` Milestone Plan section currently covers milestones v3.2.0 through v3.7.0 only. The v3.8.0 milestone (Server Implementation) exists in the repository with 373 open issues and 133 closed issues but has **no corresponding Milestone Plan section** in the specification. The spec header at line 46800 explicitly states: *"This plan covers v3.2.0 through v3.7.0 — the production-ready target."* However, v3.8.0 is actively being worked on (373 open issues) and requires spec coverage per the spec-first development principle. Note: PR #8846 (AUTO-ARCH-5) adds a v3.9.0 section but skips v3.8.0. Both sections are needed. --- ## Classification **Implementation found a better approach** → The v3.8.0 milestone is being actively developed without spec coverage in the Milestone Plan. The spec should be updated to reflect this. --- ## Proposed Change Add a `### v3.8.0 — Server Implementation` section to the Milestone Plan in `docs/specification.md`, following the same format as v3.2.0–v3.7.0 sections. The section should: 1. State the goal: Implement the CleverAgents server and all server-dependent capabilities using the A2A protocol standard 2. Reference existing spec sections: [Server and Client Architecture](#server-and-client-architecture), [A2A Protocol](#agent-to-agent-protocol-a2a) 3. Reference key ADRs: ADR-047 (A2A Standard Adoption), ADR-048 (Server Application Architecture) 4. List key deliverables from the v3.8.0 milestone description: - A2A JSON-RPC 2.0 wire format and `_cleveragents/` extension method routing - A2A stdio transport (local mode) - A2A HTTP transport (server mode) - Server application structure (FastAPI + A2A SDK) - Authentication and authorization (API tokens, team RBAC) - Entity sync via `_cleveragents/sync/*` extension methods - Multi-device experience, shared namespaces, PostgreSQL backend - Server deployment (Docker + Kubernetes + Helm) 5. Also update the milestone status note to include v3.8.0 and v3.9.0 --- ## Approval Required This is a **Step 1 Proposal**. Human approval is required before a spec-update-worker will be dispatched to create the actual PR. To approve: Add the `needs feedback` label or comment "APPROVED" on this issue. To reject: Close this issue. --- **Automated by CleverAgents Bot** Agent: new-issue-creator Supervisor: Spec Update | Agent: spec-update-pool-supervisor
HAL9000 added this to the v3.8.0 milestone 2026-04-14 03:19:58 +00:00
Author
Owner

Triage Decision: VERIFIED — MoSCoW/Should Have

Valid spec documentation proposal: adding the v3.8.0 milestone plan section to docs/specification.md is important for developer clarity about the Server Implementation milestone scope. This is a Should Have documentation improvement.

Priority/Medium — Documentation improvement for v3.8.0 milestone.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Triage Decision: VERIFIED — MoSCoW/Should Have** Valid spec documentation proposal: adding the v3.8.0 milestone plan section to `docs/specification.md` is important for developer clarity about the Server Implementation milestone scope. This is a Should Have documentation improvement. **Priority/Medium** — Documentation improvement for v3.8.0 milestone. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8877
No description provided.