spk-admin-dashboard

# spk-admin-dashboard Open the dashboard directly or show the user its URL. Do not treat the dashboard as a generic status abstraction. ## Flow 1. Prefer `spec-kitty dashboard --open` so lifecycle validation checks project, token, health, and daemon state before showing a URL. 2. If `.kittify/.dashboard` exists, treat it as diagnostic metadata only; do not show the URL until validation succeeds. 3. Use `spec-kitty dashboard --json` only for machine-readable mission rows. 4. Use `spec-kitty dashboard --kill` only when the user asks to stop it. 5. When presenting `/spec-kitty.status` in a text TUI, load `spk-doctrine-show-me` and follow its status rendering contract. ## Reference Read `references/dashboard-daemon.md` before diagnosing dashboard metadata, ports, tokens, or stale PID behavior. ## Rule The dashboard is a localhost daemon, not a cloud page. Prefer `spec-kitty dashboard --open` over manually trusting recorded metadata.