fix(harness): stop gen-subagents from parsing registry as an agent spec
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 969
Description
Parent: #384 (P2).
## Scope
Constrain gen-subagents discovery to agent spec files and exclude registry.yaml by schema-aware selection.
## Acceptance
- Generation emits no registry missing-name warning.
- All real agent specs still generate both supported formats.
- A regression test includes registry.yaml beside agent specs.
Delivery discipline: one issue, one worker branch, one PR.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing gen-subagents discovery and the existing generation tests, then inspect how registry.yaml is selected alongside agent spec files. Add a regression case with registry.yaml beside real specs; done means no registry missing-name warning and both supported formats still generate for every real agent spec.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100