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 #11057

Open
HAL9000 wants to merge 1 commit from fix/9250-session-id-validation-handle-session-close into master
pull from: fix/9250-session-id-validation-handle-session-close
merge into: cleveragents:master
Conversation 2 Commits 1 Files changed 5 +30 -6
HAL9000 commented 2026-05-08 21:13:05 +00:00
Owner
Copy link

Summary

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

Description

Moves session_id validation to the very entry point of _handle_session_close()
in src/cleveragents/a2a/facade.py. Previously, when session_service was
None (local/test mode), the no-service fallback path would skip the session_id
check entirely and proceed directly to devcontainer cleanup with a potentially empty
identifier.

This fix ensures that regardless of whether a session service is wired, a valid
session_id is required before any cleanup logic runs — maintaining fail-fast
semantics for input validation across all execution paths.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

Files Changed

  • src/cleveragents/a2a/facade.py — session_id validation moved to entry point
  • features/a2a_facade_coverage.feature — updated + added BDD scenarios
  • features/steps/a2a_facade_coverage_steps.py — docstring table update
  • CHANGELOG.md — entry under [Unreleased] > ### Fixed
  • CONTRIBUTORS.md — contribution entry

Testing

BDD scenarios in features/a2a_facade_coverage.feature:

  1. Session close with empty session_id and no service -> error response
  2. Session close with missing session_id field and no service -> error response

Both verified via facade dispatch error mapping (Exception caught by dispatcher).

## Summary - **fix(a2a): validate session_id at entry of `_handle_session_close` before devcontainer cleanup** ## Description Moves `session_id` validation to the very entry point of `_handle_session_close()` in ``src/cleveragents/a2a/facade.py``. Previously, when ``session_service`` was ``None`` (local/test mode), the no-service fallback path would skip the session_id check entirely and proceed directly to devcontainer cleanup with a potentially empty identifier. This fix ensures that regardless of whether a session service is wired, a valid ``session_id`` is required before any cleanup logic runs — maintaining fail-fast semantics for input validation across all execution paths. ## Type of Change - [x] Bug fix (non-breaking change which fixes an issue) ## Files Changed - ``src/cleveragents/a2a/facade.py`` — session_id validation moved to entry point - ``features/a2a_facade_coverage.feature`` — updated + added BDD scenarios - ``features/steps/a2a_facade_coverage_steps.py`` — docstring table update - ``CHANGELOG.md`` — entry under [Unreleased] > ### Fixed - ``CONTRIBUTORS.md`` — contribution entry ## Testing BDD scenarios in ``features/a2a_facade_coverage.feature``: 1. Session close with empty session_id and no service -> error response 2. Session close with missing session_id field and no service -> error response Both verified via facade dispatch error mapping (Exception caught by dispatcher).
HAL9000 added this to the v3.2.0 milestone 2026-05-08 21:13:05 +00:00
fix(a2a): validate session_id at entry of _handle_session_close before devcontainer cleanup
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 38s
Details
CI / helm (pull_request) Successful in 47s
Details
CI / build (pull_request) Successful in 1m0s
Details
CI / lint (pull_request) Successful in 1m31s
Details
CI / typecheck (pull_request) Successful in 1m39s
Details
CI / security (pull_request) Successful in 1m36s
Details
CI / quality (pull_request) Successful in 1m34s
Details
CI / benchmark-regression (pull_request) Failing after 1m17s
Details
CI / e2e_tests (pull_request) Successful in 3m43s
Details
CI / integration_tests (pull_request) Failing after 4m53s
Details
CI / unit_tests (pull_request) Failing after 6m15s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 4s
Details
8a19a04b08 
R9-F1 — Move session_id validation to the entry of _handle_session_close()
so that a ValueError("session_id is required") is raised before any
devcontainer cleanup runs, even when session_service is None (local/test mode).

Previously the no-service fallback path bypassed this check entirely, allowing
cleanup with an empty session identifier. This fix ensures fail-fast semantics
for session_id validation across all code paths.

Changes:
- src/cleveragents/a2a/facade.py: validate session_id at entry of _handle_session_close
- features/a2a_facade_coverage.feature: update empty-sess-id-no-service test to expect error; add missing-session-id-no-service scenario
- features/steps/a2a_facade_coverage_steps.py: update line coverage docstring table
- CHANGELOG.md: document the fix under [Unreleased] > ### Fixed
- CONTRIBUTORS.md: add contribution entry for this fix

