status(2): ghost +U fix confirmed (upgrade GREEN); recipe-PR #1 created; re-running with REF for PR head (first PR run missed REF→fetched 1.2.0)

machine-docs/STATUS-2.md

@@ -75,8 +75,16 @@ below); restore FAIL (real recipe gap, see below).
   chaos-version before the HC1 commit match. The untracked overlay makes abra stamp
   `chaos-version='<commit>+U'`; the commit equals head_ref (HC1 ok) but `+U` broke the exact-prefix
   match → spurious upgrade FAIL. Fix preserves HC1. **Needs a re-run to confirm upgrade now PASSES.**
-- **NEXT:** (a) re-run to confirm upgrade-tier GREEN with `a7e2af4`; (b) mirror ghost + recipe-PR for
-  the mysql restore hook; (c) final green full-lifecycle run with the PR (restore→GREEN); then CLAIM.
+- **PROGRESS @2026-05-30:** (a) `+U` fix CONFIRMED — run `ccci-ghost-pr1`: install/upgrade/backup/
+  custom PASS, deploy-count=1, create-post PASSED; upgrade-tier now GREEN. (b) recipe-PR
+  `recipe-maintainers/ghost#1` (`ci/mysql-backup`, head `a1e95fcb`) created: single-file mysqldump
+  backup + `/mysql_backup.sh restore` reimport hook + config mount + 1.2.0→1.3.0. (c) FIRST PR run
+  (`ccci-ghost-pr1`) accidentally ran WITHOUT `REF` → harness fetched catalogue 1.2.0 (no hook), so
+  restore still RED — `fetch_recipe` needs BOTH `SRC`+`REF`. RE-RUNNING with
+  `REF=a1e95fcbcd2b015d43af3b440d03102e350db458` (`ccci-ghost-pr1b.log`) to deploy the PR head; expect
+  restore→GREEN. (d) then CLAIM. **HOW (Adversary):** `RECIPE=ghost PR=1
+  REF=a1e95fcbcd2b015d43af3b440d03102e350db458 SRC=recipe-maintainers/ghost
+  STAGES=install,upgrade,backup,restore,custom cc-ci-run runner/run_recipe_ci.py`.
 - **Operator note:** cc-ci VM bumped 2→4 vCPU, sole VM on b1 (mid-session). Heavy ghost migration
   still needs the healthcheck overlay regardless (round-trip-bound).