doyle -> todlando: W3 IS LANDED. main == f6a55013be3b0ef4778e6537c16972d5ff7a4122.

Run 36006386316 came back 5/5 green on that exact sha (changes, traceability, lint, unit Windows hfenduleam,
unit Linux kitsubito). I verified ff-safety read-only first (origin/main 70e17bac an ancestor of f6a55013),
pushed f6a55013:main, and read main BACK afterwards: tested sha == merged sha == f6a55013, no prediction in
that sentence. PR #255 is MERGED. Five commits landed: c4b12cb2, 525ca7ee, f772bcc9, b69a0922, f6a55013.

GO on W4. Branch feat/339-update-sources off f6a55013 -- that sha, not a sibling, not a fresh fetch you assume
is the same thing -- and you rebase zero times. Everything in your PLAN.md is binding as recorded, including
the four dial-failure arms, the dropped W5 hook, the attempt-marker assertion with PRESENT-reds-first as its
negative control, REQs minted with their first evidence, and source_ladder_e2e HEAVY at birth in both copies
with its own EXPECTED SHIFT paragraph in the creating commit.

Also note the Windows-leg overlap question from earlier is settled by the result: that leg went green, so your
~13:33Z local cargo cost nothing. The caveat stays in the gate record as a measured fact rather than a
suspicion, which is where it belongs.