Workflow step cannot resolve agent definition from same repo source

[dkliban]

Description

A workflow step that references an agent definition from the same repo source fails with two contradictory errors:

1. Sync Error: Step 'upgrade-dependencies' references unknown agent 'Upgrade Pulp Dependencies'
2. Warning: Step 'upgrade-dependencies' references a disabled agent — enable it in the catalog

The agent definition IS synced and visible via alcove agents list, but the workflow cannot resolve the reference. The two messages also contradict each other — the agent can't be both "unknown" and "disabled".

Screenshot

The Workflows page in the Bridge dashboard shows both errors on the "Pulp Dependency Upgrade Pipeline" workflow.

Steps to Reproduce

1. Create an agent task definition in .alcove/tasks/upgrade-deps.yml:

   name: Upgrade Pulp Dependencies
   description: |
     Upgrades pulpcore and/or plugin versions...
   timeout: 7200
   dev_container:
     image: ghcr.io/pulp/hosted-pulp-dev-env:main
   repos:
     - url: https://github.com/pulp/pulp-service
       ref: main
       name: pulp-service

2. Create a workflow in .alcove/workflows/upgrade-deps-pipeline.yml:

   name: Pulp Dependency Upgrade Pipeline
   workflow:
     - id: upgrade-dependencies
       type: agent
       agent: Upgrade Pulp Dependencies
       outputs: [packages_upgraded, patches_modified, patches_removed, tests_passed, pr_url]

3. Push to the repo and run alcove agents sync

4. alcove agents list shows the agent as synced:

   NAME              DEV_CONTAINER  LAST_SYNCED       SOURCE
   upgrade-deps.yml  no             2026-04-19 18:23  https://github.com/dkliban/pulp-service
   

5. But the Workflows page shows both errors above.

Expected Behavior

The workflow step should resolve the agent reference Upgrade Pulp Dependencies to the synced agent definition from the same repo source.

Additional Notes

• The agent name in alcove agents list shows as upgrade-deps.yml (the filename) rather than the name field value Upgrade Pulp Dependencies — this might be related to the resolution failure.
• There is no alcove agents enable CLI command, and the "enable it in the catalog" link in the UI suggests agent definitions need to go through the catalog system, but the catalog has no mechanism for repo-sourced agent definitions.
• Alcove CLI v0.26.0, Bridge v0.26.0

Environment

• Alcove CLI: v0.26.0
• Bridge: v0.26.0
• Bridge URL: (stage instance)