registrystack / registrystack/registry-stack
caseworkctl init --template should publish its possible values
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 130
Description
## Problem
`caseworkctl init --template` accepts a free-form string and lists no possible
values in its generated command metadata. Invalid values are rejected only after
argument parsing. This differs from the closed template catalog now published by
`bregctl init --template`.
## Expected
- Publish the maintained Casework template ids as possible values in Clap and the
generated CLI reference.
- Keep template selection backed by the owning starter catalog rather than a
duplicated list.
- Add command-metadata and invalid-value regression coverage.
Found while reviewing #1016. The behavior predates that pull request.
Contributor guide
Research direction
Start at the caseworkctl init --template command definition and its owning starter catalog, then compare the published metadata with bregctl init --template. Add command-metadata and invalid-value regression coverage. Done means maintained Casework template ids appear as Clap and generated-reference possible values while selection still uses the owning catalog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100