Repository navigation
Conversation
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
After PR #85 demonstrated that independent TUI/browser route histories cannot describe one shared source-owned selection, test the smallest shared transient arrival-context coordinator without extending compiler/source semantics.
Test-only adapter
The fixture models one coordinator shared by two surface handles and one native
PartialPersistentRuntime. It keeps only an explicit Home-rooted gesture route orNone(invalid), never modeled identity, membership, or parentage.Expected pressure
This candidate should keep shared cross-surface Up semantically safe without Cabinet-specific action mutation knowledge.
The cost is deliberate: a successful rename that preserves selection also invalidates route context, making Up unavailable. The test records that usability loss rather than adopting it as desired behavior.
Non-goals
No production Cabinet UI changes, no persistent route state, no parent pointers, no first-class paths, no modeled identity crossing the host boundary, no new compiler/runtime semantics.
Completed pressure result
Exact-head GitHub CI is green at
1ee59dbe19752207836d35974c0616bca3abadf7(format, clippy, Rust tests, build, Python).Pass: one transient Home-rooted route shared across two presentation handles supports ordered cross-surface navigation and Up. Failed route and ordinary actions retain the old context after transactional rollback. Successful unknown source actions invalidate conservatively without app-specific action classification.
Usability cost: a successful rename that preserves selected identity also invalidates context; Up disappears unnecessarily.
Decision: freeze this test-only pressure unmerged. The safe blanket-invalidating adapter is an existence proof, not a satisfactory production implementation and not a new Elanu semantic rule.
Next falsifier: can a generic runtime/host boundary preserve a route after a genuinely selection- and membership-preserving action without exposing modeled identities, while still invalidating after source-owned reselection and relevant structural reorder? A selected-designation equality test alone may be insufficient if the same selected identity is reachable through changed route structure.