poomscandClaude Fable 5 34608ce291 feat(bar): support --port for ccs bar with sticky port persistence ...

ccs bar always forced the dashboard onto port 3000 (first free of a
hardcoded candidate list), which collides with other local dev servers, and
bar.json was rewritten to 3000 on every launch.

- `ccs bar [launch] --port N` runs the server on exactly N: reuses a live
  server already on N, moves a running server from another port (SIGTERM via
  server.pid, wait for exit), errors clearly when N is busy or the value is
  invalid.
- The chosen port is persisted into launch.json args, so the Swift app
  self-starts the server on the same port.
- Without --port, launch and serve now try the port recorded in bar.json
  first (sticky), so the server keeps coming back on the port the user last
  chose instead of reverting to 3000.
- Bare flags (`ccs bar --port N`) route to the launch subcommand; --port is
  documented in `ccs bar --help`.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-08 14:09:58 +07:00

..

hardening-inventory.json

feat(bar): support --port for ccs bar with sticky port persistence

2026-08-08 14:09:58 +07:00

hardening-inventory.md

feat(bar): support --port for ccs bar with sticky port persistence

2026-08-08 14:09:58 +07:00

typed-error-exit-code-compat-audit.md

docs(roadmap): replace historical trackers with live guidance

2026-07-26 09:36:00 -04:00