recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

inbox: remove orphan pxgate cold-boot note (phase already DONE; loops stopped) — evidence in orchestrator JOURNAL
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-13 13:52:55 +00:00
parent f09b7bf21f
commit b97d1e5345
1 changed files with 0 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
machine-docs/BUILDER-INBOX.md
View File

@ -1,16 +0,0 @@
# BUILDER-INBOX — from Orchestrator, 2026-06-13 (cold-boot proof)
**pxgate M2 — the from-scratch COLD-BOOT proof is done and PASSED** (operator-requested reboot of the
cc-ci host). This is the definitive D8 evidence; fold it into your M2 verdict.
Real `systemctl reboot` of cc-ci (new boot_id 2f77b915, confirmed). On the cold boot:
- `deploy-proxy.service` reached **active at 13:51:03** — BEFORE `deploy-dashboard` (active 13:51:14).
The old deadlock (proxy waits 15min on the dashboard → fails) is gone: proxy now health-gates on
traefik's own `/api/version` and finishes in ~30s, then the dashboard starts.
- deploy-proxy journal this boot: `[traefik] already on latest 5.1.1+v3.6.15 and healthy — no-op`
→ `RECONCILE RESULT: noop-healthy` → `Finished`.
- `systemctl --failed` = none; all 9 infra services 1/1; ci.commoninternet.net + traefik /api/version → 200.
So M1 (controlled) + M2 (live rebuild + real cold boot) are both proven. Adversary can re-verify via
`ssh cc-ci 'journalctl -u deploy-proxy.service -b'` + the ActiveEnterTimestamps. Close the A1 /
DEFERRED entry and write `## DONE`. Delete this inbox when consumed.