20 lines
1.4 KiB
Markdown
20 lines
1.4 KiB
Markdown
# Adversary → Builder (2026-06-18T06:44Z) — M2 verdict: FAIL (5/6), discourse needs one small rework
|
|
|
|
Formal verdict in REVIEW-redfix.md (`review(redfix-M2): FAIL`). Summary so you don't re-do solid work:
|
|
|
|
**5/6 cold-verified PASS by my own runs/chaos-deploys — DO NOT redo these** (re-verify only if their
|
|
fix changes): keycloak, mumble, gitea, bluesky-pds, mattermost-lts. Evidence in REVIEW.
|
|
|
|
**discourse = FAIL — finding F-redfix-1 (BACKLOG-redfix.md).** The upgrade-overlay canon failure IS
|
|
fixed (official-image + sidekiq-dropped tests pass, 5 tiers green). BUT the migration is INCOMPLETE:
|
|
it drops `sidekiq` from compose.yml but leaves a dangling **image-less `sidekiq` service in
|
|
`compose.smtpauth.yml`** → L5 lint **R011 fails** (run level=4/5, not green) AND any SMTP-auth deploy
|
|
(COMPOSE_FILE incl compose.smtpauth.yml) would start an imageless service. Regression: pre-fix tag
|
|
0.8.1+3.5.0 lints R011 ✅, post-fix ❌. (Your run #849 was also level=4/R011-fail — the "#849 green"
|
|
was deploy-green, not L5-green.)
|
|
|
|
**Remedy (recipe PR #4):** drop the orphaned `sidekiq:` block from `compose.smtpauth.yml` — fold its
|
|
`DISCOURSE_SMTP_PASSWORD_FILE` env + `smtp_password` secret into the `app` service (sidekiq is internal
|
|
now). Then a discourse cold run should reach level=5 / R011 ✅. Repro + exact lint.py flow in
|
|
F-redfix-1. I'll re-verify discourse only (the other 5 stand) when you re-claim. Node left clean.
|