diff --git a/machine-docs/JOURNAL-5.md b/machine-docs/JOURNAL-5.md
index 55dc7d3..f2fe320 100644
--- a/machine-docs/JOURNAL-5.md
+++ b/machine-docs/JOURNAL-5.md
@@ -165,3 +165,53 @@ Conclusion:
   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.
+
+## 2026-06-01 — Resume loop: cryptpad green, lasuite-meet not enrolled
+
+Pulled the latest Adversary review (`REVIEW-5.md` 2026-06-01T03:50:00Z): V2 poll-only on `n8n` PR #2
+still PASSes cold (`VERDICT=GREEN`, build `#47`). No new finding to fix.
+
+Live cryptpad probe:
+- Registry check showed a real app upgrade beyond the current recipe head:
+  `cryptpad/cryptpad:version-2026.2.0 -> version-2026.5.1` (plus `nginx 1.29 -> 1.31`).
+- On cc-ci `~/.abra/recipes/cryptpad`, created branch `phase5-v5-cryptpad-2026-5-1`, updated
+  `compose.yml`, and committed:
+  - `cryptpad/cryptpad:version-2026.2.0 -> version-2026.5.1`
+  - `nginx:1.29 -> 1.31`
+  - recipe version label `0.5.4+v2026.2.0 -> 0.5.5+v2026.5.1`
+  - commit: `9db61d3 feat: upgrade to 0.5.5+v2026.5.1`
+- Opened mirror PR via `open-recipe-pr.sh`:
+  - `PR_URL=https://git.autonomic.zone/recipe-maintainers/cryptpad/pulls/3`
+  - branch `upgrade-0.5.5+v2026.5.1`
+- Real cc-ci verdict:
+  - `POST=1 MAX_WAIT=90 INTERVAL=5 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh cryptpad 3`
+    -> `VERDICT=PENDING`
+    -> `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/50`
+  - `POST=0 MAX_WAIT=300 INTERVAL=10 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh cryptpad 3`
+    -> `VERDICT=GREEN`
+    -> `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/50`
+- Conclusion: cryptpad does NOT provide the V5 stale-test branch either; its live upgrade stayed green.
+
+Live lasuite-meet probe:
+- `ssh cc-ci "export PATH=/run/current-system/sw/bin:$PATH; abra recipe upgrade lasuite-meet -m -n"`
+  showed a real app upgrade: frontend/backend/celery `v1.16.0 -> v1.17.0`, redis `8.6.3 -> 8.8.0`.
+- On cc-ci `~/.abra/recipes/lasuite-meet`, created branch `phase5-v5-lasuite-meet-v1-17-0`, updated
+  `compose.yml`, and committed:
+  - frontend/backend/celery `v1.16.0 -> v1.17.0`
+  - `redis:8.6.3 -> 8.8.0`
+  - recipe version label `0.3.0+v1.16.0 -> 0.3.1+v1.17.0`
+  - commit: `2d0c707 feat: upgrade to 0.3.1+v1.17.0`
+- Opened mirror PR via `open-recipe-pr.sh`:
+  - `PR_URL=https://git.autonomic.zone/recipe-maintainers/lasuite-meet/pulls/2`
+  - branch `upgrade-0.3.1+v1.17.0`
+- Real trigger attempts:
+  - `POST=1 MAX_WAIT=90 INTERVAL=5 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh lasuite-meet 2`
+    -> `VERDICT=PENDING`
+    -> `BUILD=?`
+  - `POST=0 MAX_WAIT=300 INTERVAL=10 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh lasuite-meet 2`
+    -> `VERDICT=PENDING`
+    -> `BUILD=?`
+  - after an extra 60s delay, `POST=0 MAX_WAIT=240 INTERVAL=10 ...` still returned `VERDICT=PENDING BUILD=?`
+- Conclusion: this is not a stale-test case yet; `recipe-maintainers/lasuite-meet` is not enrolled in the
+  bridge poll set, so `!testme` never entered the real CI path. Keep V5/V6 search on already-enrolled
+  recipes.
diff --git a/machine-docs/STATUS-5.md b/machine-docs/STATUS-5.md
index a18fbd4..9b6ce98 100644
--- a/machine-docs/STATUS-5.md
+++ b/machine-docs/STATUS-5.md
@@ -6,8 +6,9 @@
 
 ## Current focus
 
-V5 next (seed a real stale-test case on a sandbox/scratch branch; `n8n` natural upgrade went GREEN);
-then V6, V8, V8a, V9 cleanup.
+V5 next: find a genuinely stale test on an already-enrolled sandbox recipe. `n8n` and `cryptpad`
+natural upgrade candidates both went GREEN; `lasuite-meet` has a live upgrade but is not currently in
+the bridge poll set, so its `!testme` PR never triggered.
 
 ## Fixes applied (A5-1, A5-2, related)
 
@@ -93,6 +94,13 @@ preferred, `/root/cc-ci` fallback) instead of hard-coding `/root/cc-ci`.
 - Conclusion: `n8n` is a good sandbox for V5/V6, but this real upgrade did **not** naturally surface the
   stale-test path. Next step is to seed the stale-test case explicitly on a sandbox/scratch branch per
   Phase 5 §2, then exercise DEFAULT comment-only and `--with-tests` flows against that seeded case.
+- Second live candidate check: `cryptpad` app image `version-2026.2.0 -> version-2026.5.1` plus
+  `nginx 1.29 -> 1.31` on PR `https://git.autonomic.zone/recipe-maintainers/cryptpad/pulls/3`
+  (`upgrade-0.5.5+v2026.5.1`, head `9db61d3`) also went GREEN on `!testme` build `#50`.
+- Additional live finding: `lasuite-meet` has a real upgrade path (`v1.16.0 -> v1.17.0`), but its PR
+  `https://git.autonomic.zone/recipe-maintainers/lasuite-meet/pulls/2` stayed `VERDICT=PENDING BUILD=?`
+  across repeated `POST=0` polls because `recipe-maintainers/lasuite-meet` is not in the bridge's
+  enrolled poll list. That makes it unusable for V5/V6 until explicitly enrolled.
 
 ## Phase 5 gates