Wednesday Post-Fest Smoke BUILD_RECEIPT Row Review - Ten Minutes After Fest Branch Unset - 2026

Monday evening: branch unset #1 latched branch_unset_ok: true. Tuesday: someone ships a "tiny" trunk fix without POSTFEST-PATCH-00N. Wednesday noon: marketing asks whether November store capsule edits and Discord "we're back on default" posts can go. Someone answers "we unset Monday" and opens Steamworks. Players still install fest beta password lore. Support still links a build_id BUILD_RECEIPT retired two days ago. Retention jq #7 will fail J5 next Monday because nobody midweek-smoked the default return.

November 2026 first weeks after October Next Fest need a midweek post-fest smoke row review—not only Monday unset and not only Friday first-week capstone. Upload week already learned this cadence: Wednesday depot smoke before Thursday store publish (D1–D10, store_publish_allowed). Post-fest needs a cousin ritual with different stakes: on Wednesday, spend ten minutes diffing BUILD_RECEIPT rows after installed smoke on the returned default (or documented post-fest trunk), then set post_fest_smoke_ok only when gates W1–W10 clear—before November sprint store edits and partner "we're live on default" claims.

Non-repetition note: Wednesday depot smoke owns upload-week D1–D10 + store_publish_allowed. Branch unset #1 owns U1–U6 evening unset. POSTFEST-PATCH opinion #9 owns numbered binary exceptions. Retention jq #7 owns Monday identity. Forward #12 owns Friday first-week capstone. This URL owns Wednesday post-fest smoke + W1–W10 + post_fest_smoke_ok.

Pair branch unset #1, PATCH opinion #9, jq weekly #7, crash recovery #4, contractor burn-down #8, depot smoke cousin, depot label mismatch help, SteamCMD tools. Forward #11 Whisper clip batch / #12 Friday capstone; Course 303 forward.

Why this matters now (November 2026 post-October fest)

1. Unset theater is not install truth — branch_unset_ok Monday does not prove Wednesday players get default bytes.
2. Silent post-fest patches land Tuesday — POSTFEST-PATCH gaps show midweek; Friday capstone is too late for store edits.
3. November sprint inherits lies — Capsule badge-strip and store copy against wrong build_id confuse partners.
4. jq weekly cannot save a half-done unset — Monday identity needs Wednesday installed smoke.
5. Contractor hours chase the wrong smoke — Burn-down B-HOTFIX / QA needs a receipt field, not endless reruns.

Direct answer: Every post-fest Wednesday (after Monday unset), run installed smoke on returned default/trunk, clear W1–W10, file post_fest_smoke_row_diff_receipt_v1.json, set BUILD_RECEIPT post_fest_smoke_ok: true only when blockers pass—refuse November store merges and "we're on default" partner posts on Monday unset theater alone.

Who this ritual is for

Time: 10 minutes for row review after smoke; smoke itself 15–25 minutes first week, ~10 later.
Prerequisites: Current BUILD_RECEIPT.json, Monday post_fest_branch_unset_receipt_v1.json, optional POSTFEST-PATCH list, Steam client install of default (or documented post-fest trunk), retention weekly pointer if ISO week rolled.

Format ladder (November post-fest week)

Upload-week teams still use depot smoke D-gates—different columns; do not reuse store_publish_allowed for post-fest default return.

Post-fest smoke row catalog (what to diff)

Store release-evidence/post-fest/receipt-row-catalog-wednesday-smoke.md:

Never delete mid-week without receipt_version bump in diff notes.

Gates W1–W10 (Wednesday post-fest blockers)

W3–W7 are November store-edit blockers when RED. W8 YELLOW allows smoke latch only with written waiver referencing analytics lag.

Beginner path — printable ten-minute card

WEDNESDAY POST-FEST SMOKE ROW REVIEW — NOVEMBER AFTER UNSET
[ ] W1 files + unset receipt open
[ ] W2 build_id matches installed footer
[ ] W3 Steam branch = default (not fest beta)
[ ] W4 branch_unset_ok this post-fest window
[ ] W5 default_branch_return_ok
[ ] W6 build_id change ⇒ POSTFEST-PATCH-00N
[ ] W7 installed smoke receipt filed today
[ ] W8 retention weekly pointer (or waiver)
[ ] W9 producer signoff
[ ] W10 post_fest_smoke_row_diff_receipt_v1.json
DECISION: post_fest_smoke_ok = YES / NO

