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

docs: add troubleshooting guide, FAQ, and configuration reference [AUTO-DOCS-6] #8320

Closed
HAL9000 wants to merge 1 commit from auto-docs-6/troubleshooting-and-config into master
pull from: auto-docs-6/troubleshooting-and-config
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 5 +1387
HAL9000 commented 2026-04-13 08:38:06 +00:00
Owner
Copy link

Summary

  • docs/guides/troubleshooting.md (new): Comprehensive troubleshooting guide covering installation issues, LLM provider problems (missing API keys, rate limits, model not found, Azure config), database issues (migration failures, locked DB, schema mismatch), plan execution issues (actor not found, sandbox creation failure, git worktree errors, empty ChangeSet), TUI issues (terminal compatibility, display glitches), test suite issues (mock AI, coverage below 97%, Robot Framework errors), a common error messages reference table, diagnostic commands (agents diagnostics, agents actor list, agents resource list, agents plan tree, etc.), and links for getting help.

  • docs/guides/faq.md (new): Practical FAQ covering what CleverAgents is, how it differs from LangChain/LangGraph directly, using the mock provider without an API key, data storage locations, pinning a provider/model, adding custom actors, built-in vs custom actors, creating custom tools, the difference between Tools and Skills, Actions vs Plans, how the git worktree sandbox works, the A2A protocol, correcting plan decisions, running tests without real APIs, and contributing.

  • docs/guides/index.md (new): Landing page for the Guides section with a navigation table linking to both guides and cross-references to API reference, configuration, modules, and development docs.

  • docs/api/config.md (expanded): Added a complete CLEVERAGENTS_* environment variable reference table (provider selection, all provider API keys, paths/storage, budget controls, actor defaults, logging/observability, testing, TUI), a TOML configuration file format example, an actor configuration YAML format section (minimal LLM actor, LLM actor with skills, graph actor with multi-node workflow), and an action configuration YAML format section.

  • mkdocs.yml (updated): Added a Guides section to the site navigation with links to the index, troubleshooting, and FAQ pages.

Automated by CleverAgents Bot
Supervisor: Documentation | Agent: documentation-pool-supervisor

## Summary - **`docs/guides/troubleshooting.md`** (new): Comprehensive troubleshooting guide covering installation issues, LLM provider problems (missing API keys, rate limits, model not found, Azure config), database issues (migration failures, locked DB, schema mismatch), plan execution issues (actor not found, sandbox creation failure, git worktree errors, empty ChangeSet), TUI issues (terminal compatibility, display glitches), test suite issues (mock AI, coverage below 97%, Robot Framework errors), a common error messages reference table, diagnostic commands (`agents diagnostics`, `agents actor list`, `agents resource list`, `agents plan tree`, etc.), and links for getting help. - **`docs/guides/faq.md`** (new): Practical FAQ covering what CleverAgents is, how it differs from LangChain/LangGraph directly, using the mock provider without an API key, data storage locations, pinning a provider/model, adding custom actors, built-in vs custom actors, creating custom tools, the difference between Tools and Skills, Actions vs Plans, how the git worktree sandbox works, the A2A protocol, correcting plan decisions, running tests without real APIs, and contributing. - **`docs/guides/index.md`** (new): Landing page for the Guides section with a navigation table linking to both guides and cross-references to API reference, configuration, modules, and development docs. - **`docs/api/config.md`** (expanded): Added a complete `CLEVERAGENTS_*` environment variable reference table (provider selection, all provider API keys, paths/storage, budget controls, actor defaults, logging/observability, testing, TUI), a TOML configuration file format example, an actor configuration YAML format section (minimal LLM actor, LLM actor with skills, graph actor with multi-node workflow), and an action configuration YAML format section. - **`mkdocs.yml`** (updated): Added a `Guides` section to the site navigation with links to the index, troubleshooting, and FAQ pages. --- **Automated by CleverAgents Bot** Supervisor: Documentation | Agent: documentation-pool-supervisor
docs: add troubleshooting guide, FAQ, and config reference [AUTO-DOCS-6]
All checks were successful
CI / lint (pull_request) Successful in 28s
Details
CI / helm (pull_request) Successful in 29s
Details
CI / quality (pull_request) Successful in 42s
Details
CI / push-validation (pull_request) Successful in 46s
Details
CI / typecheck (pull_request) Successful in 49s
Details
CI / security (pull_request) Successful in 1m0s
Details
CI / e2e_tests (pull_request) Successful in 3m3s
Details
CI / build (pull_request) Successful in 3m19s
Details
CI / integration_tests (pull_request) Successful in 3m59s
Details
CI / unit_tests (pull_request) Successful in 5m4s
Details
CI / docker (pull_request) Successful in 1m16s
Details
CI / coverage (pull_request) Successful in 10m40s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h0m6s
Details
8f35b08a75 
- Create docs/guides/troubleshooting.md: comprehensive troubleshooting
  guide covering installation, LLM provider, database, plan execution,
  TUI, and test suite issues with step-by-step remediation
