feat(cli): wire project context CLI stubs to ACMS pipeline #534

Merged

CoreRasurae merged 1 commit from feature/m5-context-cli-wiring into master 2026-03-03 23:41:23 +00:00

Conversation 2 Commits 1 Files changed 13 +2079 -103

CoreRasurae commented 2026-03-03 19:46:40 +00:00

Member

Copy link

Summary

Wire all four project context CLI commands (inspect, simulate, set, show) to live ACMS pipeline services, replacing the previous NotImplementedError stubs with fully functional implementations backed by ContextTierService and CRP models. Also fixes two bugs found during review: context inspect incorrectly reported global tier fragment counts instead of project-scoped counts, and context simulate --focus silently ignored the focus URIs.

Closes #499

Changes

Source

src/cleveragents/cli/commands/project_context.py (+720/-11)

• context inspect: Queries ContextTierService for project-scoped tier metrics (hot/warm/cold fragment counts, hit/miss rates) and per-project fragments. Supports optional filtering by --strategy, --focus, --breadth, and --depth. Displays tier budget utilisation, per-actor visibility (strategist/executor/reviewer), and fragment details (first 20). All output formats supported (rich/json/yaml/plain/table).
• context simulate: Performs dry-run context assembly using CRP models (ContextRequest, ContextFragment, AssembledContext). Builds simulated fragments from tier data with budget enforcement. Configurable --budget (token limit override) and --strategy (repeatable hint). When --focus is provided, fragments are filtered by matching resource_id against the focus URIs. Outputs fragment provenance, total tokens, budget usage percentage, strategy list, and a context hash.
• context set: Gains 12 new ACMS pipeline options: --hot-max-tokens, --warm-max-decisions, --cold-max-decisions, --summary-max-tokens, --temporal-scope, --auto-refresh/--no-auto-refresh, --summarize/--no-summarize, --strategy, --default-breadth, --default-depth, --skeleton-ratio, --query-limit. Persists ACMS config alongside the context policy via _write_policy() / _read_acms_config().
• context show: Displays ACMS pipeline configuration (tier budgets, strategies, temporal scope, auto-refresh, skeleton ratio) alongside existing context policy in all output formats.
• Helper functions: _get_context_tier_service(), _read_acms_config(), _default_acms_config(), _write_policy() (extended with acms_config parameter), _tier_metrics_to_dict(), _fragment_to_dict(), _assembled_to_dict(), _simulate_context_assembly().

src/cleveragents/application/services/context_tiers.py (+27)

• Added get_scoped_metrics(project_names) method to ContextTierService. Returns TierMetrics with fragment counts (hot/warm/cold) filtered to the specified projects using ScopedBackendView, while keeping hit/miss counters as global service-level cache metrics. Raises ValueError if project_names is empty.

src/cleveragents/shared/redaction.py (+2)

• Added hot_max_tokens and summary_max_tokens to _FALSE_POSITIVE_KEYS to prevent legitimate ACMS config keys from being redacted as sensitive data.

Bug Fixes

• Scoped inspect metrics: context inspect displayed global tier fragment counts across all projects instead of counts for the target project only. Fixed by calling get_scoped_metrics([project]) instead of get_metrics().
• Focus URI filtering: context simulate --focus accepted focus URIs and passed them to the ContextRequest model but never applied them to filter the fragment list, making --focus a no-op. Fixed by adding a filtering step in _simulate_context_assembly() that retains only fragments whose resource_id matches a supplied focus URI.

Tests

Behave BDD (unit-level)

• New file: features/context_cli_wiring.feature — 30 scenarios covering all ACMS set options (12 scenarios), show with ACMS config (2), inspect with tier data (6, including scoped metrics verification and error cases), and simulate with budget/strategy/focus/fragments (8, including focus URI filtering and error cases).
• New file: features/steps/context_cli_wiring_steps.py — 646 lines of step definitions using an in-memory SQLite database and a real ContextTierService instance with mocked DI container.
• Updated: features/project_context_cli.feature — replaced NotImplementedError expectations for inspect/simulate with wired success assertions (2 scenarios updated).
• Updated: features/steps/project_context_cli_steps.py — added ContextTierService to mock container, added width=500, soft_wrap=True to Rich Console to prevent JSON parse failures from line-wrapping, added inspect/simulate success step definitions.
• Updated: features/m5_acms_smoke.feature — replaced NotImplementedError expectations with wired ACMS success assertions (2 scenarios updated).
• Updated: features/steps/m5_acms_smoke_steps.py — rewired inspect/simulate steps to use mocked DI container with real ContextTierService, added success assertion steps.

Robot Framework (integration)

