Skip to content

Unify Workspace confirmations and commit Surface moves synchronously - #888

Merged
nedtwigg merged 5 commits into
mainfrom
review-move-followups
Oct 2, 2026
Merged

nedtwigg merged 5 commits into
mainfrom
review-move-followups

Conversation

@nedtwigg

@nedtwigg nedtwigg commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

Close and move confirmations now share one slot: starting another close or move cancels the previous question. Surface departure, adoption, and publication of both workspace records run synchronously, without a persistence batch.

Review fixes prevent older asynchronous close/window-probe/editor preparation from replacing newer consent or acting afterward. Saves collected during React’s move commit are fenced as well, preserving a moved exited terminal’s retained cwd. Updated the specs and navigation guide, with regression tests for both races. Fixed a pre-existing date-sensitive Network Settings story fixture exposed by Argos after midnight.

Validation: full pnpm test and pnpm build passed; standalone TypeScript check and Storybook build passed. Innerdogfood verified real terminal moves to existing and new workspaces, superseded iframe consent, and refresh after the displayed confirmation key.

nedtwigg and others added 4 commits October 1, 2026 17:26
The Workspace close, the cross-Window iframe move gate and the Surface move
iframe consent shared the strip as three typed-letter slots with their own
precedence. They are now one slot: a newer confirmation, or any close,
cross-Window move or Surface move starting by gesture or dor, answers the
pending one no first.

A declined consent releases the Surface move's guard and transfer flags
synchronously, so the verb that cancelled it starts at once and the
superseded move's cleanup cannot clear a newer move's flags. Move
eligibility is one surfaceMoveRefusal shared by the coordinator, the drag
targets and the picker; it no longer refuses for an open dialog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…atch

With the cwd probe skipped, building a record never awaits, and a new
Workspace's Wall registers inside its flushSync render. So after the last
await the coordinator creates the destination, fences both revisions,
departs, adopts, finishes both Walls and publishes both records in one
synchronous run.

session-save splits a synchronous assemblePersistedSession out of
buildPersistedSession; the Wall handle's serializeNow replaces the async
serializePersistence. The aggregator's write batch becomes
publishWorkspaceSessions, which sets several records behind one scheduled
write, so even a pagehide write never holds half a move. Rollback can only
run before finishSurfaceMove, so it no longer disposes an auto-refill
shell, and no record needs republishing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Deploying mouseterm with  Cloudflare Pages  Cloudflare Pages

Latest commit: 45bed76
Status: ✅  Deploy successful!
Preview URL: https://7b6b3824.mouseterm.pages.dev
Branch Preview URL: https://review-move-followups.mouseterm.pages.dev

View logs

@nedtwigg
nedtwigg merged commit ac7a2d3 into main Oct 2, 2026
15 checks passed
@nedtwigg
nedtwigg deleted the review-move-followups branch October 2, 2026 01:10

This branch is waiting to be deployed

1 waiting deployment
hosted-preview — 45bed764 Waiting Oct 2, 2026 by nedtwigg via cleanup #661
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.

2 participants