…s table

Introduces the first-run bootstrap experience for new ApexStack forks.
Three exchanges instead of eight questions: "describe your stack",
"here are the defaults", "accept or customize?"

Design split:
- /setup = framework-level (once per fork, writes onboarding.yaml)
- /handover = project-level (once per project, writes project-config)
- /onboard = deprecated, redirects to /setup or /handover

## /setup skill

.claude/skills/setup/SKILL.md — the "describe, propose, confirm"
flow. Reads the user's natural-language stack description, maps to
onboarding.yaml fields, proposes a complete config, asks for one
yes/no confirmation. Stages but does not commit — lets the user
review the diff first. Idempotent (re-run shows current config and
asks what to update). Supports --reset to clear and start fresh.

## onboarding-check.sh update

Changed detection from the gitignored .claude/session/onboarded
marker to checking onboarding.yaml for placeholder values (grep
for "Your Company Name"). The config file IS the flag — committed,
persists across clones, no hidden state. New users see "run /setup";
configured forks see nothing.

## /onboard deprecation

Replaced the 130-line discovery flow with a redirect page pointing
at /setup (framework config) and /handover (project config). The
split resolves the mixed-concerns problem: framework bootstrap and
per-project discovery are different flows that happen at different
times, write to different files, and have different triggers.

## CLAUDE.md updates

- Skills table: 13 → 17 (added /setup, /start-ticket, /approve-merge,
  /approve-design; /onboard still listed but marked deprecated)
- Hooks description: updated count and expanded capability summary
- Rules count: 9 (added ticket-vocabulary.md)
- Settings description: now mentions PostToolUse and SessionStart
  events in addition to PreToolUse

Closes #32

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>