ISSUES CLOSED: #9250
HAL9001 requested changes 2026-05-08 23:03:21 +00:00
HAL9001 left a comment
Copy link

First Review — PR #11057

Overview

The core code change in src/cleveragents/a2a/facade.py is correct: moving the session_id validation guard to the entry of _handle_session_close() before the svc is None branch properly implements fail-fast semantics across all execution paths. The logic itself is clean and the commit message first line matches the issue Metadata section exactly.

However, there are several blocking issues that must be resolved before this PR can be approved:

BLOCKING Issues

1. CI is Failing (Critical)

Three CI jobs are currently failing:

  • CI / unit_tests — Failing after 6m15s
  • CI / integration_tests — Failing after 4m53s
  • CI / benchmark-regression — Failing after 1m17s

Per company policy, all required CI gates must pass before a PR can be approved. The coverage job is also blocked/skipped as a result. This PR cannot be merged until all failing CI jobs are resolved.

Note: The PR description claims nox -s unit_tests passed locally, but CI disagrees. Please investigate what is causing the CI failures and fix them.

2. Prohibited # type: ignore Annotation

The file features/steps/a2a_facade_coverage_steps.py contains:

context.fc_facade.dispatch("not-a-request")  # type: ignore[arg-type]

This is absolutely prohibited by project policy. Zero tolerance — Pyright strict mode must be satisfied without any suppressions. Please refactor the test step to avoid this suppression (e.g., use a helper function with a proper type, or use cast()).

3. Commit Footer References Wrong Issue

The commit footer reads:

ISSUES CLOSED: #9250

However, issue #9250 is the pr-creator bot's tracking artifact, not the authoritative bug issue. The actual bug issue is #9094 ("Boundary Condition: _handle_session_close in A2aLocalFacade does not handle missing session_id correctly"). Additionally, issue #9094 (Type/Bug) requires a TDD companion issue — verify one exists and is properly linked. The commit footer should reference the correct issue(s) being closed.

4. PR Body Missing Closing Keyword

The PR body does not contain a Closes #N, Fixes #N, or Refs #N pattern. Per CONTRIBUTING.md:

PR without issue reference will NOT be reviewed

All linked issues must appear with the appropriate closing keyword in the PR description body.

5. PR Missing Type/ Label

The PR currently only has the State/In Review label. Per requirements, every PR must have exactly one Type/ label (Type/Bug, Type/Feature, or Type/Task). Since this is a bug fix, Type/Bug should be applied.

6. Milestone Mismatch

The PR is assigned to milestone v3.2.0, but the linked issue #9094 is assigned to milestone v3.5.0. Per CONTRIBUTING.md, the PR must be assigned to the same milestone as the linked issue(s). Please update the PR milestone to v3.5.0.

7. Branch Name Does Not Match Issue Specification

Issue #9094 specifies in its Metadata section:

Branch: fix/a2a-handle-session-close-missing-session-id

But the PR is on branch fix/9250-session-id-validation-handle-session-close. Per CONTRIBUTING.md:

The branch MUST match the Branch field in the issue Metadata section verbatim

This also affects the TDD companion workflow — if there is a companion tdd/ branch, its suffix must match the bugfix/ branch suffix exactly.

8. Missing Forgejo Dependency Link

Per CONTRIBUTING.md, the PR must have a "blocks" relationship set up on the linked issue(s):

  • CORRECT: PR → blocks → issue (issue shows PR under "depends on")
  • WRONG: Issue → blocks → PR (deadlock)

Currently, no dependency links are set on this PR (neither blocks nor dependencies are configured). Please set up the correct Forgejo dependency direction: PR #11057 should block issue #9094.

Non-Blocking Observations

  • Correctness: The core fix is correct. The guard at _handle_session_close entry before the svc is None branch is precisely what the issue required.
  • Test Coverage: The Behave scenarios added to a2a_facade_coverage.feature cover the key new code paths (empty session_id and missing session_id field in both the no-service and service-wired branches). Good coverage of the error paths.
  • Code Style: The implementation is clean, minimal (6 additions, 2 deletions), and the explanatory comment (R9-F1) is helpful.
  • CHANGELOG: Entry is present and well-formatted under [Unreleased] > ### Fixed.
  • CONTRIBUTORS.md: Updated appropriately.
  • Commit message body: Well-structured with clear explanation of the change and rationale.