Beginner rule: If you cannot point to today's installed smoke on default, November store edits and Discord "we're back" posts are NO—even if Monday unset was GREEN.

Creator Monday hook (shareable)

"After Next Fest, we don't trust the unset toast. Wednesday we smoke default for ten minutes and file a receipt before any store edit." Paste the card into your #post-fest-ops channel.

Minute-by-minute ritual

Calendar invite: "Wednesday post-fest smoke — default return gate."

Developer path — receipt template

File as release-evidence/post-fest/smoke/2026-W45-wednesday.json:

{
  "schema": "post_fest_smoke_row_diff_receipt_v1",
  "iso_week": "2026-W45",
  "reviewed_at_utc": "2026-11-05T15:10:00Z",
  "current_build_id": "2026-11-05-trunk02",
  "baseline_build_id": "2026-11-01-trunk01",
  "paired_unset_receipt": "release-evidence/post-fest/branch-unset/post_fest_branch_unset_receipt_v1.json",
  "paired_patch_list": "release-evidence/post-fest/patches/post_fest_patch_exception_list_receipt_v1.json",
  "paired_weekly_receipt": "release-evidence/post-fest/post_october_fest_retention_weekly_log.jsonl",
  "installed_smoke": {
    "path": "release-evidence/post-fest/smoke/2026-W45-installed.json",
    "client": "steam_desktop",
    "branch": "default",
    "footer_build_id": "2026-11-05-trunk02",
    "golden_path": "boot_to_title_menu_ok"
  },
  "gates": {
    "W1": "GREEN",
    "W2": "GREEN",
    "W3": "GREEN",
    "W4": "GREEN",
    "W5": "GREEN",
    "W6": "GREEN",
    "W7": "GREEN",
    "W8": "GREEN",
    "W9": "GREEN",
    "W10": "GREEN"
  },
  "row_diff": [
    {
      "key": "build_id",
      "baseline": "2026-11-01-trunk01",
      "current": "2026-11-05-trunk02",
      "expected": "2026-11-05-trunk02",
      "status": "expected_change",
      "note": "POSTFEST-PATCH-001"
    },
    {
      "key": "branch_intent",
      "baseline": "fest_rc_unset_pending",
      "current": "default",
      "expected": "default",
      "status": "expected_change",
      "note": "U1–U6 unset Monday"
    }
  ],
  "post_fest_smoke_ok": true,
  "notes": "Installed smoke on default; POSTFEST-PATCH-001 documented; no fest beta leftover"
}

BUILD_RECEIPT rows

{
  "branch_unset_ok": true,
  "default_branch_return_ok": true,
  "post_fest_patch_exception_list_ok": true,
  "post_fest_smoke_ok": true,
  "post_fest_smoke_receipt": "release-evidence/post-fest/smoke/2026-W45-wednesday.json",
  "november_store_edits_allowed": true
}

Fail-closed: November store CI / producer checklist must require post_fest_smoke_ok == true from this ISO week's Wednesday receipt—not last week's boolean. Optional alias november_store_edits_allowed mirrors upload week's store_publish_allowed for company diligence language.

Installed smoke minimum (W7)

Before the ten-minute row review:

1. Install from Steam default (or documented post-fest trunk)—clear fest beta password if still set.
2. Record footer / in-game build_id if present.
3. Boot to title; run one golden path (menu → first interactive screen).
4. Confirm branch name in Steam properties / beta dropdown shows default.
5. Save installed_smoke JSON with optional screenshot paths.

Pair help: depot promoted build label mismatch when footer ≠ receipt. Pair crash recovery #4 when golden path still crashes—smoke fails closed; do not latch GREEN.

verify_post_fest_smoke.sh

#!/usr/bin/env bash
set -euo pipefail
SMOKE="${1:-release-evidence/post-fest/smoke/latest-wednesday.json}"
BR="${2:-BUILD_RECEIPT.json}"

jq -e '.schema == "post_fest_smoke_row_diff_receipt_v1"' "$SMOKE" >/dev/null
jq -e '.post_fest_smoke_ok == true' "$SMOKE" >/dev/null

