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

fix(tui): add ctrl+r reload and f2/ctrl+comma settings key bindings #10735

Open
HAL9000 wants to merge 3 commits from fix/tui-bindings-reload-settings into master
pull from: fix/tui-bindings-reload-settings
merge into: cleveragents:master
Conversation 8 Commits 3 Files changed 5 +226 -2
HAL9000 commented 2026-04-19 09:22:39 +00:00
Owner
Copy link

Summary

Implements missing keyboard bindings for the TUI application: ctrl+r for reload functionality and f2/ctrl+, for settings access. This resolves critical usability gaps identified in both TDD and UAT testing phases.

Changes

  • Keyboard Bindings: Added three new key bindings to BINDINGS in src/cleveragents/tui/app.py:

    • ctrl+r -> action_reload() - Resets session transcript and refreshes persona bar
    • f2 -> action_settings() - Toggles settings overlay
    • ctrl+, -> action_settings() - Alternative binding for settings overlay

  • Action Methods: Implemented two new action methods in app.py:

    • action_reload() - Clears session transcript and refreshes the persona bar display
    • action_settings() - Toggles the SettingsScreen overlay visibility

  • Settings Widget: Created new src/cleveragents/tui/widgets/settings_screen.py containing the SettingsScreen widget class for displaying and managing application settings

  • App Integration: Updated app.py to:

    • Add SettingsScreen to the compose() method
    • Initialize SettingsScreen in on_mount()

  • Test Coverage: Added comprehensive Behave scenarios in features/tui_app_coverage.feature:

    • Scenario for ctrl+r reload functionality
    • Scenarios for f2 and ctrl+, settings access
    • Updated existing BINDINGS count assertion from 3 to 6

  • Step Definitions: Added corresponding step implementations in features/steps/tui_app_coverage_steps.py for the new scenarios

Testing

  • Unit Tests: All 28 TUI coverage scenarios pass with 0 failures
  • Quality Gates:
    • Lint checks OK
    • Type checking OK
    • Dead code analysis OK
    • Unit tests OK

Issue Reference

Closes #10475
Closes #10473

Automated by CleverAgents Bot
Supervisor: Implementation Pool | Agent: implementation-worker

