You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Specify and verify CLI behavior before adding command routes #1297
A maintainer can compare CLI router changes against a recorded baseline and tell an intentional command change from a regression.
Current gap
The #1292 pilots found multiple command rosters and a pinned Deno case where adding --plugin changes routing for session and sidekick. Decide the intended behavior before using the current behavior as a contract.
Acceptance
Record the Architect’s decisions on routing, help, and startup order. Cover default document shorthand, flags and malformed invocations, normalized execution-plugin command names, and routing with and without --plugin.
Verify that help and version avoid execution-plugin loading and that REPL argument and project admission precede loading those plugins or acquiring terminal resources.
Run the affected CLI checks on Deno, Node, and Bun. The design pilot’s 35-row baseline was Deno-only.
Source used by the #1292 pilots was 6e1075c4189737011bf9c9b949218877966e9a39. Exact Configliere candidate qualification can proceed in parallel through #796 and #802. Test the exact artifact against argv/help, document-derived props, nested routes, and emitted npm and compiled binaries. An approved upgrade gets its own PR and becomes a router prerequisite only if it preserves behavior and materially simplifies the work.
Activity