UAT: `agents validation add` rich output panel missing spec-required `Config` and `Created` fields #4487

New issue

Open

opened 2026-04-08 13:36:30 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-08 13:36:30 +00:00

Owner

Metadata

Branch: fix/validation-add-rich-panel-config-created-fields
Commit Message: fix(cli): add Config, Created, and Capability panel to validation add output
Milestone: v3.8.0
Parent Epic: #4182

Bug Report

Feature Area: Validation CLI — agents validation add

Expected Behavior (from spec)

The spec (CLI Commands > agents validation add) shows that agents validation add should output a rich panel with the following structure:

╭─ Validation Registered ────────────────────────────────╮
│ Name:        local/run-tests                           │
│ Description: Run unit tests with coverage              │
│ Source:      custom                                    │
│ Mode:        required                                  │
│ Config:      ./validations/run-tests.yaml              │
│ Created:     2026-02-09 10:15                          │
╰────────────────────────────────────────────────────────╯

╭─ Capability ────────────────────────╮
│ Read-Only:      true (enforced)     │
│ Checkpointable: false (enforced)    │
│ Timeout:        600s                │
╰─────────────────────────────────────╯

✓ OK Validation registered

The panel must include:

Name, Description, Source, Mode — all present
Config — the path to the YAML config file used to register the validation
Created — the timestamp when the validation was registered
A separate Capability panel showing Read-Only: true (enforced), Checkpointable: false (enforced), and Timeout

Actual Behavior

The implementation in src/cleveragents/cli/commands/validation.py (_print_validation() function) renders a panel with only:

Name
Description
Source
Mode
(optionally) Wraps
(optionally) Transform

Missing fields:

Config — the path to the YAML config file
Created — the registration timestamp
A separate Capability panel showing the enforced read-only constraints

Code Location

src/cleveragents/cli/commands/validation.py — _print_validation() function and _validation_spec_dict() function.

Impact

Users cannot confirm which config file was used to register a validation. The enforced read-only/checkpointable constraints are not displayed, which is important for users to understand the safety guarantees of validations. The spec explicitly shows these fields as part of the registration confirmation.

Steps to Reproduce

Create a validation YAML config file
Run: agents validation add --config ./my-validation.yaml
Observe the output panel is missing Config, Created, and the Capability sub-panel

Subtasks

Inspect _print_validation() and _validation_spec_dict() in src/cleveragents/cli/commands/validation.py
Add Config field (YAML config file path) to the main validation panel output
Add Created field (registration timestamp) to the main validation panel output
Implement a separate Capability panel displaying Read-Only: true (enforced), Checkpointable: false (enforced), and Timeout
Write/update Behave unit tests covering the new panel fields
Verify all nox quality gates pass

Definition of Done

agents validation add output includes Config and Created fields in the main panel
A separate Capability panel is rendered with Read-Only, Checkpointable, and Timeout fields
Output matches the spec example exactly (field names, formatting, enforced labels)
Behave unit tests cover the new fields and the Capability panel
All nox stages pass
Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: new-issue-creator

## Metadata - **Branch**: `fix/validation-add-rich-panel-config-created-fields` - **Commit Message**: `fix(cli): add Config, Created, and Capability panel to validation add output` - **Milestone**: v3.8.0 - **Parent Epic**: #4182 ## Bug Report **Feature Area:** Validation CLI — `agents validation add` ### Expected Behavior (from spec) The spec (CLI Commands > agents validation add) shows that `agents validation add` should output a rich panel with the following structure: ``` ╭─ Validation Registered ────────────────────────────────╮ │ Name: local/run-tests │ │ Description: Run unit tests with coverage │ │ Source: custom │ │ Mode: required │ │ Config: ./validations/run-tests.yaml │ │ Created: 2026-02-09 10:15 │ ╰────────────────────────────────────────────────────────╯ ╭─ Capability ────────────────────────╮ │ Read-Only: true (enforced) │ │ Checkpointable: false (enforced) │ │ Timeout: 600s │ ╰─────────────────────────────────────╯ ✓ OK Validation registered ``` The panel must include: - `Name`, `Description`, `Source`, `Mode` — all present - `Config` — the path to the YAML config file used to register the validation - `Created` — the timestamp when the validation was registered - A separate `Capability` panel showing `Read-Only: true (enforced)`, `Checkpointable: false (enforced)`, and `Timeout` ### Actual Behavior The implementation in `src/cleveragents/cli/commands/validation.py` (`_print_validation()` function) renders a panel with only: - Name - Description - Source - Mode - (optionally) Wraps - (optionally) Transform Missing fields: 1. `Config` — the path to the YAML config file 2. `Created` — the registration timestamp 3. A separate `Capability` panel showing the enforced read-only constraints ### Code Location `src/cleveragents/cli/commands/validation.py` — `_print_validation()` function and `_validation_spec_dict()` function. ### Impact Users cannot confirm which config file was used to register a validation. The enforced read-only/checkpointable constraints are not displayed, which is important for users to understand the safety guarantees of validations. The spec explicitly shows these fields as part of the registration confirmation. ### Steps to Reproduce 1. Create a validation YAML config file 2. Run: `agents validation add --config ./my-validation.yaml` 3. Observe the output panel is missing `Config`, `Created`, and the `Capability` sub-panel ## Subtasks - [ ] Inspect `_print_validation()` and `_validation_spec_dict()` in `src/cleveragents/cli/commands/validation.py` - [ ] Add `Config` field (YAML config file path) to the main validation panel output - [ ] Add `Created` field (registration timestamp) to the main validation panel output - [ ] Implement a separate `Capability` panel displaying `Read-Only: true (enforced)`, `Checkpointable: false (enforced)`, and `Timeout` - [ ] Write/update Behave unit tests covering the new panel fields - [ ] Verify all nox quality gates pass ## Definition of Done - [ ] `agents validation add` output includes `Config` and `Created` fields in the main panel - [ ] A separate `Capability` panel is rendered with `Read-Only`, `Checkpointable`, and `Timeout` fields - [ ] Output matches the spec example exactly (field names, formatting, enforced labels) - [ ] Behave unit tests cover the new fields and the Capability panel - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: new-issue-creator

HAL9000 added this to the v3.8.0 milestone

2026-04-08 13:37:13 +00:00

HAL9000 added a new dependency

2026-04-08 13:37:20 +00:00

#4182 Epic: Legacy CLI command removal and full verification of CLI interface and workflows

HAL9000 added the