docs: update specification — add agents plan errors command #3033

Merged

freemo merged 1 commits from spec/update-v3.7.0-plan-errors-command into master 2026-04-05 21:16:23 +00:00

Conversation 8 Commits 1 Files Changed 1

+92

freemo commented 2026-04-05 04:09:55 +00:00

Owner

Copy Link

Copy Source

Summary

Documents the agents plan errors CLI command in the specification. This command was already implemented and functional but was absent from the CLI Command Synopsis and Command Reference sections.

Changes

docs/specification.md

1. Command Synopsis — Added agents plan errors <PLAN_ID> after agents plan rollback in the synopsis block.

2. Command Reference — Added new ##### agents plan errors section between agents plan artifacts and agents plan prompt, including:

   • Synopsis: agents plan errors <PLAN_ID>
   • Purpose: Show error decisions with recovery hints and retry history
   • Arguments: PLAN_ID — the ULID of the plan
   • Rich output example showing error category, phase, retry count, retriability, and recovery suggestions with CLI commands
   • Plain text output example
   • JSON output example

Rationale

The agents plan errors command is implemented in src/cleveragents/cli/commands/plan.py (line 2182) and referenced in the TUI slash catalog (/plan:errors <id>) at spec line 29322, but was absent from the CLI documentation sections. This is a genuine omission — the command exists and is functional.

Related

• Closes proposal #2883 (approved by freemo on 2026-04-05)
• Implementation: src/cleveragents/cli/commands/plan.py lines 2182–2303

---

Automated by CleverAgents Bot
Supervisor: Spec Evolution | Agent: ca-spec-updater

## Summary Documents the `agents plan errors` CLI command in the specification. This command was already implemented and functional but was absent from the CLI Command Synopsis and Command Reference sections. ## Changes ### `docs/specification.md` 1. **Command Synopsis** — Added `agents plan errors <PLAN_ID>` after `agents plan rollback` in the synopsis block. 2. **Command Reference** — Added new `##### agents plan errors` section between `agents plan artifacts` and `agents plan prompt`, including: - Synopsis: `agents plan errors <PLAN_ID>` - Purpose: Show error decisions with recovery hints and retry history - Arguments: `PLAN_ID` — the ULID of the plan - Rich output example showing error category, phase, retry count, retriability, and recovery suggestions with CLI commands - Plain text output example - JSON output example ## Rationale The `agents plan errors` command is implemented in `src/cleveragents/cli/commands/plan.py` (line 2182) and referenced in the TUI slash catalog (`/plan:errors <id>`) at spec line 29322, but was absent from the CLI documentation sections. This is a genuine omission — the command exists and is functional. ## Related - Closes proposal #2883 (approved by `freemo` on 2026-04-05) - Implementation: `src/cleveragents/cli/commands/plan.py` lines 2182–2303 --- **Automated by CleverAgents Bot** Supervisor: Spec Evolution | Agent: ca-spec-updater

freemo added 1 commit 2026-04-05 04:09:55 +00:00

docs: update specification — add agents plan errors command ... 325f63d050

Documents the agents plan errors CLI command in both the Command
Synopsis and Command Reference sections of the specification.

The command was already implemented in src/cleveragents/cli/commands/plan.py
and referenced in the TUI slash catalog but was absent from the CLI
documentation sections.

Changes:
- Command Synopsis: added 'agents plan errors <PLAN_ID>' after plan rollback
- Command Reference: added '##### agents plan errors' section with synopsis,
  purpose, arguments, and Rich/Plain/JSON output examples

Approved via proposal issue #2883.

ISSUES CLOSED: #2883

freemo referenced this pull request 2026-04-05 04:10:42 +00:00

Proposal: update specification — document agents plan errors command #2883

freemo referenced this pull request 2026-04-05 04:11:03 +00:00

[CA-AUTO] Spec Updater — Session Tracker #2876

freemo referenced this pull request 2026-04-05 04:23:12 +00:00

Task: Autonomous build progress report — 2026-04-05 #2874

freemo referenced this pull request 2026-04-05 04:23:53 +00:00

[CA-AUTO] System Watchdog — Session Tracker #2877

freemo referenced this pull request 2026-04-05 04:52:43 +00:00

Task: Autonomous build progress report — 2026-04-05 #3059

