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

fix(a2a): validate session_id at entry of _handle_session_close before devcontainer cleanup #11098

Open
HAL9000 wants to merge 2 commits from feature/9250-fix-a2a-session-close into master
pull from: feature/9250-fix-a2a-session-close
merge into: cleveragents:master
Conversation 4 Commits 2 Files changed 6 +45 -6
HAL9000 commented 2026-05-09 14:23:02 +00:00
Owner
Copy link

Summary

  • Move session_id validation to top of _handle_session_close() in A2aLocalFacade
  • Add BDD test for no-service + empty session_id path (wiring and coverage features)
  • Update CHANGELOG.md under Fixed section with fix description
  • Update CONTRIBUTORS.md with HAL 9000 contribution entry

Changes Made

  • src/cleveragents/a2a/facade.py — moved session_id validation before devcontainer cleanup in _handle_session_close()
  • features/a2a_facade_wiring.feature — added scenario for no-service + empty session_id
    CHANGELOG.md — Added Fixed entry
    CONTRIBUTORS.md — Updated with new contribution entry

Closes #9250

## Summary - Move session_id validation to top of _handle_session_close() in A2aLocalFacade - Add BDD test for no-service + empty session_id path (wiring and coverage features) - Update CHANGELOG.md under Fixed section with fix description - Update CONTRIBUTORS.md with HAL 9000 contribution entry ## Changes Made - src/cleveragents/a2a/facade.py — moved session_id validation before devcontainer cleanup in _handle_session_close() - features/a2a_facade_wiring.feature — added scenario for no-service + empty session_id CHANGELOG.md — Added Fixed entry CONTRIBUTORS.md — Updated with new contribution entry Closes #9250
The _handle_session_close handler in the A2A local facade previously validated
session_id only after checking whether a session service was wired. When no
session service was available, _cleanup_session_devcontainers() was invoked
with an empty or missing session_id, risking incorrect container lifecycle
operations on unknown sessions. This fix moves validation to the top of
_handle_session_close so it applies uniformly across both code paths.

Updated BDD tests in features/a2a_facade_wiring.feature and
features/a2a_facade_coverage.feature to reflect the new validation behavior.

PR-CLOSED: #9250
fix(a2a): close session_id validation bypass in _handle_session_close
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 51s
Details
CI / lint (pull_request) Failing after 1m9s
Details
CI / benchmark-regression (pull_request) Failing after 1m16s
Details
CI / build (pull_request) Successful in 1m4s
Details
CI / integration_tests (pull_request) Failing after 1m23s
Details
CI / e2e_tests (pull_request) Failing after 1m24s
Details
CI / quality (pull_request) Successful in 1m28s
Details
CI / unit_tests (pull_request) Failing after 1m37s
Details
CI / typecheck (pull_request) Failing after 1m39s
Details
CI / security (pull_request) Failing after 2m4s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 22s
Details
CI / status-check (pull_request) Failing after 3s
Details
e1a75e472d 
Removed unreachable duplicate code left over after moving session_id validation
to the top of _handle_session_close(). Updated BDD test scenario in
a2a_facade_wiring.feature to cover the no-service + empty session_id path.

PR-CLOSED: #9250
HAL9000 added this to the v3.5.0 milestone 2026-05-09 14:28:10 +00:00
HAL9001 requested changes 2026-05-09 17:48:28 +00:00
HAL9001 left a comment
Copy link

Code Review — PR #11098

The intent of this fix is correct: moving session_id validation to the top of _handle_session_close() is the right approach. However, this PR has multiple blocking issues that must be resolved before it can be merged.

BLOCKING Issues

1. Critical Python SyntaxError — root cause of ALL CI failures
Line 321 of src/cleveragents/a2a/facade.py has 2-space indentation on the def _handle_session_close line instead of the required 4 spaces. Python raises IndentationError when importing this module. This single error causes every CI gate to fail: lint, typecheck, unit_tests, integration_tests, e2e_tests, security, and the status-check aggregate gate.

Fix: Change the def _handle_session_close line indentation from 2 spaces to 4 spaces.

2. Missing TDD Regression Test
This PR closes issue #9250, labeled Type/Bug. Per the mandatory Bug Fix Workflow in CONTRIBUTING.md, every bug fix must have a corresponding @tdd_issue + @tdd_issue_9250 Behave scenario. No such tag exists anywhere in features/. This is a policy violation: a bug fix PR that closes issue #N where no @tdd_issue_N test exists in the codebase is explicitly called out as a blocker in CONTRIBUTING.md.

