Diego Rodrigues de Sa e Souza 1a1ef10009 fix(cli): wire the contexts command into the CLI program (#4369) ...

Found by end-to-end testing of remote mode: `omniroute contexts list/current/use`
fell through to `serve` ("too many arguments for 'serve'"). `connect` even tells
users "Switch back to local with: omniroute contexts use default" — a dead command.

Root cause: `bin/cli/commands/contexts.mjs` implements `registerContexts` (with
list/add/use/current/show/remove/rename/export/import), and it had an isolated unit
test using a FAKE program — but `registry.mjs` never imported or called it, so the
command was never wired into the real CLI. Add the import + registration alongside
the other remote-mode commands (connect/tokens/configure).

Regression test: build the REAL program via createProgram() and assert the
top-level contexts/connect/tokens/configure commands exist and that `contexts`
exposes its list/use/current subcommands (RED before, GREEN after). The previous
isolated fake-program test could not catch the missing wiring.

2026-06-20 06:37:49 -03:00

..

cli

fix(cli): wire the contexts command into the CLI program (#4369)

2026-06-20 06:37:49 -03:00

mcp-server.mjs

Release v3.8.24 (#3747)

2026-06-13 17:27:40 -03:00

nodeRuntimeSupport.mjs

fix(infrastructure): move wreq-js to optionalDependencies and add Node 25/26 to secure runtime policy (#1924)

2026-05-04 02:03:20 -03:00

omniroute.mjs

fix(cli): don't write STORAGE_ENCRYPTION_KEY to .env on informational commands (#3129)

2026-06-03 18:53:22 -03:00

reset-password.mjs

Release v3.8.13 (#3327)

2026-06-06 19:13:11 -03:00