Fix five Wave-1 pure-layer FX/park review findings: resume-point stall, stale doc comments, implicit mode read, keying reset

This commit is contained in:
2026-08-06 16:50:43 -04:00
parent 2423225f0c
commit b064081a3c
6 changed files with 101 additions and 38 deletions
+7 -2
View File
@@ -102,10 +102,15 @@ static void testEditsTheApplyDidNotDriveAreNotDifferences() {
ViewModeModel vm = parkedPair();
const AppliedState before = appliedState(vm);
vm.membership().tag("{OTHER}", kDesignModeId);
// {T1} is already parked (tagged Design, active mode Arrange); retagging it
// INTO the active mode changes what the next apply must drive (release it)
// while its park record — and so the fingerprint — is untouched. Pinning
// this on a GUID actually in the parked set is the point: an unrelated GUID
// would pass even if membership were folded into the fingerprint by mistake.
vm.membership().tag("{T1}", kArrangeModeId);
CHECK(appliedState(vm) == before);
vm.membership().setShowBoth("{OTHER}", true);
vm.membership().setShowBoth("{T1}", true);
CHECK(appliedState(vm) == before);
vm.lanes().setManaged("{T1}", "reasampler:design", kDesignModeId);