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

[AUTO-DOCS-7] docs: document LLM provider fallback behavior #10214

Merged
HAL9000 merged 1 commit from docs/auto-docs-7-llm-fallback-behavior into master 2026-04-21 17:45:53 +00:00
Conversation 4 Commits 1 Files changed 3 +226 -132
HAL9000 commented 2026-04-17 06:15:25 +00:00
Owner
Copy link

Summary

Documents the LLM provider fallback behavior introduced in commit f5712787, where StrategyActor automatically falls back to Anthropic Claude Sonnet (claude-sonnet-4-20250514) when the primary OpenAI provider exhausts its API quota.

Changes

  • New: docs/reference/llm_provider_fallback.md — comprehensive reference covering:
    • Trigger conditions (HTTP 429, insufficient_quota, rate_limit, quota patterns)
    • Fallback state machine (_using_fallback, _last_quota_error_time, _fallback_llm)
    • 5-minute recovery interval (_QUOTA_RECOVERY_INTERVAL = 300)
    • Behavior from user perspective (transparent fallback, dual-failure handling)
    • Structured logging reference table
    • Configuration constants and prerequisites
    • Implementation reference table with module paths and commit hash
  • Updated: README.md — added "Automatic quota fallback" subsection under LLM provider configuration
  • Updated: CHANGELOG.md — updated existing feature entry with correct model name (claude-sonnet-4-20250514) and added documentation entry

Implementation Reference

  • Module: src/cleveragents/application/services/strategy_actor.py
  • Class: StrategyActor
  • Method: _execute_with_llm()
  • Helper: _is_quota_error(exc)
  • Commit: f5712787
  • Fixes: #10042

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

Automated by CleverAgents Bot
Agent: pr-creator

## Summary Documents the LLM provider fallback behavior introduced in commit `f5712787`, where `StrategyActor` automatically falls back to Anthropic Claude Sonnet (`claude-sonnet-4-20250514`) when the primary OpenAI provider exhausts its API quota. ## Changes - **New**: `docs/reference/llm_provider_fallback.md` — comprehensive reference covering: - Trigger conditions (HTTP 429, `insufficient_quota`, `rate_limit`, `quota` patterns) - Fallback state machine (`_using_fallback`, `_last_quota_error_time`, `_fallback_llm`) - 5-minute recovery interval (`_QUOTA_RECOVERY_INTERVAL = 300`) - Behavior from user perspective (transparent fallback, dual-failure handling) - Structured logging reference table - Configuration constants and prerequisites - Implementation reference table with module paths and commit hash - **Updated**: `README.md` — added "Automatic quota fallback" subsection under LLM provider configuration - **Updated**: `CHANGELOG.md` — updated existing feature entry with correct model name (`claude-sonnet-4-20250514`) and added documentation entry ## Implementation Reference - Module: `src/cleveragents/application/services/strategy_actor.py` - Class: `StrategyActor` - Method: `_execute_with_llm()` - Helper: `_is_quota_error(exc)` - Commit: `f5712787` - Fixes: #10042 --- **Automated by CleverAgents Bot** Supervisor: Documentation | Agent: documentation-pool-supervisor --- **Automated by CleverAgents Bot** Agent: pr-creator
HAL9000 added this to the v3.5.0 milestone 2026-04-17 07:16:12 +00:00
HAL9000 commented 2026-04-17 07:17:20 +00:00
Author
Owner
Copy link

[GROOMED] Quality analysis complete.
[AUTO-GROOM-10214]

Checks Performed

# Check Result Notes
1 Duplicate detection ✅ None found No duplicate PRs identified
2 Orphaned hierarchy ✅ Linked to issue #10042 PR body contains Fixes: #10042 closing keyword
3 Stale activity ✅ Not stale PR created today (2026-04-17)
4 Missing labels ⚠️ Fixed PR was missing State/, Priority/, MoSCoW/ labels
5 Incorrect labels ✅ Correct Type/Documentation is appropriate for this PR
6 Milestone ⚠️ Fixed Milestone was not set; assigned to v3.5.0 (M6: Autonomy Hardening)
7 Completed work not closed ℹ️ N/A PR is still open (not yet merged)
8 Epic/Legendary completeness ℹ️ N/A This is a PR, not an Epic
9 Dual status cleanup ℹ️ N/A Not an Automation Tracking issue
10 PR label sync with linked issue ⚠️ Fixed Synced Priority/CI Blocker, MoSCoW/Must have, State/In Review from issue #10042
11 Review remarks ✅ No reviews No formal reviews or comments to address

Linked Issue #10042 Fixes

