Bug: cast --name/--role and hire are no-op stubs but exit successfully (v1.0.1) #2191

Environment

Homebrew standalone Squad CLI/SDK 1.0.1, macOS arm64, bundled Node.js v22.20.0. Active squad --version reports 1.0.1.

Version correction: the initial report tested a coexisting npm 0.13.1 installation. Reproduced again through the active Homebrew 1.0.1 command.

Reproduction

In a project with an existing .squad/ team, run:

squad cast --name Probe --role developer
echo $?
squad hire --name Probe --role developer
echo $?

Both commands print:

🎬 Squad cast — team creation wizard starting... (full implementation pending)
   Name: Probe
   Role: developer

Both exit with code 0, without prompting or creating an agent. Verified that fixture files remained unchanged. Bare squad hire also reaches the stub; bare squad cast correctly lists the existing roster.

Expected / suggested fix

squad cast --help advertises adding an agent and launching a creation wizard. Wire that creation path, or return a clear unsupported error with a nonzero exit status and correct the help until implemented. Add a regression test that checks persisted agent creation rather than console output alone.

Source

cli-entry.ts at v1.0.1, lines 799–820: the creation branch only logs the placeholder/name/role and returns.