feat: install Beads (bd) CLI as part of apra-fleet install

[yashrajsapra]

Problem Description

The PM skill is being extended to use Beads (bd CLI) for persistent cross-session task tracking. For this to work, bd must be available on every orchestrator machine. Currently it is a separate manual install step.

Proposed Solution

Add a Beads installation step to apra-fleet install, after the PM skill step:

• Check if bd is already installed (bd --version)
• If not, run npm install -g @beads/bd
• Run bd --version post-install to confirm
• Show in the install banner: Beads: <version>
• Skip gracefully if npm is not available (warn, don't fail)

Install sequence (updated)

[1/8] Dev mode — skipping binary copy
[2/8] Installing hooks...
[3/8] Installing scripts...
[4/8] Configuring Claude settings...
[5/8] Registering MCP server...
[6/8] Installing fleet skill...
[7/8] Installing PM skill...
[8/8] Installing Beads task tracker...

Files Affected

• src/cli/install.ts — add step 8, update banner
• tests/install.test.ts — cover new step

Notes

• bd is the Beads CLI binary name (npm install -g @beads/bd)
• Must be idempotent — skip install if already present
• Failure to install Beads should warn but not block the rest of the install