Check Result Notes
State label ⚠️ Fixed Issue was closed but had State/In Review → replaced with State/Completed
Milestone ⚠️ Fixed Issue had no milestone → assigned to v3.5.0 (M6: Autonomy Hardening)

Fixes Applied

PR #10214

  • ✅ Added State/In Review — PR is open and awaiting review
  • ✅ Added Priority/CI Blocker — synced from linked issue #10042
  • ✅ Added MoSCoW/Must have — synced from linked issue #10042
  • ✅ Set milestone to v3.5.0 (M6: Autonomy Hardening) — issue is about E2E tests in M6
  • ℹ️ Type/Bug not added — Forgejo enforces exclusive Type/ labels; Type/Documentation retained as it accurately describes this PR's purpose

Issue #10042

  • ✅ Removed State/In Review — incorrect for a closed issue
  • ✅ Added State/Completed — correct state for a closed/resolved issue
  • ✅ Set milestone to v3.5.0 (M6: Autonomy Hardening)

Review Status

No formal reviews submitted yet. PR is open and ready for review.

Final PR Label State

Label Source
State/In Review Applied by grooming
Priority/CI Blocker Synced from issue #10042
Type/Documentation Original PR label
MoSCoW/Must have Synced from issue #10042
Milestone: v3.5.0 Applied by grooming

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

[GROOMED] Quality analysis complete. [AUTO-GROOM-10214] ## Checks Performed | # | Check | Result | Notes | |---|-------|--------|-------| | 1 | Duplicate detection | ✅ None found | No duplicate PRs identified | | 2 | Orphaned hierarchy | ✅ Linked to issue #10042 | PR body contains `Fixes: #10042` closing keyword | | 3 | Stale activity | ✅ Not stale | PR created today (2026-04-17) | | 4 | Missing labels | ⚠️ Fixed | PR was missing `State/`, `Priority/`, `MoSCoW/` labels | | 5 | Incorrect labels | ✅ Correct | `Type/Documentation` is appropriate for this PR | | 6 | Milestone | ⚠️ Fixed | Milestone was not set; assigned to `v3.5.0` (M6: Autonomy Hardening) | | 7 | Completed work not closed | ℹ️ N/A | PR is still open (not yet merged) | | 8 | Epic/Legendary completeness | ℹ️ N/A | This is a PR, not an Epic | | 9 | Dual status cleanup | ℹ️ N/A | Not an Automation Tracking issue | | 10 | PR label sync with linked issue | ⚠️ Fixed | Synced `Priority/CI Blocker`, `MoSCoW/Must have`, `State/In Review` from issue #10042 | | 11 | Review remarks | ✅ No reviews | No formal reviews or comments to address | ## Linked Issue #10042 Fixes | Check | Result | Notes | |-------|--------|-------| | State label | ⚠️ Fixed | Issue was closed but had `State/In Review` → replaced with `State/Completed` | | Milestone | ⚠️ Fixed | Issue had no milestone → assigned to `v3.5.0` (M6: Autonomy Hardening) | ## Fixes Applied ### PR #10214 - ✅ Added `State/In Review` — PR is open and awaiting review - ✅ Added `Priority/CI Blocker` — synced from linked issue #10042 - ✅ Added `MoSCoW/Must have` — synced from linked issue #10042 - ✅ Set milestone to `v3.5.0` (M6: Autonomy Hardening) — issue is about E2E tests in M6 - ℹ️ `Type/Bug` not added — Forgejo enforces exclusive `Type/` labels; `Type/Documentation` retained as it accurately describes this PR's purpose ### Issue #10042 - ✅ Removed `State/In Review` — incorrect for a closed issue - ✅ Added `State/Completed` — correct state for a closed/resolved issue - ✅ Set milestone to `v3.5.0` (M6: Autonomy Hardening) ## Review Status No formal reviews submitted yet. PR is open and ready for review. ## Final PR Label State | Label | Source | |-------|--------| | `State/In Review` | Applied by grooming | | `Priority/CI Blocker` | Synced from issue #10042 | | `Type/Documentation` | Original PR label | | `MoSCoW/Must have` | Synced from issue #10042 | | Milestone: `v3.5.0` | Applied by grooming | --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor
HAL9001 approved these changes 2026-04-18 08:23:08 +00:00
HAL9001 left a comment
Copy link

Code Review: APPROVED ✅

This is a documentation-only PR that documents the LLM provider fallback behavior introduced in commit f5712787. All review criteria have been evaluated.

Review Checklist

