MOTION: spacefs-style choreography for the capsule swap, menus and popovers (≤500 ms), unified selection toolbar

kayg commented

2026-09-27 12:42:09 +00:00

Owner

Owner request (2026-09-27): adopt the spacefs.com menu choreography (menu open/close and how items populate) for (1) the bottom capsule swapping between the tab bar and the selection/context toolbar, and (2) every "opening" surface: ⋯ menus, context menus, popovers. Sub-view switches stay instant.

Decided (owner grill)

Scope: capsule swap + ⋯ menus + context menus + popovers (one motion language for things that open).
Duration cap: 500 ms total for every one of these animations (trigger → last item fully settled). Owner: "it would be annoying if every animation took that long… cap it at 500ms and let's see how it feels". Keep the character of the reference (easeOutQuint, overdamped spring with the same damping ratio ≈1.08 and no overshoot, stagger in reading order, rise from below, outgoing fade shorter than incoming) but time-scale it so the cap holds. Suggested starting point: outgoing fade 120 ms; first item delay 90 ms; stagger 25 ms with the index capped at 4; rise ≈310 ms (raise spring stiffness to settle in that time at the same damping ratio); capsule width morph 400 ms easeOutQuint. Put the values in ONE shared motion module (tokens), documented; tune once from real recordings.
Unified selection toolbar on every screen size: desktop multi-select (Files, Photos, anything with selection) uses the same floating bottom capsule as the phone. Remove the old desktop selection toolbars/buttons it replaces (reuse gate: one component, fewer buttons; owner: "anything that makes the app simpler and more consistent / fewer buttons").
Capsule swap choreography: width morphs from tab bar width to toolbar width; outgoing icons fade (no exit motion on items); incoming actions rise with stagger. Reverse on deselect with the same rules. Actions are tappable immediately (pointer events on during the animation). For a horizontally scrolling toolbar, only visible actions stagger.
Selected-count label ("3 selected") uses the label roll (old rolls up/out, new rolls in from below) when the count changes.
Semantics: tab bar stays navigation; the selection bar is role="toolbar" with an aria-live announcement ("3 selected, actions"). Focus management: if focus was on a tab icon, move it to the first action; return it on deselect.
Reduced motion: instant swap, no stagger, no roll.
Implementation notes from the owner's reference (verified by the orchestrator): keyed {#each [current] as x (x.id)} (not {#key}) so the outgoing content keeps its data during its outro; |global on item intros; prefersReducedMotion from svelte/motion; custom css transitions (compositor-friendly transform/opacity); no intro on first render. Not applicable: fixed 504 px inner width, height morph, tablist roles, Tailwind (we use tokens).
Performance: only transform/opacity animate except the capsule width (small fixed-position element); verify no long tasks/INP regression on a mid phone profile.

Depends on

#219 (phone chrome: shared contextual bottom bar) must be merged first; build on its component.

Evidence

Screen recordings (video or frame strips) of: phone select/deselect in Files and Photos, desktop multi-select in Files and Photos, ⋯ menu open/close, context menu, a popover; light + dark; plus reduced-motion. The orchestrator reviews them and sends them to the owner.

Owner request (2026-09-27): adopt the spacefs.com menu choreography (menu open/close and how items populate) for (1) the bottom capsule swapping between the tab bar and the selection/context toolbar, and (2) every "opening" surface: ⋯ menus, context menus, popovers. Sub-view switches stay instant. ## Decided (owner grill) - **Scope**: capsule swap + ⋯ menus + context menus + popovers (one motion language for things that open). - **Duration cap: 500 ms total** for every one of these animations (trigger → last item fully settled). Owner: "it would be annoying if every animation took that long… cap it at 500ms and let's see how it feels". Keep the *character* of the reference (easeOutQuint, overdamped spring with the same damping ratio ≈1.08 and no overshoot, stagger in reading order, rise from below, outgoing fade shorter than incoming) but time-scale it so the cap holds. Suggested starting point: outgoing fade 120 ms; first item delay 90 ms; stagger 25 ms with the index capped at 4; rise ≈310 ms (raise spring stiffness to settle in that time at the same damping ratio); capsule width morph 400 ms easeOutQuint. Put the values in ONE shared motion module (tokens), documented; tune once from real recordings. - **Unified selection toolbar on every screen size**: desktop multi-select (Files, Photos, anything with selection) uses the same floating bottom capsule as the phone. Remove the old desktop selection toolbars/buttons it replaces (reuse gate: one component, fewer buttons; owner: "anything that makes the app simpler and more consistent / fewer buttons"). - Capsule swap choreography: width morphs from tab bar width to toolbar width; outgoing icons fade (no exit motion on items); incoming actions rise with stagger. Reverse on deselect with the same rules. Actions are tappable immediately (pointer events on during the animation). For a horizontally scrolling toolbar, only visible actions stagger. - Selected-count label ("3 selected") uses the label roll (old rolls up/out, new rolls in from below) when the count changes. - Semantics: tab bar stays navigation; the selection bar is `role="toolbar"` with an aria-live announcement ("3 selected, actions"). Focus management: if focus was on a tab icon, move it to the first action; return it on deselect. - Reduced motion: instant swap, no stagger, no roll. - Implementation notes from the owner's reference (verified by the orchestrator): keyed `{#each [current] as x (x.id)}` (not `{#key}`) so the outgoing content keeps its data during its outro; `|global` on item intros; `prefersReducedMotion` from `svelte/motion`; custom `css` transitions (compositor-friendly transform/opacity); no intro on first render. Not applicable: fixed 504 px inner width, height morph, tablist roles, Tailwind (we use tokens). - Performance: only transform/opacity animate except the capsule width (small fixed-position element); verify no long tasks/INP regression on a mid phone profile. ## Depends on #219 (phone chrome: shared contextual bottom bar) must be merged first; build on its component. ## Evidence Screen recordings (video or frame strips) of: phone select/deselect in Files and Photos, desktop multi-select in Files and Photos, ⋯ menu open/close, context menu, a popover; light + dark; plus reduced-motion. The orchestrator reviews them and sends them to the owner.

files-folder-light.png

954 KiB

files-selection-light.png

962 KiB

files-selection-dark.png

762 KiB

capsule-shortcuts-light.png

841 KiB

desktop-photos-selection.png

510 KiB

capsule-choreography.webm

266 KiB

capsule-choreography.webm

383 KiB

capsule-choreography-desktop.webm

372 KiB

capsule-choreography-390-frames.png

1.5 MiB

capsule-choreography-1440-frames.png

1.4 MiB

capsule-choreography.webm

367 KiB

capsule-choreography-390-frames.png

1.2 MiB

capsule-choreography-desktop.webm

339 KiB

capsule-choreography-1440-frames.png

1.2 MiB

capsule-choreography.webm

356 KiB

capsule-choreography-390-frames.png

1.2 MiB

capsule-choreography-desktop.webm

405 KiB

capsule-choreography-1440-frames.png

1.4 MiB

capsule-choreography-390-frames.png

1 MiB

capsule-choreography-1440-frames.png

723 KiB

capsule-choreography.webm

358 KiB

capsule-choreography-desktop.webm

202 KiB

capsule-choreography-390-frames.png

1.2 MiB

capsule-choreography-1440-frames.png

1.8 MiB

kayg referenced this issue

2026-09-27 12:42:14 +00:00

Owner test tracker: every request and when it is testable on o2 #203

kayg referenced this issue

2026-09-27 13:29:03 +00:00

BUG: Files list breaks in select mode; toasts overlap the phone tab bar #239

kayg referenced this issue