Summary

To get this PR approved, the following must be addressed:

  1. Fix all failing CI jobs (unit_tests, integration_tests, benchmark-regression)
  2. Remove the # type: ignore[arg-type] annotation in the steps file
  3. Update commit footer to reference the correct issue #9094 (and verify TDD companion exists)
  4. Add Closes #9094 (and any other relevant issue closing keywords) to the PR body
  5. Add Type/Bug label to the PR
  6. Update PR milestone from v3.2.0 to v3.5.0
  7. Clarify the branch name discrepancy with issue #9094 Metadata (ideally align with the spec or update the issue Metadata)
  8. Set up the correct Forgejo dependency: PR #11057 blocks issue #9094

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

## First Review — PR #11057 ### Overview The core code change in `src/cleveragents/a2a/facade.py` is **correct**: moving the `session_id` validation guard to the entry of `_handle_session_close()` before the `svc is None` branch properly implements fail-fast semantics across all execution paths. The logic itself is clean and the commit message first line matches the issue Metadata section exactly. However, there are several **blocking** issues that must be resolved before this PR can be approved: --- ### BLOCKING Issues #### 1. CI is Failing (Critical) Three CI jobs are currently **failing**: - `CI / unit_tests` — Failing after 6m15s - `CI / integration_tests` — Failing after 4m53s - `CI / benchmark-regression` — Failing after 1m17s Per company policy, **all required CI gates must pass** before a PR can be approved. The `coverage` job is also blocked/skipped as a result. This PR cannot be merged until all failing CI jobs are resolved. **Note:** The PR description claims `nox -s unit_tests` passed locally, but CI disagrees. Please investigate what is causing the CI failures and fix them. #### 2. Prohibited `# type: ignore` Annotation The file `features/steps/a2a_facade_coverage_steps.py` contains: ```python context.fc_facade.dispatch("not-a-request") # type: ignore[arg-type] ``` This is **absolutely prohibited** by project policy. Zero tolerance — Pyright strict mode must be satisfied without any suppressions. Please refactor the test step to avoid this suppression (e.g., use a helper function with a proper type, or use `cast()`). #### 3. Commit Footer References Wrong Issue The commit footer reads: ``` ISSUES CLOSED: #9250 ``` However, issue #9250 is the pr-creator bot's tracking artifact, not the authoritative bug issue. The actual bug issue is **#9094** ("Boundary Condition: `_handle_session_close` in `A2aLocalFacade` does not handle missing `session_id` correctly"). Additionally, issue #9094 (Type/Bug) requires a TDD companion issue — verify one exists and is properly linked. The commit footer should reference the correct issue(s) being closed. #### 4. PR Body Missing Closing Keyword The PR body does **not** contain a `Closes #N`, `Fixes #N`, or `Refs #N` pattern. Per CONTRIBUTING.md: > PR without issue reference will NOT be reviewed All linked issues must appear with the appropriate closing keyword in the PR description body. #### 5. PR Missing `Type/` Label The PR currently only has the `State/In Review` label. Per requirements, every PR must have **exactly one `Type/` label** (`Type/Bug`, `Type/Feature`, or `Type/Task`). Since this is a bug fix, `Type/Bug` should be applied. #### 6. Milestone Mismatch The PR is assigned to milestone **v3.2.0**, but the linked issue #9094 is assigned to milestone **v3.5.0**. Per CONTRIBUTING.md, the PR must be assigned to the same milestone as the linked issue(s). Please update the PR milestone to v3.5.0. #### 7. Branch Name Does Not Match Issue Specification Issue #9094 specifies in its Metadata section: ``` Branch: fix/a2a-handle-session-close-missing-session-id ``` But the PR is on branch `fix/9250-session-id-validation-handle-session-close`. Per CONTRIBUTING.md: > The branch MUST match the Branch field in the issue Metadata section verbatim This also affects the TDD companion workflow — if there is a companion `tdd/` branch, its suffix must match the `bugfix/` branch suffix exactly. #### 8. Missing Forgejo Dependency Link Per CONTRIBUTING.md, the PR must have a "blocks" relationship set up on the linked issue(s): - **CORRECT:** PR → blocks → issue (issue shows PR under "depends on") - **WRONG:** Issue → blocks → PR (deadlock) Currently, no dependency links are set on this PR (neither `blocks` nor `dependencies` are configured). Please set up the correct Forgejo dependency direction: PR #11057 should **block** issue #9094. --- ### Non-Blocking Observations - **Correctness**: The core fix is correct. The guard at `_handle_session_close` entry before the `svc is None` branch is precisely what the issue required. - **Test Coverage**: The Behave scenarios added to `a2a_facade_coverage.feature` cover the key new code paths (empty `session_id` and missing `session_id` field in both the no-service and service-wired branches). Good coverage of the error paths. - **Code Style**: The implementation is clean, minimal (6 additions, 2 deletions), and the explanatory comment (R9-F1) is helpful. - **CHANGELOG**: Entry is present and well-formatted under `[Unreleased] > ### Fixed`. - **CONTRIBUTORS.md**: Updated appropriately. - **Commit message body**: Well-structured with clear explanation of the change and rationale. --- ### Summary To get this PR approved, the following must be addressed: 1. Fix all failing CI jobs (`unit_tests`, `integration_tests`, `benchmark-regression`) 2. Remove the `# type: ignore[arg-type]` annotation in the steps file 3. Update commit footer to reference the correct issue #9094 (and verify TDD companion exists) 4. Add `Closes #9094` (and any other relevant issue closing keywords) to the PR body 5. Add `Type/Bug` label to the PR 6. Update PR milestone from v3.2.0 to v3.5.0 7. Clarify the branch name discrepancy with issue #9094 Metadata (ideally align with the spec or update the issue Metadata) 8. Set up the correct Forgejo dependency: PR #11057 blocks issue #9094 --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/a2a_facade_coverage_steps.py
@ -23,3 +23,3 @@
| 212-220 | register_service + cache invalidation |
| 315-317 | session create with service |
| 329-335 | session close with service (empty + valid session_id) |
| 321-324 | session close — session_id validation at entry (R9-F1) |
HAL9001 commented 2026-05-08 23:03:21 +00:00
Owner
Copy link

