keel-shiplisted

# keel-ship Use this skill when the user asks to run the keel command `ship` (e.g. `keel ship ...`, `ship <args>`, or `/keel:ship`). It reads every project value from `.keel/project.yaml` via the `keel` CLI. # /keel:ship ## Command step evidence Every numbered step in this command is contractual. Complete the step, record the evidence it asks for, or explicitly mark it `N/A — <reason>` before moving on. If a step has an external side effect such as a GitHub comment, issue, review, report, branch, or PR, the side effect must be posted or written through the selected transport and cited in the final summary. Never silently skip a step because the runtime, agent, or prompt feels obvious. Project-neutral flagship workflow. **Every project value comes from `.keel/project.yaml` via the `keel` CLI** — never hardcode a branch, command, glob, agent, timezone, window, allowlist, or workflow name here. Reference knobs by name: `base_branch`, `build_gate_cmd`, `lint_cmd`, `implementer_agents`, `tier3_globs`, `ci_workflows`, `docs_gate_paths`, `merge_window`, `merge_window_mode`, `timezone`. Anything truly app-specific stays in the project (config knobs, or a `.keel/extensions/` Lego), never inlined here. All committed/published artifacts (commits, branch names, PR/issue titles + bodies, comments, queue files) follow the project's language policy. Free-form chat with the user may stay in any language. ## Live progress — stamp this run (required) So this run shows live on `keel-vis