2026-09-27 16:36:07 +00:00

BUG: mode tray scroll jumps active tab to the left; highlight moves before the view (slow on real network) #243

kayg commented

2026-09-27 16:44:27 +00:00

Author

Owner

Owner grill (2026-09-27) ADDS a third capsule state to this issue (same component, same choreography; code reuse is paramount):

Keyboard shortcuts card. Pressing ? (existing shortcut, registry entry 'Show keyboard shortcuts') morphs the bottom tab-bar capsule UPWARD into a scrollable card on the shared card/overlay surface, using the exact capsule-swap choreography of this issue (width/height morph ≤ 500 ms total, items rise with the capped stagger, reverse on close; Esc / ? again / click outside closes; focus trapped while open, returned on close; reduced motion = instant). It REPLACES today's shortcut help, which opens as a bottom presentation sheet on desktop (owner screenshot: 'Help / Keyboard shortcuts' sheet with drag handle). Content: the current view's shortcuts first, then every group (General, Navigation, …), scrollable, key caps as today, prettier (owner: 'it needs to look prettier'). No hold-⌘ trigger (owner: it interferes with OS shortcuts and screenshots). No key badges on buttons.
Phone: no keyboard, so no card; with a hardware keyboard (iPad), the same morph applies.

Owner grill (2026-09-27) ADDS a third capsule state to this issue (same component, same choreography; code reuse is paramount): **Keyboard shortcuts card.** Pressing `?` (existing shortcut, registry entry 'Show keyboard shortcuts') morphs the bottom tab-bar capsule UPWARD into a scrollable card on the shared card/overlay surface, using the exact capsule-swap choreography of this issue (width/height morph ≤ 500 ms total, items rise with the capped stagger, reverse on close; Esc / `?` again / click outside closes; focus trapped while open, returned on close; reduced motion = instant). It REPLACES today's shortcut help, which opens as a bottom presentation sheet on desktop (owner screenshot: 'Help / Keyboard shortcuts' sheet with drag handle). Content: the current view's shortcuts first, then every group (General, Navigation, …), scrollable, key caps as today, prettier (owner: 'it needs to look prettier'). No hold-⌘ trigger (owner: it interferes with OS shortcuts and screenshots). No key badges on buttons. Phone: no keyboard, so no card; with a hardware keyboard (iPad), the same morph applies.

kayg referenced this issue

2026-09-27 16:44:28 +00:00

CHROME: title collapse only on phone document pages (never desktop/Calendar); desktop overlays instead of sheets #244

kayg referenced this issue

2026-09-27 17:08:53 +00:00

Owner test tracker: every request and when it is testable on o2 #203

kayg commented

2026-09-27 18:50:15 +00:00

Author

Owner

Starting #236 on branch job/motion, based on dev at d231efe9ddc5e83e12bb79577d0a518654acd9bb (the merged #219 phone chrome component). I have read the issue body and comments. I am implementing the capsule choreography, shared motion tokens, the shortcut-card state, and desktop selection-bar reuse first. I will check whether #246 has merged before touching menu primitives.

Starting #236 on branch `job/motion`, based on `dev` at `d231efe9ddc5e83e12bb79577d0a518654acd9bb` (the merged #219 phone chrome component). I have read the issue body and comments. I am implementing the capsule choreography, shared motion tokens, the shortcut-card state, and desktop selection-bar reuse first. I will check whether #246 has merged before touching menu primitives.

kayg commented

2026-09-27 19:17:20 +00:00

Author

Owner

Finding from the first targeted UI run: the capsule state tests failed with TypeError: Cannot read properties of undefined (reading 'exitFade') in TabBar.svelte. In this app build, $lib/motion inside packages/ui resolved to the web app module, not the UI package module. I changed the three UI consumers to import the package-local shared motion module. Evidence after the fix: bun run test -- src/lib/tray.svelte.test.ts — 1 file passed, 11 tests passed.

Finding from the first targeted UI run: the capsule state tests failed with `TypeError: Cannot read properties of undefined (reading 'exitFade')` in `TabBar.svelte`. In this app build, `$lib/motion` inside `packages/ui` resolved to the web app module, not the UI package module. I changed the three UI consumers to import the package-local shared motion module. Evidence after the fix: `bun run test -- src/lib/tray.svelte.test.ts` — 1 file passed, 11 tests passed.

kayg commented

2026-09-27 19:24:37 +00:00

Author

Owner

Step 1 is implemented in commits 8175730c (shared 500 ms motion budget) and cb4c2535 (three capsule states and unified selection toolbar). Targeted tests passed: Test Files 5 passed (5) and Tests 16 passed (16).

I ran the required #246 check after step 1. git fetch && git log origin/dev --oneline | grep -m1 '#246' returned 1dbd6bcd fix(web): defer sheet blur root fix to #246; there is no #246 merge commit on origin/dev. I am leaving menu/context-menu/popover choreography as the remaining step and will not touch those shared menu surfaces in this branch.

Step 1 is implemented in commits `8175730c` (shared 500 ms motion budget) and `cb4c2535` (three capsule states and unified selection toolbar). Targeted tests passed: `Test Files 5 passed (5)` and `Tests 16 passed (16)`. I ran the required #246 check after step 1. `git fetch && git log origin/dev --oneline | grep -m1 '#246'` returned `1dbd6bcd fix(web): defer sheet blur root fix to #246`; there is no #246 merge commit on `origin/dev`. I am leaving menu/context-menu/popover choreography as the remaining step and will not touch those shared menu surfaces in this branch.

kayg commented

2026-09-27 20:02:58 +00:00

Author

Owner

Production browser evidence for step 1 is attached below. The phone and desktop selection states use the shared capsule, and the phone shortcut card replaces the selection toolbar and mode tabs.

Phone chrome E2E output:
PHONE CHROME E2E PASSED; screenshots in /home/kayg/Developer/calternal-wt/motion/artifacts/phone-chrome

The runner also reports the existing sheet-blur XFAILs assigned to #246: normalized Laplacian ratios 1.013 (light) and 0.969 (dark), expected < 0.3. The exact #246 merge check still finds only 1dbd6bcd fix(web): defer sheet blur root fix to #246, so step 2 remains deferred.

Capsule choreography video: https://git.kayg.org/attachments/42eba42e-fe40-4711-86bb-5d900a8403fd

Production browser evidence for step 1 is attached below. The phone and desktop selection states use the shared capsule, and the phone shortcut card replaces the selection toolbar and mode tabs. Phone chrome E2E output: `PHONE CHROME E2E PASSED; screenshots in /home/kayg/Developer/calternal-wt/motion/artifacts/phone-chrome` The runner also reports the existing sheet-blur XFAILs assigned to #246: normalized Laplacian ratios 1.013 (light) and 0.969 (dark), expected < 0.3. The exact #246 merge check still finds only `1dbd6bcd fix(web): defer sheet blur root fix to #246`, so step 2 remains deferred. Capsule choreography video: https://git.kayg.org/attachments/42eba42e-fe40-4711-86bb-5d900a8403fd ![Phone mode tabs](https://git.kayg.org/attachments/37378883-5303-4d02-ab1f-749799a5384f) ![Phone selection capsule, light](https://git.kayg.org/attachments/754bf446-ec2c-4a79-89cf-2135e5345768) ![Phone selection capsule, dark](https://git.kayg.org/attachments/a6525b0a-55d4-4654-92c7-1ce958e8ddf8) ![Keyboard shortcuts capsule](https://git.kayg.org/attachments/5350b578-a6f1-40a5-8da5-3409f535d5ea) ![Desktop Photos selection capsule](https://git.kayg.org/attachments/b18e02b4-965e-4a71-88cd-8815499c935a)