Fix: Ensure there is a Behave scenario tagged @tdd_issue @tdd_issue_9250 (with @tdd_expected_fail removed since the fix is now implemented) in the codebase.

3. Wrong Commit Footer Format — Both Commits
Both commits use PR-CLOSED: #9250 in their footers. The required format is: ISSUES CLOSED: #9250. The PR-CLOSED trailer is not recognized by Forgejo for auto-closing issues.

Fix: Amend both commits to use ISSUES CLOSED: #9250.

4. Wrong Branch Name Prefix
Bug fix branches must use the prefix bugfix/mN- per CONTRIBUTING.md Bug Fix Workflow. This PR uses feature/9250-fix-a2a-session-close. For milestone v3.5.0 (M6), the correct prefix would be bugfix/m6-.

5. CONTRIBUTORS.md References Wrong PR and Issue Numbers
The new entry says PR #11053 / issue #9094 but this PR is #11098 and closes issue #9250.

Non-Blocking Observations

A. The early-return guard if not session_id: return inside _cleanup_session_devcontainers is now unreachable dead code since the entry validation ensures session_id is always non-empty before that method is called. Consider removing it in a follow-up or adding a comment noting it is a belt-and-suspenders guard.

B. The new step definition the facade-cov response error should contain session_id is required added in a2a_facade_coverage_steps.py is not referenced by any of the new scenarios. Either use it for a stronger assertion or remove it.

C. The comment in a2a_facade_wiring.feature says PR #9250 but #9250 is the issue number; this PR is #11098.

CI Status