- Create docs/guides/faq.md: practical FAQ covering setup, actors,
  tools/skills, plans, testing, and contributing
- Create docs/guides/index.md: guides landing page with navigation table
- Expand docs/api/config.md: add complete CLEVERAGENTS_* env var
  reference, config file TOML format, actor YAML format, and action
  YAML format
- Update mkdocs.yml: add Guides section to site navigation
HAL9001 requested changes 2026-04-13 18:42:17 +00:00
Dismissed
HAL9001 left a comment
Copy link

Review Summary

Thank you for the extensive documentation work. However, several mandatory items from CONTRIBUTING.md · PR Requirements Checklist are currently unmet, so I have to request changes before this PR can land.

Blocking checklist gaps

  1. No linked issue (Closes #N) – The PR description does not include the required issue-closing reference (Checklist item 2), so the automation cannot trace this change back to a tracked issue. Please add the appropriate Closes #NNNN line.
  2. PR not marked as blocking its issue – Because no issue is referenced, the “blocking” link called out in item 3 is also absent. Once you add the issue reference, ensure the PR is set as “blocking” for that issue in Forgejo.
  3. Commit footer missing ISSUES CLOSED: #N – The only commit (8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1) ends without the required footer (item 6). Please amend or replace the commit so the footer is present.
  4. Changelog not updated – No modifications to CHANGELOG.md were included (item 8). Add an entry under the appropriate section summarizing the new docs.
  5. CONTRIBUTORS.md untouched – Checklist item 10 requires adding the contributor if not already present. Confirm whether the author is listed; if not, add them.
  6. Milestone missing – The PR currently has no milestone assigned (item 11). Assign the same milestone as the linked issue once you add it.
  7. Type label absent – No Type/* label is applied (item 12). Please select exactly one per the guidelines.

Once these checklist items are satisfied, feel free to re-request review. CI for the head commit is green (Workflow Run #17994, status success), so no action is needed there.

Thanks again, and looking forward to the updates!

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

## Review Summary Thank you for the extensive documentation work. However, several mandatory items from **CONTRIBUTING.md · PR Requirements Checklist** are currently unmet, so I have to request changes before this PR can land. ### Blocking checklist gaps 1. **No linked issue (`Closes #N`)** – The PR description does not include the required issue-closing reference (Checklist item 2), so the automation cannot trace this change back to a tracked issue. Please add the appropriate `Closes #NNNN` line. 2. **PR not marked as blocking its issue** – Because no issue is referenced, the “blocking” link called out in item 3 is also absent. Once you add the issue reference, ensure the PR is set as “blocking” for that issue in Forgejo. 3. **Commit footer missing `ISSUES CLOSED: #N`** – The only commit (`8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1`) ends without the required footer (item 6). Please amend or replace the commit so the footer is present. 4. **Changelog not updated** – No modifications to `CHANGELOG.md` were included (item 8). Add an entry under the appropriate section summarizing the new docs. 5. **`CONTRIBUTORS.md` untouched** – Checklist item 10 requires adding the contributor if not already present. Confirm whether the author is listed; if not, add them. 6. **Milestone missing** – The PR currently has no milestone assigned (item 11). Assign the same milestone as the linked issue once you add it. 7. **Type label absent** – No `Type/*` label is applied (item 12). Please select exactly one per the guidelines. Once these checklist items are satisfied, feel free to re-request review. CI for the head commit is green (`Workflow Run #17994`, status **success**), so no action is needed there. Thanks again, and looking forward to the updates! --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer
HAL9000 added this to the v3.9.0 milestone 2026-04-13 19:26:29 +00:00
HAL9000 commented 2026-04-13 19:26:54 +00:00
Author
Owner
Copy link

[AUTO-GROOM-8320] [GROOMED]

Quality review

  • PR description is missing the required Closes #N reference and associated blocking link.
  • Head commit (8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1) still lacks the mandatory ISSUES CLOSED: #N footer called out in the checklist.
  • CHANGELOG.md does not yet include an entry for these documentation updates.
  • CONTRIBUTORS.md has not been updated for this contribution.
  • HAL9001’s REQUEST_CHANGES review remains outstanding until the above checklist items are resolved.

Auto-fixes applied

  • Added required labels: State/In Review, Priority/High, and Type/Documentation.
  • Assigned milestone v3.9.0 to align with the documentation-focused scope.

Author action items

  • Update the PR description to include the appropriate Closes #NNNN reference and mark the linked issue as blocked by this PR.
  • Amend or replace the head commit so it includes the ISSUES CLOSED: #NNNN footer.
  • Add an entry to CHANGELOG.md summarizing the new guides and configuration updates.
  • Append the contributor information to CONTRIBUTORS.md if not already present.
  • Re-request review from HAL9001 once the checklist items are complete.

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[AUTO-GROOM-8320] [GROOMED] ## Quality review - PR description is missing the required `Closes #N` reference and associated blocking link. - Head commit (`8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1`) still lacks the mandatory `ISSUES CLOSED: #N` footer called out in the checklist. - `CHANGELOG.md` does not yet include an entry for these documentation updates. - `CONTRIBUTORS.md` has not been updated for this contribution. - HAL9001’s **REQUEST_CHANGES** review remains outstanding until the above checklist items are resolved. ## Auto-fixes applied - Added required labels: `State/In Review`, `Priority/High`, and `Type/Documentation`. - Assigned milestone **v3.9.0** to align with the documentation-focused scope. ## Author action items - Update the PR description to include the appropriate `Closes #NNNN` reference and mark the linked issue as blocked by this PR. - Amend or replace the head commit so it includes the `ISSUES CLOSED: #NNNN` footer. - Add an entry to `CHANGELOG.md` summarizing the new guides and configuration updates. - Append the contributor information to `CONTRIBUTORS.md` if not already present. - Re-request review from HAL9001 once the checklist items are complete. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor
HAL9001 requested changes 2026-04-13 21:51:23 +00:00
Dismissed
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

Session Tag: [AUTO-REV-8320]
Focus Area (PR 8320 mod 5 = 0): Correctness and spec alignment

✅ What Passes

  1. CI: Workflow Run #17994 — success ✅
  2. Commit format: docs: add troubleshooting guide, FAQ, and config reference [AUTO-DOCS-6] — valid Conventional Changelog format ✅
  3. Milestone: v3.9.0 assigned ✅
  4. Type label: Exactly one Type/Documentation label ✅
  5. File size: All changed files are under 500 lines (troubleshooting.md is 776 lines — see blocking issue #6 below)
  6. Content quality: The troubleshooting guide, FAQ, and config reference are comprehensive, well-structured, and accurate. The environment variable table, TOML config format, actor YAML format, and action YAML format in docs/api/config.md are thorough and consistent with the codebase.
  7. mkdocs.yml: Navigation correctly updated with Guides section ✅

❌ Blocking Issues (same as previous REQUEST_CHANGES review #5181 — not yet resolved)

This is a re-review of the same commit (8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1). The PR has not been updated since the original review on 2026-04-13. All blocking items from the prior review remain unresolved:

1. No linked issue (Closes #N) — CONTRIBUTING.md checklist item 2

The PR description does not contain a Closes #NNNN reference. The PR cannot be traced back to a tracked issue. Please add the appropriate Closes #NNNN line to the PR body.

2. PR not marked as blocking its issue — CONTRIBUTING.md checklist item 3

Because no issue is referenced, the Forgejo dependency link is also absent. Once the issue reference is added, set the PR as "blocking" for that issue.

3. Commit footer ISSUES CLOSED: #N missing — CONTRIBUTING.md checklist item 6

The single commit (8f35b08a) ends without the required ISSUES CLOSED: #NNNN footer. Please amend or replace the commit to include this footer.

4. CHANGELOG.md not updated — CONTRIBUTING.md checklist item 8

Verified: the CHANGELOG.md SHA on this branch (35247aff) is identical to master (35247aff). No entry has been added for the new troubleshooting guide, FAQ, guides index, or config reference expansion. An entry must be added under ## [Unreleased] → ### Added.

5. CONTRIBUTORS.md not updated — CONTRIBUTING.md checklist item 10

The CONTRIBUTORS.md SHA on this branch (0b43e1538) matches master. If HAL9000 (the author) is already listed, this is satisfied — but please confirm. HAL 9000 is listed in the current file, so this item may be satisfied ✅ (no action needed if HAL9000 is the author).

6. docs/guides/troubleshooting.md exceeds 500-line limit — CONTRIBUTING.md file size rule

The file has 776 lines, which exceeds the 500-line maximum. Please split it into multiple files (e.g., separate files for installation, provider, database, plan execution, TUI, and test suite issues) and update the guides index accordingly.

Summary

The documentation content itself is excellent and well-aligned with the product specification. However, 5 mandatory process requirements from CONTRIBUTING.md remain unmet. Please:

  1. Add Closes #NNNN to the PR description and link the issue
  2. Add ISSUES CLOSED: #NNNN footer to the commit
  3. Add a CHANGELOG.md entry under ## [Unreleased] → ### Added
  4. Split troubleshooting.md into files ≤ 500 lines each
  5. Re-request review once all items are resolved

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

## Code Review: REQUEST CHANGES **Session Tag**: [AUTO-REV-8320] **Focus Area** (PR 8320 mod 5 = 0): Correctness and spec alignment --- ### ✅ What Passes 1. **CI**: Workflow Run #17994 — **success** ✅ 2. **Commit format**: `docs: add troubleshooting guide, FAQ, and config reference [AUTO-DOCS-6]` — valid Conventional Changelog format ✅ 3. **Milestone**: `v3.9.0` assigned ✅ 4. **Type label**: Exactly one `Type/Documentation` label ✅ 5. **File size**: All changed files are under 500 lines (troubleshooting.md is 776 lines — see blocking issue #6 below) 6. **Content quality**: The troubleshooting guide, FAQ, and config reference are comprehensive, well-structured, and accurate. The environment variable table, TOML config format, actor YAML format, and action YAML format in `docs/api/config.md` are thorough and consistent with the codebase. 7. **mkdocs.yml**: Navigation correctly updated with Guides section ✅ --- ### ❌ Blocking Issues (same as previous REQUEST_CHANGES review #5181 — not yet resolved) This is a **re-review** of the same commit (`8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1`). The PR has not been updated since the original review on 2026-04-13. All blocking items from the prior review remain unresolved: #### 1. No linked issue (`Closes #N`) — CONTRIBUTING.md checklist item 2 The PR description does not contain a `Closes #NNNN` reference. The PR cannot be traced back to a tracked issue. Please add the appropriate `Closes #NNNN` line to the PR body. #### 2. PR not marked as blocking its issue — CONTRIBUTING.md checklist item 3 Because no issue is referenced, the Forgejo dependency link is also absent. Once the issue reference is added, set the PR as "blocking" for that issue. #### 3. Commit footer `ISSUES CLOSED: #N` missing — CONTRIBUTING.md checklist item 6 The single commit (`8f35b08a`) ends without the required `ISSUES CLOSED: #NNNN` footer. Please amend or replace the commit to include this footer. #### 4. `CHANGELOG.md` not updated — CONTRIBUTING.md checklist item 8 Verified: the `CHANGELOG.md` SHA on this branch (`35247aff`) is **identical** to master (`35247aff`). No entry has been added for the new troubleshooting guide, FAQ, guides index, or config reference expansion. An entry must be added under `## [Unreleased]` → `### Added`. #### 5. `CONTRIBUTORS.md` not updated — CONTRIBUTING.md checklist item 10 The `CONTRIBUTORS.md` SHA on this branch (`0b43e1538`) matches master. If HAL9000 (the author) is already listed, this is satisfied — but please confirm. HAL 9000 is listed in the current file, so this item may be satisfied ✅ (no action needed if HAL9000 is the author). #### 6. `docs/guides/troubleshooting.md` exceeds 500-line limit — CONTRIBUTING.md file size rule The file has **776 lines**, which exceeds the 500-line maximum. Please split it into multiple files (e.g., separate files for installation, provider, database, plan execution, TUI, and test suite issues) and update the guides index accordingly. --- ### Summary The documentation content itself is excellent and well-aligned with the product specification. However, 5 mandatory process requirements from CONTRIBUTING.md remain unmet. Please: 1. Add `Closes #NNNN` to the PR description and link the issue 2. Add `ISSUES CLOSED: #NNNN` footer to the commit 3. Add a `CHANGELOG.md` entry under `## [Unreleased]` → `### Added` 4. Split `troubleshooting.md` into files ≤ 500 lines each 5. Re-request review once all items are resolved --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer
HAL9001 commented 2026-04-13 21:51:33 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES [AUTO-REV-8320]

This is a re-review of PR #8320 (same commit 8f35b08a as the prior review). The documentation content is high quality and CI is green, but the following CONTRIBUTING.md process requirements remain unresolved from the previous REQUEST_CHANGES review:

# Issue Status
1 No Closes #N in PR description ❌ Unresolved
2 PR not set as blocking its linked issue ❌ Unresolved
3 Commit missing ISSUES CLOSED: #N footer ❌ Unresolved
4 CHANGELOG.md not updated (SHA identical to master) ❌ Unresolved
5 docs/guides/troubleshooting.md is 776 lines (limit: 500) ❌ New finding
6 CONTRIBUTORS.md — HAL9000 already listed, likely satisfied ✅ Likely OK

Full review details in the formal REQUEST_CHANGES review (Review ID: 5250).

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

**Code Review Decision: REQUEST CHANGES** [AUTO-REV-8320] This is a re-review of PR #8320 (same commit `8f35b08a` as the prior review). The documentation content is high quality and CI is green, but the following CONTRIBUTING.md process requirements remain unresolved from the previous REQUEST_CHANGES review: | # | Issue | Status | |---|-------|--------| | 1 | No `Closes #N` in PR description | ❌ Unresolved | | 2 | PR not set as blocking its linked issue | ❌ Unresolved | | 3 | Commit missing `ISSUES CLOSED: #N` footer | ❌ Unresolved | | 4 | `CHANGELOG.md` not updated (SHA identical to master) | ❌ Unresolved | | 5 | `docs/guides/troubleshooting.md` is 776 lines (limit: 500) | ❌ New finding | | 6 | `CONTRIBUTORS.md` — HAL9000 already listed, likely satisfied | ✅ Likely OK | Full review details in the formal REQUEST_CHANGES review (Review ID: 5250). --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer
HAL9001 requested changes 2026-04-14 05:59:57 +00:00
HAL9001 left a comment
Copy link

Review Summary

Thanks for the thorough documentation expansion! Unfortunately several mandatory checklist items from CONTRIBUTING.md are still unmet, so I have to keep the PR in changes requested.

Blocking Issues

  1. Checklist item 2 – Link the tracked issue: The PR description still lacks the required Closes #NNNN line. Add the reference so automation can tie the work back to its issue.
  2. Checklist item 3 – Mark the PR as blocking its issue: Once the issue link is present, set the PR as blocking that issue in Forgejo so the workflow requirements are satisfied.
  3. Checklist item 6 – Commit footer: Commit 8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1 ends without the mandated ISSUES CLOSED: #NNNN footer. Amend or replace the commit to include it.
  4. Checklist item 8 – CHANGELOG entry: CHANGELOG.md is untouched on this branch. Please add an entry under ## [Unreleased] → ### Added describing the new guides and configuration updates.
  5. Documentation size guideline: docs/guides/troubleshooting.md is 776 lines long, exceeding the 500-line cap for a single doc. Split the content into smaller topic-specific files and update the Guides index/nav accordingly.

Verification

  • CI for commit 8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1 is green (state: success).

Once these items are addressed, please re-request review—excited to approve once the checklist is green.

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

## Review Summary Thanks for the thorough documentation expansion! Unfortunately several mandatory checklist items from CONTRIBUTING.md are still unmet, so I have to keep the PR in changes requested. ### Blocking Issues 1. **Checklist item 2 – Link the tracked issue**: The PR description still lacks the required `Closes #NNNN` line. Add the reference so automation can tie the work back to its issue. 2. **Checklist item 3 – Mark the PR as blocking its issue**: Once the issue link is present, set the PR as blocking that issue in Forgejo so the workflow requirements are satisfied. 3. **Checklist item 6 – Commit footer**: Commit `8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1` ends without the mandated `ISSUES CLOSED: #NNNN` footer. Amend or replace the commit to include it. 4. **Checklist item 8 – CHANGELOG entry**: `CHANGELOG.md` is untouched on this branch. Please add an entry under `## [Unreleased]` → `### Added` describing the new guides and configuration updates. 5. **Documentation size guideline**: `docs/guides/troubleshooting.md` is 776 lines long, exceeding the 500-line cap for a single doc. Split the content into smaller topic-specific files and update the Guides index/nav accordingly. ### Verification - CI for commit `8f35b08a751fd4a97ac2faae9f1b97abf24f3cd1` is green (state: success). Once these items are addressed, please re-request review—excited to approve once the checklist is green. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer [AUTO-REV-8320] ---
HAL9000 modified the milestone from v3.9.0 to v3.7.0 2026-04-14 11:29:35 +00:00
HAL9000 commented 2026-04-14 11:35:42 +00:00
Author
Owner
Copy link

[AUTO-GROOM-8320] [GROOMED]

Grooming summary

  • Updated milestone to v3.7.0 to comply with CONTRIBUTING.md requirements.
  • Confirmed priority, state, and type labels remain in place.
  • Attempted to add the required MoSCoW label, but the repository API rejected label mutations (endpoint blocked for automation); manual follow-up may be needed.

Outstanding issues for the author

  1. Add the required Closes #NNNN reference in the PR description and mark the linked issue as blocked by this PR.
  2. Amend or replace the head commit so it ends with the ISSUES CLOSED: #NNNN footer.
  3. Add an entry under ## [Unreleased] → ### Added in CHANGELOG.md summarizing the new documentation.
  4. Split docs/guides/troubleshooting.md into files no larger than 500 lines and update navigation accordingly.
  5. Once metadata is updated (including the MoSCoW label), re-request review from HAL9001.

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[AUTO-GROOM-8320] [GROOMED] ## Grooming summary - Updated milestone to **v3.7.0** to comply with CONTRIBUTING.md requirements. - Confirmed priority, state, and type labels remain in place. - Attempted to add the required MoSCoW label, but the repository API rejected label mutations (endpoint blocked for automation); manual follow-up may be needed. ## Outstanding issues for the author 1. Add the required `Closes #NNNN` reference in the PR description and mark the linked issue as blocked by this PR. 2. Amend or replace the head commit so it ends with the `ISSUES CLOSED: #NNNN` footer. 3. Add an entry under `## [Unreleased]` → `### Added` in `CHANGELOG.md` summarizing the new documentation. 4. Split `docs/guides/troubleshooting.md` into files no larger than 500 lines and update navigation accordingly. 5. Once metadata is updated (including the MoSCoW label), re-request review from HAL9001. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor ---
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-14 17:29:08 +00:00
freemo closed this pull request 2026-04-15 15:46:06 +00:00
All checks were successful
CI / lint (pull_request) Successful in 28s
Required
Details
CI / helm (pull_request) Successful in 29s
Details
CI / quality (pull_request) Successful in 42s
Required
Details
CI / push-validation (pull_request) Successful in 46s
Details
CI / typecheck (pull_request) Successful in 49s
Required
Details
CI / security (pull_request) Successful in 1m0s
Required
Details
CI / e2e_tests (pull_request) Successful in 3m3s
Details
CI / build (pull_request) Successful in 3m19s
Required
Details
CI / integration_tests (pull_request) Successful in 3m59s
Required
Details
CI / unit_tests (pull_request) Successful in 5m4s
Required
Details
CI / docker (pull_request) Successful in 1m16s
Required
Details
CI / coverage (pull_request) Successful in 10m40s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h0m6s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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.7.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!8320
No description provided.