shiplisted

Use this skill when the user explicitly wants to ship the branch. Resolve helpers before running them: set `FORGEFLOW_HELPER_DIR` to `scripts/forgeflow` when that directory exists, otherwise to `${CODEX_HOME:-$HOME/.codex}/forgeflow/scripts/forgeflow`. A missing helper means the Codex runtime installation needs repair; it does not mean shipping is unsupported in Codex. Start by running: ```bash "$FORGEFLOW_HELPER_DIR/ensure-forgeflow-state.sh" "$FORGEFLOW_HELPER_DIR/ship-prepare.sh" "<optional title>" ``` `ship-prepare.sh` creates: - `.forgeflow/<project-name>/ship/ship-summary.json` - `.forgeflow/<project-name>/ship/ship-presentation.html` - `.forgeflow/<project-name>/ship/pr-body.md` Workflow: 1. Verify recent review state and confirm the branch is ready to ship. 2. Gather summary context from git history, changed files, and `.forgeflow/` artifacts. 3. Review and refine the generated ship artifacts instead of rebuilding them from scratch. 4. If asked and approvals allow it, create or update the PR with: ```bash scripts/forgeflow/ship-open-pr.sh "<title>" ".forgeflow/<project-name>/ship/pr-body.md" "<base-branch>" ``` 5. If asked and approvals allow it, check CI status with: ```bash scripts/forgeflow/ship-ci-status.sh scripts/forgeflow/ship-ci-status.sh --watch ``` 6. If CI fails and the user wants fixes, route the failure to the most relevant implementer(s). Rules: - Do not push, create PRs, or mutate remote state without the required approvals. - Treat review gat