Repository navigation
Conversation
This was referenced Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Test the next Cabinet host-leakage frontier after PR #84 without selecting a path/parent/occurrence feature in advance.
Positive pressure
Adds a bounded source action:
This should prove that an explicit Home-rooted runtime-sized route can replay atomically through existing sequence action composition, including after partial-persistence restart and with rollback on a later invalid segment.
Negative pressure
Pins two host-boundary problems before changing either UI:
selectedFolder, but separate surface-local route histories do not compose when navigation crosses surfaces.createFoldercan changeselectedFolderwithout a structural-index gesture, so a host gesture route can stop describing the current selection.These tests are evidence, not selected language law.
Explicit non-goals
Folder.parentIf this pressure confirms the mismatch, the next question is the exact semantic status of arrival context when selection itself is shared source-owned state.
Result
Pressure confirmed at exact head
c86bd5c1b4b52bbac3fa6f65a2bc93db5a0207acwith green CI.Positive result:
Negative result:
selectedFolder;selectedFolderwithout emitting a structural-index navigation gesture, so a gesture-only host route can become stale without the host being able to repair it honestly.Conclusion:
This PR is being closed unmerged as completed pressure evidence.