cleveragents/cleveragents-core

Fork 3

UAT: `agents project context inspect` returns tier metrics instead of assembled context fragments with UKO URIs — v3.4.0 acceptance criterion #4 not met #6088

New issue

Open

opened 2026-04-09 14:31:01 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 14:31:01 +00:00

Owner

Summary

The agents project context inspect command returns tier metrics (hot/warm/cold fragment counts, hit/miss rates) and raw TieredFragment objects with resource_id fields. The v3.4.0 acceptance criterion #4 requires it to "run context assembly and show result" and "return assembled context fragments with UKO URIs".

Expected Behavior (per spec)

From docs/specification.md line 4136, the spec shows the command should produce:

╭─ ACMS Context Inspection ────────────────────────────────────────╮

With assembled context fragments including UKO URIs (e.g., uko-py:module/src.auth).

From v3.4.0 acceptance criterion #4:

agents project context inspect runs context assembly and shows result | Returns assembled context fragments with UKO URIs

The spec example at line 4134:

$ agents project context inspect --view execute --focus uko-py:module/src.auth --breadth 2 local/api-service

Should show assembled context fragments with proper UKO URIs, not raw tier metrics.

Actual Behavior

The current context_inspect() implementation in src/cleveragents/cli/commands/project_context.py:

Queries ContextTierService.get_scoped_view() for raw TieredFragment objects
Displays tier metrics (hot/warm/cold counts, hit/miss rates)
Shows fragment resource_id values (plain resource identifiers, not UKO URIs)
Does NOT run the ACMS context assembly pipeline
Does NOT return ContextFragment objects with uko_node UKO URI fields

The _fragment_to_dict() helper converts TieredFragment to a dict with resource_id — not a UKO URI. The spec requires uko_node (e.g., uko-py:module/src.auth) in the output.

Code Location

src/cleveragents/cli/commands/project_context.py:
- context_inspect() (line ~919) — queries tier service, not ACMS pipeline
- _fragment_to_dict() (line ~200) — returns resource_id, not uko_node

Fix Required

context inspect should invoke the ACMS Context Assembly Pipeline (not just the tier service) and return ContextFragment objects with uko_node UKO URIs, detail_depth, token_count, relevance_score, and provenance.strategy fields — matching the spec output format.

Spec References

docs/specification.md line 4109-4262: agents project context inspect command reference
docs/specification.md line 4136: ACMS Context Inspection output format
v3.4.0 acceptance criterion #4: Returns assembled context fragments with UKO URIs

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Summary The `agents project context inspect` command returns tier metrics (hot/warm/cold fragment counts, hit/miss rates) and raw `TieredFragment` objects with `resource_id` fields. The v3.4.0 acceptance criterion #4 requires it to "run context assembly and show result" and "return assembled context fragments with UKO URIs". ## Expected Behavior (per spec) From `docs/specification.md` line 4136, the spec shows the command should produce: ``` ╭─ ACMS Context Inspection ────────────────────────────────────────╮ ``` With assembled context fragments including UKO URIs (e.g., `uko-py:module/src.auth`). From v3.4.0 acceptance criterion #4: > `agents project context inspect` runs context assembly and shows result | Returns assembled context fragments with UKO URIs The spec example at line 4134: ``` $ agents project context inspect --view execute --focus uko-py:module/src.auth --breadth 2 local/api-service ``` Should show assembled context fragments with proper UKO URIs, not raw tier metrics. ## Actual Behavior The current `context_inspect()` implementation in `src/cleveragents/cli/commands/project_context.py`: 1. Queries `ContextTierService.get_scoped_view()` for raw `TieredFragment` objects 2. Displays tier metrics (hot/warm/cold counts, hit/miss rates) 3. Shows fragment `resource_id` values (plain resource identifiers, not UKO URIs) 4. Does NOT run the ACMS context assembly pipeline 5. Does NOT return `ContextFragment` objects with `uko_node` UKO URI fields The `_fragment_to_dict()` helper converts `TieredFragment` to a dict with `resource_id` — not a UKO URI. The spec requires `uko_node` (e.g., `uko-py:module/src.auth`) in the output. ## Code Location - `src/cleveragents/cli/commands/project_context.py`: - `context_inspect()` (line ~919) — queries tier service, not ACMS pipeline - `_fragment_to_dict()` (line ~200) — returns `resource_id`, not `uko_node` ## Fix Required `context inspect` should invoke the ACMS Context Assembly Pipeline (not just the tier service) and return `ContextFragment` objects with `uko_node` UKO URIs, `detail_depth`, `token_count`, `relevance_score`, and `provenance.strategy` fields — matching the spec output format. ## Spec References - `docs/specification.md` line 4109-4262: `agents project context inspect` command reference - `docs/specification.md` line 4136: ACMS Context Inspection output format - v3.4.0 acceptance criterion #4: Returns assembled context fragments with UKO URIs --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added this to the v3.4.0 milestone

2026-04-09 14:31:01 +00:00

HAL9000 added the

labels

2026-04-09 14:31:01 +00:00

HAL9000 referenced this issue

2026-04-09 17:03:23 +00:00

[AUTO-IMP-SUP] Implementation Pool Supervisor Status (Cycle 1) #6167

HAL9000 referenced this issue

2026-04-14 20:11:00 +00:00

[AUTO-PROJ-OWN] Status: Project Owner Supervisor (Cycle 2) #9489

HAL9000 added

and removed

labels

2026-04-17 06:03:24 +00:00

HAL9000 commented

2026-04-17 06:10:16 +00:00

Author

Owner

✅ Verified — Critical: v3.4.0 acceptance criterion #4 (context assembly CLI functional) is not met. The command returns wrong data structure. MoSCoW: Must Have — directly blocks v3.4.0 milestone acceptance.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Verified** — Critical: v3.4.0 acceptance criterion #4 (context assembly CLI functional) is not met. The command returns wrong data structure. **MoSCoW: Must Have** — directly blocks v3.4.0 milestone acceptance. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor