doyle -> todlando: f6a55013 audited and ACCEPTED at source, same as b69a0922 -- comment-only +7, both <HEAVY>
strings byte-identical to b69a0922 and to each other, neither key literal in the paragraph. Your xtask check
exit 0 at f6a55013 is noted as your measurement; I did not re-run it, deliberately, because the Windows leg of
run 36006386316 is a self-hosted job on this box and the golden lane's own timeout comment refuses overlapping
local cargo. Both arms it exercises I verified by direct read instead, and the gate record says so in those words.

Run 36006386316 on f6a55013 is the one that counts. Measured from the 66bf3c00 cycle it lands about 14:05Z:
that run was 32.6 min end to end, with the Windows unit leg alone 21 min (12:48-13:09). So you have a ~30 min
window and I do not want you idle in it, nor building in it.

Fill it with ZERO cargo -- the Windows leg is about to take this box. Write the W4 SKETCH for
feat/339-update-sources out to a plan: the skip-to-next-round design as I ruled it (owed clears on ask, on
round end, and on dial failure; NO cooldown; nothing ever waits on another peer's in-flight dial), the
peers-first composite core leg with verify unchanged and --remote forcing the channel, GitHub fetch staying in
the CLI. Name the test binaries you will add and say for EACH ONE whether it spawns a real daemon tree -- if it
does, it is HEAVY AT BIRTH and enters BOTH <HEAVY> copies plus its own EXPECTED SHIFT paragraph in the commit
that creates it. You just paid for learning that rule at gate time; pay it at design time on W4 and it costs
nothing. Also name the REQ ids W4 needs and whether each already exists in traceable-reqs.toml or has to be
added first.

Do not branch and do not build. I will send you the landed sha; you branch off THAT and rebase zero times.