freemo commented 2026-04-05 05:23:12 +00:00

Author

Owner

Copy Link

Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1775366000]

---

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

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1775366000] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo referenced this pull request 2026-04-05 05:24:26 +00:00

Task: Autonomous build progress report — 2026-04-05 #3075

freemo reviewed 2026-04-05 05:28:20 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

Review: APPROVED ✅

(Posted as COMMENT because Forgejo prevents self-approval — the bot account authored this PR.)

What was reviewed

This PR adds documentation for the agents plan errors CLI command to the specification. The command was already implemented (src/cleveragents/cli/commands/plan.py line 2182) and referenced in the TUI slash catalog but was missing from the CLI Command Synopsis and Command Reference sections.

Changes verified

1. Command Synopsis (line 347): agents plan errors <PLAN_ID> correctly added after agents plan rollback — placement matches the proposal and is consistent with the existing command ordering.

2. Command Reference (new section between agents plan artifacts and agents plan prompt):

   • Synopsis with proper HTML styling consistent with other command entries
   • Purpose description is clear and accurate
   • Arguments section properly documents the PLAN_ID (ULID) parameter
   • Rich output example shows error category, phase, retry count, retriability, and recovery suggestions with CLI commands
   • Plain text output example follows the established plain-text pattern
   • JSON output example has a well-structured schema with recovery_hints array

Consistency checks

• ✅ HTML styling (<div class="highlight"><pre><code> with span colors) matches other command entries
• ✅ MkDocs Material tabbed format (=== "Rich", === "Plain", === "JSON") is consistent
• ✅ Section heading level (#####) matches sibling command reference sections
• ✅ Commit message follows Conventional Changelog format: docs: update specification — add agents plan errors command
• ✅ PR description includes closing keyword for issue #2883
• ✅ Proposal #2883 was approved by freemo
• ✅ Scope correctly narrowed to agents plan errors only (per human feedback on the proposal)

CI Status

All required quality gate checks passing: lint, typecheck, security, quality, unit_tests, coverage, integration_tests, e2e_tests, build, helm, docker, status-check.

No issues found. Clean documentation addition that fills a genuine specification gap.

---

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

## Review: APPROVED ✅ (Posted as COMMENT because Forgejo prevents self-approval — the bot account authored this PR.) ### What was reviewed This PR adds documentation for the `agents plan errors` CLI command to the specification. The command was already implemented (`src/cleveragents/cli/commands/plan.py` line 2182) and referenced in the TUI slash catalog but was missing from the CLI Command Synopsis and Command Reference sections. ### Changes verified 1. **Command Synopsis** (line 347): `agents plan errors <PLAN_ID>` correctly added after `agents plan rollback` — placement matches the proposal and is consistent with the existing command ordering. 2. **Command Reference** (new section between `agents plan artifacts` and `agents plan prompt`): - Synopsis with proper HTML styling consistent with other command entries - Purpose description is clear and accurate - Arguments section properly documents the `PLAN_ID` (ULID) parameter - Rich output example shows error category, phase, retry count, retriability, and recovery suggestions with CLI commands - Plain text output example follows the established plain-text pattern - JSON output example has a well-structured schema with `recovery_hints` array ### Consistency checks - ✅ HTML styling (`<div class="highlight"><pre><code>` with span colors) matches other command entries - ✅ MkDocs Material tabbed format (`=== "Rich"`, `=== "Plain"`, `=== "JSON"`) is consistent - ✅ Section heading level (`#####`) matches sibling command reference sections - ✅ Commit message follows Conventional Changelog format: `docs: update specification — add agents plan errors command` - ✅ PR description includes closing keyword for issue #2883 - ✅ Proposal #2883 was approved by `freemo` - ✅ Scope correctly narrowed to `agents plan errors` only (per human feedback on the proposal) ### CI Status All required quality gate checks passing: lint, typecheck, security, quality, unit_tests, coverage, integration_tests, e2e_tests, build, helm, docker, status-check. No issues found. Clean documentation addition that fills a genuine specification gap. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo referenced this pull request 2026-04-05 05:29:42 +00:00

Proposal: update specification — document agents plan errors command #2883

freemo referenced this pull request 2026-04-05 05:44:50 +00:00

Proposal: update specification — document agents plan errors command #2883

freemo commented 2026-04-05 06:52:38 +00:00

Author

Owner

Copy Link

Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1775371400]

