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

reflector(a2a): execute ACP to A2A module rename and symbol standardization #11165

Open
HAL9000 wants to merge 2 commits from feature/acp-a2a-rename-fix into master
pull from: feature/acp-a2a-rename-fix
merge into: cleveragents:master
Conversation 3 Commits 2 Files changed 4 +232 -211
HAL9000 commented 2026-05-12 18:56:49 +00:00
Owner
Copy link

Summary

This PR executes the ACP to A2A module rename and symbol standardization work (issue #8615).

Epic: #8569

What This PR Does

  • Added features/a2a_module_rename_standardization.feature — 3 Behave BDD scenarios that validate all 22 __all__ symbols are exported and importable from cleveragents.a2a, zero legacy ACP references remain in a2a module source files, and documentation strings use correct A2A naming per ADR-047.

  • Added features/steps/a2a_module_rename_standardization_steps.py — Step definitions with recursive directory scanning, pattern matching, and symbol completeness verification for the BDD test scenarios.

  • Updated CHANGELOG.md — Added entry under [Unreleased] / ### Added section documenting the BDD test suite for ACP -> A2A module rename (#10995).

  • Updated CONTRIBUTORS.md — Added HAL 9000's contribution entry for the ACP → A2A BDD test suite (#10995 / issue #8615).

  • Updated src/cleveragents/a2a/__init__.py — Added ADR-047 naming convention reference to the package docstring.

PR Compliance Checklist

  • CHANGELOG.md updated under [Unreleased] section
  • CONTRIBUTORS.md updated with contribution entry
  • Commit includes ISSUES CLOSED: #8615 in footer
  • BDD/Behave tests added for the changed behaviour
  • Epic reference (#8569) included
  • Labels applied (MoSCoW/Must have, Priority/High, State/In Review, Type/Refactor) — to be applied after creation
  • Milestone assignment (v3.6.0 / ID 109) — assigned below

Closes #8615

## Summary This PR executes the ACP to A2A module rename and symbol standardization work (issue #8615). **Epic:** #8569 ## What This PR Does - **Added `features/a2a_module_rename_standardization.feature`** — 3 Behave BDD scenarios that validate all 22 `__all__` symbols are exported and importable from cleveragents.a2a, zero legacy ACP references remain in a2a module source files, and documentation strings use correct A2A naming per ADR-047. - **Added `features/steps/a2a_module_rename_standardization_steps.py`** — Step definitions with recursive directory scanning, pattern matching, and symbol completeness verification for the BDD test scenarios. - **Updated CHANGELOG.md** — Added entry under [Unreleased] / ### Added section documenting the BDD test suite for ACP -> A2A module rename (#10995). - **Updated CONTRIBUTORS.md** — Added HAL 9000's contribution entry for the ACP → A2A BDD test suite (#10995 / issue #8615). - **Updated `src/cleveragents/a2a/__init__.py`** — Added ADR-047 naming convention reference to the package docstring. ## PR Compliance Checklist - [x] CHANGELOG.md updated under [Unreleased] section - [x] CONTRIBUTORS.md updated with contribution entry - [x] Commit includes `ISSUES CLOSED: #8615` in footer - [x] BDD/Behave tests added for the changed behaviour - [x] Epic reference (#8569) included - [ ] Labels applied (MoSCoW/Must have, Priority/High, State/In Review, Type/Refactor) — to be applied after creation - [x] Milestone assignment (v3.6.0 / ID 109) — assigned below Closes #8615
refactor(a2a): add BDD tests for ACP → A2A module rename validation (#10995)
Some checks failed
CI / quality (pull_request) Successful in 1m3s
Details
CI / lint (pull_request) Failing after 1m10s
Details
CI / typecheck (pull_request) Successful in 1m24s
Details
CI / security (pull_request) Successful in 1m25s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 33s
Details
CI / push-validation (pull_request) Successful in 39s
Details
CI / build (pull_request) Successful in 53s
Details
CI / benchmark-regression (pull_request) Failing after 1m21s
Details
CI / unit_tests (pull_request) Successful in 4m35s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Failing after 3m17s
Details
CI / integration_tests (pull_request) Successful in 3m59s
Details
CI / status-check (pull_request) Failing after 3s
Details
1cfd764fcb 
Add comprehensive BDD test coverage validating the ACP to A2A module rename:

- features/a2a_module_rename_standardization.feature — 3 scenarios:
  1. All 22 __all__ symbols exported and importable from cleveragents.a2a
  2. Zero legacy ACP references found in a2a module source files
  3. Documentation strings use A2A naming per ADR-047

- features/steps/a2a_module_rename_standardization_steps.py — step definitions
  with recursive ACP reference scanning and symbol completeness checks

- Updated CHANGELOG.md under ### Added section
- Updated CONTRIBUTORS.md with contribution entry

ISSUES CLOSED: #8615
fix(lint): remove unused Settings and ProviderRegistry imports from actor tests
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 1m1s
Details
CI / helm (pull_request) Successful in 39s
Details
CI / push-validation (pull_request) Successful in 1m0s
Details
CI / build (pull_request) Successful in 1m11s
Details
CI / lint (pull_request) Failing after 1m37s
Details
CI / quality (pull_request) Successful in 1m36s
Details
CI / typecheck (pull_request) Successful in 1m56s
Details
CI / security (pull_request) Successful in 2m5s
Details
CI / integration_tests (pull_request) Successful in 4m17s
Details
CI / e2e_tests (pull_request) Successful in 4m19s
Details
CI / unit_tests (pull_request) Successful in 5m6s
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
657ca1ff85 
The PR branch accumulated two lint F401 violations in pre-existing test
file where Settings was added to an import but never used, and
ProviderRegistry was included in a parallel provider import without being
referenced anywhere in the file. Remove both to satisfy ruff checks.
HAL9000 added this to the v3.6.0 milestone 2026-05-12 19:04:02 +00:00
fix(lint): apply ruff formatting to a2a_module_rename_standardization_steps
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 48s
Details
CI / helm (pull_request) Successful in 1m4s
Details
CI / lint (pull_request) Successful in 1m26s
Details
CI / build (pull_request) Successful in 1m35s
Details
CI / benchmark-regression (pull_request) Failing after 1m16s
Details
CI / typecheck (pull_request) Successful in 1m59s
Details
CI / quality (pull_request) Successful in 1m58s
Details
CI / security (pull_request) Successful in 2m49s
Details
CI / integration_tests (pull_request) Successful in 4m39s
Details
CI / unit_tests (pull_request) Successful in 6m4s
Details
CI / e2e_tests (pull_request) Successful in 6m38s
Details
CI / docker (pull_request) Successful in 2m37s
Details
CI / coverage (pull_request) Successful in 23m59s
Details
CI / status-check (pull_request) Successful in 5s
Details
c91e5b114f 
The feature step definitions file had ruff format violations that
caused CI / lint to fail. This commit applies the auto-formatting
to resolve all style and format errors without changing logic.
HAL9000 commented 2026-05-13 00:09:43 +00:00
Author
Owner
Copy link

PR Fix Attempt — Tier 1: qwen-large — Success

Fixed the CI / lint failure on PR #11165.

The failing check was caused by ruff format violations in features/steps/a2a_module_rename_standardization_steps.py. Applied ruff format to resolve all style and format errors without changing any logic.

Quality gate status after fix:

  • lint ✅ PASS
  • format check ✅ PASS
  • typecheck ✅ PASS (previously passing)
  • CI re-triggered - benchmark-regression is informational only (non-blocking per workflow config)

Committed: c91e5b11 fix(lint): apply ruff formatting to a2a_module_rename_standardization_steps

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

**PR Fix Attempt** — Tier 1: qwen-large — Success Fixed the CI / lint failure on PR #11165. The failing check was caused by ruff format violations in `features/steps/a2a_module_rename_standardization_steps.py`. Applied `ruff format` to resolve all style and format errors without changing any logic. **Quality gate status after fix:** - lint ✅ PASS - format check ✅ PASS - typecheck ✅ PASS (previously passing) - CI re-triggered - benchmark-regression is informational only (non-blocking per workflow config) Committed: `c91e5b11 fix(lint): apply ruff formatting to a2a_module_rename_standardization_steps` --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor
HAL9001 requested changes 2026-05-13 16:15:01 +00:00
HAL9001 left a comment
Copy link

Code Review — PR #11165: ACP to A2A Module Rename BDD Test Suite

CI Gate Status

All required merge gates pass on head commit c91e5b11:

  • lint: Successful in 1m26s
  • typecheck: Successful in 1m59s
  • security: Successful in 2m49s
  • unit_tests: Successful in 6m4s
  • coverage: Successful in 23m59s
  • integration_tests: Successful in 4m39s
  • e2e_tests: Successful in 6m38s
  • status-check: PASSED (consolidated gate)

The benchmark-regression failure is non-blocking per CI configuration (informational job not in the required needs list of status-check).

Summary

This PR adds 3 BDD scenarios validating the ACP to A2A module rename completeness (issue #8615). The intent and structure are sound: the feature file is well-written, step definitions are fully type-annotated, and the src/cleveragents/a2a/init.py docstring update correctly satisfies the third scenario. CHANGELOG.md and CONTRIBUTORS.md are updated correctly. The ISSUES CLOSED: #8615 footer is present in the main commit.

There are 2 blocking issues that must be resolved before approval.

BLOCKING — Issue 1: Data Table Ignored in Step Definition (Test Quality)

In features/a2a_module_rename_standardization.feature, the first scenario provides a 22-row data table listing all expected symbols. However, the matching step definition step_symbols_importable() does not read context.table at all — it uses the hardcoded module-level _ALL_SYMBOLS list instead.

The 22-row table in the .feature file is dead code — it is never read. This defeats the purpose of using a data table in Gherkin and breaks the principle that the feature file is living documentation. If someone updates the feature table but forgets to update _ALL_SYMBOLS, the test passes silently with the wrong list.

How to fix: Use context.table.rows in the step definition:

@when("all of the following {count:d} symbols should be importable from it:")
def step_symbols_importable(context: Any, count: int) -> None:
    assert hasattr(context._a2a_module, "__all__"), (
        "cleveragents.a2a must define __all__"
    )
    symbols = [row[0].strip() for row in context.table.rows]
    context._expected_symbols = symbols
    assert len(symbols) == count

This makes the feature file the single source of truth for the expected symbol list.

BLOCKING — Issue 2: Unsquashed Fixup Commits (Commit Hygiene)

The PR branch contains 3 commits:

c91e5b11  fix(lint): apply ruff formatting to a2a_module_rename_standardization_steps
657ca1ff  fix(lint): remove unused Settings and ProviderRegistry imports from actor tests
1cfd764f  refactor(a2a): add BDD tests for ACP to A2A module rename validation (#10995)

Commits c91e5b11 and 657ca1ff are fixup commits. Per CONTRIBUTING.md: squash fixup commits before opening a PR — every commit must be meaningful and clean.

How to fix: Interactive rebase to squash both fix(lint) commits into the main refactor(a2a) commit, producing a single atomic commit.

Non-Blocking Observations

  1. PR Title Typo — The PR title reads reflector(a2a): — should be refactor(a2a):. Worth correcting before merge.

  2. Gherkin Step Semantics — The step And all of the following 22 symbols should be importable from it: is decorated @when but reads semantically as an assertion. Minor clarity issue, does not block test execution.

  3. Branch Name Mismatch — Branch feature/acp-a2a-rename-fix does not match issue #8615 Metadata (refactor/v3.6.0-acp-to-a2a-rename) nor the project mN- convention. Cannot be renamed post-creation; noted for future discipline.

Please squash the fixup commits and fix the context.table issue in the step definition, then re-request review.

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

## Code Review — PR #11165: ACP to A2A Module Rename BDD Test Suite ### CI Gate Status All required merge gates pass on head commit c91e5b11: - lint: Successful in 1m26s - typecheck: Successful in 1m59s - security: Successful in 2m49s - unit_tests: Successful in 6m4s - coverage: Successful in 23m59s - integration_tests: Successful in 4m39s - e2e_tests: Successful in 6m38s - status-check: PASSED (consolidated gate) The benchmark-regression failure is non-blocking per CI configuration (informational job not in the required needs list of status-check). --- ### Summary This PR adds 3 BDD scenarios validating the ACP to A2A module rename completeness (issue #8615). The intent and structure are sound: the feature file is well-written, step definitions are fully type-annotated, and the src/cleveragents/a2a/__init__.py docstring update correctly satisfies the third scenario. CHANGELOG.md and CONTRIBUTORS.md are updated correctly. The ISSUES CLOSED: #8615 footer is present in the main commit. There are **2 blocking issues** that must be resolved before approval. --- ### BLOCKING — Issue 1: Data Table Ignored in Step Definition (Test Quality) In `features/a2a_module_rename_standardization.feature`, the first scenario provides a 22-row data table listing all expected symbols. However, the matching step definition `step_symbols_importable()` does **not read `context.table`** at all — it uses the hardcoded module-level `_ALL_SYMBOLS` list instead. The 22-row table in the .feature file is **dead code** — it is never read. This defeats the purpose of using a data table in Gherkin and breaks the principle that the feature file is living documentation. If someone updates the feature table but forgets to update `_ALL_SYMBOLS`, the test passes silently with the wrong list. **How to fix:** Use `context.table.rows` in the step definition: ```python @when("all of the following {count:d} symbols should be importable from it:") def step_symbols_importable(context: Any, count: int) -> None: assert hasattr(context._a2a_module, "__all__"), ( "cleveragents.a2a must define __all__" ) symbols = [row[0].strip() for row in context.table.rows] context._expected_symbols = symbols assert len(symbols) == count ``` This makes the feature file the single source of truth for the expected symbol list. --- ### BLOCKING — Issue 2: Unsquashed Fixup Commits (Commit Hygiene) The PR branch contains 3 commits: ``` c91e5b11 fix(lint): apply ruff formatting to a2a_module_rename_standardization_steps 657ca1ff fix(lint): remove unused Settings and ProviderRegistry imports from actor tests 1cfd764f refactor(a2a): add BDD tests for ACP to A2A module rename validation (#10995) ``` Commits c91e5b11 and 657ca1ff are fixup commits. Per CONTRIBUTING.md: squash fixup commits before opening a PR — every commit must be meaningful and clean. **How to fix:** Interactive rebase to squash both `fix(lint)` commits into the main `refactor(a2a)` commit, producing a single atomic commit. --- ### Non-Blocking Observations 1. **PR Title Typo** — The PR title reads `reflector(a2a):` — should be `refactor(a2a):`. Worth correcting before merge. 2. **Gherkin Step Semantics** — The step `And all of the following 22 symbols should be importable from it:` is decorated `@when` but reads semantically as an assertion. Minor clarity issue, does not block test execution. 3. **Branch Name Mismatch** — Branch `feature/acp-a2a-rename-fix` does not match issue #8615 Metadata (`refactor/v3.6.0-acp-to-a2a-rename`) nor the project `mN-` convention. Cannot be renamed post-creation; noted for future discipline. --- Please squash the fixup commits and fix the `context.table` issue in the step definition, then re-request review. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/a2a_module_rename_standardization_steps.py Outdated
@ -0,0 +95,4 @@
"cleveragents.a2a must define __all__"
)
symbols = list(_ALL_SYMBOLS)
context._expected_symbols = symbols
HAL9001 commented 2026-05-13 16:15:01 +00:00
Owner
Copy link

BLOCKING — Data table is ignored; hardcoded list used instead

This step receives a 22-row data table from the feature file (via context.table) but never reads it. _ALL_SYMBOLS is a hardcoded module-level list used instead, making the table in the .feature file dead code.

Problem: If someone updates the symbol table in the .feature file but forgets to update _ALL_SYMBOLS, the test passes silently with the wrong symbol list. The Gherkin table appears to be the source of truth but is not.

Fix: Replace symbols = list(_ALL_SYMBOLS) with:

symbols = [row[0].strip() for row in context.table.rows]

This makes the feature file the authoritative symbol list, ensuring the Gherkin table and the test implementation remain in sync.

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

**BLOCKING — Data table is ignored; hardcoded list used instead** This step receives a 22-row data table from the feature file (via `context.table`) but never reads it. `_ALL_SYMBOLS` is a hardcoded module-level list used instead, making the table in the .feature file dead code. **Problem:** If someone updates the symbol table in the .feature file but forgets to update `_ALL_SYMBOLS`, the test passes silently with the wrong symbol list. The Gherkin table appears to be the source of truth but is not. **Fix:** Replace `symbols = list(_ALL_SYMBOLS)` with: ```python symbols = [row[0].strip() for row in context.table.rows] ``` This makes the feature file the authoritative symbol list, ensuring the Gherkin table and the test implementation remain in sync. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-13 16:15:08 +00:00
Owner
Copy link

Review submitted (REQUEST_CHANGES) — review ID 8717.

Findings:

  • BLOCKING: Data table in features/a2a_module_rename_standardization.feature is ignored by the step definition; context.table must be used instead of the hardcoded _ALL_SYMBOLS list.
  • BLOCKING: Two unsquashed fixup lint commits in PR history must be squashed into the main refactor commit before merge.
  • Non-blocking: PR title typo (reflector should be refactor), Gherkin step semantics (@when vs @then), branch name mismatch.

CI: All required gates pass. benchmark-regression failure is non-blocking.

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

Review submitted (REQUEST_CHANGES) — review ID 8717. **Findings:** - BLOCKING: Data table in `features/a2a_module_rename_standardization.feature` is ignored by the step definition; `context.table` must be used instead of the hardcoded `_ALL_SYMBOLS` list. - BLOCKING: Two unsquashed fixup lint commits in PR history must be squashed into the main refactor commit before merge. - Non-blocking: PR title typo (`reflector` should be `refactor`), Gherkin step semantics (@when vs @then), branch name mismatch. **CI:** All required gates pass. `benchmark-regression` failure is non-blocking. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9000 force-pushed feature/acp-a2a-rename-fix from c91e5b114f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 48s
Details
CI / helm (pull_request) Successful in 1m4s
Details
CI / lint (pull_request) Successful in 1m26s
Details
CI / build (pull_request) Successful in 1m35s
Details
CI / benchmark-regression (pull_request) Failing after 1m16s
Details
CI / typecheck (pull_request) Successful in 1m59s
Details
CI / quality (pull_request) Successful in 1m58s
Details
CI / security (pull_request) Successful in 2m49s
Details
CI / integration_tests (pull_request) Successful in 4m39s
Details
CI / unit_tests (pull_request) Successful in 6m4s
Details
CI / e2e_tests (pull_request) Successful in 6m38s
Details
CI / docker (pull_request) Successful in 2m37s
Details
CI / coverage (pull_request) Successful in 23m59s
Details
CI / status-check (pull_request) Successful in 5s
Details
to ac91b9e9a5
All checks were successful
CI / helm (pull_request) Successful in 54s
Details
CI / push-validation (pull_request) Successful in 1m14s
Details
CI / build (pull_request) Successful in 1m9s
Details
CI / lint (pull_request) Successful in 1m17s
Details
CI / quality (pull_request) Successful in 1m59s
Details
CI / typecheck (pull_request) Successful in 2m3s
Details
CI / security (pull_request) Successful in 2m3s
Details
CI / integration_tests (pull_request) Successful in 3m38s
Details
CI / unit_tests (pull_request) Successful in 4m58s
Details
CI / docker (pull_request) Successful in 1m28s
Details
CI / coverage (pull_request) Successful in 11m6s
Details
CI / status-check (pull_request) Successful in 3s
Details
2026-05-14 11:05:59 +00:00 Compare
All checks were successful
CI / helm (pull_request) Successful in 54s
Details
CI / push-validation (pull_request) Successful in 1m14s
Details
CI / build (pull_request) Successful in 1m9s
Required
Details
CI / lint (pull_request) Successful in 1m17s
Required
Details
CI / quality (pull_request) Successful in 1m59s
Required
Details
CI / typecheck (pull_request) Successful in 2m3s
Required
Details
CI / security (pull_request) Successful in 2m3s
Required
Details
CI / integration_tests (pull_request) Successful in 3m38s
Required
Details
CI / unit_tests (pull_request) Successful in 4m58s
Required
Details
CI / docker (pull_request) Successful in 1m28s
Required
Details
CI / coverage (pull_request) Successful in 11m6s
Required
Details
CI / status-check (pull_request) Successful in 3s
Details
This pull request has changes conflicting with the target branch.
  • 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/acp-a2a-rename-fix:feature/acp-a2a-rename-fix
git switch feature/acp-a2a-rename-fix
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.6.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!11165
No description provided.