• Updated: robot/project_context_cli.robot — 5 test cases: set-show round-trip, inspect-wired, simulate-wired, set-acms, show-acms (replaces 3 previous tests that tested stubs).
• Updated: robot/helper_project_context_cli.py — added _make_mock_container(), _run_cli_func() helpers with mocked DI; added test_context_inspect_wired(), test_context_simulate_wired(), test_context_set_acms_options(), test_context_show_acms_config() (replaces stub tests).

Documentation

• docs/reference/project_context_cli.md (+169/-12): Full reference documentation for all four commands. Added ACMS pipeline options table for set, output descriptions for show/inspect/simulate, usage examples for ACMS configuration, and replaced stub notices with complete command references.
• CHANGELOG.md: Three entries under Unreleased — one for the feature wiring, one for the scoped inspect metrics fix, one for the focus URI filtering fix. All reference #499.

Verification

Check	Result
ruff check (lint)	Pass
ruff format --check (format)	Pass
pyright (typecheck)	Pass (0 errors on both modified source files)
BDD: context_cli_wiring.feature	30/30 scenarios pass
BDD: project_context_cli.feature	19/19 scenarios pass
BDD: m5_acms_smoke.feature	26/26 scenarios pass
Coverage: project_context.py	92% (new code paths exercised)

## Summary Wire all four project context CLI commands (`inspect`, `simulate`, `set`, `show`) to live ACMS pipeline services, replacing the previous `NotImplementedError` stubs with fully functional implementations backed by `ContextTierService` and CRP models. Also fixes two bugs found during review: `context inspect` incorrectly reported global tier fragment counts instead of project-scoped counts, and `context simulate --focus` silently ignored the focus URIs. Closes #499 ## Changes ### Source #### `src/cleveragents/cli/commands/project_context.py` (+720/-11) - **`context inspect`**: Queries `ContextTierService` for project-scoped tier metrics (hot/warm/cold fragment counts, hit/miss rates) and per-project fragments. Supports optional filtering by `--strategy`, `--focus`, `--breadth`, and `--depth`. Displays tier budget utilisation, per-actor visibility (strategist/executor/reviewer), and fragment details (first 20). All output formats supported (rich/json/yaml/plain/table). - **`context simulate`**: Performs dry-run context assembly using CRP models (`ContextRequest`, `ContextFragment`, `AssembledContext`). Builds simulated fragments from tier data with budget enforcement. Configurable `--budget` (token limit override) and `--strategy` (repeatable hint). When `--focus` is provided, fragments are filtered by matching `resource_id` against the focus URIs. Outputs fragment provenance, total tokens, budget usage percentage, strategy list, and a context hash. - **`context set`**: Gains 12 new ACMS pipeline options: `--hot-max-tokens`, `--warm-max-decisions`, `--cold-max-decisions`, `--summary-max-tokens`, `--temporal-scope`, `--auto-refresh/--no-auto-refresh`, `--summarize/--no-summarize`, `--strategy`, `--default-breadth`, `--default-depth`, `--skeleton-ratio`, `--query-limit`. Persists ACMS config alongside the context policy via `_write_policy()` / `_read_acms_config()`. - **`context show`**: Displays ACMS pipeline configuration (tier budgets, strategies, temporal scope, auto-refresh, skeleton ratio) alongside existing context policy in all output formats. - **Helper functions**: `_get_context_tier_service()`, `_read_acms_config()`, `_default_acms_config()`, `_write_policy()` (extended with `acms_config` parameter), `_tier_metrics_to_dict()`, `_fragment_to_dict()`, `_assembled_to_dict()`, `_simulate_context_assembly()`. #### `src/cleveragents/application/services/context_tiers.py` (+27) - Added `get_scoped_metrics(project_names)` method to `ContextTierService`. Returns `TierMetrics` with fragment counts (hot/warm/cold) filtered to the specified projects using `ScopedBackendView`, while keeping hit/miss counters as global service-level cache metrics. Raises `ValueError` if `project_names` is empty. #### `src/cleveragents/shared/redaction.py` (+2) - Added `hot_max_tokens` and `summary_max_tokens` to `_FALSE_POSITIVE_KEYS` to prevent legitimate ACMS config keys from being redacted as sensitive data. ### Bug Fixes - **Scoped inspect metrics**: `context inspect` displayed global tier fragment counts across all projects instead of counts for the target project only. Fixed by calling `get_scoped_metrics([project])` instead of `get_metrics()`. - **Focus URI filtering**: `context simulate --focus` accepted focus URIs and passed them to the `ContextRequest` model but never applied them to filter the fragment list, making `--focus` a no-op. Fixed by adding a filtering step in `_simulate_context_assembly()` that retains only fragments whose `resource_id` matches a supplied focus URI. ### Tests #### Behave BDD (unit-level) - **New file**: `features/context_cli_wiring.feature` — 30 scenarios covering all ACMS set options (12 scenarios), show with ACMS config (2), inspect with tier data (6, including scoped metrics verification and error cases), and simulate with budget/strategy/focus/fragments (8, including focus URI filtering and error cases). - **New file**: `features/steps/context_cli_wiring_steps.py` — 646 lines of step definitions using an in-memory SQLite database and a real `ContextTierService` instance with mocked DI container. - **Updated**: `features/project_context_cli.feature` — replaced `NotImplementedError` expectations for inspect/simulate with wired success assertions (2 scenarios updated). - **Updated**: `features/steps/project_context_cli_steps.py` — added `ContextTierService` to mock container, added `width=500, soft_wrap=True` to Rich Console to prevent JSON parse failures from line-wrapping, added inspect/simulate success step definitions. - **Updated**: `features/m5_acms_smoke.feature` — replaced `NotImplementedError` expectations with wired ACMS success assertions (2 scenarios updated). - **Updated**: `features/steps/m5_acms_smoke_steps.py` — rewired inspect/simulate steps to use mocked DI container with real `ContextTierService`, added success assertion steps. #### Robot Framework (integration) - **Updated**: `robot/project_context_cli.robot` — 5 test cases: set-show round-trip, inspect-wired, simulate-wired, set-acms, show-acms (replaces 3 previous tests that tested stubs). - **Updated**: `robot/helper_project_context_cli.py` — added `_make_mock_container()`, `_run_cli_func()` helpers with mocked DI; added `test_context_inspect_wired()`, `test_context_simulate_wired()`, `test_context_set_acms_options()`, `test_context_show_acms_config()` (replaces stub tests). ### Documentation - **`docs/reference/project_context_cli.md`** (+169/-12): Full reference documentation for all four commands. Added ACMS pipeline options table for `set`, output descriptions for `show`/`inspect`/`simulate`, usage examples for ACMS configuration, and replaced stub notices with complete command references. - **`CHANGELOG.md`**: Three entries under Unreleased — one for the feature wiring, one for the scoped inspect metrics fix, one for the focus URI filtering fix. All reference #499. ## Verification | Check | Result | |---|---| | `ruff check` (lint) | Pass | | `ruff format --check` (format) | Pass | | `pyright` (typecheck) | Pass (0 errors on both modified source files) | | BDD: `context_cli_wiring.feature` | 30/30 scenarios pass | | BDD: `project_context_cli.feature` | 19/19 scenarios pass | | BDD: `m5_acms_smoke.feature` | 26/26 scenarios pass | | Coverage: `project_context.py` | 92% (new code paths exercised) |

