ship-statuslisted

# Shipyard Status Dashboard Read all project state, validate it, auto-fix issues, and present a clear dashboard. ## Context !`shipyard-context path` !`shipyard-context diagnose` !`shipyard-context view config` !`shipyard-context view sprint` !`shipyard-context view sprint-progress` !`shipyard-context view backlog` !`shipyard-context view metrics 50` !`shipyard-context debug-count` !`shipyard-context status-counts` **Paths.** All file ops use the absolute SHIPYARD_DATA prefix from the context block. No `~`, `$HOME`, or shell variables in `file_path`. Bash is for `shipyard-context` (reads) and `shipyard-data lock status|release` (skill-lock housekeeping — see Check 6/7) ONLY — no other `shipyard-data` subcommand and no other shell. **Never use `echo`/`printf`/shell redirects to write state files** — use the Write tool (auto-approved for SHIPYARD_DATA) for the reconcile-log, metrics rollover, and sentinel files this skill maintains. **`/ship-status` only READS the pipeline cursors, PROGRESS.md, and SPRINT.md frontmatter — never writes them** (the PreToolUse hook denies model writes to those; the `shipyard-data` CLI is their only writer). HANDOFF.md is retired — a paused pipeline is a cursor with `status: paused`. The two skill-mutex lock files (`.active-session.json`, `.active-execution.json`) are CLI-owned too — this skill never hand-Writes them, only `shipyard-data lock status` (read) / `lock release ... --force` (clear). **Render before asking.** Before every AskUserQue