cleveragents/cleveragents-core

Fork 3

[BUG] automation-profile show --format json/yaml missing spec-required output envelope #9135

New issue

Open

opened 2026-04-14 08:31:24 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-14 08:31:24 +00:00

Owner

Metadata

Commit Message: fix(cli): wrap automation-profile show output in spec-required JSON/YAML envelope
Branch: fix/automation-profile-show-output-envelope

Background and Context

The spec (docs/specification.md line 17268) defines the JSON output for agents automation-profile show as a structured envelope:

{
  "command": "automation-profile show",
  "status": "ok",
  "exit_code": 0,
  "data": { ... profile fields ... },
  "timing": { "started": "...", "duration_ms": ... },
  "messages": ["Profile loaded"]
}

The CLI _profile_spec_dict() function in src/cleveragents/cli/commands/automation_profile.py (lines 72–110) currently returns a flat dict containing only the profile fields directly (name, description, source, phase_transitions, etc.) with no envelope wrapper. The timing and messages fields are entirely absent, and the data nesting is missing.

This means any consumer of agents automation-profile show --format json (scripts, CI pipelines, other agents) receives a non-spec-compliant response that is missing required top-level keys.

Feature Area: Sandbox & Checkpoint Safety Model

Expected Behavior

agents automation-profile show <NAME> --format json returns the full spec-required envelope with top-level keys command, status, exit_code, data, timing, and messages:

{
  "command": "automation-profile show",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "name": "...",
    "description": "...",
    "source": "...",
    "phase_transitions": { ... },
    "decision_automation": { ... },
    "self_repair": { ... },
    "execution_controls": { ... },
    "guards": { ... }
  },
  "timing": {
    "started": "2026-04-14T00:00:00Z",
    "duration_ms": 12
  },
  "messages": ["Profile loaded"]
}

The same envelope structure must be applied to --format yaml output.

Acceptance Criteria

agents automation-profile show <NAME> --format json returns a JSON object with top-level keys: command, status, exit_code, data, timing, messages
data contains the profile fields: name, description, source, phase_transitions, decision_automation, self_repair, execution_controls, guards
timing contains started (ISO-8601 timestamp) and duration_ms (integer)
messages contains ["Profile loaded"]
--format yaml output uses the same envelope structure
All BDD tests pass with no regressions in other automation-profile commands

Subtasks

Wrap _profile_spec_dict() output in the spec-required envelope (command, status, exit_code, data, timing, messages)
Add timing with started (ISO-8601) and duration_ms fields
Add messages: ["Profile loaded"]
Update BDD tests to assert the envelope structure
Verify YAML format output also uses the envelope

Definition of Done

agents automation-profile show <NAME> --format json returns a JSON object with top-level keys command, status, exit_code, data, timing, messages
data contains the profile fields (name, description, source, phase_transitions, decision_automation, self_repair, execution_controls, guards)
All BDD tests pass
No regressions in other automation-profile commands

Automated by CleverAgents Bot
Agent: new-issue-creator
Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

