UAT: `agents project link-resource` JSON output missing spec-required `resource_linked`, `access`, and `indexing` sections #6494

New issue

Open

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

HAL9000 commented

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

Owner

Bug Report

Feature Area

Resource System — agents project link-resource JSON output format

Spec Reference

docs/specification.md §2870–2898 (agents project link-resource JSON output)

From spec §2872–2898:

{
  "command": "agents project link-resource local/api-service local/api-repo",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "resource_linked": {
      "project": "local/api-service",
      "resource": "local/api-repo",
      "type": "git-checkout",
      "read_only": false
    },
    "access": {
      "read": "allowed",
      "write": "allowed",
      "apply": "requires approval"
    },
    "indexing": {
      "status": "indexing",
      "files_found": 347,
      "language": "Python (primary)",
      "estimated_time_seconds": 20
    }
  },
  "timing": { "duration_ms": 92 },
  "messages": [{ "level": "ok", "text": "Resource linked to project" }]
}

Expected Behavior (from spec)

The JSON output of agents project link-resource should include:

data.resource_linked with project, resource, type, read_only
data.access with read, write, apply permissions
data.indexing with status, files_found, language, estimated_time_seconds
command field set to the full command string

Actual Behavior

Running agents project link-resource local/test-project local/my-repo --format json produces:

{
  "command": "",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "project": "local/test-project",
    "resource_id": "01KNKJY4X9K7ZDNEK7M6TKJTDG",
    "resource_name": "local/my-repo",
    "read_only": false,
    "alias": null
  },
  "timing": {"duration_ms": 0},
  "messages": [{"level": "ok", "text": "ok"}]
}

Issues:

❌ data.resource_linked section missing — flat structure instead of nested resource_linked
❌ data.access section missing entirely
❌ data.indexing section missing entirely
❌ data.type field missing (resource type not included)
❌ command field is empty string instead of the full command
❌ data.resource_id (ULID) instead of data.resource (name)

Code Location

src/cleveragents/cli/commands/project.py — project_link_resource() command — uses flat dict instead of spec-required nested structure

Steps to Reproduce

agents project link-resource local/test-project local/my-repo --format json

Observe: flat dict without resource_linked, access, or indexing sections.

Severity

Medium — downstream automation tools that parse agents project link-resource --format json output will fail to find the data.resource_linked, data.access, and data.indexing keys defined in the spec.

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

## Bug Report ### Feature Area Resource System — `agents project link-resource` JSON output format ### Spec Reference `docs/specification.md` §2870–2898 (`agents project link-resource` JSON output) From spec §2872–2898: ```json { "command": "agents project link-resource local/api-service local/api-repo", "status": "ok", "exit_code": 0, "data": { "resource_linked": { "project": "local/api-service", "resource": "local/api-repo", "type": "git-checkout", "read_only": false }, "access": { "read": "allowed", "write": "allowed", "apply": "requires approval" }, "indexing": { "status": "indexing", "files_found": 347, "language": "Python (primary)", "estimated_time_seconds": 20 } }, "timing": { "duration_ms": 92 }, "messages": [{ "level": "ok", "text": "Resource linked to project" }] } ``` ### Expected Behavior (from spec) The JSON output of `agents project link-resource` should include: 1. `data.resource_linked` with `project`, `resource`, `type`, `read_only` 2. `data.access` with `read`, `write`, `apply` permissions 3. `data.indexing` with `status`, `files_found`, `language`, `estimated_time_seconds` 4. `command` field set to the full command string ### Actual Behavior Running `agents project link-resource local/test-project local/my-repo --format json` produces: ```json { "command": "", "status": "ok", "exit_code": 0, "data": { "project": "local/test-project", "resource_id": "01KNKJY4X9K7ZDNEK7M6TKJTDG", "resource_name": "local/my-repo", "read_only": false, "alias": null }, "timing": {"duration_ms": 0}, "messages": [{"level": "ok", "text": "ok"}] } ``` **Issues:** 1. ❌ `data.resource_linked` section missing — flat structure instead of nested `resource_linked` 2. ❌ `data.access` section missing entirely 3. ❌ `data.indexing` section missing entirely 4. ❌ `data.type` field missing (resource type not included) 5. ❌ `command` field is empty string instead of the full command 6. ❌ `data.resource_id` (ULID) instead of `data.resource` (name) ### Code Location - `src/cleveragents/cli/commands/project.py` — `project_link_resource()` command — uses flat dict instead of spec-required nested structure ### Steps to Reproduce ```bash agents project link-resource local/test-project local/my-repo --format json ``` Observe: flat dict without `resource_linked`, `access`, or `indexing` sections. ### Severity Medium — downstream automation tools that parse `agents project link-resource --format json` output will fail to find the `data.resource_linked`, `data.access`, and `data.indexing` keys defined in the spec. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

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

HAL9000 referenced this issue

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

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