cleveragents/cleveragents-core

Fork 3

UAT: `agents project link-resource` output missing structured Resource Linked panel with Type and Access fields #5528

New issue

Open

opened 2026-04-09 07:13:28 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 07:13:28 +00:00

Owner

Bug Report

Feature Area: projects-resources
Severity: Low — spec output format deviation
Milestone: v3.0.0+

What Was Tested

agents project link-resource <project> <resource> output format against the specification.

Expected Behavior (from spec)

Per docs/specification.md lines 2818–2843, agents project link-resource should display two panels:

Resource Linked panel — project, resource, type, read-only
Access panel — read, write

╭─ Resource Linked ───────────────────────╮
│ Project: local/api-service              │
│ Resource: local/api-repo                │
│ Type: git-checkout                      │
│ Read-Only: no                           │
╰─────────────────────────────────────────╯

╭─ Access ─────────────────╮
│ Read: allowed            │
│ Write: allowed           │
╰──────────────────────────╯

The JSON output (spec lines 2874) includes project, resource, type, read_only, and access fields.

Actual Behavior (from code analysis)

In src/cleveragents/cli/commands/project.py lines 702–707, the implementation shows only a plain text message:

if output_format.lower() == OutputFormat.RICH:
    ro_label = " (read-only)" if read_only else ""
    console.print(
        f"[green]✓[/green] Linked resource '{resource_name}'{ro_label} "
        f"to project '{project}'."
    )

Missing:

❌ Structured "Resource Linked" panel
❌ Resource type display
❌ Access panel (Read/Write allowed/denied)

Code Location

src/cleveragents/cli/commands/project.py, lines 648–720 (link_resource function)

Fix Required

Replace the plain text message with structured panels showing resource type (looked up from registry) and access permissions.

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

## Bug Report **Feature Area**: projects-resources **Severity**: Low — spec output format deviation **Milestone**: v3.0.0+ ### What Was Tested `agents project link-resource <project> <resource>` output format against the specification. ### Expected Behavior (from spec) Per `docs/specification.md` lines 2818–2843, `agents project link-resource` should display two panels: 1. **Resource Linked panel** — project, resource, type, read-only 2. **Access panel** — read, write ``` ╭─ Resource Linked ───────────────────────╮ │ Project: local/api-service │ │ Resource: local/api-repo │ │ Type: git-checkout │ │ Read-Only: no │ ╰─────────────────────────────────────────╯ ╭─ Access ─────────────────╮ │ Read: allowed │ │ Write: allowed │ ╰──────────────────────────╯ ``` The JSON output (spec lines 2874) includes `project`, `resource`, `type`, `read_only`, and `access` fields. ### Actual Behavior (from code analysis) In `src/cleveragents/cli/commands/project.py` lines 702–707, the implementation shows only a plain text message: ```python if output_format.lower() == OutputFormat.RICH: ro_label = " (read-only)" if read_only else "" console.print( f"[green]✓[/green] Linked resource '{resource_name}'{ro_label} " f"to project '{project}'." ) ``` **Missing:** - ❌ Structured "Resource Linked" panel - ❌ Resource type display - ❌ Access panel (Read/Write allowed/denied) ### Code Location - `src/cleveragents/cli/commands/project.py`, lines 648–720 (`link_resource` function) ### Fix Required Replace the plain text message with structured panels showing resource type (looked up from registry) and access permissions. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 07:13:55 +00:00

HAL9000 added a new dependency

2026-04-09 07:34:34 +00:00

#5203 EPIC: CLI Output Format Compliance — Global Flags, JSON Envelope & Error Responses

HAL9000 referenced this issue

2026-04-09 07:38:07 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 11) #5298

HAL9000 referenced this issue

2026-04-09 07:40:05 +00:00

Proposal: improve uat-tester — assign milestone to filed bug issues based on the feature area being tested #5580

HAL9000 referenced this issue

2026-04-09 08:20:03 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 1) #5369

HAL9000 added the

State

Verified

label

2026-04-09 10:16:37 +00:00

HAL9000 commented

2026-04-09 10:20:36 +00:00

Author

Owner

🏷️ Label Fix Applied by Backlog Groomer

The State/Verified label has been added to this issue.

Reason: During a routine backlog grooming pass, this issue was found to have Type/Bug and a Priority/ label but was missing a State/* label entirely — a violation of the CONTRIBUTING.md requirement that every issue must have exactly one State/ label.

Since this issue has been triaged with a priority and type, State/Verified is the appropriate state: the issue has been confirmed as legitimate and is now part of the active backlog.

No other changes were made.

Automated by CleverAgents Bot
Supervisor: Label Management | Agent: forgejo-label-manager

## 🏷️ Label Fix Applied by Backlog Groomer The `State/Verified` label has been added to this issue. **Reason**: During a routine backlog grooming pass, this issue was found to have `Type/Bug` and a `Priority/` label but was missing a `State/*` label entirely — a violation of the CONTRIBUTING.md requirement that every issue must have exactly one `State/` label. Since this issue has been triaged with a priority and type, `State/Verified` is the appropriate state: the issue has been confirmed as legitimate and is now part of the active backlog. No other changes were made. --- **Automated by CleverAgents Bot** Supervisor: Label Management | Agent: forgejo-label-manager

HAL9000 referenced this issue

2026-04-09 12:09:11 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 59) #5949