CoreRasurae referenced this pull request 2026-03-03 19:46:51 +00:00

feat(cli): wire project context CLI stubs to ACMS pipeline #499

brent.edwards approved these changes 2026-03-03 22:24:11 +00:00

Dismissed

brent.edwards left a comment

Copy link

Review — PR #534 feat(cli): wire project context CLI stubs to ACMS pipeline

Verdict: APPROVED with comments

Nice end-to-end wiring of project context commands with comprehensive Behave + Robot coverage and solid reference docs. The ACMS config persistence via shared policy JSON is consistent with existing patterns, and the new redaction allowlist keys close the false-positive leak for config output.

No P0 or P1 findings.

---

P2:should-fix

1. Missing required PR label — Per CONTRIBUTING.md, every PR must carry exactly one Type/ label. This PR has no labels. The linked issue #499 is Type/Feature.

2. Missing PR milestone — Per CONTRIBUTING.md, the PR milestone must match the linked issue. This PR has no milestone set. Issue #499 is assigned to milestone v3.4.0.

3. context inspect tier metrics are global, not project-scoped — The command is per-project but ContextTierService.get_metrics() is global. In multi-project setups, the "Tier Metrics" panel and JSON tier_metrics will reflect all fragments, not just the target project. Please either compute metrics from get_scoped_view([project]) or add a scoped metrics helper so inspect reflects the project-specific tier state. (See src/cleveragents/cli/commands/project_context.py.)

4. context simulate --focus is ignored in the simulated assembly — focus_uris are only passed into ContextRequest, but the simulated fragment selection uses project_fragments without filtering. This makes --focus a no-op for the CLI output. Please filter the selected TieredFragment list by resource_id/fragment ID when --focus is provided so the simulation respects the option. (See _simulate_context_assembly in src/cleveragents/cli/commands/project_context.py.)

---

P2 items should be addressed in a follow-up within 3 business days.

