feat(cli): wire project context CLI stubs to ACMS pipeline #534
Merged
CoreRasurae
merged 1 commits from 2026-03-03 23:41:23 +00:00
feature/m5-context-cli-wiring into master
No Reviewers
Labels
Clear labels
auto/needs-reevaluation
controller-managed
overdue
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Needs Feedback
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
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.
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.
Currently being processed by an implementer worker.
Currently being processed by the merge driver.
Currently being processed by a reviewer worker.
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
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.
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.
Tracking issues used by the AI Automation system for agents to communicate and report.
Rebase conflict needs LLM conflict-resolver.
Failing CI needs implementer attention.
Documenting a driver incident or rollback.
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.
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
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.
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
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.
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
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.
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.
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.
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.
Projects
Clear projects
No project
Assignees
aditya (Aditya Chhabra)
aleenaumair (Aleena Umair)
brent.edwards (Brent Edwards)
CoreRasurae (Luis Mendes)
drew (Drew Morris)
eugen.thaci (Eugen Thaci)
freemo (Jeffrey Phillips Freeman)
HAL9000 (HAL 9000)
HAL9001 (HAL9001)
hamza.khyari (Hamza Khyari)
hurui200320 (Rui Hu)
justin.morris
khird (Kyle Hird)
org.cleveragents
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cleveragents/cleveragents-core#534
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "feature/m5-context-cli-wiring"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Wire all four project context CLI commands (
inspect,simulate,set,show) to live ACMS pipeline services, replacing the previousNotImplementedErrorstubs with fully functional implementations backed byContextTierServiceand CRP models. Also fixes two bugs found during review:context inspectincorrectly reported global tier fragment counts instead of project-scoped counts, andcontext simulate --focussilently ignored the focus URIs.Closes #499
Changes
Source
src/cleveragents/cli/commands/project_context.py(+720/-11)context inspect: QueriesContextTierServicefor 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--focusis provided, fragments are filtered by matchingresource_idagainst 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._get_context_tier_service(),_read_acms_config(),_default_acms_config(),_write_policy()(extended withacms_configparameter),_tier_metrics_to_dict(),_fragment_to_dict(),_assembled_to_dict(),_simulate_context_assembly().src/cleveragents/application/services/context_tiers.py(+27)get_scoped_metrics(project_names)method toContextTierService. ReturnsTierMetricswith fragment counts (hot/warm/cold) filtered to the specified projects usingScopedBackendView, while keeping hit/miss counters as global service-level cache metrics. RaisesValueErrorifproject_namesis empty.src/cleveragents/shared/redaction.py(+2)hot_max_tokensandsummary_max_tokensto_FALSE_POSITIVE_KEYSto prevent legitimate ACMS config keys from being redacted as sensitive data.Bug Fixes
context inspectdisplayed global tier fragment counts across all projects instead of counts for the target project only. Fixed by callingget_scoped_metrics([project])instead ofget_metrics().context simulate --focusaccepted focus URIs and passed them to theContextRequestmodel but never applied them to filter the fragment list, making--focusa no-op. Fixed by adding a filtering step in_simulate_context_assembly()that retains only fragments whoseresource_idmatches a supplied focus URI.Tests
Behave BDD (unit-level)
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).features/steps/context_cli_wiring_steps.py— 646 lines of step definitions using an in-memory SQLite database and a realContextTierServiceinstance with mocked DI container.features/project_context_cli.feature— replacedNotImplementedErrorexpectations for inspect/simulate with wired success assertions (2 scenarios updated).features/steps/project_context_cli_steps.py— addedContextTierServiceto mock container, addedwidth=500, soft_wrap=Trueto Rich Console to prevent JSON parse failures from line-wrapping, added inspect/simulate success step definitions.features/m5_acms_smoke.feature— replacedNotImplementedErrorexpectations with wired ACMS success assertions (2 scenarios updated).features/steps/m5_acms_smoke_steps.py— rewired inspect/simulate steps to use mocked DI container with realContextTierService, added success assertion steps.Robot Framework (integration)
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).robot/helper_project_context_cli.py— added_make_mock_container(),_run_cli_func()helpers with mocked DI; addedtest_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 forset, output descriptions forshow/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
ruff check(lint)ruff format --check(format)pyright(typecheck)context_cli_wiring.featureproject_context_cli.featurem5_acms_smoke.featureproject_context.pyReview — PR #534
feat(cli): wire project context CLI stubs to ACMS pipelineVerdict: APPROVED with comments
Nice end-to-end wiring of
project contextcommands 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
Missing required PR label — Per
CONTRIBUTING.md, every PR must carry exactly oneType/label. This PR has no labels. The linked issue #499 isType/Feature.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 milestonev3.4.0.context inspecttier metrics are global, not project-scoped — The command is per-project butContextTierService.get_metrics()is global. In multi-project setups, the "Tier Metrics" panel and JSONtier_metricswill reflect all fragments, not just the target project. Please either compute metrics fromget_scoped_view([project])or add a scoped metrics helper soinspectreflects the project-specific tier state. (Seesrc/cleveragents/cli/commands/project_context.py.)context simulate --focusis ignored in the simulated assembly —focus_urisare only passed intoContextRequest, but the simulated fragment selection usesproject_fragmentswithout filtering. This makes--focusa no-op for the CLI output. Please filter the selectedTieredFragmentlist byresource_id/fragment ID when--focusis provided so the simulation respects the option. (See_simulate_context_assemblyinsrc/cleveragents/cli/commands/project_context.py.)P2 items should be addressed in a follow-up within 3 business days.
cf514957a7to70cd342e97New commits pushed, approval review dismissed automatically according to repository settings
Review — PR #534 (updated)
Verdict: APPROVED
Verified all prior P2 findings are resolved:
Type/Featurelabel and milestonev3.4.0.context inspectnow uses project-scoped tier metrics viaget_scoped_metrics([project]).context simulate --focusnow filters fragments by focus URIs in_simulate_context_assembly().ContextTierService.get_scoped_metrics()added to support scoped counts (global hit/miss retained as intended).No P0/P1 findings. No remaining P2/P3 items.
70cd342e97toff42d59d6dNew commits pushed, approval review dismissed automatically according to repository settings