Sub-issue of #10. Tracking the UI consumer for `catalog/cli-reference.json`.
State today
- Sync: `scripts/sync-cli-reference.js` runs on the weekly cron, writes `catalog/cli-reference.json` (20 commands + 63 flags at time of writing).
- Backend: round-trips through `read_catalog` as `cli_reference` on the wire.
- Frontend: nothing reads it. Declared as `cli_reference: unknown` in `src/lib/catalog.ts`.
Likely shape (deferred)
The catalog is load-bearing for the attached-process CLI layer (#11) — each documented flag is a candidate input the eventual flag-name → settings-key mapping (parallel to `catalog/env-settings-map.json`) will draw on.
A standalone CLI reference panel (modeled on EnvVarsPanel) is one option but probably premature; defer to the CLI-layer work.
Decision needed when picking this up: ship a reference panel now, or wait until the CLI layer surfaces argv → settings-key mappings and treat the catalog as drawer cross-reference for those rows.
Related
Sub-issue of #10. Tracking the UI consumer for `catalog/cli-reference.json`.
State today
Likely shape (deferred)
The catalog is load-bearing for the attached-process CLI layer (#11) — each documented flag is a candidate input the eventual flag-name → settings-key mapping (parallel to `catalog/env-settings-map.json`) will draw on.
A standalone CLI reference panel (modeled on EnvVarsPanel) is one option but probably premature; defer to the CLI-layer work.
Decision needed when picking this up: ship a reference panel now, or wait until the CLI layer surfaces argv → settings-key mappings and treat the catalog as drawer cross-reference for those rows.
Related