Problem
The chat bridge flag in `setup.sh` is `--chat `, but callers (skills, docs, ad-hoc usage) frequently reach for the more descriptive `--chat-bridge `. The shorter name is unintuitive given the internal variable is `CHAT_BRIDGE` and the concept everywhere else is "chat bridge", not "chat".
Because `--chat-bridge` isn't parsed, bash silently drops through to the default-bridge-for-runtime logic (`cc-connect` for claude-code, `kimaki` for everything else). No warning, no usage error — the user thinks they picked kimaki but the run actually used cc-connect. Discovered while validating #62: the kimaki branch never fired even with `--chat-bridge kimaki` passed, and had to debug with `bash -x` to spot it.
Suggestion
Accept `--chat-bridge` as a synonym for `--chat` in `setup.sh`'s argument parser:
```bash
--chat|--chat-bridge)
CHAT_BRIDGE="$2"
shift 2
;;
```
Keep `--chat` working for backwards compat. Same treatment in `upgrade.sh` if it has the same flag.
Also: consider emitting an `error` (not `warn`) on unknown flags instead of silently falling through to argument-shift defaults. Would have caught this immediately.
Context
Surfaced while validating #62. Not a blocker for that PR (the fix works; the flag is just hard to guess).
Problem
The chat bridge flag in `setup.sh` is `--chat `, but callers (skills, docs, ad-hoc usage) frequently reach for the more descriptive `--chat-bridge `. The shorter name is unintuitive given the internal variable is `CHAT_BRIDGE` and the concept everywhere else is "chat bridge", not "chat".
Because `--chat-bridge` isn't parsed, bash silently drops through to the default-bridge-for-runtime logic (`cc-connect` for claude-code, `kimaki` for everything else). No warning, no usage error — the user thinks they picked kimaki but the run actually used cc-connect. Discovered while validating #62: the kimaki branch never fired even with `--chat-bridge kimaki` passed, and had to debug with `bash -x` to spot it.
Suggestion
Accept `--chat-bridge` as a synonym for `--chat` in `setup.sh`'s argument parser:
```bash
--chat|--chat-bridge)
CHAT_BRIDGE="$2"
shift 2
;;
```
Keep `--chat` working for backwards compat. Same treatment in `upgrade.sh` if it has the same flag.
Also: consider emitting an `error` (not `warn`) on unknown flags instead of silently falling through to argument-shift defaults. Would have caught this immediately.
Context
Surfaced while validating #62. Not a blocker for that PR (the fix works; the flag is just hard to guess).