UAT: fs-mount built-in resource type not registered in BUILTIN_TYPES — agents resource add fs-mount fails with "Resource type not found" #3501

Closed
opened 2026-04-05 18:41:27 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: fix/fs-mount-builtin-type-registration
  • Commit Message: fix(resource-registry): register fs-mount as built-in resource type in BUILTIN_TYPES
  • Milestone: None (Backlog)
  • Parent Epic: #398

Description

The fs-mount built-in resource type is listed in the specification (docs/specification.md) as a user-addable built-in type, but it is not registered in the BUILTIN_TYPES list in src/cleveragents/application/services/_resource_registry_data.py.

Notably, BUILTIN_TYPE_NAMES in src/cleveragents/domain/models/core/_resource_type_validation.py already includes "fs-mount", confirming the type was intended to be built-in — the registration entry in _resource_registry_data.py was simply never added.

Current Behavior

Running agents resource add fs-mount local/my-mount --path /mnt/data fails with:

Resource type not found: fs-mount

The _GIT_FS_CONTAINER_TYPES list in _resource_registry_data.py contains git-checkout, fs-directory, container-instance, and devcontainer-instance — but fs-mount is absent.

Expected Behavior (from spec)

fs-mount should be a registered built-in resource type with:

Field Value
resource_kind physical
sandbox_strategy copy_on_write
user_addable True
built_in True
cli_args --path (required, path to mount point)
parent_types [] (top-level resource)
child_types ["fs-directory"] (1 required auto-discovered child)
Description "A physical mount point on the local system (e.g., /mnt/data, /home). Represents the mount itself — the filesystem type (ext4, btrfs, etc.) is a property. The root directory is a required auto-discovered fs-directory child."

Affected Files

  • src/cleveragents/application/services/_resource_registry_data.py_GIT_FS_CONTAINER_TYPES list (missing fs-mount entry)
  • src/cleveragents/domain/models/core/_resource_type_validation.pyBUILTIN_TYPE_NAMES frozenset (line 25: "fs-mount" is already listed here, confirming intent)

Backlog note: This issue was discovered during autonomous operation
on milestone v3.6.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Subtasks

  • Add fs-mount entry to _GIT_FS_CONTAINER_TYPES list in _resource_registry_data.py with all required fields (resource_kind, sandbox_strategy, user_addable, built_in, cli_args, parent_types, child_types, description)
  • Verify BUILTIN_TYPE_NAMES in _resource_type_validation.py already includes "fs-mount" (no change needed there)
  • Write BDD scenario in features/ covering agents resource add fs-mount happy path
  • Write BDD scenario covering fs-mount auto-discovery of fs-directory child
  • Run nox -e unit_tests and confirm all scenarios pass
  • Run nox -e integration_tests and confirm agents resource add fs-mount end-to-end
  • Run nox -e coverage_report and confirm coverage >= 97%
  • Run nox -e typecheck and confirm no type errors
  • Run nox -e lint and confirm no lint errors

Definition of Done

  • fs-mount entry added to _GIT_FS_CONTAINER_TYPES in _resource_registry_data.py with all spec-required fields
  • agents resource add fs-mount local/my-mount --path /mnt/data succeeds without error
  • BDD scenarios written and passing for fs-mount registration and child auto-discovery
  • All nox stages pass
  • Coverage >= 97%
  • PR merged to correct branch with correct commit message

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

