#463's head carries #452's original history, and with it #438's first
research note (docs/research/wai-cross-fabric.md), which names fleet hosts and
addresses; #465 replaces that history with one squash so the note never enters
main's. So #463 is not merged by its head: its own commits are replayed with
cherry-pick -x onto the train's #465 merge (767d2aa7a), the second parent here:
- #452's platform-decode commits, which the review's split gave to EN-C and
#465 left out: 6ad92e2e8, 8695bc75f, fed8694f4;
- EN-C's fourteen: df5ea962f11b255682ff069acc2244a715b32a8d45aa0a203eae239b6e4bada1ffceb5086c03ba72cce38948da1ca593124507f4cd9ec9533773913964c944.
#463's merges of main and of #452 are not replayed; their conflict
resolutions (SPEC §7.1 step 2, the CHANGELOG) are reached by the later commits.
Checked: the replay's tree equals a three-way merge of #463's head onto the
replay's platform-decode commits with #452's head merged into main 1a465f23 as
the base, file for file, except the two files that merge conflicts on
(int_kernels_vectors.rs: #465's wgsl line and EN-C's platform-decode line, both
kept), and its CHANGELOG is #465's with #463's energy-honesty entry exactly.
No address of the fleet appears in the replayed commits.
Merging the replay here: CHANGELOG only, #463's entry on top. The registry
export is up to date after the merge.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
bfa44f4c1d