## Summary Implements missing keyboard bindings for the TUI application: `ctrl+r` for reload functionality and `f2`/`ctrl+,` for settings access. This resolves critical usability gaps identified in both TDD and UAT testing phases. ## Changes - **Keyboard Bindings**: Added three new key bindings to `BINDINGS` in `src/cleveragents/tui/app.py`: - `ctrl+r` -> `action_reload()` - Resets session transcript and refreshes persona bar - `f2` -> `action_settings()` - Toggles settings overlay - `ctrl+,` -> `action_settings()` - Alternative binding for settings overlay - **Action Methods**: Implemented two new action methods in `app.py`: - `action_reload()` - Clears session transcript and refreshes the persona bar display - `action_settings()` - Toggles the SettingsScreen overlay visibility - **Settings Widget**: Created new `src/cleveragents/tui/widgets/settings_screen.py` containing the `SettingsScreen` widget class for displaying and managing application settings - **App Integration**: Updated `app.py` to: - Add `SettingsScreen` to the `compose()` method - Initialize `SettingsScreen` in `on_mount()` - **Test Coverage**: Added comprehensive Behave scenarios in `features/tui_app_coverage.feature`: - Scenario for `ctrl+r` reload functionality - Scenarios for `f2` and `ctrl+,` settings access - Updated existing BINDINGS count assertion from 3 to 6 - **Step Definitions**: Added corresponding step implementations in `features/steps/tui_app_coverage_steps.py` for the new scenarios ## Testing - **Unit Tests**: All 28 TUI coverage scenarios pass with 0 failures - **Quality Gates**: - Lint checks OK - Type checking OK - Dead code analysis OK - Unit tests OK ## Issue Reference Closes #10475 Closes #10473 --- **Automated by CleverAgents Bot** Supervisor: Implementation Pool | Agent: implementation-worker
HAL9000 added this to the v3.7.0 milestone 2026-04-19 09:22:39 +00:00
fix(tui): add ctrl+r reload and f2/ctrl+, settings key bindings
Some checks failed
CI / unit_tests (pull_request) Failing after 12s
Details
CI / helm (pull_request) Successful in 41s
Details
CI / push-validation (pull_request) Successful in 33s
Details
CI / build (pull_request) Successful in 3m51s
Details
CI / lint (pull_request) Successful in 4m10s
Details
CI / quality (pull_request) Successful in 4m34s
Details
CI / typecheck (pull_request) Successful in 4m49s
Details
CI / security (pull_request) Successful in 4m54s
Details
CI / docker (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Successful in 7m2s
Details
CI / integration_tests (pull_request) Successful in 7m58s
Details
CI / coverage (pull_request) Successful in 16m40s
Details
CI / status-check (pull_request) Failing after 3s
Details
dc05f04306 
- Added ctrl+r (reload), f2 (settings), and ctrl+, (settings) to BINDINGS in src/cleveragents/tui/app.py

- Implemented action_reload() to reset session transcript and refresh the persona bar

- Implemented action_settings() to toggle the SettingsScreen overlay

- Created new src/cleveragents/tui/widgets/settings_screen.py with SettingsScreen widget

- Added SettingsScreen to compose() method and on_mount() initialization in app.py

- Added Behave scenarios for ctrl+r reload and f2/ctrl+, settings in features/tui_app_coverage.feature

- Added step definitions for the new scenarios in features/steps/tui_app_coverage_steps.py

- Updated BINDINGS count from 3 to 6 in existing test scenario

ISSUES CLOSED: #10475
fix(tui): export SettingsScreen from widgets package
Some checks failed
CI / helm (pull_request) Successful in 35s
Details
CI / build (pull_request) Successful in 3m50s
Details
CI / lint (pull_request) Successful in 3m59s
Details
CI / quality (pull_request) Successful in 4m22s
Details
CI / typecheck (pull_request) Successful in 4m40s
Details
CI / security (pull_request) Successful in 4m46s
Details
CI / unit_tests (pull_request) Failing after 5m40s
Details
CI / docker (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 22s
Details
CI / integration_tests (pull_request) Successful in 8m29s
Details
CI / e2e_tests (pull_request) Successful in 8m37s
Details
CI / coverage (pull_request) Successful in 15m37s
Details
CI / status-check (pull_request) Failing after 5s
Details
747c6c7910
HAL9001 requested changes 2026-04-26 16:33:13 +00:00
HAL9001 left a comment
Copy link

The CI checks are failing for this PR. All CI gates (lint, typecheck, security, unit_tests, coverage) must pass before a PR can be approved and merged. Please ensure the changes do not introduce any failures and that all tests pass.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

The CI checks are failing for this PR. All CI gates (lint, typecheck, security, unit_tests, coverage) must pass before a PR can be approved and merged. Please ensure the changes do not introduce any failures and that all tests pass. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 requested changes 2026-04-26 16:33:13 +00:00
HAL9001 left a comment
Copy link

The CI checks are failing for this PR. All CI gates (lint, typecheck, security, unit_tests, coverage) must pass before a PR can be approved and merged. Please ensure the changes do not introduce any failures and that all tests pass.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

The CI checks are failing for this PR. All CI gates (lint, typecheck, security, unit_tests, coverage) must pass before a PR can be approved and merged. Please ensure the changes do not introduce any failures and that all tests pass. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9000 commented 2026-06-06 12:13:51 +00:00
Author
Owner
Copy link

[CONTROLLER-DEFER:Gate 1:needs_evaluation]

This PR has been deferred for re-evaluation. The controller has stepped back
from processing it. To resume, a human or scope-evaluator must clear the
deferral flag AND re-add the auto/sentinel label.

Decision:

  • Gate: Gate 1
  • Reason category: needs_evaluation
  • Canonical: #10651
  • LLM confidence: medium
  • LLM reasoning: Both PRs implement TUI Settings screen functionality. Anchor #10735 adds specific keyboard bindings (ctrl+r, f2, ctrl+,) with comprehensive test coverage for those bindings, closing issues #10475 and #10473. PR #10651 is a broader feature implementation of the Settings screen itself (668 additions vs 226). The overlap is clear—both touch SettingsScreen implementation—but the anchor may have unique value in its targeted bindings and test coverage. Requires human judgment to determine if they're complementary or if one fully subsumes the other.
  • Preserved value (when applicable): Anchor's specific keyboard binding test scenarios (ctrl+r reload, f2 settings, ctrl+, settings) and dedicated test coverage may not be present in #10651. These bindings close specific UAT-identified issues (#10475, #10473) and represent user-facing usability improvements distinct from the broader Settings screen feature work.

To clear the deferral (SQL):
UPDATE workflows SET deferred_reason=NULL,
deferred_at=NULL,
deferred_target_workflow_id=NULL
WHERE workflow_id = 306;

INSERT INTO controller_events
  (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts)
VALUES (306, datetime('now'), 'deferral_cleared',
        json_object('cleared_by', 'operator', 'reason', '<your reason>'),
        'operator', 0, 0);

Audit ID: 69887

Automated by the CleverAgents controller pipeline.
Identity: HAL9000 (pipeline action)

[CONTROLLER-DEFER:Gate 1:needs_evaluation] This PR has been deferred for re-evaluation. The controller has stepped back from processing it. To resume, a human or scope-evaluator must clear the deferral flag AND re-add the auto/sentinel label. Decision: - Gate: Gate 1 - Reason category: needs_evaluation - Canonical: #10651 - LLM confidence: medium - LLM reasoning: Both PRs implement TUI Settings screen functionality. Anchor #10735 adds specific keyboard bindings (ctrl+r, f2, ctrl+,) with comprehensive test coverage for those bindings, closing issues #10475 and #10473. PR #10651 is a broader feature implementation of the Settings screen itself (668 additions vs 226). The overlap is clear—both touch SettingsScreen implementation—but the anchor may have unique value in its targeted bindings and test coverage. Requires human judgment to determine if they're complementary or if one fully subsumes the other. - Preserved value (when applicable): Anchor's specific keyboard binding test scenarios (ctrl+r reload, f2 settings, ctrl+, settings) and dedicated test coverage may not be present in #10651. These bindings close specific UAT-identified issues (#10475, #10473) and represent user-facing usability improvements distinct from the broader Settings screen feature work. To clear the deferral (SQL): UPDATE workflows SET deferred_reason=NULL, deferred_at=NULL, deferred_target_workflow_id=NULL WHERE workflow_id = 306; INSERT INTO controller_events (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts) VALUES (306, datetime('now'), 'deferral_cleared', json_object('cleared_by', 'operator', 'reason', '<your reason>'), 'operator', 0, 0); Audit ID: 69887 --- Automated by the CleverAgents controller pipeline. Identity: HAL9000 (pipeline action) <!-- controller:fingerprint:197ee94c52aa430d -->
chore: re-trigger CI [controller]
Some checks failed
CI / lint (pull_request) Successful in 1m1s
Details
CI / push-validation (pull_request) Successful in 36s
Details
CI / helm (pull_request) Successful in 38s
Details
CI / build (pull_request) Successful in 52s
Details
CI / typecheck (pull_request) Successful in 1m20s
Details
CI / quality (pull_request) Successful in 1m31s
Details
CI / security (pull_request) Successful in 1m43s
Details
CI / e2e_tests (pull_request) Successful in 4m51s
Details
CI / integration_tests (pull_request) Failing after 4m58s
Details
CI / unit_tests (pull_request) Failing after 6m17s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Successful in 11m33s
Details
CI / status-check (pull_request) Failing after 3s
Details
90b8e84191
HAL9000 commented 2026-06-13 08:52:28 +00:00
Author
Owner
Copy link

📋 Estimate: tier 1.

Multi-file TUI change: new SettingsScreen widget, 2 action methods, 3 key bindings wired into app.py compose/on_mount, plus new Behave scenarios and step definitions. CI is failing on unit_tests (3 scenarios failed/7 errored out of 15K+) and integration_tests (2 Robot "Unknown Actor Name Error" failures likely pre-existing but need triage). New logic + test additions + active CI failures to diagnose and fix place this firmly at tier 1.

**📋 Estimate: tier 1.** Multi-file TUI change: new SettingsScreen widget, 2 action methods, 3 key bindings wired into app.py compose/on_mount, plus new Behave scenarios and step definitions. CI is failing on unit_tests (3 scenarios failed/7 errored out of 15K+) and integration_tests (2 Robot "Unknown Actor Name Error" failures likely pre-existing but need triage). New logic + test additions + active CI failures to diagnose and fix place this firmly at tier 1. <!-- controller:fingerprint:6adb3eabae219ee3 -->
HAL9000 commented 2026-06-13 14:22:15 +00:00
Author
Owner
Copy link

🌱 Grooming: proceed — PR cleared for processing.

(check no_duplicates, category no_duplicates)

PR #10735 adds three specific keybindings (ctrl+r reload, f2/ctrl+, settings) and implements a new SettingsScreen widget. Scanned 289 open PRs for TUI keybinding and settings work; found multiple other keybinding PRs but each targets distinct functionality (persona cycling, block navigation, session screens). No other PR claims the ctrl+r, f2, or ctrl+, keybindings. SettingsScreen widget is unique to this PR. Closes issues #10475 and #10473 which are not referenced by any other open PR. Clear topical separation from all existing work.

**🌱 Grooming: proceed** — PR cleared for processing. (check `no_duplicates`, category `no_duplicates`) PR #10735 adds three specific keybindings (ctrl+r reload, f2/ctrl+, settings) and implements a new SettingsScreen widget. Scanned 289 open PRs for TUI keybinding and settings work; found multiple other keybinding PRs but each targets distinct functionality (persona cycling, block navigation, session screens). No other PR claims the ctrl+r, f2, or ctrl+, keybindings. SettingsScreen widget is unique to this PR. Closes issues #10475 and #10473 which are not referenced by any other open PR. Clear topical separation from all existing work. <!-- controller:fingerprint:b207989fcc56e10c -->
HAL9000 commented 2026-06-14 09:55:15 +00:00
Author
Owner
Copy link

📋 Estimate: tier 1.

Multi-file change (5 files, +226/-2) adding new TUI key bindings, two action methods, a new SettingsScreen widget class, and Behave test scenarios with step definitions. CI is failing: unit_tests shows 3 scenarios failed/7 errored (likely in the newly added TUI coverage scenarios), and integration_tests shows Robot "Unknown Actor Name Error" failures (possibly pre-existing but must be assessed). New logic branches (action_reload, action_settings), a new widget file, and failing tests requiring diagnosis all place this firmly at tier 1 — standard multi-file engineering work with cross-file context needed to fix CI.

**📋 Estimate: tier 1.** Multi-file change (5 files, +226/-2) adding new TUI key bindings, two action methods, a new SettingsScreen widget class, and Behave test scenarios with step definitions. CI is failing: unit_tests shows 3 scenarios failed/7 errored (likely in the newly added TUI coverage scenarios), and integration_tests shows Robot "Unknown Actor Name Error" failures (possibly pre-existing but must be assessed). New logic branches (action_reload, action_settings), a new widget file, and failing tests requiring diagnosis all place this firmly at tier 1 — standard multi-file engineering work with cross-file context needed to fix CI. <!-- controller:fingerprint:0ae73808bd7a61ca -->
HAL9000 force-pushed fix/tui-bindings-reload-settings from 90b8e84191
Some checks failed
CI / lint (pull_request) Successful in 1m1s
Details
CI / push-validation (pull_request) Successful in 36s
Details
CI / helm (pull_request) Successful in 38s
Details
CI / build (pull_request) Successful in 52s
Details
CI / typecheck (pull_request) Successful in 1m20s
Details
CI / quality (pull_request) Successful in 1m31s
Details
CI / security (pull_request) Successful in 1m43s
Details
CI / e2e_tests (pull_request) Successful in 4m51s
Details
CI / integration_tests (pull_request) Failing after 4m58s
Details
CI / unit_tests (pull_request) Failing after 6m17s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Successful in 11m33s
Details
CI / status-check (pull_request) Failing after 3s
Details
to f15780c5e5
Some checks failed
CI / lint (pull_request) Successful in 38s
Details
CI / build (pull_request) Successful in 41s
Details
CI / helm (pull_request) Successful in 39s
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / typecheck (pull_request) Successful in 1m1s
Details
CI / quality (pull_request) Successful in 1m15s
Details
CI / security (pull_request) Successful in 1m21s
Details
CI / unit_tests (pull_request) Failing after 2m59s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / integration_tests (pull_request) Successful in 9m9s
Details
CI / status-check (pull_request) Failing after 4s
Details
2026-06-14 12:25:45 +00:00 Compare
HAL9000 commented 2026-06-14 12:28:20 +00:00
Author
Owner
Copy link

(attempt #16, tier 1)

🔧 Implementer attempt — ci-not-ready.

_(attempt #16, tier 1)_ **🔧 Implementer attempt — `ci-not-ready`.** <!-- controller:fingerprint:8b917901d2c2d6de -->
HAL9000 commented 2026-06-14 15:11:27 +00:00
Author
Owner
Copy link

(attempt #20, tier 2)

🔧 Implementer attempt — blocked.

Blockers:

  • CI/local test result divergence; cannot diagnose without log access. Worktree is clean at f15780c5e (which already includes a prior controller-issued CI re-trigger commit). The local coverage_report gate just passed at 96.6% coverage (>96.5% threshold) — all 8 unit-test chunks ran successfully and produced coverage data, so unit_tests pass locally on this exact HEAD. CI, however, reports the unit_tests gate failing with this summary: "0 features passed, 0 failed, 8 errored, 0 skipped" and "0 scenarios passed, 0 failed, 0 errored, 0 skipped" with a Wall time of 2m 2.160s. Zero scenarios were attempted across all 8 chunks — only worker-process-level errors. This pattern (8 chunks killed before scenarios ran, short wall time, no traceback in summary) matches the documented CI runner reaper incident (intermittent external killer reaping CI jobs). The prior re-trigger commit (f15780c5e) did not resolve it. The full CI log cannot be fetched right now (ci_fetch_pr_failure_logs returned log:AttributeError), so I cannot confirm what the workers errored with — only the per-chunk summary is visible in the prompt excerpt. ci-infra-failure does not strictly apply because the CI log has a verdict (nox > Command ... failed with exit code 1 + summary line), not the "no verdict / stops mid-run" pattern the criteria require. resolved does not apply because there is nothing to fix in the code — the worktree is clean and the local gate passes. noop fails because the CI verdict is failure. Recommended operator action: (1) fetch the full CI log for run 23236 job 4 to confirm whether the 8 errors are worker preemption (infra) vs an environment-specific code issue that doesn't reproduce locally; (2) if confirmed as infra, push a single targeted re-trigger from the operator's session (the controller's prior auto-re-trigger commit did not help, suggesting the reaper is hitting consistently rather than transiently). No commits, files, or pushes were produced from this implementer attempt because there is no code-level work to do here.
_(attempt #20, tier 2)_ **🔧 Implementer attempt — `blocked`.** Blockers: - CI/local test result divergence; cannot diagnose without log access. Worktree is clean at f15780c5e (which already includes a prior controller-issued CI re-trigger commit). The local coverage_report gate just passed at 96.6% coverage (>96.5% threshold) — all 8 unit-test chunks ran successfully and produced coverage data, so unit_tests pass locally on this exact HEAD. CI, however, reports the unit_tests gate failing with this summary: "0 features passed, 0 failed, 8 errored, 0 skipped" and "0 scenarios passed, 0 failed, 0 errored, 0 skipped" with a Wall time of 2m 2.160s. Zero scenarios were attempted across all 8 chunks — only worker-process-level errors. This pattern (8 chunks killed before scenarios ran, short wall time, no traceback in summary) matches the documented CI runner reaper incident (intermittent external killer reaping CI jobs). The prior re-trigger commit (f15780c5e) did not resolve it. The full CI log cannot be fetched right now (ci_fetch_pr_failure_logs returned log:AttributeError), so I cannot confirm what the workers errored with — only the per-chunk summary is visible in the prompt excerpt. ci-infra-failure does not strictly apply because the CI log has a verdict (nox > Command ... failed with exit code 1 + summary line), not the "no verdict / stops mid-run" pattern the criteria require. resolved does not apply because there is nothing to fix in the code — the worktree is clean and the local gate passes. noop fails because the CI verdict is failure. Recommended operator action: (1) fetch the full CI log for run 23236 job 4 to confirm whether the 8 errors are worker preemption (infra) vs an environment-specific code issue that doesn't reproduce locally; (2) if confirmed as infra, push a single targeted re-trigger from the operator's session (the controller's prior auto-re-trigger commit did not help, suggesting the reaper is hitting consistently rather than transiently). No commits, files, or pushes were produced from this implementer attempt because there is no code-level work to do here. <!-- controller:fingerprint:d31e101189f1b7ac -->
Some checks failed
CI / lint (pull_request) Successful in 38s
Required
Details
CI / build (pull_request) Successful in 41s
Required
Details
CI / helm (pull_request) Successful in 39s
Details
CI / push-validation (pull_request) Successful in 27s
Details
CI / typecheck (pull_request) Successful in 1m1s
Required
Details
CI / quality (pull_request) Successful in 1m15s
Required
Details
CI / security (pull_request) Successful in 1m21s
Required
Details
CI / unit_tests (pull_request) Failing after 2m59s
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / integration_tests (pull_request) Successful in 9m9s
Required
Details
CI / status-check (pull_request) Failing after 4s
Details
This pull request has changes conflicting with the target branch.
  • features/steps/tui_app_coverage_steps.py
  • features/tui_app_coverage.feature
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix/tui-bindings-reload-settings:fix/tui-bindings-reload-settings
git switch fix/tui-bindings-reload-settings
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.

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