task: record /ship-spec PR-ready preference

User feedback (2026-05-24): /ship-spec must end with `gh pr ready
<N>`; don't leave PRs in draft. Overrides the skill's documented
"v1 stops at draft" stance. Recorded in both the harness MEMORY.md
and the auto-memory feedback store so future sessions apply the
preference without re-correction.

Follow-up (deferred): update .claude/skills/ship-spec/SKILL.md
Stage 9 to call `gh pr ready <N>` as the final step.

Refs #350.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

memory/MEMORY.md

@@ -18,3 +18,4 @@ Long-term lessons distilled from session experience. Append-only. See `context/r
 - **2026-05-24**: `/ship-spec` Stage 4's "HALT on HIGH findings" gate can be safely substituted by in-place AC mitigation when (a) all HIGH findings are in the "AC-tightening" category — no architectural HALT signals like `[PROTECTED-PATH]` violations, orchestrator-boundary crossings, or unstated assumptions that block `/delegate` — and (b) `critique.md` records a Synthesis paragraph naming each HIGH finding and its mitigation as the audit trail. Saves a critic round-trip when fixes are mechanical. Encountered shipping the Karpathy wiki integration (PR #351): 7 HIGH findings, all mitigated inline; gate PROCEEDED rather than HALTED.
 - **2026-05-24**: `/ship-spec` Stage 7 template path `tasks/openharness-v07-convergence/prompt.md` has been archived to `tasks/archive/openharness-v07-convergence/prompt.md`; the skill prose at `.claude/skills/ship-spec/SKILL.md` § Stage 7 still references the old (now-empty) location. Most recent live `prompt.md` example: `tasks/fork-friendly-install/prompt.md`. Either update the skill to point at the archive copy or seed a non-task-coupled template in the skill's own directory.
 - **2026-05-24**: `context/rules/memory.md` § Layout claims `memory/YYYY-MM-DD/log.md` is "gitignored directory; log.md tracked inside," but `.gitignore:42` (`memory/[0-9]*/`) excludes the entire directory contents. `git add memory/<date>/log.md` fails without `-f`; no daily log has ever been committed (verified via `git log --all --diff-filter=A`). In practice daily logs are local-only working state; only `MEMORY.md` is the long-term tracked store. The rule's "tracked inside" wording is aspirational. Either update the rule's prose to match the gitignore behavior OR add an exemption (`!memory/[0-9]*/log.md`).
+- **2026-05-24**: `/ship-spec` MUST end with `gh pr ready <N>` — do not leave PRs in draft. The skill's documented "v1 stops at draft PR creation" stance is overridden by user preference (correction received after PR #351 was left as draft). Applies to any equivalent end-to-end PR scaffold flow. Update the skill prose to make readiness the final step rather than a deferred manual action.