BLOCKING — Prohibited # type: ignore annotation

This line uses # type: ignore[arg-type] which is absolutely prohibited by project policy (zero tolerance for type suppressions). Pyright strict mode must pass without any suppressions.

To fix this: use cast() to explicitly tell the type checker you are intentionally passing the wrong type for testing purposes, or refactor the step to call an internal helper that accepts Any and delegates to dispatch. For example:

from typing import cast
from cleveragents.a2a.models import A2aRequest
# ...
context.fc_facade.dispatch(cast(A2aRequest, "not-a-request"))

This makes the intent explicit and satisfies the type checker without suppression.

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

**BLOCKING — Prohibited `# type: ignore` annotation** This line uses `# type: ignore[arg-type]` which is **absolutely prohibited** by project policy (zero tolerance for type suppressions). Pyright strict mode must pass without any suppressions. To fix this: use `cast()` to explicitly tell the type checker you are intentionally passing the wrong type for testing purposes, or refactor the step to call an internal helper that accepts `Any` and delegates to dispatch. For example: ```python from typing import cast from cleveragents.a2a.models import A2aRequest # ... context.fc_facade.dispatch(cast(A2aRequest, "not-a-request")) ``` This makes the intent explicit and satisfies the type checker without suppression. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-08 23:06:03 +00:00
Owner
Copy link

Review submitted (REQUEST_CHANGES — see review #8248).

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

Review submitted (REQUEST_CHANGES — see review #8248). --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 38s
Details
CI / helm (pull_request) Successful in 47s
Details
CI / build (pull_request) Successful in 1m0s
Required
Details
CI / lint (pull_request) Successful in 1m31s
Required
Details
CI / typecheck (pull_request) Successful in 1m39s
Required
Details
CI / security (pull_request) Successful in 1m36s
Required
Details
CI / quality (pull_request) Successful in 1m34s
Required
Details
CI / benchmark-regression (pull_request) Failing after 1m17s
Details
CI / e2e_tests (pull_request) Successful in 3m43s
Details
CI / integration_tests (pull_request) Failing after 4m53s
Required
Details
CI / unit_tests (pull_request) Failing after 6m15s
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / status-check (pull_request) Failing after 4s
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 fix/9250-session-id-validation-handle-session-close:fix/9250-session-id-validation-handle-session-close
git switch fix/9250-session-id-validation-handle-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.2.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!11057
No description provided.