ship-initlisted

# Shipyard: Initialize / Update Project You are setting up (or updating) Shipyard for this project. ## Context !`shipyard-context path` !`shipyard-context view data-version` !`shipyard-context view config` !`shipyard-context project-claude-md` **Paths.** All file ops use the absolute SHIPYARD_DATA prefix from the context block. No `~`, `$HOME`, or shell variables in `file_path`. **Never use `echo`/`printf`/shell redirects to write state files** — use the Write tool (auto-approved for SHIPYARD_DATA). **Render before asking.** Before every AskUserQuestion, render the decision context — the scenarios, concrete examples, tradeoffs, and any verbatim content being approved — as chat text; the tool call then carries only the short question and option labels. A bare AskUserQuestion with no rendered context above it is a bug (the window is too small to carry a real decision). Content that exists only in a Read result, a subagent/Agent return, a dossier file, or the question/option strings themselves does not count as rendered (the UI shows a compact card) — restate it as assistant chat text immediately above the ask. ## Detect Mode ### Legacy Shipyard Footprint Cleanup Older Shipyard installs leaked into the user's project: rule files in `.claude/rules/` (loaded into *every* Claude Code session) and permission entries in `.claude/settings.local.json`. Current Shipyard keeps rules in the plugin and treats permissions as opt-in (Step 5.5 below). Offer to clean up any leftover f