1c/W5.5: point to authoritative E2E-TESTME spec (E1-E6); orchestrator-signal-gated

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

JOURNAL-1c.md

@@ -311,3 +311,16 @@ public gateway** (curl the public subdomain, not localhost) → test passes →
 reported. Record Drone run # + public-URL curl in JOURNAL-1c/STATUS-1c as functional acceptance of
 D8/clean-room. Until the swap-done signal: keep the rebuilt VM's full stack running, do NOT tear down,
 do NOT start the e2e. (Tracked as W5.5 in BACKLOG-1c.)
+
+## 2026-05-27 — E2E-TESTME spec is authoritative (cc-ci-plan/test-e2e-testme-acceptance.md)
+
+Orchestrator: the full spec at `/srv/cc-ci/cc-ci-plan/test-e2e-testme-acceptance.md` is the AUTHORITY
+(supersedes earlier inline wording). Read it. It's MY test to execute; Adversary independently
+verifies. Preconditions P1-P3 are orchestrator-provided (node rename → cc-nix-test, public-gateway
+routing, then a SIGNAL). Self-check on signal: `curl https://ci.commoninternet.net/` → 200 ssl_verify=0.
+Pass criteria E1-E6 (new spec §3): E1 self-check; E2 new Drone build via bridge (not manual); E3 app
+answers EXTERNAL request at `<app>.ci.commoninternet.net` through gateway (real 200+cert+content, not
+localhost); E4 real assertions pass / build success; E5 clean undeploy; E6 reported + dashboard
+updated. Evidence→JOURNAL-1c, verdict→STATUS/REVIEW-1c as E2E-TESTME PASS. On fail: clean-room finding
+→ fix in GIT SOURCE (base/cc-ci-secrets), not the live VM → re-run. Bound: one recipe, one green run.
+Not started — awaiting orchestrator signal; rebuilt VM stack kept up.