Skip to content

Add shared-runtime Cabinet browser surface - #81

Merged
mtc1122 merged 5 commits into
mainfrom
app-notes-cabinet-browser-shell
Sep 27, 2026
Merged

mtc1122 merged 5 commits into
mainfrom
app-notes-cabinet-browser-shell

Conversation

@mtc1122

@mtc1122 mtc1122 commented Sep 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • refactor the Notes Cabinet example so the terminal and browser surfaces share one native PartialPersistentRuntime
  • add a tiny local HTTP browser surface over generic runtime observations
  • allow browser folder/note selection through existing Elanu actions
  • allow editing the selected note in the browser through editSelectedNote
  • expose Home and Trash using existing Cabinet actions
  • add form decoding and a bounded HTTP request size

Semantic boundary

  • no new Elanu source semantics
  • no modeled IDs cross the host boundary
  • no browser-owned selection, membership, parentage, trash, restore, or persistence semantics
  • no second runtime or persistence reread
  • no Folder.parent, reverse-reference graph, or route/path language feature

Manual pressure result

The TUI and browser both observe and mutate the same application-owned selectedFolder / selectedNote state. Browser edits are committed through the existing Elanu action and are visible from the TUI, and vice versa.

Nested structural "up" navigation remains intentionally out of scope for this PR; that pressure is being kept separate from the completed foreign-surface milestone.

@mtc1122
mtc1122 merged commit 4645b7b into main Sep 27, 2026
2 checks passed
@mtc1122
mtc1122 deleted the app-notes-cabinet-browser-shell branch September 27, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant