status(5): record V5/V6 groundwork and n8n probe

machine-docs/JOURNAL-5.md

@@ -129,3 +129,39 @@ Verification:
   → `AFTER=5`
 
 Next: consume `BUILDER-INBOX.md` in git, then continue with V5 stale-test candidate selection.
+
+## 2026-06-01 — Adversary re-test PASS; V5/V6 helpers added; n8n live probe
+
+Adversary review update:
+- `REVIEW-5.md` 2026-06-01T03:31:30Z closed A5-3 after a cold re-test. The rerun helper now returns the
+  fresh build URL on same-head re-`!testme`.
+
+V5/V6 automation gap closed in the orchestration repo (new files only; did not rewrite the already-dirty
+ helper scripts):
+- `/srv/cc-ci-orch/.claude/skills/recipe-upgrade/post-pr-comment.sh`
+- `/srv/cc-ci-orch/.claude/skills/ci-test-review/open-cc-ci-pr.sh`
+- Verification: `bash -n` on both new scripts exited 0 after `chmod +x`.
+
+Live stale-test candidate exploration:
+- `ssh cc-ci "export PATH=/run/current-system/sw/bin:$PATH; abra recipe upgrade n8n -m -n"`
+  showed a real available upgrade: app `2.20.6 -> 2.23.1`, db `17-alpine -> 18-alpine`.
+- On cc-ci `~/.abra/recipes/n8n`, created a scratch upgrade commit:
+  - `compose.yml`: `n8nio/n8n:2.20.6 -> 2.23.1`
+  - `compose.yml`: version label `3.2.0+2.20.6 -> 3.3.0+2.23.1`
+  - `compose.postgres.yml`: `pgautoupgrade/pgautoupgrade:17-alpine -> 18-alpine`
+- Opened mirror PR via `open-recipe-pr.sh`:
+  - `PR_URL=https://git.autonomic.zone/recipe-maintainers/n8n/pulls/2`
+  - branch `upgrade-3.3.0+2.23.1`, head `c8d27a2`
+- Triggered real cc-ci gate:
+  - `POST=1 MAX_WAIT=90 INTERVAL=5 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh n8n 2`
+    -> `VERDICT=PENDING`
+    -> `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/47`
+  - `POST=0 MAX_WAIT=300 INTERVAL=10 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh n8n 2`
+    -> `VERDICT=GREEN`
+    -> `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/47`
+
+Conclusion:
+- `n8n` remains the best V5/V6 sandbox candidate because its tests have real version-shape assertions,
+  but the natural upgrade path did NOT yield a stale-test failure. Per Phase 5 §2, the next move is to
+  seed a stale-test case explicitly on a sandbox/scratch branch and then run the DEFAULT comment-only and
+  `--with-tests` paths against that seeded case.