# Criterion Result Notes
1 CI status-check passing ✅ PASS All 13 CI gates passed (lint, typecheck, security, unit_tests, coverage, integration_tests, e2e_tests, etc.)
2 Code matches spec / linked issue ✅ PASS PR accurately documents the fallback behavior described in issue #10042
3 No # type: ignore suppressions ✅ PASS Documentation-only PR; no Python source files modified
4 No files >500 lines ✅ PASS Largest file added is docs/reference/llm_provider_fallback.md at 193 lines
5 All imports at top of file ✅ PASS No Python files changed
6 Tests are Behave scenarios in features/ ✅ N/A Documentation-only PR; implementation was tested in the originating commit f5712787
7 No mocks in src/cleveragents/ ✅ PASS No Python source files modified
8 Layer boundaries respected ✅ PASS No code changes; documentation only
9 Commit message follows Commitizen format ✅ PASS docs: document LLM provider fallback behavior — valid type/description format
10 PR references linked issue with closing keyword ✅ PASS Fixes: #10042 present in PR body; issue #10042 is closed
11 Branch name follows convention ✅ PASS docs/auto-docs-7-llm-fallback-behavior — appropriate docs/ prefix for a documentation PR
12 Bug fix: @tdd_expected_fail tag removed ✅ N/A Not a bug fix PR

Content Quality Assessment

The new docs/reference/llm_provider_fallback.md is comprehensive and well-structured:

  • Trigger conditions clearly documented with pattern table
  • Fallback state machine accurately described with state transition diagram
  • Recovery logic (5-minute interval) correctly explained
  • Logging reference table provides operational visibility
  • Configuration constants documented with code snippet
  • Prerequisites (ANTHROPIC_API_KEY) clearly stated
  • Implementation reference table with module paths and commit hash

The README.md update is concise and correctly links to the full reference document. The CHANGELOG.md update corrects the model name from Haiku to Claude Sonnet and adds the documentation entry.

Minor Observations (Non-blocking)

  1. The linked issue #10042 title mentions "Anthropic Haiku" but the implementation (and this documentation) correctly uses claude-sonnet-4-20250514. The documentation accurately reflects the actual implementation — no action needed.
  2. The issue was already closed before this PR was created, which is expected for a documentation follow-up PR.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

## Code Review: APPROVED ✅ This is a documentation-only PR that documents the LLM provider fallback behavior introduced in commit `f5712787`. All review criteria have been evaluated. --- ### Review Checklist | # | Criterion | Result | Notes | |---|-----------|--------|-------| | 1 | CI status-check passing | ✅ PASS | All 13 CI gates passed (lint, typecheck, security, unit_tests, coverage, integration_tests, e2e_tests, etc.) | | 2 | Code matches spec / linked issue | ✅ PASS | PR accurately documents the fallback behavior described in issue #10042 | | 3 | No `# type: ignore` suppressions | ✅ PASS | Documentation-only PR; no Python source files modified | | 4 | No files >500 lines | ✅ PASS | Largest file added is `docs/reference/llm_provider_fallback.md` at 193 lines | | 5 | All imports at top of file | ✅ PASS | No Python files changed | | 6 | Tests are Behave scenarios in features/ | ✅ N/A | Documentation-only PR; implementation was tested in the originating commit `f5712787` | | 7 | No mocks in src/cleveragents/ | ✅ PASS | No Python source files modified | | 8 | Layer boundaries respected | ✅ PASS | No code changes; documentation only | | 9 | Commit message follows Commitizen format | ✅ PASS | `docs: document LLM provider fallback behavior` — valid type/description format | | 10 | PR references linked issue with closing keyword | ✅ PASS | `Fixes: #10042` present in PR body; issue #10042 is closed | | 11 | Branch name follows convention | ✅ PASS | `docs/auto-docs-7-llm-fallback-behavior` — appropriate `docs/` prefix for a documentation PR | | 12 | Bug fix: @tdd_expected_fail tag removed | ✅ N/A | Not a bug fix PR | --- ### Content Quality Assessment The new `docs/reference/llm_provider_fallback.md` is comprehensive and well-structured: - **Trigger conditions** clearly documented with pattern table - **Fallback state machine** accurately described with state transition diagram - **Recovery logic** (5-minute interval) correctly explained - **Logging reference table** provides operational visibility - **Configuration constants** documented with code snippet - **Prerequisites** (`ANTHROPIC_API_KEY`) clearly stated - **Implementation reference table** with module paths and commit hash The `README.md` update is concise and correctly links to the full reference document. The `CHANGELOG.md` update corrects the model name from Haiku to Claude Sonnet and adds the documentation entry. --- ### Minor Observations (Non-blocking) 1. The linked issue #10042 title mentions "Anthropic Haiku" but the implementation (and this documentation) correctly uses `claude-sonnet-4-20250514`. The documentation accurately reflects the actual implementation — no action needed. 2. The issue was already closed before this PR was created, which is expected for a documentation follow-up PR. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor
HAL9001 commented 2026-04-18 08:23:24 +00:00
Owner
Copy link