kayg commented

2026-09-27 21:06:15 +00:00

Author

Owner

Completed step 1 of #236. The job/motion branch is pushed; no merge or deploy was made.

Built

Added shared capsule timing and transitions for the mode tabs, contextual selection toolbar, and ? shortcuts card.
Replaced the separate desktop multi-select bar with the same capsule used on phone. The shortcuts card opens from the bottom bar and returns focus to the selection toolbar.
Added production browser coverage for phone and desktop selection, shortcut-card focus, and the three-state choreography recording.

Files

packages/ui/src/motion.ts, packages/ui/src/index.ts
packages/ui/src/components/TabBar.svelte, SegmentedControl.svelte, SelectionBar.svelte, pageChrome.ts
apps/web/src/routes/+layout.svelte
apps/web/src/lib/components/KeyboardShortcutsCard.svelte (removed KeyboardShortcutsSheet.svelte)
apps/web/src/lib/a11y/focusTrap.ts, apps/web/src/lib/files/FilesBrowser.svelte, apps/web/src/lib/photos/PhotosView.svelte
Capsule, focus, selection, tray, and theme tests under apps/web/src/lib/
apps/web/e2e/phone-chrome.mjs

Commits and head

8175730c shared capsule motion budget
cb4c2535 capsule state choreography and unified selection
9a4838fc production capsule screenshots and recording
4cf53207 Svelte typecheck fix and updated theme assertion
Head: 4cf532076f863b2058d4c130f877e5529218d205

Gates

Verbatim final output lines:

cargo fmt --check
(no output; exit 0)

cargo clippy --all-targets -- -D warnings
Finished `dev` profile [unoptimized + debuginfo] target(s) in 23m 53s

cargo test
Finished `test` profile [unoptimized + debuginfo] target(s) in 12m 46s
test result: ok. 110 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 39.54s
test result: ok. 486 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.39s
test result: ok. 51 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 15.02s

bun run check
svelte-check found 0 errors and 0 warnings

bun run test
Test Files  89 passed (89)
Tests       609 passed (609)
Start at    22:59:39
Duration    123.97s (transform 68%, import 13%, environment 11%, tests 6%, setup 2%)

PHONE CHROME E2E PASSED; screenshots in /home/kayg/Developer/calternal-wt/motion/artifacts/phone-chrome

Evidence

The production phone mode-tabs, phone selection (light and dark), shortcuts card, desktop Photos selection, and 6.4-second capsule recording are attached in the preceding evidence comment. Recording: https://git.kayg.org/attachments/42eba42e-fe40-4711-86bb-5d900a8403fd

Known gaps

Step 2 (menu, context-menu, and popover cascade) is deferred. The required origin/dev check found 1dbd6bcd fix(web): defer sheet blur root fix to #246; #246 is not merged. No menu primitives were changed.
The production E2E still reports the #246 sheet-blur XFAIL: light ratio 1.013 and dark ratio 0.969, expected below 0.3.
Documented model/performance and process-isolation tests remain ignored because they require pinned assets or a separate runner.

Decisions

The item entrance cap is 500 ms: 90 ms initial delay, 25 ms stagger capped at four intervals, and a 310 ms rise. The capsule morph is 400 ms; exit fade is 120 ms; count roll is 180 ms; the spring damping ratio is 1.08.
The shortcut card puts the active mode group first and the current view's shortcuts first within that group. Closing with ? or Escape restores focus to the prior toolbar control when available, then to the current mode tab.

Completed step 1 of #236. The `job/motion` branch is pushed; no merge or deploy was made. ## Built - Added shared capsule timing and transitions for the mode tabs, contextual selection toolbar, and `?` shortcuts card. - Replaced the separate desktop multi-select bar with the same capsule used on phone. The shortcuts card opens from the bottom bar and returns focus to the selection toolbar. - Added production browser coverage for phone and desktop selection, shortcut-card focus, and the three-state choreography recording. ## Files - `packages/ui/src/motion.ts`, `packages/ui/src/index.ts` - `packages/ui/src/components/TabBar.svelte`, `SegmentedControl.svelte`, `SelectionBar.svelte`, `pageChrome.ts` - `apps/web/src/routes/+layout.svelte` - `apps/web/src/lib/components/KeyboardShortcutsCard.svelte` (removed `KeyboardShortcutsSheet.svelte`) - `apps/web/src/lib/a11y/focusTrap.ts`, `apps/web/src/lib/files/FilesBrowser.svelte`, `apps/web/src/lib/photos/PhotosView.svelte` - Capsule, focus, selection, tray, and theme tests under `apps/web/src/lib/` - `apps/web/e2e/phone-chrome.mjs` ## Commits and head - `8175730c` shared capsule motion budget - `cb4c2535` capsule state choreography and unified selection - `9a4838fc` production capsule screenshots and recording - `4cf53207` Svelte typecheck fix and updated theme assertion - Head: `4cf532076f863b2058d4c130f877e5529218d205` ## Gates Verbatim final output lines: ```text cargo fmt --check (no output; exit 0) cargo clippy --all-targets -- -D warnings Finished `dev` profile [unoptimized + debuginfo] target(s) in 23m 53s cargo test Finished `test` profile [unoptimized + debuginfo] target(s) in 12m 46s test result: ok. 110 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 39.54s test result: ok. 486 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.39s test result: ok. 51 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 15.02s bun run check svelte-check found 0 errors and 0 warnings bun run test Test Files 89 passed (89) Tests 609 passed (609) Start at 22:59:39 Duration 123.97s (transform 68%, import 13%, environment 11%, tests 6%, setup 2%) PHONE CHROME E2E PASSED; screenshots in /home/kayg/Developer/calternal-wt/motion/artifacts/phone-chrome ``` ## Evidence The production phone mode-tabs, phone selection (light and dark), shortcuts card, desktop Photos selection, and 6.4-second capsule recording are attached in the preceding evidence comment. Recording: https://git.kayg.org/attachments/42eba42e-fe40-4711-86bb-5d900a8403fd ## Known gaps - Step 2 (menu, context-menu, and popover cascade) is deferred. The required `origin/dev` check found `1dbd6bcd fix(web): defer sheet blur root fix to #246`; #246 is not merged. No menu primitives were changed. - The production E2E still reports the #246 sheet-blur XFAIL: light ratio 1.013 and dark ratio 0.969, expected below 0.3. - Documented model/performance and process-isolation tests remain ignored because they require pinned assets or a separate runner. ## Decisions - The item entrance cap is 500 ms: 90 ms initial delay, 25 ms stagger capped at four intervals, and a 310 ms rise. The capsule morph is 400 ms; exit fade is 120 ms; count roll is 180 ms; the spring damping ratio is 1.08. - The shortcut card puts the active mode group first and the current view's shortcuts first within that group. Closing with `?` or Escape restores focus to the prior toolbar control when available, then to the current mode tab.

kayg commented

2026-09-27 21:11:15 +00:00

Author

Owner

Starting #236 on branch job/motion, from dev base 3ad937ec888c1fe45ce6e1d3052383e024dc5220 (initial HEAD 4cf532076f863b2058d4c130f877e5529218d205). I will re-record the capsule choreography from the production build at the requested sizes and themes, then re-check #246 and #156 on origin/dev.

Starting #236 on branch `job/motion`, from dev base `3ad937ec888c1fe45ce6e1d3052383e024dc5220` (initial HEAD `4cf532076f863b2058d4c130f877e5529218d205`). I will re-record the capsule choreography from the production build at the requested sizes and themes, then re-check #246 and #156 on origin/dev.