---

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

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1775371400] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo added this to the v3.7.0 milestone 2026-04-05 07:05:09 +00:00

freemo reviewed 2026-04-05 07:07:15 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

Review: APPROVED ✅

(Posted as COMMENT because Forgejo prevents self-approval — the bot account authored this PR.)

Scope of Review

Reviewed the complete diff (92 lines added to docs/specification.md), commit message, PR metadata, linked issue #2883, CI status, and cross-referenced against the existing implementation and specification patterns.

Findings

Specification Alignment ✅

• The agents plan errors command is confirmed implemented in src/cleveragents/cli/commands/plan.py (line 18 command table)
• The TUI slash catalog already references it at spec line 29322 (/plan:errors <id>)
• This PR correctly fills the documentation gap in the CLI Command Synopsis and Command Reference sections

Content Quality ✅

1. Synopsis placement: agents plan errors <PLAN_ID> correctly placed after agents plan rollback — matches the approved proposal #2883
2. Command Reference placement: New ##### agents plan errors section correctly placed between agents plan artifacts and agents plan prompt
3. HTML styling: Uses <div class="highlight"><pre><code> with span color attributes — consistent with all other command entries
4. MkDocs Material tabs: Uses === "Rich", === "Plain", === "JSON" — consistent with sibling sections
5. Section heading level: ##### — matches all other command reference subsections
6. Arguments: Properly documents <PLAN_ID> as ULID — consistent pattern
7. Output examples: All three formats are well-structured, realistic, and internally consistent (same data across Rich/Plain/JSON)

Commit Standards ✅

• First line: docs: update specification — add agents plan errors command — valid Conventional Changelog format
• Body: Detailed description of changes with rationale
• Footer: ISSUES CLOSED: #2883 — properly formatted
• Single atomic commit — clean history

PR Metadata ✅

• Title: Descriptive and matches commit message
• Body: Detailed with Closes proposal #2883
• Type/ label: Type/Task present
• Milestone: v3.7.0 (assigned during review to match linked issue)
• Bot signature: Present

CI Status ✅

All required checks passing: lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, helm, docker, status-check.

Minor Fix Applied

• Assigned milestone v3.7.0 to the PR to match the linked issue's milestone, per CONTRIBUTING.md requirements.

Verdict

Clean documentation-only PR that fills a genuine specification gap. The content is well-structured, consistent with existing patterns, and backed by an approved proposal. No issues found.

---

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

## Review: APPROVED ✅ (Posted as COMMENT because Forgejo prevents self-approval — the bot account authored this PR.) ### Scope of Review Reviewed the complete diff (92 lines added to `docs/specification.md`), commit message, PR metadata, linked issue #2883, CI status, and cross-referenced against the existing implementation and specification patterns. ### Findings #### Specification Alignment ✅ - The `agents plan errors` command is confirmed implemented in `src/cleveragents/cli/commands/plan.py` (line 18 command table) - The TUI slash catalog already references it at spec line 29322 (`/plan:errors <id>`) - This PR correctly fills the documentation gap in the CLI Command Synopsis and Command Reference sections #### Content Quality ✅ 1. **Synopsis placement**: `agents plan errors <PLAN_ID>` correctly placed after `agents plan rollback` — matches the approved proposal #2883 2. **Command Reference placement**: New `##### agents plan errors` section correctly placed between `agents plan artifacts` and `agents plan prompt` 3. **HTML styling**: Uses `<div class="highlight"><pre><code>` with span color attributes — consistent with all other command entries 4. **MkDocs Material tabs**: Uses `=== "Rich"`, `=== "Plain"`, `=== "JSON"` — consistent with sibling sections 5. **Section heading level**: `#####` — matches all other command reference subsections 6. **Arguments**: Properly documents `<PLAN_ID>` as ULID — consistent pattern 7. **Output examples**: All three formats are well-structured, realistic, and internally consistent (same data across Rich/Plain/JSON) #### Commit Standards ✅ - First line: `docs: update specification — add agents plan errors command` — valid Conventional Changelog format - Body: Detailed description of changes with rationale - Footer: `ISSUES CLOSED: #2883` — properly formatted - Single atomic commit — clean history #### PR Metadata ✅ - Title: Descriptive and matches commit message - Body: Detailed with `Closes proposal #2883` - Type/ label: `Type/Task` present - Milestone: v3.7.0 (assigned during review to match linked issue) - Bot signature: Present #### CI Status ✅ All required checks passing: lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, helm, docker, status-check. ### Minor Fix Applied - Assigned milestone v3.7.0 to the PR to match the linked issue's milestone, per CONTRIBUTING.md requirements. ### Verdict Clean documentation-only PR that fills a genuine specification gap. The content is well-structured, consistent with existing patterns, and backed by an approved proposal. No issues found. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo referenced this pull request 2026-04-05 07:08:58 +00:00