All CI failures trace back to the indentation SyntaxError in facade.py (Blocker #1). Fixing that will restore CI, but the TDD tag requirement and commit footer format must also be corrected.

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

## Code Review — PR #11098 The intent of this fix is correct: moving session_id validation to the top of _handle_session_close() is the right approach. However, this PR has multiple blocking issues that must be resolved before it can be merged. ### BLOCKING Issues **1. Critical Python SyntaxError — root cause of ALL CI failures** Line 321 of src/cleveragents/a2a/facade.py has 2-space indentation on the def _handle_session_close line instead of the required 4 spaces. Python raises IndentationError when importing this module. This single error causes every CI gate to fail: lint, typecheck, unit_tests, integration_tests, e2e_tests, security, and the status-check aggregate gate. Fix: Change the def _handle_session_close line indentation from 2 spaces to 4 spaces. **2. Missing TDD Regression Test** This PR closes issue #9250, labeled Type/Bug. Per the mandatory Bug Fix Workflow in CONTRIBUTING.md, every bug fix must have a corresponding @tdd_issue + @tdd_issue_9250 Behave scenario. No such tag exists anywhere in features/. This is a policy violation: a bug fix PR that closes issue #N where no @tdd_issue_N test exists in the codebase is explicitly called out as a blocker in CONTRIBUTING.md. Fix: Ensure there is a Behave scenario tagged @tdd_issue @tdd_issue_9250 (with @tdd_expected_fail removed since the fix is now implemented) in the codebase. **3. Wrong Commit Footer Format — Both Commits** Both commits use PR-CLOSED: #9250 in their footers. The required format is: ISSUES CLOSED: #9250. The PR-CLOSED trailer is not recognized by Forgejo for auto-closing issues. Fix: Amend both commits to use ISSUES CLOSED: #9250. **4. Wrong Branch Name Prefix** Bug fix branches must use the prefix bugfix/mN- per CONTRIBUTING.md Bug Fix Workflow. This PR uses feature/9250-fix-a2a-session-close. For milestone v3.5.0 (M6), the correct prefix would be bugfix/m6-. **5. CONTRIBUTORS.md References Wrong PR and Issue Numbers** The new entry says PR #11053 / issue #9094 but this PR is #11098 and closes issue #9250. ### Non-Blocking Observations **A.** The early-return guard if not session_id: return inside _cleanup_session_devcontainers is now unreachable dead code since the entry validation ensures session_id is always non-empty before that method is called. Consider removing it in a follow-up or adding a comment noting it is a belt-and-suspenders guard. **B.** The new step definition the facade-cov response error should contain session_id is required added in a2a_facade_coverage_steps.py is not referenced by any of the new scenarios. Either use it for a stronger assertion or remove it. **C.** The comment in a2a_facade_wiring.feature says PR #9250 but #9250 is the issue number; this PR is #11098. ### CI Status All CI failures trace back to the indentation SyntaxError in facade.py (Blocker #1). Fixing that will restore CI, but the TDD tag requirement and commit footer format must also be corrected. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-09 17:48:35 +00:00
Owner
Copy link

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

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 requested changes 2026-05-09 18:46:00 +00:00
HAL9001 left a comment
Copy link

Code Review — PR #11098

The intent of this fix is correct: moving session_id validation to the top of _handle_session_close() is the right approach and the logic change itself is sound. However, this PR has five blocking issues that must be resolved before it can be merged.

BLOCKING Issues

1. Critical Python IndentationError — root cause of ALL CI failures

Line 321 of src/cleveragents/a2a/facade.py has 2-space indentation on def _handle_session_close instead of the required 4 spaces. Python raises IndentationError when importing this module. This single error cascades into every CI gate failing: lint, typecheck, unit_tests, integration_tests, e2e_tests, security, and the status-check aggregate gate. See inline comment on facade.py.

2. Missing mandatory TDD regression test (@tdd_issue_9250)

Issue #9250 is labelled Type/Bug. Per the mandatory Bug Fix Workflow in CONTRIBUTING.md, every bug fix must include a Behave scenario tagged @tdd_issue and @tdd_issue_9250. No such tag exists anywhere in the features/ directory. The new scenarios added in a2a_facade_coverage.feature and a2a_facade_wiring.feature are not tagged. This is a hard policy requirement — the PR cannot be merged without it.

Fix: Add @tdd_issue @tdd_issue_9250 tags to at least one of the new scenarios that directly tests the corrected validation behaviour (e.g. the empty session_id → ValueError path). Remove @tdd_expected_fail since the fix is already implemented.

3. Wrong commit footer format — both commits

Both commits use PR-CLOSED: #9250 in their trailers. The required format per CONTRIBUTING.md is:

ISSUES CLOSED: #9250

The PR-CLOSED trailer is not a recognised Conventional Changelog footer and will not trigger auto-close of the linked issue.

Fix: Amend both commits to use ISSUES CLOSED: #9250.

4. Wrong branch name prefix

Bug fix branches must use the bugfix/mN- prefix per CONTRIBUTING.md Bug Fix Workflow. This branch is named feature/9250-fix-a2a-session-close. For milestone v3.5.0 (M6), the correct prefix would be bugfix/m6-9250-fix-a2a-session-close.

5. CONTRIBUTORS.md entry references wrong PR and issue numbers

The new entry at the bottom of CONTRIBUTORS.md says PR #11053 / issue #9094. This PR is #11098 and it closes issue #9250. The entry must be corrected.

Non-Blocking Observations

A. Dead code in _cleanup_session_devcontainers

The guard if not session_id: return at the top of _cleanup_session_devcontainers() is now unreachable — entry validation in _handle_session_close guarantees session_id is non-empty before that method is ever called. Consider removing it in a follow-up commit or adding a comment noting it is a belt-and-suspenders guard.

B. Unused step definition

The new step the facade-cov response error should contain session_id is required added in a2a_facade_coverage_steps.py is not referenced by any scenario. Either use it for a stronger assertion in one of the new scenarios, or remove it to avoid dead test infrastructure.

C. Feature file comment references wrong PR number

The comment in a2a_facade_wiring.feature line 37 reads PR #9250 — that is the issue number. The PR number is #11098.

CI Status

Failing gates: lint, typecheck, unit_tests, integration_tests, e2e_tests, security, benchmark-regression, status-check. All failures are caused by the IndentationError in facade.py (Blocker #1). Fixing the indentation will restore the import chain, but Blockers #2–#5 must also be addressed before this PR is ready to merge.

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

## Code Review — PR #11098 The intent of this fix is correct: moving `session_id` validation to the top of `_handle_session_close()` is the right approach and the logic change itself is sound. However, this PR has **five blocking issues** that must be resolved before it can be merged. --- ### BLOCKING Issues **1. Critical Python IndentationError — root cause of ALL CI failures** Line 321 of `src/cleveragents/a2a/facade.py` has **2-space indentation** on `def _handle_session_close` instead of the required 4 spaces. Python raises `IndentationError` when importing this module. This single error cascades into every CI gate failing: `lint`, `typecheck`, `unit_tests`, `integration_tests`, `e2e_tests`, `security`, and the `status-check` aggregate gate. See inline comment on `facade.py`. **2. Missing mandatory TDD regression test (`@tdd_issue_9250`)** Issue #9250 is labelled `Type/Bug`. Per the mandatory Bug Fix Workflow in CONTRIBUTING.md, every bug fix **must** include a Behave scenario tagged `@tdd_issue` and `@tdd_issue_9250`. No such tag exists anywhere in the `features/` directory. The new scenarios added in `a2a_facade_coverage.feature` and `a2a_facade_wiring.feature` are not tagged. This is a hard policy requirement — the PR cannot be merged without it. *Fix:* Add `@tdd_issue @tdd_issue_9250` tags to at least one of the new scenarios that directly tests the corrected validation behaviour (e.g. the empty `session_id` → `ValueError` path). Remove `@tdd_expected_fail` since the fix is already implemented. **3. Wrong commit footer format — both commits** Both commits use `PR-CLOSED: #9250` in their trailers. The required format per CONTRIBUTING.md is: ``` ISSUES CLOSED: #9250 ``` The `PR-CLOSED` trailer is not a recognised Conventional Changelog footer and will not trigger auto-close of the linked issue. *Fix:* Amend both commits to use `ISSUES CLOSED: #9250`. **4. Wrong branch name prefix** Bug fix branches must use the `bugfix/mN-` prefix per CONTRIBUTING.md Bug Fix Workflow. This branch is named `feature/9250-fix-a2a-session-close`. For milestone v3.5.0 (M6), the correct prefix would be `bugfix/m6-9250-fix-a2a-session-close`. **5. CONTRIBUTORS.md entry references wrong PR and issue numbers** The new entry at the bottom of `CONTRIBUTORS.md` says `PR #11053 / issue #9094`. This PR is `#11098` and it closes issue `#9250`. The entry must be corrected. --- ### Non-Blocking Observations **A. Dead code in `_cleanup_session_devcontainers`** The guard `if not session_id: return` at the top of `_cleanup_session_devcontainers()` is now unreachable — entry validation in `_handle_session_close` guarantees `session_id` is non-empty before that method is ever called. Consider removing it in a follow-up commit or adding a comment noting it is a belt-and-suspenders guard. **B. Unused step definition** The new step `the facade-cov response error should contain session_id is required` added in `a2a_facade_coverage_steps.py` is not referenced by any scenario. Either use it for a stronger assertion in one of the new scenarios, or remove it to avoid dead test infrastructure. **C. Feature file comment references wrong PR number** The comment in `a2a_facade_wiring.feature` line 37 reads `PR #9250` — that is the issue number. The PR number is `#11098`. --- ### CI Status Failing gates: `lint`, `typecheck`, `unit_tests`, `integration_tests`, `e2e_tests`, `security`, `benchmark-regression`, `status-check`. All failures are caused by the `IndentationError` in `facade.py` (Blocker #1). Fixing the indentation will restore the import chain, but Blockers #2–#5 must also be addressed before this PR is ready to merge. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
CONTRIBUTORS.md
@ -39,3 +39,4 @@ Below are some of the specific details of various contributions.
* HAL 9000 has contributed the error-suppression removal fix (PR #9247 / issue #9060): removed both `try...except Exception:` blocks in `register_registry_agents()` that silently suppressed errors from `actor_registry.list_actors()` and the route bridge refresh, enabling exceptions to propagate per CONTRIBUTING.md fail-fast policy. Added three Behave scenarios verifying RuntimeError, AttributeError, and TypeError propagation.
* HAL 9000 has contributed the Strategize phase full context snapshot fix (issue #9056): added `_build_strategize_context_snapshot()` helper to `PlanLifecycleService`, updated `_try_record_decision()` to accept and forward a `ContextSnapshot` parameter, and added BDD test coverage verifying all four `ContextSnapshot` fields (`hot_context_hash`, `hot_context_ref`, `actor_state_ref`, `relevant_resources`) are populated during the Strategize phase.
* HAL 9000 has contributed the ACMS context path matching fix (PR #10975 / issue #10972): corrects `_path_matches()` and `_matches_pattern()` to properly match absolute fragment paths against relative glob patterns by auto-prefixing with `**/` before calling `PurePath.full_match()`, preventing silent inefficacy of include/exclude filters for absolute paths in fragment metadata.
* HAL 9000 has contributed the a2a session_id validation fix (PR #11053 / issue #9094): moved the session_id validation guard to the top of `_handle_session_close()` in `A2aLocalFacade`, closing the validation bypass path where empty or null session IDs could slip through to devcontainer cleanup when `SessionService` was not wired.
HAL9001 commented 2026-05-09 18:46:00 +00:00
Owner
Copy link

BLOCKER — Wrong PR and Issue Numbers

This entry references PR #11053 / issue #9094, but this PR is #11098 and it closes issue #9250. Please correct the entry to reference the correct numbers.

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

**BLOCKER — Wrong PR and Issue Numbers** This entry references `PR #11053 / issue #9094`, but this PR is **#11098** and it closes issue **#9250**. Please correct the entry to reference the correct numbers. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/a2a_facade_coverage.feature
HAL9001 commented 2026-05-09 18:46:00 +00:00
Owner
Copy link

BLOCKER — Missing @tdd_issue @tdd_issue_9250 tags

Issue #9250 is labelled Type/Bug. CONTRIBUTING.md mandates that every bug fix includes a Behave scenario tagged @tdd_issue and @tdd_issue_9250 (without @tdd_expected_fail since the fix is implemented). None of the new scenarios in this file carry these tags.

Please add @tdd_issue @tdd_issue_9250 to at least one scenario that directly exercises the corrected validation behaviour. Example:

  @tdd_issue @tdd_issue_9250
  Scenario: Session close with empty session_id and no service raises ValueError error

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

**BLOCKER — Missing @tdd_issue @tdd_issue_9250 tags** Issue #9250 is labelled Type/Bug. CONTRIBUTING.md mandates that every bug fix includes a Behave scenario tagged @tdd_issue and @tdd_issue_9250 (without @tdd_expected_fail since the fix is implemented). None of the new scenarios in this file carry these tags. Please add @tdd_issue @tdd_issue_9250 to at least one scenario that directly exercises the corrected validation behaviour. Example: ```gherkin @tdd_issue @tdd_issue_9250 Scenario: Session close with empty session_id and no service raises ValueError error ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/a2a_facade_coverage_steps.py
HAL9001 commented 2026-05-09 18:46:00 +00:00
Owner
Copy link

Suggestion — Unused step definition

This new step the facade-cov response error should contain session_id is required is not referenced by any scenario in the feature files. Either wire it up to one of the new @tdd_issue_9250 scenarios for a stronger assertion, or remove it to avoid dead test code.

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

**Suggestion — Unused step definition** This new step `the facade-cov response error should contain session_id is required` is not referenced by any scenario in the feature files. Either wire it up to one of the new @tdd_issue_9250 scenarios for a stronger assertion, or remove it to avoid dead test code. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
src/cleveragents/a2a/facade.py
HAL9001 commented 2026-05-09 18:46:00 +00:00
Owner
Copy link

BLOCKER — Python IndentationError

This def statement has 2-space indentation instead of the required 4 spaces for a class method. Python will raise IndentationError when importing this module, which is the root cause of every CI failure on this PR.

CURRENT (wrong — 2 spaces):

  def _handle_session_close(self, params: dict[str, Any]) -> dict[str, Any]:

CORRECT (4 spaces):

    def _handle_session_close(self, params: dict[str, Any]) -> dict[str, Any]:

This is a copy-paste or editor artefact. Fixing this single character will restore all CI gates.

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

**BLOCKER — Python IndentationError** This `def` statement has **2-space indentation** instead of the required 4 spaces for a class method. Python will raise `IndentationError` when importing this module, which is the root cause of every CI failure on this PR. CURRENT (wrong — 2 spaces): ```python def _handle_session_close(self, params: dict[str, Any]) -> dict[str, Any]: ``` CORRECT (4 spaces): ```python def _handle_session_close(self, params: dict[str, Any]) -> dict[str, Any]: ``` This is a copy-paste or editor artefact. Fixing this single character will restore all CI gates. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-09 18:46:06 +00:00
Owner
Copy link

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

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 51s
Details
CI / lint (pull_request) Failing after 1m9s
Required
Details
CI / benchmark-regression (pull_request) Failing after 1m16s
Details
CI / build (pull_request) Successful in 1m4s
Required
Details
CI / integration_tests (pull_request) Failing after 1m23s
Required
Details
CI / e2e_tests (pull_request) Failing after 1m24s
Details
CI / quality (pull_request) Successful in 1m28s
Required
Details
CI / unit_tests (pull_request) Failing after 1m37s
Required
Details
CI / typecheck (pull_request) Failing after 1m39s
Required
Details
CI / security (pull_request) Failing after 2m4s
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / push-validation (pull_request) Successful in 22s
Details
CI / status-check (pull_request) Failing after 3s
Details
This pull request has changes conflicting with the target branch.
  • CHANGELOG.md
  • CONTRIBUTORS.md
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 feature/9250-fix-a2a-session-close:feature/9250-fix-a2a-session-close
git switch feature/9250-fix-a2a-session-close
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!11098
No description provided.