chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

aicodeman@1.29.0

Minor Changes

• c5c015d: install.sh and the Docker agent image now read the shipped CLI catalogue instead of
  hand-maintaining their own lists.

  Adding a CLI to src/config/cli-registry/stock.ts and running
  npm run generate:cli-catalog wires it into the installer's detection, its install menu and
  its closing reminder, and into the agent image's npm layer. Previously each of those was a
  separate hand-written list that had to be kept in step and was not: upstream b6d0f1fa is
  "wire OMP into install.sh's CLI detection (it had none)", where a user with only omp
  installed was told no AI CLI was found and offered Claude Code, and the section comment above
  that code named six of the nine CLIs.

  The generator emits two committed artifacts, because neither consumer can import TypeScript:
  config/clis.stock.json for the Docker build, and a marked block inside install.sh itself,
  which runs via curl | bash before any checkout exists. The embedded copy is the FULL
  catalogue: an earlier attempt fetched it and fell back to a hardcoded two-CLI list, degrading
  silently on an empty response, and there is no degraded mode to fall into now — nor a network
  fetch at all, since a curl | bash from master already carries a catalogue exactly as fresh as
  the script itself.

  Trust model is unchanged and now mechanical. The server still never executes an entry's
  install command. install.sh executes only commands embedded in itself — same file, same TLS
  fetch, same commit as the curl | bash line that fetched it — and nothing pulled from the
  network at install time is ever run, because nothing is fetched at install time at all.

  The agent image respects enabled. The generated catalogue carries that flag, so a CLI
  shipping disabled is no longer baked into every image. It reads the stock catalogue rather than
  the merged registry, so a user's ~/.codeman/clis.json cannot change what is inside an image
  tagged codeman/agent:base.

  User-visible changes, all in the installer:

  • The install menu is built from the catalogue, so it offers every enabled CLI with an install command that can drive a pane on its own — eight today, rather than the previous fixed two. Gemini had a command in the registry and appeared in no list in the script at all. DeepSeek is the one enabled CLI with a registry command that is deliberately NOT offered: npm install -g @deepseek-ai/dsh installs only the launcher, which ships no profile that can drive a terminal on its own, so choosing it used to leave the user with an AI CLI the installer considered "found" but that could not actually run anything. It still gets a hint pointing at its docs.
  • Its entries use the registry's labels ("Claude" rather than "Claude Code"), the same trade already made for codeman doctor rows. A suffix map would just be the hand-maintained list again.
  • On a wget-only host, only the menu entries that actually need curl are held back (still shown as copy-paste hints); the npm install -g entries, which never needed it, are unaffected. Rewriting curl to wget inside a string about to be executed is the wrong instinct either way.
  • CODEMAN_NONINTERACTIVE=1 still defaults to Claude Code, unchanged.

  install.sh remains bash 3.2 compatible (macOS ships it): parallel indexed arrays with
  offset/length windows instead of delimiters, no associative arrays, namerefs, mapfile or
  here-strings. CI now runs bash -n, executes the script inside a real bash:3.2 container —
  which is what catches expanding an empty array under set -u, a runtime abort bash -n cannot
  see — and checks the generated artifacts are in sync.

  docker/server.Dockerfile is deliberately untouched; its narrower CLI list is now asserted as
  a declared omission list so the divergence is visible rather than accidental.

[Ark0N]

Superseded by the manual release commit c03714e: master is already at 1.28.2 with .changeset/cli-catalog-consumers.md consumed and its content folded into the 1.28.2 changelog entry (as a patch, with a Thanks section). Merging this would re-apply a narrower changelog and a minor bump on top of a version that has shipped.