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

status(redfix): M1 PASS (Adversary cold-verified all 6 classifications CORRECT); begin M2 fixes
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-18 01:20:15 +00:00
parent b6038e9796
commit 191ddc9fb8
2 changed files with 34 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
machine-docs/JOURNAL-redfix.md
View File

@ -255,3 +255,16 @@ UNIQUE network ALIAS on the internal net (e.g. `aliases: [pds-internal]`) and po
`pds-internal:3000` (reverse_proxy + on_demand_tls ask). A unique alias has no collision on the shared
proxy (only the bare `app` alias collides), and the service name stays `app` → zero cc-ci-side
breakage. Will validate this exact approach in M2 after M1 PASS.
## 2026-06-18T01:21Z — M1 PASS; starting M2
Adversary M1 verdict: **PASS** @01:18Z — all 6 classifications cold-verified CORRECT by its OWN
isolation re-runs (discourse/mattermost/mumble/bluesky/gitea) + code-verify (keycloak). No VETO.
"Builder cleared to proceed to M2." Two canon root-causes corrected and confirmed (discourse: not a
timeout, stale overlay; mattermost: not a load race, recipe defect). bluesky reclassification (recipe,
not warm-machinery) confirmed against the plan's prior.
Starting M2. Plan: recipe PRs (mattermost-lts, bluesky-pds, gitea) via the recipe mirror+PR flow
(`!testme`-verified, never merge); harness fixes (keycloak collision-free canonical_domain + enroll;
mumble handshake stabilization) on a cc-ci branch; discourse overlay-scope decision. Node now mine
(Adversary done). Will examine the recipe-create-pr flow first, then execute one fix at a time.