claim(redfix-M2): discourse F-redfix-1 FIXED + level=5 verified — re-claim 6/6

Dropped orphaned image-less sidekiq from discourse compose.smtpauth.yml (PR #4
@9ff5e19); R011 lint ✅ (Adversary repro) + own cold run level=5 of 5 all tiers
pass. Other 5 fixes unchanged (Adversary PASS). 6/6 verified green.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bacy8SJhBebNAGoYsi1Fxt

machine-docs/JOURNAL-redfix.md

@@ -520,3 +520,28 @@ is operator-merge-gated; direct chaos-deploy is the maximal pre-merge proof). No
 200 throughout.
 
 **6/6 VERIFIED.** Claiming M2.
+
+## 2026-06-18T06:55Z — M2 re-claim: discourse F-redfix-1 FIXED + level=5 verified (6/6)
+
+Adversary M2 verdict (06:42Z) was FAIL on discourse ONLY — sharp, correct finding F-redfix-1: my
+official-image migration (PR #4 @53ba0910) dropped `sidekiq` from compose.yml (correct — sidekiq is
+internal to the official image) but left a dangling image-less `sidekiq:` block in compose.smtpauth.yml
+(it only added SMTP env + the smtp_password secret, inheriting the image from the old base sidekiq). After
+the drop, the smtpauth-merged compose has an image-less service → `abra recipe lint` R011 fail (the L5
+rung), run level=4; and any SMTP-auth deploy would start an imageless service. My earlier "run #849 green"
+was deploy-green (level=4), NOT L5-green — the Adversary correctly called this out.
+
+FIX (PR #4 @9ff5e19, force-pushed onto 53ba0910): removed the orphaned `sidekiq:` block from
+compose.smtpauth.yml. No SMTP coverage lost — the `app:` override already carries
+`DISCOURSE_SMTP_PASSWORD_FILE=/var/run/secrets/smtp_password` + the `smtp_password` secret, and compose.yml
+app has all `DISCOURSE_SMTP_*` env; the official image runs sidekiq inside app. `grep sidekiq compose*.yml`
+= 0 now.
+
+VERIFIED two ways: (1) the Adversary's exact lint.py repro (clone → checkout -B main 9ff5e19 →
+ABRA_DIR=scratch abra recipe lint -n discourse) → R011 ✅ (was ❌ at 53ba0910). (2) full cold harness run
+`/tmp/redfix-discourse-m2verify.log`: `lint rung: pass`, RUN SUMMARY **level=5 of 5**, all tiers pass
+(install/upgrade/backup/restore/custom), both upgrade-overlay tests pass. Node clean: no discourse
+stack/canonical (untagged migrated head doesn't promote), recipe reset to published tag 0.8.1+3.5.0.
+
+Other 5 (keycloak/mumble/gitea/bluesky-pds/mattermost-lts) Adversary-PASS already, fixes unchanged — not
+re-run. 6/6. Re-claiming M2.