## Metadata - **Branch**: `fix/fs-mount-builtin-type-registration` - **Commit Message**: `fix(resource-registry): register fs-mount as built-in resource type in BUILTIN_TYPES` - **Milestone**: None (Backlog) - **Parent Epic**: #398 ## Description The `fs-mount` built-in resource type is listed in the specification (`docs/specification.md`) as a user-addable built-in type, but it is **not registered** in the `BUILTIN_TYPES` list in `src/cleveragents/application/services/_resource_registry_data.py`. Notably, `BUILTIN_TYPE_NAMES` in `src/cleveragents/domain/models/core/_resource_type_validation.py` already includes `"fs-mount"`, confirming the type was intended to be built-in — the registration entry in `_resource_registry_data.py` was simply never added. ### Current Behavior Running `agents resource add fs-mount local/my-mount --path /mnt/data` fails with: ``` Resource type not found: fs-mount ``` The `_GIT_FS_CONTAINER_TYPES` list in `_resource_registry_data.py` contains `git-checkout`, `fs-directory`, `container-instance`, and `devcontainer-instance` — but `fs-mount` is absent. ### Expected Behavior (from spec) `fs-mount` should be a registered built-in resource type with: | Field | Value | |---|---| | `resource_kind` | `physical` | | `sandbox_strategy` | `copy_on_write` | | `user_addable` | `True` | | `built_in` | `True` | | `cli_args` | `--path` (required, path to mount point) | | `parent_types` | `[]` (top-level resource) | | `child_types` | `["fs-directory"]` (1 required auto-discovered child) | | Description | "A physical mount point on the local system (e.g., /mnt/data, /home). Represents the mount itself — the filesystem type (ext4, btrfs, etc.) is a property. The root directory is a required auto-discovered fs-directory child." | ### Affected Files - `src/cleveragents/application/services/_resource_registry_data.py` — `_GIT_FS_CONTAINER_TYPES` list (missing `fs-mount` entry) - `src/cleveragents/domain/models/core/_resource_type_validation.py` — `BUILTIN_TYPE_NAMES` frozenset (line 25: `"fs-mount"` is already listed here, confirming intent) > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.6.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Subtasks - [ ] Add `fs-mount` entry to `_GIT_FS_CONTAINER_TYPES` list in `_resource_registry_data.py` with all required fields (`resource_kind`, `sandbox_strategy`, `user_addable`, `built_in`, `cli_args`, `parent_types`, `child_types`, description) - [ ] Verify `BUILTIN_TYPE_NAMES` in `_resource_type_validation.py` already includes `"fs-mount"` (no change needed there) - [ ] Write BDD scenario in `features/` covering `agents resource add fs-mount` happy path - [ ] Write BDD scenario covering `fs-mount` auto-discovery of `fs-directory` child - [ ] Run `nox -e unit_tests` and confirm all scenarios pass - [ ] Run `nox -e integration_tests` and confirm `agents resource add fs-mount` end-to-end - [ ] Run `nox -e coverage_report` and confirm coverage >= 97% - [ ] Run `nox -e typecheck` and confirm no type errors - [ ] Run `nox -e lint` and confirm no lint errors ## Definition of Done - [ ] `fs-mount` entry added to `_GIT_FS_CONTAINER_TYPES` in `_resource_registry_data.py` with all spec-required fields - [ ] `agents resource add fs-mount local/my-mount --path /mnt/data` succeeds without error - [ ] BDD scenarios written and passing for `fs-mount` registration and child auto-discovery - [ ] All nox stages pass - [ ] Coverage >= 97% - [ ] PR merged to correct branch with correct commit message --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-uat-tester
Author
Owner

Closing as duplicate of #3400.

Both issues describe the same bug: fs-mount built-in resource type is missing from BUILTIN_TYPES in _resource_registry_data.py. Issue #3400 is the established tracking issue (v3.6.0 milestone, Priority/Critical, State/Verified, MoSCoW/Must Have). See also #2506 which is the older backlog version. Please track this work in #3400.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Closing as duplicate of #3400. Both issues describe the same bug: `fs-mount` built-in resource type is missing from `BUILTIN_TYPES` in `_resource_registry_data.py`. Issue #3400 is the established tracking issue (v3.6.0 milestone, `Priority/Critical`, `State/Verified`, `MoSCoW/Must Have`). See also #2506 which is the older backlog version. Please track this work in #3400. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#398 Epic: Post-MVP Resources
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#3501
No description provided.