Add fs-mount ResourceTypeDefinition to _GIT_FS_CONTAINER_TYPES in
_resource_registry_data.py so that bootstrap_builtin_types() seeds it
into the registry at startup.
The fs-mount type was listed in BUILTIN_TYPE_NAMES (validation frozenset)
but had no corresponding type definition in BUILTIN_TYPES, causing:
- 'agents resource type list' to omit fs-mount
- 'agents resource add fs-mount ...' to fail with 'Resource type not found'
- fs-directory to be unable to reference fs-mount as a parent type
Changes:
- Add fs-mount definition to _GIT_FS_CONTAINER_TYPES with correct fields:
name, description, resource_kind=physical, sandbox_strategy=copy_on_write,
user_addable=True, cli_args=[path], parent_types=[], child_types=[fs-directory],
auto_discovery with fs-directory rule, handler=fs_mount:FsMountHandler,
capabilities (read/write/sandbox=True, checkpoint=False)
- Add fs-mount to fs-directory's parent_types so fs-directory can be
nested under an fs-mount resource
- Add BDD scenarios in resource_type_bootstrap_fs_mount.feature covering
registration, user_addable, child_types, parent_types, resource add,
and fs-directory parent resolution
- Add Robot Framework integration tests in resource_type_bootstrap_fs_mount.robot
covering all four acceptance criteria end-to-end
ISSUES CLOSED: #2911
freemo