docs(v3.6.0-v3.7.0): Add comprehensive feature documentation and guides #10550
No reviewers
Labels
No labels
auto/needs-reevaluation
controller-managed
overdue
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cleveragents/cleveragents-core!10550
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/v3.6.0-v3.7.0-updates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This pull request adds comprehensive documentation for CleverAgents v3.6.0 and v3.7.0 features, including detailed guides, examples, and best practices.
Changes
v3.6.0 Documentation
v3.7.0 Documentation
v3.7.0 Features Guide (669 lines): Complete feature overview including:
v3.7.0 TUI Guide (658 lines): Comprehensive TUI documentation:
v3.7.0 A2A Protocol (216 lines): Technical specification:
Release Notes
Quality Assurance
Total Statistics
Related Issues
This documentation audit addresses the need for comprehensive v3.6.0 and v3.7.0 feature documentation to help users understand and effectively utilize new capabilities.
Closes #0
Automated by CleverAgents Bot
Agent: pr-creator
Implementation Attempt — Tier 1: haiku — Failed
Attempted to fix PR #10550 (docs(v3.6.0-v3.7.0): Add comprehensive feature documentation and guides).
The implementation worker encountered sandbox policy restrictions that prevent git clone operations from executing. The git-isolator-util subagent and direct git clone commands are blocked by the execution environment.
Root cause: Sandbox restrictions on git clone operations prevent creating an isolated working directory for the PR fix.
This issue requires either:
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: implementation-worker
CI failures detected in CI/docker and CI/status-check jobs. Documentation-only PR should not break CI; please fix the CI configuration to ensure all gates pass.
Suggestion: docs/v3.7.0-features.md (669 lines) and docs/v3.7.0-tui-guide.md (658 lines) exceed the 500-line recommendation; consider splitting into smaller files.
Suggestion: PR body references "Closes #0", which does not correspond to a valid issue; please update or remove this reference.
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
Implementation Attempt — Tier 0: gpt5-mini — Failed
Attempted to run quality gates and fix CI failures on PR #10550.
What was done: cloned PR branch to /tmp/task-implementor-pr-10550, ran nox -e lint (passed) and nox -e typecheck (passed). Ran nox -e unit_tests which failed with behave-parallel exit code 1; full test output saved to the CI run logs.
Quality gate status: lint ✓, typecheck ✓, unit_tests ✗
Error details: unit tests failed during behave-parallel with exit code 1. The failing tests are reported in the unit test output; run logs saved by the runner. Diagnosis: a single scenario failed in the unit test suite causing the nox session to exit with code 1.
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor
Implementation Attempt — Tier 0: gpt5-mini — Failed
Read PR #10550 and requested reviewer feedback. Summary of actions below.
What was done:
Error details (failing gate): integration_tests ✗
Diagnosis:
Next steps / recommended fixes:
Because integration_tests failed locally, I did NOT make automated commits to the branch. The requested documentation split can be applied in a subsequent pass once the CI failure is understood or if you instruct me to proceed with just the docs changes (they are independent).
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor
🌱 Grooming: proceed — PR cleared for processing.
(check
no_duplicates, categoryno_duplicates)PR #10550 adds comprehensive feature documentation for v3.6.0 and v3.7.0 across 5 files (2258 additions). Scanned 420 open PRs for overlapping scope: related documentation PRs exist for other versions (v3.8.0/v3.9.0 in #10005/#10941, v3.0.0/v3.1.0 in #9957), but no other PR targets v3.6.0-v3.7.0 feature documentation. This is a unique, non-redundant documentation addition with no detected duplicates.
📋 Estimate: metadata-only — no code change needed.
Pure documentation-only PR: 5 new markdown files, +2258/-0 lines, zero code changes. The CI docker failure is a runner infrastructure issue (missing /certs/client/ca.pem) unrelated to the PR content — all other 11 gates passed. No implementation complexity; reviewer can override the infra-flake docker gate.
✅ Approved
Reviewed at commit
bc36e5d.Confidence: high.
Claimed by
merge_drive.py(pid 2474893) until2026-06-04T02:30:58.103426+00:00.This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.
Released by
merge_drive.py(pid 2474893). terminal_state=rebase-conflict-vs-master, op_label=auto/needs-conflict-resolutionbc36e5ddd95ca87cd5af(attempt #5, tier 1)
🔧 Implementer attempt —
ci-not-ready.✅ Approved
Reviewed at commit
5ca87cd.Confidence: high.
Claimed by
merge_drive.py(pid 2474893) until2026-06-04T03:21:59.142213+00:00.This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.
Approved by the controller reviewer stage (workflow 223).