Generate shell-completion command sets from route metadata #1527

ORG_PROJECT_COMMANDS and ORG_ONLY_COMMANDS in packages/cli/src/lib/complete.ts are hand-maintained. Every new org- or project-scoped command has to be added by hand (e.g. integration list/delete in #1523), and the only guard is the drift test in test/lib/completions.property.test.ts, which fails after the fact.

Why it's manual today: the __complete fast path deliberately skips the Stricli boot (see the complete.ts header), so it can't walk the route tree at runtime.

Proposal: generate both sets at build time from the route tree, like the other script/generate-*.ts outputs, and import the generated module from complete.ts.

• Classify commands from positional metadata instead of the current heuristic (placeholder mentions org, or is issue). An explicit per-command target kind (org-only vs org/project) would be more reliable than parsing placeholder text.
• Keep the special cases (project create) explicit.
• Replace the drift test with a check that the generated file is current.

Raised in review of #1523: #1523 (comment)

via Junior system actor event.

--

View Junior Session [Sentry]