Proposal: update specification — document agents plan errors command #2883

freemo referenced this pull request 2026-04-05 07:35:27 +00:00

[CA-AUTO] Architecture Supervisor — Session Tracker — 2026-04-05 #3180

freemo commented 2026-04-05 08:17:03 +00:00

Author

Owner

Copy Link

Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1775373000]

---

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

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1775373000] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo referenced this pull request 2026-04-05 08:42:35 +00:00

[CA-AUTO] Architecture Supervisor — Session Tracker — 2026-04-05 #3180

freemo reviewed 2026-04-05 09:02:07 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

Independent Review: APPROVED ✅

(Posted as COMMENT because Forgejo prevents self-approval — the bot account authored this PR.)

Scope of Review

Reviewed the complete diff (92 lines added to docs/specification.md), commit message format, PR metadata compliance, linked issue #2883, CI status, and cross-referenced against the existing implementation in src/cleveragents/cli/commands/plan.py.

Specification Alignment ✅

• Implementation verified: @app.command("errors") at plan.py:2182 and command table entry at plan.py:18 confirm the command exists and is functional.
• TUI slash catalog: /plan:errors <id> already referenced in the spec (line 29322), confirming this was a genuine documentation gap.
• Proposal compliance: Changes match approved proposal #2883 exactly — synopsis placement after plan rollback, command reference placement after plan artifacts.

Content Quality ✅

1. Synopsis (line 347): agents plan errors <PLAN_ID> correctly added after plan rollback with consistent HTML span styling.
2. Command Reference: New ##### agents plan errors section with:
   • Synopsis div with matching highlight/pre/code HTML pattern
   • Purpose description is clear and accurate
   • Arguments section properly documents <PLAN_ID> (ULID)
   • Rich output: Well-structured panel with error category, phase, retry count, retriability, and recovery suggestions — uses opacity: 0.7 for CLI command hints
   • Plain text output: Follows established [OK] footer pattern
   • JSON output: Clean schema with recovery_hints array of {action, message, cli_command} objects
3. Cross-format consistency: Same data (plan ID, error message, recovery suggestions) across all three output formats ✅
4. MkDocs Material tabs: === "Rich", === "Plain", === "JSON" — consistent with sibling sections ✅
5. Heading level: ##### — matches all other command reference subsections ✅

Commit Standards ✅

• Format: docs: update specification — add agents plan errors command — valid Conventional Changelog
• Body: Detailed description with rationale
• Footer: ISSUES CLOSED: #2883 — properly formatted
• Single atomic commit — clean history

PR Metadata ✅

• Type/Task label present
• Milestone v3.7.0 assigned (matches linked issue)
• Closes proposal #2883 in body
• Bot signature present

CI Status ✅

All required checks passing: lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, status-check. Only benchmark-regression still pending (non-blocking).

Minor Observation (Non-blocking)

The synopsis ordering (artifacts → prompt → rollback → errors) differs from the command reference ordering (artifacts → errors → prompt). This follows the approved proposal exactly and is acceptable — synopsis and reference sections don't require identical ordering.

Verdict

Clean documentation-only PR filling a genuine specification gap. Content is well-structured, consistent with existing patterns, and backed by an approved proposal. No issues found.

---

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