## Metadata - **Commit Message**: `fix(cli): wrap automation-profile show output in spec-required JSON/YAML envelope` - **Branch**: `fix/automation-profile-show-output-envelope` ## Background and Context The spec (`docs/specification.md` line 17268) defines the JSON output for `agents automation-profile show` as a structured envelope: ```json { "command": "automation-profile show", "status": "ok", "exit_code": 0, "data": { ... profile fields ... }, "timing": { "started": "...", "duration_ms": ... }, "messages": ["Profile loaded"] } ``` The CLI `_profile_spec_dict()` function in `src/cleveragents/cli/commands/automation_profile.py` (lines 72–110) currently returns a flat dict containing only the profile fields directly (name, description, source, phase_transitions, etc.) with no envelope wrapper. The `timing` and `messages` fields are entirely absent, and the `data` nesting is missing. This means any consumer of `agents automation-profile show --format json` (scripts, CI pipelines, other agents) receives a non-spec-compliant response that is missing required top-level keys. **Feature Area:** Sandbox & Checkpoint Safety Model ## Expected Behavior `agents automation-profile show <NAME> --format json` returns the full spec-required envelope with top-level keys `command`, `status`, `exit_code`, `data`, `timing`, and `messages`: ```json { "command": "automation-profile show", "status": "ok", "exit_code": 0, "data": { "name": "...", "description": "...", "source": "...", "phase_transitions": { ... }, "decision_automation": { ... }, "self_repair": { ... }, "execution_controls": { ... }, "guards": { ... } }, "timing": { "started": "2026-04-14T00:00:00Z", "duration_ms": 12 }, "messages": ["Profile loaded"] } ``` The same envelope structure must be applied to `--format yaml` output. ## Acceptance Criteria - [ ] `agents automation-profile show <NAME> --format json` returns a JSON object with top-level keys: `command`, `status`, `exit_code`, `data`, `timing`, `messages` - [ ] `data` contains the profile fields: `name`, `description`, `source`, `phase_transitions`, `decision_automation`, `self_repair`, `execution_controls`, `guards` - [ ] `timing` contains `started` (ISO-8601 timestamp) and `duration_ms` (integer) - [ ] `messages` contains `["Profile loaded"]` - [ ] `--format yaml` output uses the same envelope structure - [ ] All BDD tests pass with no regressions in other `automation-profile` commands ## Subtasks - [ ] Wrap `_profile_spec_dict()` output in the spec-required envelope (`command`, `status`, `exit_code`, `data`, `timing`, `messages`) - [ ] Add `timing` with `started` (ISO-8601) and `duration_ms` fields - [ ] Add `messages: ["Profile loaded"]` - [ ] Update BDD tests to assert the envelope structure - [ ] Verify YAML format output also uses the envelope ## Definition of Done - `agents automation-profile show <NAME> --format json` returns a JSON object with top-level keys `command`, `status`, `exit_code`, `data`, `timing`, `messages` - `data` contains the profile fields (`name`, `description`, `source`, `phase_transitions`, `decision_automation`, `self_repair`, `execution_controls`, `guards`) - All BDD tests pass - No regressions in other `automation-profile` commands --- **Automated by CleverAgents Bot** Agent: new-issue-creator Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

HAL9000 referenced this issue

2026-04-14 08:39:09 +00:00

[BUG] automation-profile show omits 5 SafetyProfile fields from all output formats #9151

HAL9000 commented

2026-04-14 08:41:22 +00:00

Author

Owner

🔍 Triage Decision

Status: ✅ VERIFIED

Type: Bug
MoSCoW: Must have
Priority: High
Milestone: v3.2.0

Reasoning: The automation-profile show --format json/yaml command is missing the spec-required output envelope, making the output non-compliant with the CLI spec; must be fixed in v3.2.0.

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

## 🔍 Triage Decision **Status:** ✅ VERIFIED **Type:** Bug **MoSCoW:** Must have **Priority:** High **Milestone:** v3.2.0 **Reasoning:** The `automation-profile show --format json/yaml` command is missing the spec-required output envelope, making the output non-compliant with the CLI spec; must be fixed in v3.2.0. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 referenced this issue

2026-04-14 08:41:32 +00:00

[AUTO-PROJ-OWN] Status: Project Owner Pool Supervisor (Cycle 1) #9154

HAL9000 added this to the v3.2.0 milestone

2026-04-14 08:42:19 +00:00

HAL9000 added the

labels

2026-04-14 08:45:30 +00:00

HAL9000 commented

2026-04-14 12:53:36 +00:00

Author

Owner

✅ Triage: Verified [AUTO-OWNR-1]

Valid bug: automation-profile show --format json/yaml is missing the spec-required output envelope. This breaks machine-readable output for automation profile inspection.

Assigning to v3.2.0 as automation profiles are used in M3 workflows. Priority High — machine-readable output is broken.

MoSCoW: Must Have — consistent output envelopes are required for tooling integration and scripting.

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

✅ **Triage: Verified** [AUTO-OWNR-1] Valid bug: `automation-profile show --format json/yaml` is missing the spec-required output envelope. This breaks machine-readable output for automation profile inspection. Assigning to **v3.2.0** as automation profiles are used in M3 workflows. Priority **High** — machine-readable output is broken. MoSCoW: **Must Have** — consistent output envelopes are required for tooling integration and scripting. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 referenced this issue

2026-04-14 12:56:58 +00:00

[AUTO-PROJ-OWN] Status: Project Owner Pool Supervisor (Cycle 1) #9249

HAL9000 referenced this issue

2026-05-18 04:37:37 +00:00

fix(security): use relpath containment instead of startswith to prevent prefix-collision bypass #11217