for g in W1 W2 W3 W4 W5 W6 W7 W8 W9 W10; do
  test "$(jq -r --arg g "$g" '.gates[$g]' "$SMOKE")" = "GREEN"
done

test -f "$(jq -r .installed_smoke.path "$SMOKE")"
FOOTER=$(jq -r .installed_smoke.footer_build_id "$SMOKE")
CUR=$(jq -r .current_build_id "$SMOKE")
test "$FOOTER" = "$CUR"

BRANCH=$(jq -r .installed_smoke.branch "$SMOKE")
test "$BRANCH" = "default" -o "$BRANCH" = "post_fest_trunk"

jq -e '.post_fest_smoke_ok == true' "$BR" >/dev/null
echo "post_fest_smoke_ok"

jq one-liners

Latch

jq -e '.schema == "post_fest_smoke_row_diff_receipt_v1"
  and .post_fest_smoke_ok == true' \
  release-evidence/post-fest/smoke/2026-W45-wednesday.json

Branch must be default (or documented trunk)

jq -e '
  .installed_smoke.branch == "default"
  or .installed_smoke.branch == "post_fest_trunk"
' release-evidence/post-fest/smoke/2026-W45-wednesday.json

Unset pointer present

jq -e '.paired_unset_receipt | type == "string" and length > 0' \
  release-evidence/post-fest/smoke/2026-W45-wednesday.json

Proof table

Scenario matrix

Contractor / company coupling

When W7 fails, contractor burn-down #8 QA hours require a smoke receipt field—max retries, then waiver or crash recovery—do not burn unlimited hours. When W6 fails, B-HOTFIX + POSTFEST-PATCH-00N required before more patch overtime.

Company diligence language: "Post-fest default return verified same ISO week via post_fest_smoke_row_diff_receipt_v1.json (W1–W10 GREEN)." Attach unset receipt + smoke + BUILD_RECEIPT excerpt. Redact player IDs from screenshots.

Same-week calendar (recommended)

Skipping Wednesday and "catching up Friday" still leaves Thursday store edits unprotected.

Partner diligence zip

1. post_fest_smoke_row_diff_receipt_v1.json
2. Installed smoke JSON + optional screenshots
3. Paired unset receipt
4. POSTFEST-PATCH list if build_id changed
5. BUILD_RECEIPT excerpt with post_fest_smoke_ok
6. Link to SteamCMD tools

Zip name: {studio}_post_fest_smoke_{iso_week}_2026.zip.

Comparison pack — smoke cousins

FAQ

Same as Monday branch unset?

No. Unset documents pointer intent; Wednesday decides installed default smoke permission.

Same as Wednesday depot smoke (upload week)?

Cousin cadence, different columns (depot/store publish vs post-fest default return). Primary keyword here: post fest steam branch smoke test.

Same as Friday first-week capstone #12?

Friday is pre-November-sprint. Wednesday protects midweek store edits after unset.

Does smoke replace POSTFEST-PATCH list?

No. Smoke proves install; POSTFEST-PATCH authorizes build_id changes after fest.

Can we edit store if W8 weekly jq is YELLOW?

Only with written waiver—prefer fix weekly pointer first.

Must smoke run on Deck?

Desktop Steam client is enough for W7; add Deck when Deck is a launch surface claim.

What if we never changed build_id after unset?

W6 GREEN with empty patch list and matching baseline—preferred. Still run W3/W7 on default.

Creator outreach before smoke GREEN?

Draft Discord posts offline; publish "we're on default" only after W10 latch.

Facilitator stand-up script (75 seconds)

1. "ISO week and Wednesday smoke path?"
2. "build_id footer matches receipt?"
3. "Steam branch = default, not fest beta?"
4. "branch_unset_ok still GREEN this window?"
5. "Any build_id change ⇒ POSTFEST-PATCH-00N?"
6. "post_fest_smoke_ok decision: YES or NO?"
7. "If NO — which W-gate is RED, and who owns the fix before Thursday 10 a.m.?"

Paste the decision into #post-fest-ops before marketing opens the store editor.

CI sketch (GitHub Actions)

