UAT: `agents project context inspect` JSON/YAML output uses internal tier metrics structure instead of spec-required `inspection`/`uko_graph`/`active_strategies`/`budget` keys #6498

New issue

Open

opened 2026-04-09 21:10:35 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 21:10:35 +00:00

Owner

Summary

The JSON and YAML output of agents project context inspect uses an internal tier-metrics-based structure instead of the spec-required structure with inspection, uko_graph, active_strategies, and budget keys.

Spec Reference

docs/specification.md §CLI Commands — agents project context inspect JSON output (line ~4210–4256):

{
  "command": "project context inspect",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "inspection": {
      "project": "local/api-service",
      "view": "execute",
      "focus": ["uko-py:module/src.auth"],
      "breadth": 2,
      "depth": 3,
      "depth_name": "MEMBER_SUMMARY"
    },
    "uko_graph": {
      "root": "uko-py:module/src.auth",
      "root_depth": 9,
      "root_depth_name": "FULL_SOURCE",
      "root_tokens": 1240,
      "edges": [
        { "relation": "contains", "target": "uko-py:class/AuthHandler", "depth": 3, "tokens": 320 },
        ...
      ]
    },
    "active_strategies": [
      { "name": "breadth-depth-navigator", "quality": 0.85, "budget_pct": 0.45, "fragments": 4 },
      ...
    ],
    "budget": {
      "model_window": 128000,
      "response_reserve": 4096,
      "tool_definitions": 2400,
      "system_prompt": 1200,
      "skeleton_reserve": 18046,
      "skeleton_ratio": 0.15,
      "available_budget": 102258,
      "used": 1990,
      "utilization": 0.019
    }
  }
}

The spec rich output shows:

"ACMS Context Inspection" panel (project, view, focus, breadth, depth)
"UKO Graph (N-hop neighborhood)" panel with graph edges
"Active Strategies" panel (strategy name, quality, budget%, fragments)
"Budget" panel (model window, response reserve, tool definitions, system prompt, skeleton reserve, available budget, used)

Observed Behavior

The context_inspect command (src/cleveragents/cli/commands/project_context.py, line 918) produces:

{
  "project": "local/api-service",
  "view": "all",
  "tier_metrics": { "hot_count": 0, "warm_count": 0, "cold_count": 0, ... },
  "tier_budget": { "max_tokens_hot": 8000, ... },
  "project_fragments": { "total": 0, "by_tier": { "hot": 0, "warm": 0, "cold": 0 } },
  "actor_visibility": { "strategist": 0, "executor": 0, "reviewer": 0, "estimator": 0 },
  "acms_config": { ... },
  "phase_analysis": { ... },
  "fragments": []
}

The rich output shows:

"Tier Metrics" table
"Tier Budget" panel
"Project Fragments" panel
"Actor Visibility" panel
"Per-Phase Context Analysis" table
"Phase Narrowing" panel

None of these match the spec-required panels.

Expected Behavior

context inspect should output:

inspection — project, view, focus, breadth, depth, depth_name
uko_graph — UKO graph structure with root node and edges (requires UKO graph backend integration)
active_strategies — list of strategies with quality/budget/fragment counts
budget — model window, reserves, available budget, utilization

The rich output should show the spec-required panels: "ACMS Context Inspection", "UKO Graph", "Active Strategies", "Budget".

Code Location

src/cleveragents/cli/commands/project_context.py — context_inspect() (line 918)
The current implementation is a useful debugging view but does not match the spec's user-facing design

Note

This is a significant output format deviation. The current implementation provides useful internal data (tier metrics, phase analysis) but the spec requires a UKO-graph-centric view. The UKO graph display requires integration with the ACMS graph backend.

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

## Summary The JSON and YAML output of `agents project context inspect` uses an internal tier-metrics-based structure instead of the spec-required structure with `inspection`, `uko_graph`, `active_strategies`, and `budget` keys. ## Spec Reference `docs/specification.md` §CLI Commands — `agents project context inspect` JSON output (line ~4210–4256): ```json { "command": "project context inspect", "status": "ok", "exit_code": 0, "data": { "inspection": { "project": "local/api-service", "view": "execute", "focus": ["uko-py:module/src.auth"], "breadth": 2, "depth": 3, "depth_name": "MEMBER_SUMMARY" }, "uko_graph": { "root": "uko-py:module/src.auth", "root_depth": 9, "root_depth_name": "FULL_SOURCE", "root_tokens": 1240, "edges": [ { "relation": "contains", "target": "uko-py:class/AuthHandler", "depth": 3, "tokens": 320 }, ... ] }, "active_strategies": [ { "name": "breadth-depth-navigator", "quality": 0.85, "budget_pct": 0.45, "fragments": 4 }, ... ], "budget": { "model_window": 128000, "response_reserve": 4096, "tool_definitions": 2400, "system_prompt": 1200, "skeleton_reserve": 18046, "skeleton_ratio": 0.15, "available_budget": 102258, "used": 1990, "utilization": 0.019 } } } ``` The spec rich output shows: - "ACMS Context Inspection" panel (project, view, focus, breadth, depth) - "UKO Graph (N-hop neighborhood)" panel with graph edges - "Active Strategies" panel (strategy name, quality, budget%, fragments) - "Budget" panel (model window, response reserve, tool definitions, system prompt, skeleton reserve, available budget, used) ## Observed Behavior The `context_inspect` command (`src/cleveragents/cli/commands/project_context.py`, line 918) produces: ```json { "project": "local/api-service", "view": "all", "tier_metrics": { "hot_count": 0, "warm_count": 0, "cold_count": 0, ... }, "tier_budget": { "max_tokens_hot": 8000, ... }, "project_fragments": { "total": 0, "by_tier": { "hot": 0, "warm": 0, "cold": 0 } }, "actor_visibility": { "strategist": 0, "executor": 0, "reviewer": 0, "estimator": 0 }, "acms_config": { ... }, "phase_analysis": { ... }, "fragments": [] } ``` The rich output shows: - "Tier Metrics" table - "Tier Budget" panel - "Project Fragments" panel - "Actor Visibility" panel - "Per-Phase Context Analysis" table - "Phase Narrowing" panel None of these match the spec-required panels. ## Expected Behavior `context inspect` should output: 1. `inspection` — project, view, focus, breadth, depth, depth_name 2. `uko_graph` — UKO graph structure with root node and edges (requires UKO graph backend integration) 3. `active_strategies` — list of strategies with quality/budget/fragment counts 4. `budget` — model window, reserves, available budget, utilization The rich output should show the spec-required panels: "ACMS Context Inspection", "UKO Graph", "Active Strategies", "Budget". ## Code Location - `src/cleveragents/cli/commands/project_context.py` — `context_inspect()` (line 918) - The current implementation is a useful debugging view but does not match the spec's user-facing design ## Note This is a significant output format deviation. The current implementation provides useful internal data (tier metrics, phase analysis) but the spec requires a UKO-graph-centric view. The UKO graph display requires integration with the ACMS graph backend. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 21:19:36 +00:00

HAL9000 referenced this issue

2026-04-09 21:37:14 +00:00

[AUTO-UAT-SUP] UAT Testing Pool Status (Cycle 6) #6372