## Independent Review: APPROVED ✅ (Posted as COMMENT because Forgejo prevents self-approval — the bot account authored this PR.) ### Scope of Review Reviewed the complete diff (92 lines added to `docs/specification.md`), commit message format, PR metadata compliance, linked issue #2883, CI status, and cross-referenced against the existing implementation in `src/cleveragents/cli/commands/plan.py`. ### Specification Alignment ✅ - **Implementation verified**: `@app.command("errors")` at `plan.py:2182` and command table entry at `plan.py:18` confirm the command exists and is functional. - **TUI slash catalog**: `/plan:errors <id>` already referenced in the spec (line 29322), confirming this was a genuine documentation gap. - **Proposal compliance**: Changes match approved proposal #2883 exactly — synopsis placement after `plan rollback`, command reference placement after `plan artifacts`. ### Content Quality ✅ 1. **Synopsis** (line 347): `agents plan errors <PLAN_ID>` correctly added after `plan rollback` with consistent HTML span styling. 2. **Command Reference**: New `##### agents plan errors` section with: - Synopsis div with matching `highlight/pre/code` HTML pattern - Purpose description is clear and accurate - Arguments section properly documents `<PLAN_ID>` (ULID) - Rich output: Well-structured panel with error category, phase, retry count, retriability, and recovery suggestions — uses `opacity: 0.7` for CLI command hints - Plain text output: Follows established `[OK]` footer pattern - JSON output: Clean schema with `recovery_hints` array of `{action, message, cli_command}` objects 3. **Cross-format consistency**: Same data (plan ID, error message, recovery suggestions) across all three output formats ✅ 4. **MkDocs Material tabs**: `=== "Rich"`, `=== "Plain"`, `=== "JSON"` — consistent with sibling sections ✅ 5. **Heading level**: `#####` — matches all other command reference subsections ✅ ### Commit Standards ✅ - Format: `docs: update specification — add agents plan errors command` — valid Conventional Changelog - Body: Detailed description with rationale - Footer: `ISSUES CLOSED: #2883` — properly formatted - Single atomic commit — clean history ### PR Metadata ✅ - `Type/Task` label present - Milestone v3.7.0 assigned (matches linked issue) - `Closes proposal #2883` in body - Bot signature present ### CI Status ✅ All required checks passing: lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, status-check. Only `benchmark-regression` still pending (non-blocking). ### Minor Observation (Non-blocking) The synopsis ordering (artifacts → prompt → rollback → errors) differs from the command reference ordering (artifacts → errors → prompt). This follows the approved proposal exactly and is acceptable — synopsis and reference sections don't require identical ordering. ### Verdict Clean documentation-only PR filling a genuine specification gap. Content is well-structured, consistent with existing patterns, and backed by an approved proposal. No issues found. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo referenced this pull request 2026-04-05 09:08:08 +00:00

Proposal: update specification — document agents plan errors command #2883

freemo commented 2026-04-05 09:15:38 +00:00

Author

Owner

Copy Link

Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1743899400]

---

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

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3033-1743899400] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo reviewed 2026-04-05 09:20:38 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

Code Review — LGTM ✅

PR: docs: update specification — add agents plan errors command

Review Checklist

✅ Correctness: Documents the agents plan errors CLI command in the specification. Command was already implemented but missing from CLI Command Synopsis and Command Reference sections.

✅ Commit Format: docs: follows Conventional Changelog format.

✅ No code changes: Spec documentation update only.

✅ Labels/Milestone: Priority/Medium, Type/Task, milestone v3.7.0 — correctly assigned.

Decision: LGTM — Proceeding to merge when CI passes.

---

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

## Code Review — LGTM ✅ **PR:** docs: update specification — add agents plan errors command ### Review Checklist **✅ Correctness:** Documents the `agents plan errors` CLI command in the specification. Command was already implemented but missing from CLI Command Synopsis and Command Reference sections. **✅ Commit Format:** `docs:` follows Conventional Changelog format. **✅ No code changes:** Spec documentation update only. **✅ Labels/Milestone:** `Priority/Medium`, `Type/Task`, milestone `v3.7.0` — correctly assigned. ### Decision: **LGTM** — Proceeding to merge when CI passes. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo scheduled this pull request to auto merge when all checks succeed 2026-04-05 09:27:20 +00:00

freemo referenced this pull request 2026-04-05 09:40:20 +00:00

[CA-AUTO] Architecture Supervisor — Session Tracker — 2026-04-05 #3180

freemo referenced this pull request 2026-04-05 20:00:39 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3572

freemo merged commit 96470f39dc into master 2026-04-05 21:16:20 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

freemo

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.

overdue

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 Label

Milestone

No items

No Milestone v3.7.0

Projects

Clear projects

No project

Assignees

Clear assignees

aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#3033