claim(ghost): revalidate current upgrade result

machine-docs/JOURNAL-ghost.md

@@ -168,3 +168,21 @@ ssh cc-ci 'docker stack ls; docker service ls; docker volume ls; docker network
 
 The result comment #16298 links build #66 and reports passed. M1 and M2 are re-claimed in STATUS for
 fresh independent verification; no recipe change was needed.
+
+## 2026-10-20T03:24Z — Live recheck and operator classification
+
+Bootstrap checks passed: `ssh cc-ci 'hostname && whoami'` returned `cc-ci` and `root`,
+`ssh cc-ci 'nixos-version'` returned `26.05.20260906.c257840 (Yarara)`, authenticated Gitea API
+version is `1.27.3`, and a random `probe-*.ci.commoninternet.net` resolved to gateway address
+`195.201.88.249`.
+
+Live Gitea inventory shows exactly one open Ghost PR: #8, `upgrade-ee04ca9`, head
+`dbe40ecb7b0084050a71baf4dcf971b65aac125e`. Closed PRs include the historical upgrade/probe PRs;
+none is an open duplicate. The clean post-proxy retry is comment #16297 / build #66. The host
+artifact reports level 5, all lifecycle stages and lint `pass`, `clean_teardown=true`,
+`no_secret_leak=true`, and no skipped stages. The proxy subnet is `10.10.0.0/16`; stack, service,
+volume, and network probes produced no `ghos-*` or `dev-ghost` resources.
+
+Posted operator-facing classification comment #16299 on PR #8. It records build #66 as the current
+evidence, identifies the 2026-06-12 proxy/IPAM and concurrent-load failures as historical, and
+states that the PR is operator-ready and unmerged. No recipe or test change was needed.