- name: Verify Wednesday post-fest smoke row review
  run: bash scripts/verify_post_fest_smoke.sh \
    "release-evidence/post-fest/smoke/${{ env.ISO_WEEK }}-wednesday.json"
- name: Block November store edits without latch
  run: jq -e '.post_fest_smoke_ok == true' \
    release-evidence/05-operations/BUILD_RECEIPT.json

Place verify after installed smoke artifact upload, before any job that exports store metadata packages or posts partner status. Document waivers in BUILD_RECEIPT notes with producer initials and UTC time.

Engine and store notes

Waiting on SteamPipe queue is not W7. W7 starts when the client has bytes installed on the intended branch.

RED / YELLOW / GREEN routing

Do not convert W7 RED into "marketing can still edit drafts." Drafts are fine; public store packages and partner-facing "we're on default" posts are not.

Worked example (W45)

Monday W45 unset GREEN on 2026-11-01-trunk01 with default return screenshots. Tuesday POSTFEST-PATCH-001 crash fix uploads 2026-11-05-trunk02. Wednesday QA installs default, footer matches, golden path boots, fest beta password cleared. Row diff marks build_id and branch_intent as expected_change. W1–W10 GREEN. Producer sets post_fest_smoke_ok: true at 15:12 UTC. Thursday capsule badge-strip runs against the same build_id. Friday #12 capstone will consume this smoke annex—do not invent a second Wednesday boolean later.

Common mistakes

1. Reusing last week's post_fest_smoke_ok — ISO week must match.
2. Smoke on fest beta still password-gated — W3 fails; finish unset.
3. Calling Steamworks UI "smoke" — UI green ≠ installed footer.
4. Skipping W6 because "tiny fix" — tiny fixes still change build_id.
5. Letting marketing decide YES in Slack — decision is the receipt file.
6. Confusing upload-week store_publish_allowed with post-fest latch — different schemas.

Enterprise notes (companies)

• Change control: Smoke receipt ID in ticket system for any partner status update.
• Audit: Append-only Wednesday receipts—no editing prior ISO week files.
• Security: Redact crash logs with player paths before diligence zip.
• Cost/ROI: Ten minutes Wednesday prevents a week of support tickets on wrong-branch installs.
• Governance: Producer + QA dual sign-off on W9—no single-person override after fest.

Key takeaways

1. Post-fest weeks need Wednesday smoke row review after fest branch unset.
2. Gates W1–W10 on post_fest_smoke_row_diff_receipt_v1.json.
3. Latch post_fest_smoke_ok only after installed smoke on default.
4. Monday unset GREEN is not midweek install permission.
5. W3–W7 RED block November store edits.
6. build_id change without POSTFEST-PATCH-00N fails W6.
7. Pair #1 unset and #9 PATCH opinion.
8. Pair #7 retention jq and #8 contractor burn-down.
9. Distinct from October Wednesday depot smoke.
10. Use SteamCMD tools and help mismatch.
11. Whisper post-fest clip batch #11 (Q1–Q6, post_fest_clip_batch_ok) for creator quote cards after smoke; Friday first-week capstone #12 indexes post_fest_smoke_ok in F1–F10.
12. Ten minutes of receipt honesty beats a week of wrong-branch support.

Related reads

• Your First SteamFest Branch Unset Default Branch Return Receipt
• Stop Shipping Post-Fest Hotfix Patches Without Numbered Exception List
• Wednesday Depot Smoke Before Thursday Store Publish — upload-week cousin
• jq Gate Sketch for post_october_fest_retention Weekly Demo Row Diff
• Post-October Fest Contractor Burn-Down Cap Worksheet
• We Recovered Steam Demo Crash Rate Spike After October Fest
• Whisper Post-October Fest Playtest VOD Batch for Creator Clip Quotes — forward #11
• Friday Post-October Fest First-Week Capstone — forward #12
• SteamCMD SteamGuard Depot Owner Validation Tools
• Steam Depot Promoted Playtest Build Label Mismatch Help

Closing

Monday unset without Wednesday smoke is how November store edits inherit fest-branch lies. Run the installed default smoke, clear W1–W10, and let post_fest_smoke_ok be a same-week decision—not a leftover boolean.

When marketing asks "can we say we're back on default?", the answer is the Wednesday card: smoke path, branch honesty, and a receipt that still matches the bits players will install.