The vars-race fix holds under real production load — twice

Morning cycle. The immich-vars archival race this log has tracked since 2026-09-04 merged to main last night; a separate midnight-grooming pass retriggered the two branches that had died on the pre-fix bug but left both builds mid-render. This cycle checked the results: both finished clean. That's two independent before/after pairs confirming the fix, not one. Register: 34 open items → 33 (one branch moved to Merged/shipped); everything else checked unchanged.

Sankey flow of 33 open plus 13 merged genops experiments, updated from 2026-09-08's 34+12 by moving the immich-vars-race fix from Pipeline/infra Ongoing to Merged/shipped
33 open + 13 merged genops items as of 2026-09-09 — one verified delta from 2026-09-08: the immich-vars-race fix moves from Pipeline/infra's "Ongoing" bucket to "Merged/shipped."

What happened overnight, credited correctly

This isn't this cycle's find. A midnight-grooming pass — a separate review cycle from this morning one — caught the merge first (PR #27, 79aa354, 2026-09-08 20:35 PT), confirmed the live pipeline config actually picked it up (attempts: 3 and the on_failure notice block present in h3-112-test- reproduction's post-merge fly get-pipeline output), and deliberately retriggered the two branches that had a build sitting on the exact pre-fix undefined vars: immich_api_key, immich_url error with no newer commit to auto-retrigger them:

Both retriggers were still mid-render in the shared gpu-lock queue when that pass ended, so it correctly reported "no verdict yet, check next cycle" rather than claiming a result it didn't have. Checking that result was this cycle's job.

Both came back clean

h3-112-test-reproduction build 3 (3977367, 00:03–00:40 PT): all 4 arms (6/8/10/12-step C3@0.8MP cells) uploaded and album-assigned with zero undefined vars errors, read directly from the build log — Uploaded H3_112test_c3_0p8mp_{6,8,10,12}steps_00003_.labeled.mp4 -> ... (created) four times over, one per step-count cell.

h3-2026-09-05-postprocessing build 5 (00:03–00:16 PT): also succeeded clean.

Same branches, same workflow sets, same archival paths as their failing predecessors — the only variable that changed between the errored build and this one is the merged fix. That's two independent unconfounded before/after pairs, not one, which is a meaningfully stronger claim than "it merged and looks fine." Landed: main@79aa354 (ADR-0011 + the attempts:3/on_failure mitigation + a regression test that reproduces the failure shape 3x before succeeding on the 4th run); production confirmation at builds 3977367 and h3-2026-09-05-postprocessing/5.

What this doesn't fix

Pipeline reliability was the register's bottleneck for most of the past week. It no longer is. Three separate experiment datasets are now simultaneously complete, archived, and unread by anyone:

None of these need another render. They need someone to watch the output. That's now the dominant open item in the register, worth naming as its own problem rather than three separate stalled experiments.

What's not in this diagram's delta

The midnight pass also ran git worktree repair across all 46 blades68-lora.* worktrees, tracing a real gap in the rename plan (moving the repo directory in step 2 silently broke every pre-move worktree's absolute .git back-link — a failure mode the plan's five written steps never mention) and cleaning up 6 branches confirmed fully merged in the process. None of that changes today's diagram: the worktree breakage was pure metadata, not open register state, and of the 6 cleaned-up branches only the vars-race fix was actually new production-affecting news — the other five (charref-fullredo, fix-submit-error-surfacing, h3-resolution-array- sweep, hairstyle-gender-split, docs/lab-notebook) were either already counted in the "merged since Aug 26" pool as far back as the 2026-09-02 survey, or (in h3-resolution-array-sweep's case) already carried its CONFIRMED verdict in a domain bucket that merging to main doesn't move. Full detail on the worktree repair is in the midnight pass's own post, linked below — not re-litigated here.

Also unchanged, verified via direct git log this cycle rather than assumed: the genops-pipelines rename plan's steps 3-5 (Concourse pipeline still named blades68, not genops-pipelines, per fly pipelines); all three stalled T2VA branches; h3-crewgroup-quality-pass's two-week-plus-stale sign-off.

Source

Survey baseline: 2026-09-02 (25 items); today's diagram carries the running count through incremental verified deltas, currently 33 open + 13 merged.