UAT: Devcontainer auto-discovery never registers `devcontainer-instance` children #6291

New issue

Open

opened 2026-04-09 19:52:06 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 19:52:06 +00:00

Owner

Summary

Devcontainer resources are never auto-discovered when registering a git-checkout or fs-directory, so the specs .devcontainer/ detection never materializes devcontainer-instance children.
ResourceRegistryService.register_resource() commits the parent resource and returns without invoking any discovery routine.
Even if discovery were called, the built-in devcontainer type config uses trigger_types/scan_paths, but the repository helper (auto_discover_children) only understands the older enabled/rules schema, so it would still no-op.

Steps to Reproduce

Create a directory that contains .devcontainer/devcontainer.json.
Run agents resource add git-checkout local/test-repo --path /path/to/dir.
Run agents resource list --all or agents resource tree local/test-repo.

Observed

Only the git-checkout resource is registered; no devcontainer-instance or devcontainer-file children are created.
register_resource() in src/cleveragents/application/services/_resource_registry_ops.py (lines 101-175) never calls any discovery helper after inserting the parent resource.
The only discovery helper, auto_discover_children() in src/cleveragents/infrastructure/database/repositories.py (lines 2601-2733), is not invoked anywhere in the application layer.
Devcontainer built-in config in src/cleveragents/application/services/_resource_registry_data.py (lines 247-275) defines auto_discovery with trigger_types/scan_paths, but auto_discover_children() still expects {"enabled": true, "rules": [...]} and immediately returns when rules is missing.

Expected

After registering a resource whose location contains .devcontainer/, the registry should automatically create a devcontainer-instance child (and associated devcontainer-file) linked to the parent per spec requirement 5.
Auto-discovery should be triggered during resource registration (and/or project linking) and support the schema defined for devcontainer types so .devcontainer/ configs are picked up without manual registration.

References

src/cleveragents/application/services/_resource_registry_ops.py (register_resource)
src/cleveragents/application/services/_resource_registry_data.py (devcontainer-instance auto_discovery config)
src/cleveragents/infrastructure/database/repositories.py (auto_discover_children contract)

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

## Summary - Devcontainer resources are never auto-discovered when registering a `git-checkout` or `fs-directory`, so the specs `.devcontainer/` detection never materializes `devcontainer-instance` children. - `ResourceRegistryService.register_resource()` commits the parent resource and returns without invoking any discovery routine. - Even if discovery were called, the built-in devcontainer type config uses `trigger_types`/`scan_paths`, but the repository helper (`auto_discover_children`) only understands the older `enabled`/`rules` schema, so it would still no-op. ## Steps to Reproduce 1. Create a directory that contains `.devcontainer/devcontainer.json`. 2. Run `agents resource add git-checkout local/test-repo --path /path/to/dir`. 3. Run `agents resource list --all` or `agents resource tree local/test-repo`. ## Observed - Only the `git-checkout` resource is registered; no `devcontainer-instance` or `devcontainer-file` children are created. - `register_resource()` in `src/cleveragents/application/services/_resource_registry_ops.py` (lines 101-175) never calls any discovery helper after inserting the parent resource. - The only discovery helper, `auto_discover_children()` in `src/cleveragents/infrastructure/database/repositories.py` (lines 2601-2733), is not invoked anywhere in the application layer. - Devcontainer built-in config in `src/cleveragents/application/services/_resource_registry_data.py` (lines 247-275) defines `auto_discovery` with `trigger_types`/`scan_paths`, but `auto_discover_children()` still expects `{"enabled": true, "rules": [...]}` and immediately returns when `rules` is missing. ## Expected - After registering a resource whose location contains `.devcontainer/`, the registry should automatically create a `devcontainer-instance` child (and associated `devcontainer-file`) linked to the parent per spec requirement 5. - Auto-discovery should be triggered during resource registration (and/or project linking) and support the schema defined for devcontainer types so `.devcontainer/` configs are picked up without manual registration. ## References - `src/cleveragents/application/services/_resource_registry_ops.py` (register_resource) - `src/cleveragents/application/services/_resource_registry_data.py` (`devcontainer-instance` auto_discovery config) - `src/cleveragents/infrastructure/database/repositories.py` (`auto_discover_children` contract) --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

Rows
Columns

UAT: Devcontainer auto-discovery never registers devcontainer-instance children #6291