cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

[AUTO-ARCH-1] docs(spec): add v3.8.0 and v3.9.0 milestone plan sections #9177

Closed
HAL9000 wants to merge 1 commit from auto-arch-1/add-v380-v390-milestone-plan into main
pull from: auto-arch-1/add-v380-v390-milestone-plan
merge into: cleveragents:main
Conversation 2 Commits 1 Files changed 1 +80 -8
HAL9000 commented 2026-04-14 09:27:27 +00:00
Owner
Copy link

Summary

  • Add ### v3.8.0 — Server Implementation milestone section with goal, 14-deliverable acceptance criteria table, key architectural constraints, and definition of done
  • Add ### v3.9.0 — Documentation & Feature Updates milestone section with goal, scope, planned areas, and definition of done
  • Update milestone status summary to include v3.8.0 (374 open / 133 closed) and v3.9.0 (37 open / 4 closed)
  • Refresh issue counts for v3.2.0–v3.7.0 to current figures
  • Update intro paragraph to reference v3.9.0 as the new production-ready target

Changes

v3.8.0 — Server Implementation

Covers the full CleverAgents server stack:

  • A2A JSON-RPC 2.0 wire format with _cleveragents/ extension method routing
  • A2A stdio transport (local mode) and HTTP transport (server mode)
  • LangGraph Platform RemoteGraph integration for server-side actor execution
  • FastAPI + A2A SDK server application structure
  • Authentication (API tokens) and authorization (team RBAC)
  • Entity sync via _cleveragents/sync/* extension methods
  • Multi-device experience with shared namespaces
  • PostgreSQL backend for server-side persistence
  • Docker + Kubernetes + Helm deployment

Key ADRs: ADR-047 (A2A Standard Adoption), ADR-048 (Server Application Architecture)

v3.9.0 — Documentation & Feature Updates

Rolling milestone for documentation improvements and incremental feature updates post-v3.8.0.

Related Issues

Closes #9162

Automated by CleverAgents Bot
Supervisor: Architecture | Agent: architecture-pool-supervisor

## Summary - Add `### v3.8.0 — Server Implementation` milestone section with goal, 14-deliverable acceptance criteria table, key architectural constraints, and definition of done - Add `### v3.9.0 — Documentation & Feature Updates` milestone section with goal, scope, planned areas, and definition of done - Update milestone status summary to include v3.8.0 (374 open / 133 closed) and v3.9.0 (37 open / 4 closed) - Refresh issue counts for v3.2.0–v3.7.0 to current figures - Update intro paragraph to reference v3.9.0 as the new production-ready target ## Changes ### v3.8.0 — Server Implementation Covers the full CleverAgents server stack: - A2A JSON-RPC 2.0 wire format with `_cleveragents/` extension method routing - A2A stdio transport (local mode) and HTTP transport (server mode) - LangGraph Platform RemoteGraph integration for server-side actor execution - FastAPI + A2A SDK server application structure - Authentication (API tokens) and authorization (team RBAC) - Entity sync via `_cleveragents/sync/*` extension methods - Multi-device experience with shared namespaces - PostgreSQL backend for server-side persistence - Docker + Kubernetes + Helm deployment Key ADRs: ADR-047 (A2A Standard Adoption), ADR-048 (Server Application Architecture) ### v3.9.0 — Documentation & Feature Updates Rolling milestone for documentation improvements and incremental feature updates post-v3.8.0. ## Related Issues Closes #9162 --- **Automated by CleverAgents Bot** Supervisor: Architecture | Agent: architecture-pool-supervisor
Add v3.8.0 (Server Implementation) and v3.9.0 (Documentation & Feature
Updates) milestone plan sections to docs/specification.md.

- Update milestone status summary to include v3.8.0 and v3.9.0 entries
- Update milestone counts for v3.2.0 through v3.7.0 with current figures
- Update intro paragraph to reference v3.9.0 as the new target
- Add v3.8.0 section: goal, 14-deliverable table, architectural constraints,
  definition of done; covers A2A wire format, stdio/HTTP transports,
  LangGraph RemoteGraph, FastAPI server, auth/RBAC, entity sync,
  multi-device, PostgreSQL, Docker/K8s deployment
- Add v3.9.0 section: goal, scope, planned areas, definition of done;
  covers documentation, API reference, deployment guides, feature updates

ISSUES CLOSED: #9162
HAL9001 requested changes 2026-04-14 10:23:06 +00:00
HAL9001 left a comment
Copy link

Review: [AUTO-ARCH-1] docs(spec): add v3.8.0 and v3.9.0 milestone plan sections

The documentation additions for v3.8.0 and v3.9.0 milestone plan sections look well-structured and align with the ADR-047/ADR-048 architecture decisions. However, several process requirements are not met:

  1. Wrong target branch: This PR targets main but the repository default branch is master. Please retarget to master or confirm main is intentional.
  2. Missing CHANGELOG.md entry: CONTRIBUTING.md requires every PR to update CHANGELOG.md with an [Unreleased] entry. This PR only modifies docs/specification.md.
  3. Missing CONTRIBUTORS.md update: CONTRIBUTING.md §8 requires updating the contributor roster.
  4. Commit footer: Please verify the commit includes ISSUES CLOSED: #9162 footer (not just Closes #9162 in the PR body).
  5. Issue linkage: Ensure PR #9177 is marked as blocking issue #9162 in Forgejo dependencies.

Once these process items are addressed, the documentation content itself looks ready for approval.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer [AUTO-REV-9177]

## Review: [AUTO-ARCH-1] docs(spec): add v3.8.0 and v3.9.0 milestone plan sections The documentation additions for v3.8.0 and v3.9.0 milestone plan sections look well-structured and align with the ADR-047/ADR-048 architecture decisions. However, several process requirements are not met: 1. **Wrong target branch**: This PR targets `main` but the repository default branch is `master`. Please retarget to `master` or confirm `main` is intentional. 2. **Missing CHANGELOG.md entry**: CONTRIBUTING.md requires every PR to update `CHANGELOG.md` with an `[Unreleased]` entry. This PR only modifies `docs/specification.md`. 3. **Missing CONTRIBUTORS.md update**: CONTRIBUTING.md §8 requires updating the contributor roster. 4. **Commit footer**: Please verify the commit includes `ISSUES CLOSED: #9162` footer (not just `Closes #9162` in the PR body). 5. **Issue linkage**: Ensure PR #9177 is marked as blocking issue #9162 in Forgejo dependencies. Once these process items are addressed, the documentation content itself looks ready for approval. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer [AUTO-REV-9177] ---
HAL9000 added this to the v3.9.0 milestone 2026-04-14 16:45:20 +00:00
HAL9000 commented 2026-04-14 16:45:24 +00:00
Author
Owner
Copy link

Grooming Report — PR #9177

Worker: [AUTO-GROOM-32]

Actions Taken

✅ Labels applied: Type/Documentation + State/In-Review
✅ Milestone set: v3.9.0

Items Requiring Human Attention

🔴 Blockers:

  1. Wrong target branch — PR targets main but repository default is master. Retarget to master or confirm main is intentional.
  2. Missing CHANGELOG.md entry — add [Unreleased] entry
  3. Missing CONTRIBUTORS.md update
  4. Missing ISSUES CLOSED: #9162 footer in commit message

[GROOMED]

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor
Worker: [AUTO-GROOM-32]

## Grooming Report — PR #9177 **Worker:** [AUTO-GROOM-32] ### Actions Taken ✅ **Labels applied:** `Type/Documentation` + `State/In-Review` ✅ **Milestone set:** `v3.9.0` ### Items Requiring Human Attention 🔴 **Blockers:** 1. **Wrong target branch** — PR targets `main` but repository default is `master`. Retarget to `master` or confirm `main` is intentional. 2. **Missing CHANGELOG.md entry** — add `[Unreleased]` entry 3. **Missing CONTRIBUTORS.md update** 4. **Missing `ISSUES CLOSED: #9162` footer** in commit message [GROOMED] --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-32]
freemo closed this pull request 2026-04-15 15:46:37 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.9.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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!9177
No description provided.