refactor(help): reorder by value, add per-command help, fit 80 columns

[colevels]

Why

tabbrew --help listed ACCOUNT → DOCS → TABS → SETUP — the product's purpose buried in third place, onboarding last, matching neither what do I do first nor what do I do most. Inside TABS the commands ran check → push → serve → list, but the workflow is serve → list → check → push.

Three other things were wrong once I looked:

• No per-command help. src/index.ts:54 short-circuited on values.help before dispatch, so tabbrew tabs push --help dumped the entire global listing. The registry already held every command's summary and flags — the data was there, unused.
• Rows past 80 columns. init's row was 89 chars, tabs check 86, one flag summary 82, six env rows over. They wrap on a standard terminal, which reads as broken output rather than a long sentence.
• help --all had no hierarchy — docs push: printed at the same indent as its own flags, so it didn't read as a heading.

What changed

Groups ordered by value, onboarding moved to a footer — the split gh/docker use. The top of the screen stays useful for the returning user who just wants a command name; the first-run path is still spelled out.

TABS  organize your Chrome tabs
  tabs serve   →  tabs list  →  tabs check  →  tabs push       (workflow order)
DOCS  send HTML into the sidepanel
ACCOUNT   login → whoami → logout
SETUP     init, update, help

GETTING STARTED
  tabbrew init        teach your AI agent that this CLI exists
  tabbrew login       sign in to your TabBrew account
  tabbrew tabs serve  run in a 2nd shell; the extension sends your tabs over

A third help view. --help now resolves through findCommand before dispatching, so tabbrew tabs push --help and tabbrew help tabs push print one command. A new optional details field on CommandSpec carries the caveat a one-line summary has no room for:

$ tabbrew tabs push --help
Send a script to the extension to preview & run

USAGE
  tabbrew tabs push <file> [options]

OPTIONS
      --port <n>  Port `tabs serve` is listening on (default 49227)

Requires `tabbrew tabs serve` to already be running. This does not run the
script: it lands in the extension's panel and you click Run there. Nothing the
CLI does can change your tabs.

Bare --help, help, help --all, and an unknown command all still fall through to the full listing.

80 columns, enforced. Summaries tightened, the budget encoded as SUMMARY_MAX, and the long form moved into details so nothing is lost. New src/registry.test.ts renders all three views and fails on any line over 80 — plus group integrity and findCommand's two-word precedence, which the dispatch change now depends on.

help --all — flags indent under a bold command name; CREDENTIALS becomes a FILES table that also names tabs.json.

Verification

• bun run typecheck clean; bun test 20 pass / 0 fail
• Every help view measured ≤ 80 cols with NO_COLOR=1 … | awk '{print length}'
• tabbrew docs push --port 9 still errors (the assertFlagsAllowed gate is intact), tabs list --json still routes, --version unchanged
• bun run build && ./dist/tabbrew tabs serve --help — verified through the compiled path, since help is bundled at compile time

No behavior change outside help rendering: no new flags, no route changes, registry.ts still the single source of truth for all three views.

🤖 Generated with Claude Code