chore(release): 0.8.0

[colevels]

Version bump for the release, per the two-step flow in CLAUDE.md → Releasing
(bump via PR → squash-merge → tag main).

Why 0.8.0 and not 0.7.0

package.json already said 0.7.0, but v0.7.0 was never tagged — the bump
landed on main and no release was ever cut, so no user received it. Users are
still on v0.6.0.

Rather than backfill a release nobody is waiting for, 0.7.0's content ships as
part of 0.8.0. Users jump 0.6.0 → 0.8.0 and get both:

• the command-surface subtraction (tabs check/push/watch/history/prompt gone,
  --port/--out/--variant gone, three tabs commands left)
• the bridge work from feat(tabs): fall back to port 49228, and prove the bridge is ours #35 — fallback port 49228, service: "tabbrew-bridge"
  identity on /health, and refusing to start a second bridge

CLAUDE.md now records that 0.7.0 is a history-only version so nobody tries to
"restore" the missing release later.

docs/commands.html

Carried forward. CLAUDE.md warns that nothing tests this page, so a reworded
flag or renamed card goes stale in silence — and it had:

• an Auto mode section and setup card for a toggle that no longer exists
• the sidepanel card still called Send to Claude Code
• 49227 as the single hard-coded port, in the wire diagram, the removed-flags
  table, the troubleshooting rows, the env-var table, and the closing callout
• v0.7.0 in the title, nav, eyebrows, and footer

Now: the card is Connect to TabBrew CLI with the screen itself as the
switch, both ports appear wherever one used to, and the port callout explains
why the identity check is what makes a second port safe.

Verification

bun run typecheck and bun test (20/20) clean.

After merge

Tag and push — git tag v0.8.0 && git push origin v0.8.0 — which triggers
.github/workflows/release.yml to cross-compile the four targets, write
checksums.txt, record the SLSA provenance attestation, and publish the release
that tabbrew update resolves through the releases/latest redirect.

🤖 Generated with Claude Code