kayg commented

2026-09-27 23:31:10 +00:00

Author

Owner

Production capsule captures are regenerated from CDP compositor frames. The UI is visible in both videos and frame strips, including the selection toolbar and shortcut card. The four transitions (tab → selection → tab, tab → shortcut card → tab) were captured in light and dark at 390 and 1440 CSS px.

The strips have a target frame every 50 ms for the first 600 ms after each trigger. CDP frame cadence makes nearest-source errors at most 17.9/10.8 ms on phone and 66.0/68.3 ms on desktop; the desktop strip can therefore repeat/skip a compositor moment. I am addressing the surface cascade next because #246 is on origin/dev. #156 is not on origin/dev yet, so I have not merged or run final gates.

Production capsule captures are regenerated from CDP compositor frames. The UI is visible in both videos and frame strips, including the selection toolbar and shortcut card. The four transitions (tab → selection → tab, tab → shortcut card → tab) were captured in light and dark at 390 and 1440 CSS px. - [390 video](https://git.kayg.org/attachments/08e9b24d-79d9-4bc3-b8ad-8b91a4025e9d) - [390 frame strip](https://git.kayg.org/attachments/23e69753-7c25-47d7-8738-c21924537772) - [1440 video](https://git.kayg.org/attachments/9b7c394a-e55f-4bcb-b2cb-81093f36abc9) - [1440 frame strip](https://git.kayg.org/attachments/9bdf2dd5-1393-44eb-bd4a-df6c3cc79bb7) The strips have a target frame every 50 ms for the first 600 ms after each trigger. CDP frame cadence makes nearest-source errors at most 17.9/10.8 ms on phone and 66.0/68.3 ms on desktop; the desktop strip can therefore repeat/skip a compositor moment. I am addressing the surface cascade next because #246 is on origin/dev. #156 is not on origin/dev yet, so I have not merged or run final gates.

kayg commented

2026-09-27 23:40:09 +00:00

Author

Owner

The shared surface cascade is implemented in commit 510088a4: menu rows and popover content regions now use the same opening tokens as the capsule; composer field popovers and the analytics range picker use the same helper. The last staggered item settles at 500 ms, outgoing content fades over 120 ms, and reduced motion is instant. The production web build passed, and the focused motion test passed (3/3).

Updated production captures from the current build (visible UI verified in both strips):

The strips target 50 ms intervals over the first 600 ms after each capsule trigger. This run's nearest-source errors were ≤19.2 ms on phone and ≤46.6 ms on desktop. All strips show the capsule and/or shortcut card in light and dark. #246 is on origin/dev. #156 remains open and is not on origin/dev, so I am holding the required merge, final gates, and push.

The shared surface cascade is implemented in commit `510088a4`: menu rows and popover content regions now use the same opening tokens as the capsule; composer field popovers and the analytics range picker use the same helper. The last staggered item settles at 500 ms, outgoing content fades over 120 ms, and reduced motion is instant. The production web build passed, and the focused motion test passed (3/3). Updated production captures from the current build (visible UI verified in both strips): - [390 video](https://git.kayg.org/attachments/dbfaf57f-7cd2-4602-8b7c-81ecd5177e10) - [390 frame strip](https://git.kayg.org/attachments/7837e390-ea2c-4491-8ec3-837bd1a1997e) - [1440 video](https://git.kayg.org/attachments/8a1fdd14-2ad9-4934-be4a-b8e04e4e7ce4) - [1440 frame strip](https://git.kayg.org/attachments/b802e6a8-5556-467b-9db1-405e8a36adcc) The strips target 50 ms intervals over the first 600 ms after each capsule trigger. This run's nearest-source errors were ≤19.2 ms on phone and ≤46.6 ms on desktop. All strips show the capsule and/or shortcut card in light and dark. #246 is on origin/dev. #156 remains open and is not on origin/dev, so I am holding the required merge, final gates, and push.

kayg commented

2026-09-27 23:42:05 +00:00

Author

Owner

Production popover smoke found a branch-base failure after its Calendar Preview and Files Inspector checks passed: bun e2e/popovers.mjs stops at Search uses the shared clear glass paint (apps/web/e2e/popovers.mjs:136). Current OverlaySurface.svelte renders only surface glass, while git diff origin/dev -- packages/ui/src/components/OverlaySurface.svelte shows #246 adds the expected glass-material, glass-overlay, glass-float, and glass-clear classes. I have not copied or changed that shared material behavior; I will validate it after the required origin/dev merge when #156 lands.

Production popover smoke found a branch-base failure after its Calendar Preview and Files Inspector checks passed: `bun e2e/popovers.mjs` stops at `Search uses the shared clear glass paint` (`apps/web/e2e/popovers.mjs:136`). Current `OverlaySurface.svelte` renders only `surface glass`, while `git diff origin/dev -- packages/ui/src/components/OverlaySurface.svelte` shows #246 adds the expected `glass-material`, `glass-overlay`, `glass-float`, and `glass-clear` classes. I have not copied or changed that shared material behavior; I will validate it after the required `origin/dev` merge when #156 lands.

kayg commented

2026-09-27 23:44:34 +00:00

Author

Owner

Checkpoint for #236. The capture repair and surface cascade are committed on job/motion; current HEAD is 510088a4cf5732f6478025f15a1cc97e13030edf. The worktree is clean. Capsule videos and frame strips from the current production build are attached in the previous comment.

Checks completed before merge:

bun run build
✓ built in 29.41s
Wrote site to "build"
✔ done

bun run test -- src/lib/capsule-motion.test.ts
Test Files  1 passed (1)
Tests       3 passed (3)
Start at    01:35:24
Duration    6.45s (transform 89%, import 10%)

CAPSULE CHOREOGRAPHY PASSED; screenshots in /home/kayg/Developer/calternal-wt/motion/artifacts/phone-chrome

bun e2e/popovers.mjs passed Calendar Preview and Files Inspector, then stopped at the pre-merge Search material assertion. Evidence and the matching #246 changes are described in the prior finding comment.

origin/dev is still at 088e17d4 (includes #246), and #156 is still Open. I have not merged, run final workspace gates, cleaned build output, or pushed. Those steps remain pending #156 landing on origin/dev.

Checkpoint for #236. The capture repair and surface cascade are committed on `job/motion`; current HEAD is `510088a4cf5732f6478025f15a1cc97e13030edf`. The worktree is clean. Capsule videos and frame strips from the current production build are attached in the previous comment. Checks completed before merge: ```text bun run build ✓ built in 29.41s Wrote site to "build" ✔ done bun run test -- src/lib/capsule-motion.test.ts Test Files 1 passed (1) Tests 3 passed (3) Start at 01:35:24 Duration 6.45s (transform 89%, import 10%) CAPSULE CHOREOGRAPHY PASSED; screenshots in /home/kayg/Developer/calternal-wt/motion/artifacts/phone-chrome ``` `bun e2e/popovers.mjs` passed Calendar Preview and Files Inspector, then stopped at the pre-merge Search material assertion. Evidence and the matching #246 changes are described in the prior finding comment. `origin/dev` is still at `088e17d4` (includes #246), and #156 is still Open. I have not merged, run final workspace gates, cleaned build output, or pushed. Those steps remain pending #156 landing on `origin/dev`.

kayg commented

2026-09-27 23:47:41 +00:00

Author

Owner

Orchestrator review of the re-recorded strips (390 frames): open choreography good (? card morphs up from the tab bar, settled ≈250 ms; selection toolbar settled ≈150 ms). Missing: the REVERSE on close/deselect: card → tab bar and selection → tab bar currently snap back at 0 ms. Spec: reverse with the same rules (card shrinks back down into the capsule, toolbar actions fade while the capsule morphs back), ≤ 500 ms. Do this when resuming after #156 lands.

kayg commented

2026-09-28 00:26:30 +00:00

Author

Owner

Resuming #236 on job/motion. Initial HEAD: 510088a4cf5732f6478025f15a1cc97e13030edf; current origin/dev: 976b804f99188feb300e391c1942836599e2d429 (the branch's current merge base is 3ad937ec888c1fe45ce6e1d3052383e024dc5220). I will implement reverse close/deselect choreography within the shared 500 ms motion budget, record production frame strips including the reverse, merge origin/dev once, run the requested gates, push job/motion, and report the evidence and output here.

Resuming #236 on `job/motion`. Initial HEAD: `510088a4cf5732f6478025f15a1cc97e13030edf`; current `origin/dev`: `976b804f99188feb300e391c1942836599e2d429` (the branch's current merge base is `3ad937ec888c1fe45ce6e1d3052383e024dc5220`). I will implement reverse close/deselect choreography within the shared 500 ms motion budget, record production frame strips including the reverse, merge `origin/dev` once, run the requested gates, push `job/motion`, and report the evidence and output here.

kayg commented

2026-09-28 00:38:28 +00:00

Author

Owner

Finding from the latest production review: the 390 px reverse rows currently snap to the tab bar. The source confirms the pane outro is only a 120 ms opacity fade (capsulePaneTransition), while the stage's 400 ms width/height change does not clip the outgoing surface. I am changing the return leg to keep the outgoing capsule surface alive for the morph, fade its contents over the existing short exit token, and clip it to the stage while the measured box shrinks. The shortcut-card focus return will happen as soon as the tab state is active.

Finding from the latest production review: the 390 px reverse rows currently snap to the tab bar. The source confirms the pane outro is only a 120 ms opacity fade (`capsulePaneTransition`), while the stage's 400 ms width/height change does not clip the outgoing surface. I am changing the return leg to keep the outgoing capsule surface alive for the morph, fade its contents over the existing short exit token, and clip it to the stage while the measured box shrinks. The shortcut-card focus return will happen as soon as the tab state is active.

kayg commented

2026-09-28 01:09:01 +00:00

Author

Owner

Production capture finding: the dedicated bun e2e/phone-chrome.mjs --capsule-only run passed, including the reverse-pane and 400 ms morph assertions at 390 and 1440 px in light and dark. A full bun e2e/phone-chrome.mjs run also reached all reverse assertions, then stopped at 1440px dark tab-to-selection 500ms frame: nearest CDP source-frame error was 118.1 ms (27 frames at 960×600; the limit is 100 ms). The prior dedicated capture's worst error was 90.3 ms. This is capture cadence under load; the capsule transition assertions passed. The existing #246 sheet-blur XFAILs were also reported by the full run (light 1.013, dark 0.969; expected <0.3).

Production capture finding: the dedicated `bun e2e/phone-chrome.mjs --capsule-only` run passed, including the reverse-pane and 400 ms morph assertions at 390 and 1440 px in light and dark. A full `bun e2e/phone-chrome.mjs` run also reached all reverse assertions, then stopped at `1440px dark tab-to-selection 500ms frame`: nearest CDP source-frame error was 118.1 ms (27 frames at 960×600; the limit is 100 ms). The prior dedicated capture's worst error was 90.3 ms. This is capture cadence under load; the capsule transition assertions passed. The existing #246 sheet-blur XFAILs were also reported by the full run (light 1.013, dark 0.969; expected <0.3).

kayg commented

2026-09-28 01:18:25 +00:00

Author

Owner

Merge finding: origin/dev adds the contextual bottom bar only on phones (from #219, commit 0c3f84b7). The merged production behavior keeps that scope. I adjusted the real-page capture accordingly: phone strips cover selection → tabs and shortcuts → tabs; desktop strips cover the shared shortcut-card reverse. This preserves the latest #219 behavior while checking each actual reverse morph.

Merge finding: `origin/dev` adds the contextual bottom bar only on phones (from #219, commit 0c3f84b7). The merged production behavior keeps that scope. I adjusted the real-page capture accordingly: phone strips cover selection → tabs and shortcuts → tabs; desktop strips cover the shared shortcut-card reverse. This preserves the latest #219 behavior while checking each actual reverse morph.

kayg commented

2026-09-28 01:20:43 +00:00

Author

Owner

Merged-build finding: the 390 px production capture reached tabs after closing selection, but its two-frame reverse check did not find .capsule-pane[data-capsule-returning]. The run stopped before saving strips. I am checking the live outgoing-pane lifecycle and will rerun capture after the fix.

Merged-build finding: the 390 px production capture reached `tabs` after closing selection, but its two-frame reverse check did not find `.capsule-pane[data-capsule-returning]`. The run stopped before saving strips. I am checking the live outgoing-pane lifecycle and will rerun capture after the fix.

kayg referenced this issue

2026-09-28 01:22:16 +00:00

Owner test tracker: every request and when it is testable on o2 #203

kayg commented

2026-09-28 01:26:49 +00:00

Author

Owner

Fix: Svelte destroys a pane's action binding when its keyed block begins an outro, before the parent effect can mark it. capsulePaneTransition now tags the outgoing pane while it owns the transition node. The capture confirmed each reverse morph at 390 px and 1440 px, and saved both light/dark frame strips and clips. It ended with only a SLOW capture threshold finding: 1440 px dark had a 600 ms nearest-sample error under host load. I retained the 100 ms assertion and made the capture write review artifacts before reporting that finding.

Fix: Svelte destroys a pane's action binding when its keyed block begins an outro, before the parent effect can mark it. `capsulePaneTransition` now tags the outgoing pane while it owns the transition node. The capture confirmed each reverse morph at 390 px and 1440 px, and saved both light/dark frame strips and clips. It ended with only a SLOW capture threshold finding: 1440 px dark had a 600 ms nearest-sample error under host load. I retained the 100 ms assertion and made the capture write review artifacts before reporting that finding.

kayg commented

2026-09-28 01:43:59 +00:00

Author

Owner

Merged web-check finding: svelte-check reported Type 'number' is not assignable to type 'Timeout' for the window.setTimeout handle in TabBar.svelte. The field now uses ReturnType<typeof window.setTimeout>, which matches the browser timer that it stores.

Merged web-check finding: `svelte-check` reported `Type 'number' is not assignable to type 'Timeout'` for the `window.setTimeout` handle in `TabBar.svelte`. The field now uses `ReturnType<typeof window.setTimeout>`, which matches the browser timer that it stores.

kayg commented

2026-09-28 01:45:28 +00:00

Author

Owner

Correction: the initial ReturnType<typeof window.setTimeout> annotation still resolved to Node's Timeout overload, while the browser call returns a number. I changed the field to number | null and both clear sites to window.clearTimeout.

Correction: the initial `ReturnType<typeof window.setTimeout>` annotation still resolved to Node's `Timeout` overload, while the browser call returns a number. I changed the field to `number | null` and both clear sites to `window.clearTimeout`.

kayg commented

2026-09-28 01:47:32 +00:00

Author

Owner

Web-unit finding: 92 files passed, but the capsule motion unit test failed because its outgoing-node fixture was {} and the reverse transition now sets a DOM marker. I am replacing that fixture with a real DOM element and adding an assertion for the marker; motion expectations remain unchanged.

Web-unit finding: 92 files passed, but the capsule motion unit test failed because its outgoing-node fixture was `{}` and the reverse transition now sets a DOM marker. I am replacing that fixture with a real DOM element and adding an assertion for the marker; motion expectations remain unchanged.

kayg commented

2026-09-28 01:48:53 +00:00

Author

Owner

Test-fixture correction: the web unit project runs in Node, so document.createElement is unavailable. I will use a small Element stub that records setAttribute, preserving the marker assertion without adding a DOM environment dependency.

Test-fixture correction: the web unit project runs in Node, so `document.createElement` is unavailable. I will use a small `Element` stub that records `setAttribute`, preserving the marker assertion without adding a DOM environment dependency.

kayg commented

2026-09-28 01:55:32 +00:00

Author

Owner

The required local adversarial round found an editor inconsistency outside the capsule change. tests/adversarial/editor.mjs reported seed 25608414: the browser state had 1 image after hostile paste/IME, then the undo storm left 1 image, and history replay ended with 3 images and a duplicate ^duplicate-id block anchor (FINDING editor browser editor paste, Unicode, and history storm). The editor probe is still running. I am filing this separately with the reproduction evidence.

The required local adversarial round found an editor inconsistency outside the capsule change. `tests/adversarial/editor.mjs` reported seed `25608414`: the browser state had 1 image after hostile paste/IME, then the undo storm left 1 image, and history replay ended with 3 images and a duplicate `^duplicate-id` block anchor (`FINDING editor browser editor paste, Unicode, and history storm`). The editor probe is still running. I am filing this separately with the reproduction evidence.

kayg referenced this issue

2026-09-28 01:55:43 +00:00

Editor undo/redo storm duplicates pasted image #280

kayg commented

2026-09-28 02:14:33 +00:00

Author

Owner

#236 final report — reverse capsule choreography is implemented and pushed on job/motion.

Built

Closing phone selection returns the selection bar to the mode tabs. Closing the shortcut card returns it to the capsule. Both reverse morphs retain the outgoing surface and contract the measured capsule over 400 ms; the content fade is 120 ms, focus moves to the live destination, and reduced motion remains instant.
Preserved origin/dev mode preloading and menu behavior. pageChrome.ts retains both the contextual bar types and the incoming breadcrumb API.
Recorded production frame strips and clips. The phone capture includes selection → tabs and shortcut card → tabs. The desktop capture includes the shortcut card reverse, matching #219's phone-only contextual bar behavior.

Files

packages/ui/src/motion.ts
packages/ui/src/components/TabBar.svelte
packages/ui/src/components/SelectionBar.svelte
packages/ui/src/components/pageChrome.ts
packages/ui/src/components/menu/Menu.svelte
packages/ui/src/components/menu/MenuItem.svelte
apps/web/src/routes/+layout.svelte
apps/web/src/lib/components/KeyboardShortcutsCard.svelte
apps/web/src/lib/capsule-motion.test.ts
apps/web/e2e/phone-chrome.mjs

Commits

Feature: f94f136a — fix(ui): morph capsule surfaces back on close
One merge of origin/dev: fd4e5ad1
Reverse transition lifecycle, browser timer typing and fixture fixes: acc1c985, 4b70c8be, 31b6bfec
Phone-only contextual bar documentation: 2101789e

Head: 2101789ead8965464b93e958d6d4e5599372eee3 (remote origin/job/motion matches). The last commit changes comments only; final gates ran on the preceding code state. cargo clean removed build output, and apps/web/build plus apps/web/.svelte-kit were deleted.

Gates

Verbatim output:

cargo fmt --check
(no stdout or stderr; exit code 0)

cargo clippy --all-targets -- -D warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 52s

cargo test
    Finished `test` profile [unoptimized + debuginfo] target(s) in 2m 59s
test result: ok. 57 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 10.95s

bun run check
svelte-check found 0 errors and 0 warnings

bun run test
 Test Files  93 passed (93)
      Tests  636 passed (636)
   Start at  03:49:08
   Duration  62.94s (transform 59%, import 16%, environment 14%, tests 8%, setup 3%)

The Rust test log had 72 per-target summaries: 1,329 passed, 0 failed and 12 ignored.

Review artifacts

Phone capsule clip · Desktop capsule clip

All reverse assertions passed. The capture exited on its preserved 100 ms sampling check after writing the artifacts: SLOW CAPSULE 1440px dark: nearest-sample error up to 600.0 ms (limit 100 ms). This is a slow capture result under host load.

Adversarial round and gaps

The local-server round ran for 15:58 and stopped during attack2.py's logrewrite section. Hostile-byte probes reported ==== HOSTILE BYTES FINDINGS 0; no other non-SLOW API finding appeared in the completed sections. The media thumbnail check did not finish within 10 seconds, so its optional header check was skipped. The zip stream and several write probes reported SLOW latency.

The editor paste/undo/redo probe found a separate content duplication: after history replay it reported 3 images and duplicate ^duplicate-id anchors, seed 25608414. I filed the evidence in #280; it is outside the capsule change and needs owner triage.

Decisions

I kept #219's phone-only contextual bar behavior from origin/dev. The desktop strip therefore covers the real shortcut-card reverse path, while the phone strip covers both selection and shortcut reversals. The capsule morph stays at 400 ms, under the 500 ms cap.

#236 final report — reverse capsule choreography is implemented and pushed on `job/motion`. ## Built - Closing phone selection returns the selection bar to the mode tabs. Closing the shortcut card returns it to the capsule. Both reverse morphs retain the outgoing surface and contract the measured capsule over 400 ms; the content fade is 120 ms, focus moves to the live destination, and reduced motion remains instant. - Preserved `origin/dev` mode preloading and menu behavior. `pageChrome.ts` retains both the contextual bar types and the incoming breadcrumb API. - Recorded production frame strips and clips. The phone capture includes selection → tabs and shortcut card → tabs. The desktop capture includes the shortcut card reverse, matching #219's phone-only contextual bar behavior. ## Files - `packages/ui/src/motion.ts` - `packages/ui/src/components/TabBar.svelte` - `packages/ui/src/components/SelectionBar.svelte` - `packages/ui/src/components/pageChrome.ts` - `packages/ui/src/components/menu/Menu.svelte` - `packages/ui/src/components/menu/MenuItem.svelte` - `apps/web/src/routes/+layout.svelte` - `apps/web/src/lib/components/KeyboardShortcutsCard.svelte` - `apps/web/src/lib/capsule-motion.test.ts` - `apps/web/e2e/phone-chrome.mjs` ## Commits - Feature: `f94f136a` — `fix(ui): morph capsule surfaces back on close` - One merge of `origin/dev`: `fd4e5ad1` - Reverse transition lifecycle, browser timer typing and fixture fixes: `acc1c985`, `4b70c8be`, `31b6bfec` - Phone-only contextual bar documentation: `2101789e` Head: `2101789ead8965464b93e958d6d4e5599372eee3` (remote `origin/job/motion` matches). The last commit changes comments only; final gates ran on the preceding code state. `cargo clean` removed build output, and `apps/web/build` plus `apps/web/.svelte-kit` were deleted. ## Gates Verbatim output: ```text cargo fmt --check (no stdout or stderr; exit code 0) cargo clippy --all-targets -- -D warnings Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 52s cargo test Finished `test` profile [unoptimized + debuginfo] target(s) in 2m 59s test result: ok. 57 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 10.95s bun run check svelte-check found 0 errors and 0 warnings bun run test Test Files 93 passed (93) Tests 636 passed (636) Start at 03:49:08 Duration 62.94s (transform 59%, import 16%, environment 14%, tests 8%, setup 3%) ``` The Rust test log had 72 per-target summaries: 1,329 passed, 0 failed and 12 ignored. ## Review artifacts ![Phone capsule frame strip](https://git.kayg.org/attachments/b2cb719d-cca7-4bed-939a-935b084cbed0) ![Desktop capsule frame strip](https://git.kayg.org/attachments/50eaf501-cf6a-4ad1-a215-434b59960e5c) [Phone capsule clip](https://git.kayg.org/attachments/1d511542-dd1f-403d-9279-3803a9bd5a47) · [Desktop capsule clip](https://git.kayg.org/attachments/0aba7729-1261-4d72-9d4e-641470cd2d63) All reverse assertions passed. The capture exited on its preserved 100 ms sampling check after writing the artifacts: `SLOW CAPSULE 1440px dark: nearest-sample error up to 600.0 ms (limit 100 ms)`. This is a slow capture result under host load. ## Adversarial round and gaps The local-server round ran for 15:58 and stopped during `attack2.py`'s `logrewrite` section. Hostile-byte probes reported `==== HOSTILE BYTES FINDINGS 0`; no other non-SLOW API finding appeared in the completed sections. The media thumbnail check did not finish within 10 seconds, so its optional header check was skipped. The zip stream and several write probes reported SLOW latency. The editor paste/undo/redo probe found a separate content duplication: after history replay it reported 3 images and duplicate `^duplicate-id` anchors, seed `25608414`. I filed the evidence in [#280](https://git.kayg.org/kayg/calternal/issues/280); it is outside the capsule change and needs owner triage. ## Decisions I kept #219's phone-only contextual bar behavior from `origin/dev`. The desktop strip therefore covers the real shortcut-card reverse path, while the phone strip covers both selection and shortcut reversals. The capsule morph stays at 400 ms, under the 500 ms cap.

kayg commented

2026-09-28 02:18:42 +00:00

Author

Owner

Starting #236 follow-up on branch job/motion at 2101789ead8965464b93e958d6d4e5599372eee3. The branch's current merge base with dev is 55a974d32c5ce1a5e138d4ff04db3db2a5b0855f; origin/dev is currently 104b7db2cd70240685e1464b7ecc3aa828a25415 and will be merged once before final gates. I am tracing the dark-theme shortcut-card outro and restoring the shared desktop selection capsule, then I will add the ≤500 ms regression check and record both desktop strips.

Starting #236 follow-up on branch `job/motion` at `2101789ead8965464b93e958d6d4e5599372eee3`. The branch's current merge base with dev is `55a974d32c5ce1a5e138d4ff04db3db2a5b0855f`; `origin/dev` is currently `104b7db2cd70240685e1464b7ecc3aa828a25415` and will be merged once before final gates. I am tracing the dark-theme shortcut-card outro and restoring the shared desktop selection capsule, then I will add the ≤500 ms regression check and record both desktop strips.

kayg commented

2026-09-28 02:24:20 +00:00

Author

Owner

Finding: commit 2101789e documents the contextual slot as phone-only and changed pageChrome.ts from “on every screen size” to “phone's bottom chrome row.” In apps/web/src/routes/+layout.svelte, the shell also filters the slot with mobile.current (line 95), so Files and Photos publish a SelectionBar on desktop but the shared TabBar never receives it. The existing same SelectionBar component and row capsule can render this state on desktop; I am removing the width filter and correcting the stale phone-only contract. The current close timing is being checked in the real production browser before identifying its cause.

Finding: commit `2101789e` documents the contextual slot as phone-only and changed `pageChrome.ts` from “on every screen size” to “phone's bottom chrome row.” In `apps/web/src/routes/+layout.svelte`, the shell also filters the slot with `mobile.current` (line 95), so Files and Photos publish a `SelectionBar` on desktop but the shared `TabBar` never receives it. The existing same `SelectionBar` component and row capsule can render this state on desktop; I am removing the width filter and correcting the stale phone-only contract. The current close timing is being checked in the real production browser before identifying its cause.

kayg commented

2026-09-28 02:49:49 +00:00

Author

Owner

Finding: the desktop production probe confirmed the close overruns the 500 ms cap. A light-theme Escape close removed the card at 538.3 ms. The in-page animation trace showed the pane's 400 ms transition beginning about 76 ms after the key event and the stage's 400 ms width morph beginning about 129 ms after it; the two-frame setup in TabBar.svelte consumed most of the remaining budget. Also, KeyboardShortcutsCard.svelte used bidirectional transition: for staggered rows, so Svelte reused their 190 ms entrance delays during an outro. I changed the rows to global intro-only transitions and am removing the second frame by flushing the transition style before measuring the new size.

Finding: the desktop production probe confirmed the close overruns the 500 ms cap. A light-theme Escape close removed the card at 538.3 ms. The in-page animation trace showed the pane's 400 ms transition beginning about 76 ms after the key event and the stage's 400 ms width morph beginning about 129 ms after it; the two-frame setup in `TabBar.svelte` consumed most of the remaining budget. Also, `KeyboardShortcutsCard.svelte` used bidirectional `transition:` for staggered rows, so Svelte reused their 190 ms entrance delays during an outro. I changed the rows to global intro-only transitions and am removing the second frame by flushing the transition style before measuring the new size.

kayg referenced this issue

2026-09-28 03:35:18 +00:00

Owner test tracker: every request and when it is testable on o2 #203

kayg commented

2026-09-28 03:37:48 +00:00

Author

Owner

Adversarial finding from the single tests/adversarial/run.sh pass: editor.mjs reported editor findings=1 at seed 25608414. After hostile paste/IME and block actions, the browser undo/redo round trip changed the editor text. The actual text omitted Image not available before ^tvdys0 and changed spacing around Anchor heading compared with the expected text. This is in the merged editor surface and is outside the motion change; recording it here for triage. The remaining probes are still running.

Adversarial finding from the single `tests/adversarial/run.sh` pass: `editor.mjs` reported `editor findings=1` at seed `25608414`. After hostile paste/IME and block actions, the browser undo/redo round trip changed the editor text. The actual text omitted `Image not available` before `^tvdys0` and changed spacing around `Anchor heading` compared with the expected text. This is in the merged editor surface and is outside the motion change; recording it here for triage. The remaining probes are still running.

kayg commented

2026-09-28 03:54:26 +00:00

Author

Owner

Completed Forgejo #236 on job/motion.

Built

Fixed shortcut-card exit timing. Shortcut rows now stagger on entry only; TabBar enables the size morph in one frame, and the shared morph is 200 ms. In the final production run, the card detached in 289–362 ms after Escape, ?, and outside pointer-down across light and dark themes.
Restored desktop photo multi-selection in the same shared bottom capsule used on phones. The 1440 px strip records tab → two-photo selection → tab and both shortcut transitions.
Added the cross-theme dismissal assertions and desktop multi-select capture to apps/web/e2e/phone-chrome.mjs.

Files changed for #236

apps/web/e2e/phone-chrome.mjs
apps/web/src/lib/components/KeyboardShortcutsCard.svelte
apps/web/src/routes/+layout.svelte
packages/ui/src/components/TabBar.svelte
packages/ui/src/components/pageChrome.ts
packages/ui/src/motion.ts

Desktop scope provenance: commit 0c3f84b7 (Share the phone contextual bottom bar, merged by c56105a9 / #219) added the mobile.current filter in +layout.svelte. Commit 2101789e changed scope comments only. The layout now passes the page bar to the same capsule at every viewport size.

Production strips

Gates

cargo fmt --check: no output; exit 0.
cargo clippy --all-targets -- -D warnings:
Finished dev profile [unoptimized + debuginfo] target(s) in 2m 35s
cargo test: the captured output has 72 test result: ok summaries and no failed results. After Cargo finished, the shell wrapper printed zsh:1: read-only variable: status and exited 1 because status is a reserved zsh variable; the suite itself completed.
bun run --cwd apps/web check:
svelte-check found 0 errors and 0 warnings
bun run --cwd apps/web test:
Test Files 106 passed (106)
Tests 684 passed (684)
Duration 52.59s (transform 54%, environment 17%, import 16%, tests 9%, setup 4%)
Production build:
✓ built in 23.45s
Wrote site to "build"
✔ done
bun apps/web/e2e/phone-chrome.mjs --capsule-only: CAPSULE CHOREOGRAPHY PASSED; six desktop dismissal checks were 289–362 ms.

Adversarial round and gaps

The real-server API matrix completed 1,083 requests; hostile-byte probes reported ==== HOSTILE BYTES FINDINGS 0, and the server remained alive. The first runner invocation stopped at its CLI section because I reused the server binary and skipped the build that creates target/debug/calternal. I built the CLI and completed only that omitted section:

cli ls names: 2
server alive at end: True
==== ROUND 2 FINDINGS 0
==== ROUND 2 SLOW 0

Load-only reports were calendar writes at 5.4–5.6 s, a ZIP stream exceeding 30 s, and a thumbnail not ready after 10 s. The editor browser probe found one unrelated undo/redo text mismatch (seed 25608414: the image fallback text and spacing around block anchors changed); I recorded its exact delta in an earlier #236 comment for triage. No editor files were changed for this job.

Decisions and commits

The design docs did not set the final morph duration. I used 200 ms after a 300 ms production run reached 538 ms from Escape to DOM removal; at 200 ms, all six final dismissal timings were 289–362 ms. The owner can review this timing in the attached strips.

Commits: 30f3d17e, 0a98b6b9, 67af1585, merge 75f0a914, and f8166680.

Head: f816668046ad2746c653dbf4cafbe78e813291b9 (pushed; Everything up-to-date).

Completed Forgejo #236 on `job/motion`. ## Built - Fixed shortcut-card exit timing. Shortcut rows now stagger on entry only; `TabBar` enables the size morph in one frame, and the shared morph is 200 ms. In the final production run, the card detached in 289–362 ms after Escape, `?`, and outside pointer-down across light and dark themes. - Restored desktop photo multi-selection in the same shared bottom capsule used on phones. The 1440 px strip records tab → two-photo selection → tab and both shortcut transitions. - Added the cross-theme dismissal assertions and desktop multi-select capture to `apps/web/e2e/phone-chrome.mjs`. ## Files changed for #236 - `apps/web/e2e/phone-chrome.mjs` - `apps/web/src/lib/components/KeyboardShortcutsCard.svelte` - `apps/web/src/routes/+layout.svelte` - `packages/ui/src/components/TabBar.svelte` - `packages/ui/src/components/pageChrome.ts` - `packages/ui/src/motion.ts` Desktop scope provenance: commit `0c3f84b7` (`Share the phone contextual bottom bar`, merged by `c56105a9` / #219) added the `mobile.current` filter in `+layout.svelte`. Commit `2101789e` changed scope comments only. The layout now passes the page bar to the same capsule at every viewport size. ## Production strips ![390 px capsule choreography](https://git.kayg.org/attachments/b275216e-5292-4a15-b744-aac1fa697a3a) ![1440 px capsule choreography with desktop selection](https://git.kayg.org/attachments/69f567af-2f8c-46e9-b922-8142ed7911e2) ## Gates - `cargo fmt --check`: no output; exit 0. - `cargo clippy --all-targets -- -D warnings`: `Finished dev profile [unoptimized + debuginfo] target(s) in 2m 35s` - `cargo test`: the captured output has 72 `test result: ok` summaries and no failed results. After Cargo finished, the shell wrapper printed `zsh:1: read-only variable: status` and exited 1 because `status` is a reserved zsh variable; the suite itself completed. - `bun run --cwd apps/web check`: `svelte-check found 0 errors and 0 warnings` - `bun run --cwd apps/web test`: `Test Files 106 passed (106)` `Tests 684 passed (684)` `Duration 52.59s (transform 54%, environment 17%, import 16%, tests 9%, setup 4%)` - Production build: `✓ built in 23.45s` `Wrote site to "build"` `✔ done` - `bun apps/web/e2e/phone-chrome.mjs --capsule-only`: `CAPSULE CHOREOGRAPHY PASSED`; six desktop dismissal checks were 289–362 ms. ## Adversarial round and gaps The real-server API matrix completed 1,083 requests; hostile-byte probes reported `==== HOSTILE BYTES FINDINGS 0`, and the server remained alive. The first runner invocation stopped at its CLI section because I reused the server binary and skipped the build that creates `target/debug/calternal`. I built the CLI and completed only that omitted section: ```text cli ls names: 2 server alive at end: True ==== ROUND 2 FINDINGS 0 ==== ROUND 2 SLOW 0 ``` Load-only reports were calendar writes at 5.4–5.6 s, a ZIP stream exceeding 30 s, and a thumbnail not ready after 10 s. The editor browser probe found one unrelated undo/redo text mismatch (seed `25608414`: the image fallback text and spacing around block anchors changed); I recorded its exact delta in an earlier #236 comment for triage. No editor files were changed for this job. ## Decisions and commits The design docs did not set the final morph duration. I used 200 ms after a 300 ms production run reached 538 ms from Escape to DOM removal; at 200 ms, all six final dismissal timings were 289–362 ms. The owner can review this timing in the attached strips. Commits: `30f3d17e`, `0a98b6b9`, `67af1585`, merge `75f0a914`, and `f8166680`. Head: `f816668046ad2746c653dbf4cafbe78e813291b9` (pushed; `Everything up-to-date`).

kayg referenced this issue from a commit

2026-09-28 03:58:12 +00:00

Merge job/motion (#236)

kayg commented

2026-09-28 03:58:38 +00:00

Author

Owner

Merged in af9ebd42 (svelte-check 0/0, web 698/698). Unified selection capsule on desktop + phone, ? shortcut card morph + reverse (dismiss 289–362 ms), menu/popover cascade, one motion token module. Open for owner review: the card's opening frames show a plain oval for ~100 ms before content appears; tune in the motion module if the owner prefers a scale morph.

Merged in af9ebd42 (svelte-check 0/0, web 698/698). Unified selection capsule on desktop + phone, ? shortcut card morph + reverse (dismiss 289–362 ms), menu/popover cascade, one motion token module. Open for owner review: the card's opening frames show a plain oval for ~100 ms before content appears; tune in the motion module if the owner prefers a scale morph.

kayg closed this issue

2026-09-28 03:58:39 +00:00

kayg referenced this issue

2026-09-28 03:58:53 +00:00

FOLLOW-UP from #235 adversarial round: DAV/Journal/bookmark timeouts, pasted-image undo duplication, 10k-block collab timeout #265

kayg referenced this issue

2026-09-28 04:13:17 +00:00

CHROME: title collapse only on phone document pages (never desktop/Calendar); desktop overlays instead of sheets #244

kayg referenced this issue

2026-09-28 06:12:32 +00:00

TABBAR: context toolbar on any item selection; ⌘/Ctrl-hold drag to reorder tabs; remove Appearance → Mode #290

kayg referenced this issue