cleveragents/cleveragents-core

Fork 3

UAT: `register_resource()` never triggers auto-discovery — child resources not created on `agents resource add` #4831

New issue

Open

opened 2026-04-08 19:58:50 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-08 19:58:50 +00:00

Owner

Bug Report

Feature Area: Resource Registry — auto-discovery on resource registration

Severity: Medium — auto-discovery is a core spec feature; child resources are never created

What Was Tested

ResourceInstanceMixin.register_resource() in src/cleveragents/application/services/_resource_registry_ops.py and the auto-discovery infrastructure in src/cleveragents/resource/handlers/discovery.py.

Expected Behavior (from spec, lines 10564, 10599)

Resources form a directed acyclic graph (DAG) with parent/child relationships, and child resources are often auto-discovered when a parent resource is registered.

The command returns the name and ULID of the newly created resource. Auto-discovered child resources are created automatically with ULIDs only (no names).

When agents resource add git-checkout local/api-repo --path /path is run, the system should:

Register the parent resource
Trigger auto-discovery (scan the path for git objects, fs-directories, devcontainers, etc.)
Create child resources with ULIDs only (no names)
Return the count of discovered children

Actual Behavior (from code)

register_resource() in _resource_registry_ops.py creates the ResourceModel and returns immediately — no auto-discovery is triggered:

# register_resource() ends here — no auto-discovery call
return Resource(
    resource_id=resource_id,
    name=name,
    ...
)

The discover_devcontainers() function exists in src/cleveragents/resource/handlers/discovery.py but is never called from register_resource(). Issue #4740 already tracks the devcontainer-specific wiring gap; this issue covers the broader auto-discovery gap for all resource types (git-checkout, fs-mount, fs-directory).

Code Location

src/cleveragents/application/services/_resource_registry_ops.py — register_resource() — missing auto-discovery call after resource creation
src/cleveragents/resource/handlers/discovery.py — discover_devcontainers() — exists but not wired
src/cleveragents/resource/handlers/git_checkout.py — GitCheckoutHandler — should provide git auto-discovery
src/cleveragents/resource/handlers/fs_directory.py — FsDirectoryHandler — should provide fs auto-discovery

Steps to Reproduce

Register a git-checkout resource pointing to a real git repo
Run agents resource list --all
Expected: hundreds of child resources (git objects, fs entries)
Actual: only the parent resource appears

Impact

agents resource add output shows "0 child resources discovered" (or no count at all)
agents resource tree shows no children for newly registered resources
Auto-discovery panel in agents resource add output is never populated

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

## Bug Report **Feature Area:** Resource Registry — auto-discovery on resource registration **Severity:** Medium — auto-discovery is a core spec feature; child resources are never created --- ## What Was Tested `ResourceInstanceMixin.register_resource()` in `src/cleveragents/application/services/_resource_registry_ops.py` and the auto-discovery infrastructure in `src/cleveragents/resource/handlers/discovery.py`. ## Expected Behavior (from spec, lines 10564, 10599) > Resources form a directed acyclic graph (DAG) with parent/child relationships, and child resources are often **auto-discovered when a parent resource is registered**. > The command returns the name and ULID of the newly created resource. **Auto-discovered child resources are created automatically with ULIDs only (no names).** When `agents resource add git-checkout local/api-repo --path /path` is run, the system should: 1. Register the parent resource 2. Trigger auto-discovery (scan the path for git objects, fs-directories, devcontainers, etc.) 3. Create child resources with ULIDs only (no names) 4. Return the count of discovered children ## Actual Behavior (from code) `register_resource()` in `_resource_registry_ops.py` creates the `ResourceModel` and returns immediately — **no auto-discovery is triggered**: ```python # register_resource() ends here — no auto-discovery call return Resource( resource_id=resource_id, name=name, ... ) ``` The `discover_devcontainers()` function exists in `src/cleveragents/resource/handlers/discovery.py` but is **never called** from `register_resource()`. Issue #4740 already tracks the devcontainer-specific wiring gap; this issue covers the broader auto-discovery gap for all resource types (git-checkout, fs-mount, fs-directory). ## Code Location - `src/cleveragents/application/services/_resource_registry_ops.py` — `register_resource()` — missing auto-discovery call after resource creation - `src/cleveragents/resource/handlers/discovery.py` — `discover_devcontainers()` — exists but not wired - `src/cleveragents/resource/handlers/git_checkout.py` — `GitCheckoutHandler` — should provide git auto-discovery - `src/cleveragents/resource/handlers/fs_directory.py` — `FsDirectoryHandler` — should provide fs auto-discovery ## Steps to Reproduce 1. Register a git-checkout resource pointing to a real git repo 2. Run `agents resource list --all` 3. Expected: hundreds of child resources (git objects, fs entries) 4. Actual: only the parent resource appears ## Impact - `agents resource add` output shows "0 child resources discovered" (or no count at all) - `agents resource tree` shows no children for newly registered resources - Auto-discovery panel in `agents resource add` output is never populated --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-08 20:08:52 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 referenced this issue

2026-04-08 20:22:25 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 added the

labels

2026-04-08 22:59:48 +00:00

HAL9000 commented

2026-04-09 03:02:38 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — spec compliance bug identified by UAT testing
Story Points: 3 (M) — targeted fix to align implementation with spec
MoSCoW: Must Have — spec compliance is required for correct system behavior

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — spec compliance bug identified by UAT testing - **Story Points**: 3 (M) — targeted fix to align implementation with spec - **MoSCoW**: Must Have — spec compliance is required for correct system behavior --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels

2026-04-09 03:02:44 +00:00

HAL9000 added this to the v3.5.0 milestone