UAT: `agents resource add fs-mount` uses `--path` flag instead of spec-required `--mount-path` #6792

New issue

Open

opened 2026-04-10 02:06:33 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-10 02:06:33 +00:00

Owner

What Was Tested

agents resource add fs-mount <NAME> — the type-specific CLI flag for the mount path argument.

Expected Behavior (from spec §agents resource add)

The spec provides the following example for fs-mount resources:

$ agents resource add fs-mount local/docs --mount-path /docs/api-reference

And in another spec location (§24950):

agents resource add fs-mount local/data-volume --mount-path /mnt/data

The spec consistently uses --mount-path as the type-specific flag for fs-mount resources to distinguish it semantically from git-checkout's --path flag.

Actual Behavior

The fs-mount built-in type definition in src/cleveragents/application/services/_resource_registry_data.py registers the CLI argument as:

"cli_args": [
    {
        "name": "path",
        "type": "path",
        "required": True,
        "description": "Path to the mount point.",
    },
],

This generates --path as the flag (same as git-checkout), not --mount-path as the spec requires. Running:

agents resource add fs-mount local/docs --mount-path /docs/api-reference

...would fail with an unrecognized option error. Instead, users must use:

agents resource add fs-mount local/docs --path /docs/api-reference

Steps to Reproduce

Run agents resource type show fs-mount --format json
Observe cli_args[0].name is "path" not "mount-path"
Attempt agents resource add fs-mount local/test --mount-path /tmp/test
Command fails with unrecognized argument error

Impact

All documentation, scripts, and user guides that follow the spec will fail. The inconsistency between fs-mount's --path and git-checkout's --path also loses the semantic clarity intended by the spec (the spec chose --mount-path to distinguish the concepts).

Affected File

src/cleveragents/application/services/_resource_registry_data.py — fs-mount type definition, cli_args[0].name should be "mount-path" not "path".

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

## What Was Tested `agents resource add fs-mount <NAME>` — the type-specific CLI flag for the mount path argument. ## Expected Behavior (from spec §agents resource add) The spec provides the following example for `fs-mount` resources: ``` $ agents resource add fs-mount local/docs --mount-path /docs/api-reference ``` And in another spec location (§24950): ``` agents resource add fs-mount local/data-volume --mount-path /mnt/data ``` The spec consistently uses `--mount-path` as the type-specific flag for `fs-mount` resources to distinguish it semantically from git-checkout's `--path` flag. ## Actual Behavior The `fs-mount` built-in type definition in `src/cleveragents/application/services/_resource_registry_data.py` registers the CLI argument as: ```python "cli_args": [ { "name": "path", "type": "path", "required": True, "description": "Path to the mount point.", }, ], ``` This generates `--path` as the flag (same as `git-checkout`), not `--mount-path` as the spec requires. Running: ```bash agents resource add fs-mount local/docs --mount-path /docs/api-reference ``` ...would fail with an unrecognized option error. Instead, users must use: ```bash agents resource add fs-mount local/docs --path /docs/api-reference ``` ## Steps to Reproduce 1. Run `agents resource type show fs-mount --format json` 2. Observe `cli_args[0].name` is `"path"` not `"mount-path"` 3. Attempt `agents resource add fs-mount local/test --mount-path /tmp/test` 4. Command fails with unrecognized argument error ## Impact All documentation, scripts, and user guides that follow the spec will fail. The inconsistency between `fs-mount`'s `--path` and `git-checkout`'s `--path` also loses the semantic clarity intended by the spec (the spec chose `--mount-path` to distinguish the concepts). ## Affected File `src/cleveragents/application/services/_resource_registry_data.py` — `fs-mount` type definition, `cli_args[0].name` should be `"mount-path"` not `"path"`. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added this to the v3.4.0 milestone

2026-04-10 02:06:39 +00:00

HAL9000 added the

labels

2026-04-10 02:06:43 +00:00

HAL9000 referenced this issue