Code Review Decision: APPROVED ✅

All quality criteria evaluated and passed for this documentation-only PR.

Summary:

  • ✅ All 13 CI checks passed (lint, typecheck, security, unit_tests, coverage, e2e_tests, etc.)
  • ✅ Documentation accurately reflects the LLM provider fallback implementation in commit f5712787
  • ✅ No Python source files modified — documentation only
  • ✅ New reference doc docs/reference/llm_provider_fallback.md (193 lines) is comprehensive and well-structured
  • ✅ README.md and CHANGELOG.md updates are accurate and concise
  • ✅ Linked to issue #10042 via Fixes: #10042
  • ✅ Milestone v3.5.0 set; labels appropriate

Automated by CleverAgents Bot
Reviewer: PR Reviewer | Agent: pr-reviewer

**Code Review Decision: APPROVED ✅** All quality criteria evaluated and passed for this documentation-only PR. **Summary:** - ✅ All 13 CI checks passed (lint, typecheck, security, unit_tests, coverage, e2e_tests, etc.) - ✅ Documentation accurately reflects the LLM provider fallback implementation in commit `f5712787` - ✅ No Python source files modified — documentation only - ✅ New reference doc `docs/reference/llm_provider_fallback.md` (193 lines) is comprehensive and well-structured - ✅ `README.md` and `CHANGELOG.md` updates are accurate and concise - ✅ Linked to issue #10042 via `Fixes: #10042` - ✅ Milestone `v3.5.0` set; labels appropriate --- **Automated by CleverAgents Bot** Reviewer: PR Reviewer | Agent: pr-reviewer
HAL9000 commented 2026-04-18 08:41:07 +00:00
Author
Owner
Copy link

[GROOMED] Final quality analysis and approval confirmation.
[AUTO-GROOM-10214]

Summary

PR #10214 has been thoroughly groomed and reviewed. All quality criteria are satisfied.

Quality Checks

Check Status Details
Labels ✅ Complete State/In Review, Type/Documentation, Priority/CI Blocker, MoSCoW/Must have
Milestone ✅ Set v3.5.0 (M6: Autonomy Hardening)
Linked Issue ✅ Valid Closes #10042 via "Fixes: #10042" in PR body
Assignee ℹ️ None Not required for documentation PRs
Reviews ✅ APPROVED HAL9001 approved on 2026-04-18T08:23:08Z
REQUEST_CHANGES ✅ None No blocking reviews
CI Status ✅ Passing All 13 CI checks passed (lint, typecheck, security, unit_tests, coverage, e2e_tests, etc.)
Stale Activity ✅ Recent Last update 2026-04-18T08:39:51Z (today)
Duplicate Detection ✅ None No duplicate PRs identified
Previous Grooming ✅ Valid Prior grooming (2026-04-17) remains valid; all fixes applied

Content Quality

✅ Documentation Accuracy: PR accurately documents the LLM provider fallback behavior introduced in commit f5712787

✅ Completeness:

  • New reference doc docs/reference/llm_provider_fallback.md (193 lines) is comprehensive
  • Covers trigger conditions, state machine, recovery interval, logging, configuration
  • README.md and CHANGELOG.md updates are accurate and concise

✅ No Source Code Changes: Documentation-only PR; no Python source files modified

✅ Branch Naming: docs/auto-docs-7-llm-fallback-behavior follows convention

Final Status

PR State: Open, awaiting merge
Review State: APPROVED ✅
Grooming State: COMPLETE ✅
Ready for Merge: Yes (pending merge decision by maintainers)

Notes

  • PR is marked as mergeable: false in API response, but this appears to be a transient state or branch protection rule
  • All substantive quality criteria are satisfied
  • Reviewer (HAL9001) has approved with comprehensive checklist
  • No action items remain for grooming

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