## Review — PR #534 `feat(cli): wire project context CLI stubs to ACMS pipeline` **Verdict: APPROVED with comments** Nice end-to-end wiring of `project context` commands with comprehensive Behave + Robot coverage and solid reference docs. The ACMS config persistence via shared policy JSON is consistent with existing patterns, and the new redaction allowlist keys close the false-positive leak for config output. No P0 or P1 findings. --- ### P2:should-fix 1. **Missing required PR label** — Per `CONTRIBUTING.md`, every PR must carry exactly one `Type/` label. This PR has no labels. The linked issue #499 is `Type/Feature`. 2. **Missing PR milestone** — Per `CONTRIBUTING.md`, the PR milestone must match the linked issue. This PR has no milestone set. Issue #499 is assigned to milestone `v3.4.0`. 3. **`context inspect` tier metrics are global, not project-scoped** — The command is per-project but `ContextTierService.get_metrics()` is global. In multi-project setups, the "Tier Metrics" panel and JSON `tier_metrics` will reflect all fragments, not just the target project. Please either compute metrics from `get_scoped_view([project])` or add a scoped metrics helper so `inspect` reflects the project-specific tier state. (See `src/cleveragents/cli/commands/project_context.py`.) 4. **`context simulate --focus` is ignored in the simulated assembly** — `focus_uris` are only passed into `ContextRequest`, but the simulated fragment selection uses `project_fragments` without filtering. This makes `--focus` a no-op for the CLI output. Please filter the selected `TieredFragment` list by `resource_id`/fragment ID when `--focus` is provided so the simulation respects the option. (See `_simulate_context_assembly` in `src/cleveragents/cli/commands/project_context.py`.) --- P2 items should be addressed in a follow-up within 3 business days.

CoreRasurae added the

Type

Feature

label 2026-03-03 23:10:35 +00:00

CoreRasurae added this to the v3.4.0 milestone 2026-03-03 23:10:35 +00:00

CoreRasurae force-pushed feature/m5-context-cli-wiring from cf514957a7 to 70cd342e97 2026-03-03 23:15:15 +00:00 Compare

CoreRasurae dismissed brent.edwards's review 2026-03-03 23:15:15 +00:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

CoreRasurae added a new dependency 2026-03-03 23:23:35 +00:00

#499 feat(cli): wire project context CLI stubs to ACMS pipeline

brent.edwards approved these changes 2026-03-03 23:28:25 +00:00

Dismissed

brent.edwards left a comment

Copy link

Review — PR #534 (updated)

Verdict: APPROVED

Verified all prior P2 findings are resolved:

• PR now has required Type/Feature label and milestone v3.4.0.
• context inspect now uses project-scoped tier metrics via get_scoped_metrics([project]).
• context simulate --focus now filters fragments by focus URIs in _simulate_context_assembly().
• New ContextTierService.get_scoped_metrics() added to support scoped counts (global hit/miss retained as intended).

No P0/P1 findings. No remaining P2/P3 items.

## Review — PR #534 (updated) **Verdict: APPROVED** Verified all prior P2 findings are resolved: - PR now has required `Type/Feature` label and milestone `v3.4.0`. - `context inspect` now uses project-scoped tier metrics via `get_scoped_metrics([project])`. - `context simulate --focus` now filters fragments by focus URIs in `_simulate_context_assembly()`. - New `ContextTierService.get_scoped_metrics()` added to support scoped counts (global hit/miss retained as intended). No P0/P1 findings. No remaining P2/P3 items.

CoreRasurae force-pushed feature/m5-context-cli-wiring from 70cd342e97 to ff42d59d6d 2026-03-03 23:36:31 +00:00 Compare

CoreRasurae dismissed brent.edwards's review 2026-03-03 23:36:31 +00:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

CoreRasurae scheduled this pull request to auto merge when all checks succeed 2026-03-03 23:36:52 +00:00

CoreRasurae merged commit ff42d59d6d into master 2026-03-03 23:41:23 +00:00

CoreRasurae deleted branch feature/m5-context-cli-wiring 2026-03-03 23:41:23 +00:00

freemo referenced this pull request 2026-03-04 00:37:55 +00:00

feat(cli): wire project context CLI stubs to ACMS pipeline #499

freemo added the

State

Completed

label 2026-03-04 00:41:32 +00:00

freemo referenced this pull request 2026-03-04 01:07:41 +00:00

feat(cli): wire project context CLI stubs to ACMS pipeline #499

freemo removed a dependency 2026-03-04 01:55:19 +00:00

#499 feat(cli): wire project context CLI stubs to ACMS pipeline

Sign in to join this conversation.

Reviewers

No reviewers

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.4.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

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!534

No description provided.