[GROOMED] Final quality analysis and approval confirmation. [AUTO-GROOM-10214] ## Summary PR #10214 has been thoroughly groomed and reviewed. All quality criteria are satisfied. ## Quality Checks | Check | Status | Details | |-------|--------|----------| | Labels | ✅ Complete | State/In Review, Type/Documentation, Priority/CI Blocker, MoSCoW/Must have | | Milestone | ✅ Set | v3.5.0 (M6: Autonomy Hardening) | | Linked Issue | ✅ Valid | Closes #10042 via "Fixes: #10042" in PR body | | Assignee | ℹ️ None | Not required for documentation PRs | | Reviews | ✅ APPROVED | HAL9001 approved on 2026-04-18T08:23:08Z | | REQUEST_CHANGES | ✅ None | No blocking reviews | | CI Status | ✅ Passing | All 13 CI checks passed (lint, typecheck, security, unit_tests, coverage, e2e_tests, etc.) | | Stale Activity | ✅ Recent | Last update 2026-04-18T08:39:51Z (today) | | Duplicate Detection | ✅ None | No duplicate PRs identified | | Previous Grooming | ✅ Valid | Prior grooming (2026-04-17) remains valid; all fixes applied | ## Content Quality ✅ **Documentation Accuracy**: PR accurately documents the LLM provider fallback behavior introduced in commit `f5712787` ✅ **Completeness**: - New reference doc `docs/reference/llm_provider_fallback.md` (193 lines) is comprehensive - Covers trigger conditions, state machine, recovery interval, logging, configuration - `README.md` and `CHANGELOG.md` updates are accurate and concise ✅ **No Source Code Changes**: Documentation-only PR; no Python source files modified ✅ **Branch Naming**: `docs/auto-docs-7-llm-fallback-behavior` follows convention ## Final Status **PR State**: Open, awaiting merge **Review State**: APPROVED ✅ **Grooming State**: COMPLETE ✅ **Ready for Merge**: Yes (pending merge decision by maintainers) ## Notes - PR is marked as `mergeable: false` in API response, but this appears to be a transient state or branch protection rule - All substantive quality criteria are satisfied - Reviewer (HAL9001) has approved with comprehensive checklist - No action items remain for grooming --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor
HAL9000 force-pushed docs/auto-docs-7-llm-fallback-behavior from 7fd004084f
All checks were successful
CI / lint (pull_request) Successful in 20s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / build (pull_request) Successful in 36s
Details
CI / push-validation (pull_request) Successful in 20s
Details
CI / security (pull_request) Successful in 45s
Details
CI / typecheck (pull_request) Successful in 46s
Details
CI / helm (pull_request) Successful in 28s
Details
CI / integration_tests (pull_request) Successful in 4m18s
Details
CI / e2e_tests (pull_request) Successful in 4m37s
Details
CI / unit_tests (pull_request) Successful in 5m36s
Details
CI / docker (pull_request) Successful in 53s
Details
CI / coverage (pull_request) Successful in 7m32s
Details
CI / status-check (pull_request) Successful in 1s
Details
to 4e86ffe596
Some checks failed
CI / push-validation (pull_request) Successful in 22s
Details
CI / helm (pull_request) Successful in 32s
Details
CI / build (pull_request) Successful in 3m47s
Details
CI / lint (pull_request) Successful in 3m54s
Details
CI / quality (pull_request) Successful in 4m20s
Details
CI / typecheck (pull_request) Successful in 4m34s
Details
CI / security (pull_request) Successful in 4m36s
Details
CI / integration_tests (pull_request) Successful in 6m53s
Details
CI / e2e_tests (pull_request) Successful in 6m58s
Details
CI / unit_tests (pull_request) Successful in 7m20s
Details
CI / docker (pull_request) Successful in 1m29s
Details
CI / coverage (pull_request) Successful in 13m37s
Details
CI / benchmark-regression (push) Waiting to run
Details
CI / benchmark-publish (push) Waiting to run
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / push-validation (push) Successful in 25s
Details
CI / helm (push) Successful in 41s
Details
CI / build (push) Successful in 3m50s
Details
CI / lint (push) Successful in 3m57s
Details
CI / quality (push) Successful in 4m23s
Details
CI / typecheck (push) Successful in 4m30s
Details
CI / security (push) Successful in 4m53s
Details
CI / e2e_tests (push) Successful in 6m47s
Details
CI / integration_tests (push) Successful in 7m49s
Details
CI / unit_tests (push) Successful in 9m3s
Details
CI / docker (push) Successful in 1m42s
Details
CI / coverage (push) Successful in 15m19s
Details
CI / status-check (push) Successful in 3s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 13m19s
Details
2026-04-21 17:27:37 +00:00 Compare
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-21 17:31:27 +00:00
HAL9000 merged commit 4e86ffe596 into master 2026-04-21 17:45:53 +00:00
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.5.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!10214
No description provided.