kayg/calternal
Watch
1
0
Fork
You've already forked calternal
 0
Code Issues 803 Pull requests Projects Releases Packages Wiki Activity Actions 430

Web: full page reloads on in-app navigation after deploys (old build chunks gone); keep previous immutable assets, graceful update #423

New issue
Open
opened 2026-09-29 09:32:29 +00:00 by kayg · 81 comments
kayg commented 2026-09-29 09:32:29 +00:00
Owner
Copy link

Bug (owner, 2026-09-29, calternal.cloud, with a screenshot of a blank page mid-reload at /files)

"I notice that a full refresh of the page happens too often. This happened when I was inside a folder and clicked the top 'Files' header to navigate to the root of the FS tree."

Leading hypothesis (orchestrator, verify first)

deploy/deploy-cloud.sh bakes the web build into the server image, and the server serves _app/immutable/* only from the current build (crates/calternal-server/src/main.rs around line 991). After each deploy (about 15 per day now), a tab opened on the old build requests route chunks that no longer exist. SvelteKit then falls back to a full location.href navigation, which shows a blank page until the new app boots.
No code in apps/web forces a reload on that link (checked: no data-sveltekit-reload, no location.assign, except the error-page retry and the OAuth flows).

Work

  1. Reproduce: serve build A, open /files/<folder>, then swap in build B (a different commit) without reloading the tab, and click the "Files" header. Record whether the page does a full document load (Performance API navigation entries, or a pagehide counter). Also try without a build change, to rule out a second cause: header link markup, a goto to a different origin or base, invalidateAll, the service worker, or an +error fallback. Report every cause found.
  2. Fix the deploy cause: keep the hashed _app/immutable/** files from previous builds for at least the last 10 deploys, or 7 days, whichever is longer. Hashed names never collide, so a union directory is safe. Store them in the persistent data volume (for example /data/.system/web-assets/, bounded and pruned by age) and serve them with the existing immutable cache headers. Old tabs then keep navigating in-app. HTML and version.json stay current.
  3. Graceful update: use SvelteKit's version.pollInterval and the updated state. When a new build exists, the next navigation performs a full load on purpose (not as a crash fallback), and only at a navigation boundary, never while the User is typing in the composer or an editor with unsaved state. Optionally show a quiet toast, "calternal was updated", with a Reload action. Never reload silently in the middle of an edit.
  4. Blank flash: when a full load does happen, app.html shows the themed background and the chrome skeleton immediately, from inline critical CSS, instead of a blank page.

Proof

  • An e2e with two builds: open a page on build A, switch the server to build B, and perform 20 in-app navigations across modes. Assert zero full document loads until the update boundary, then exactly one.
  • Measure the size of the retained-asset store after 10 simulated deploys.
  • The adversarial round: request paths under _app/immutable/ with traversal, huge names and unknown hashes. Unknown hashes return 404, never an index fallback.
    Gates as in the preamble.
## Bug (owner, 2026-09-29, calternal.cloud, with a screenshot of a blank page mid-reload at /files) "I notice that a full refresh of the page happens too often. This happened when I was inside a folder and clicked the top 'Files' header to navigate to the root of the FS tree." ## Leading hypothesis (orchestrator, verify first) `deploy/deploy-cloud.sh` bakes the web build into the server image, and the server serves `_app/immutable/*` only from the current build (`crates/calternal-server/src/main.rs` around line 991). After each deploy (about 15 per day now), a tab opened on the old build requests route chunks that no longer exist. SvelteKit then falls back to a full `location.href` navigation, which shows a blank page until the new app boots. No code in `apps/web` forces a reload on that link (checked: no `data-sveltekit-reload`, no `location.assign`, except the error-page retry and the OAuth flows). ## Work 1. **Reproduce:** serve build A, open `/files/<folder>`, then swap in build B (a different commit) without reloading the tab, and click the "Files" header. Record whether the page does a full document load (Performance API `navigation` entries, or a `pagehide` counter). Also try without a build change, to rule out a second cause: header link markup, a `goto` to a different origin or base, `invalidateAll`, the service worker, or an `+error` fallback. Report every cause found. 2. **Fix the deploy cause:** keep the hashed `_app/immutable/**` files from previous builds for at least the last 10 deploys, or 7 days, whichever is longer. Hashed names never collide, so a union directory is safe. Store them in the persistent data volume (for example `/data/.system/web-assets/`, bounded and pruned by age) and serve them with the existing immutable cache headers. Old tabs then keep navigating in-app. HTML and `version.json` stay current. 3. **Graceful update:** use SvelteKit's `version.pollInterval` and the `updated` state. When a new build exists, the next navigation performs a full load *on purpose* (not as a crash fallback), and only at a navigation boundary, never while the User is typing in the composer or an editor with unsaved state. Optionally show a quiet toast, "calternal was updated", with a Reload action. Never reload silently in the middle of an edit. 4. **Blank flash:** when a full load does happen, `app.html` shows the themed background and the chrome skeleton immediately, from inline critical CSS, instead of a blank page. ## Proof - An e2e with two builds: open a page on build A, switch the server to build B, and perform 20 in-app navigations across modes. Assert zero full document loads until the update boundary, then exactly one. - Measure the size of the retained-asset store after 10 simulated deploys. - The adversarial round: request paths under `_app/immutable/` with traversal, huge names and unknown hashes. Unknown hashes return 404, never an index fallback. Gates as in the preamble.
reload-423-screenshots.zip
8.2 MiB
boot-390-light.png
251 KiB
boot-390-dark.png
234 KiB
boot-1440-light.png
564 KiB
boot-1440-dark.png
360 KiB
reload-423-same-build-capture.zip
5.9 KiB
update-toast-1440-dark.png
371 KiB
update-toast-1440-light.png
534 KiB
update-toast-390-dark.png
239 KiB
update-toast-390-light.png
256 KiB
update-toast-820-dark.png
272 KiB
update-toast-820-light.png
355 KiB
boot-390-light.png boot-390-dark.png boot-1440-light.png boot-1440-dark.png update-toast-1440-dark.png update-toast-1440-light.png update-toast-390-dark.png update-toast-390-light.png update-toast-820-dark.png update-toast-820-light.png
kayg commented 2026-09-29 09:33:09 +00:00
Author
Owner
Copy link

Started work on job/reload-423 from dev at 191b179baa. I am tracing immutable asset serving, deploy persistence, and SvelteKit update/navigation handling before implementing the retention and safe update boundary.

Started work on job/reload-423 from dev at 191b179baac3ef4f5bebfe07ce91c4b7a887ace2. I am tracing immutable asset serving, deploy persistence, and SvelteKit update/navigation handling before implementing the retention and safe update boundary.
kayg commented 2026-09-29 09:33:56 +00:00
Author
Owner
Copy link

Correction (owner): the page still blanks after a hard refresh, so the stale-chunk hypothesis does not explain this bug. The job was relaunched with a reproduce-first brief and a list of candidate causes. Keeping old chunks across deploys stays in scope as a secondary fix.

Correction (owner): the page still blanks after a hard refresh, so the stale-chunk hypothesis does not explain this bug. The job was relaunched with a reproduce-first brief and a list of candidate causes. Keeping old chunks across deploys stays in scope as a secondary fix.
kayg commented 2026-09-29 09:34:20 +00:00
Author
Owner
Copy link

Starting #423 on job/reload-423, based on dev at 191b179baac3ef4f5bebfe07ce91c4b7a887ace2.

Starting #423 on `job/reload-423`, based on `dev` at `191b179baac3ef4f5bebfe07ce91c4b7a887ace2`.
kayg commented 2026-09-29 09:57:35 +00:00
Author
Owner
Copy link

Reproduction work found a separate client-navigation edge case in the fallback path: crates/calternal-server/src/main.rs::serve_spa returns the embedded index.html for any missing URL, including unknown /_app/immutable/... chunks. That can make a missing stale chunk look like a successful document response rather than a clear 404. The worktree is clean at this point; I am building the production server for the pre-fix A/B reproduction, then I will add retained hashed assets and an explicit missing-chunk 404.

Reproduction work found a separate client-navigation edge case in the fallback path: `crates/calternal-server/src/main.rs::serve_spa` returns the embedded `index.html` for any missing URL, including unknown `/_app/immutable/...` chunks. That can make a missing stale chunk look like a successful document response rather than a clear 404. The worktree is clean at this point; I am building the production server for the pre-fix A/B reproduction, then I will add retained hashed assets and an explicit missing-chunk 404.
kayg commented 2026-09-29 12:26:11 +00:00
Author
Owner
Copy link

Production reproduction finding (#423): on one unchanged local production binary, after loading /files and opening Documents/Archive, clicking the Files root crumb issued a second main-frame document request. The e2e assertion observed 2 document loads where the same-build path must stay at 1. This run had no service worker registered and had not swapped builds. The baseline stopped at this finding before the A→B stale-chunk probe; I am adding navigation/chunk request diagnostics to locate the fallback trigger.

Production reproduction finding (#423): on one unchanged local production binary, after loading `/files` and opening `Documents/Archive`, clicking the Files root crumb issued a second main-frame `document` request. The e2e assertion observed 2 document loads where the same-build path must stay at 1. This run had no service worker registered and had not swapped builds. The baseline stopped at this finding before the A→B stale-chunk probe; I am adding navigation/chunk request diagnostics to locate the fallback trigger.
kayg commented 2026-09-29 12:31:10 +00:00
Author
Owner
Copy link

Lead for the reload job: apps/web/src/lib/components/app-sidebar.svelte:200 threw TypeError: Cannot read properties of null (reading 'origin') inside afterNavigate whenever from.url or to.url was null (found by the #406 job in Photos and Composer e2e runs). Fixed on dev in the next push (optional chaining). Check whether this exception, or another one thrown during client navigation, makes SvelteKit fall back to a full document load on the Files crumb. Reproduce with the fix reverted, then with it applied.

Lead for the reload job: `apps/web/src/lib/components/app-sidebar.svelte:200` threw `TypeError: Cannot read properties of null (reading 'origin')` inside `afterNavigate` whenever `from.url` or `to.url` was null (found by the #406 job in Photos and Composer e2e runs). Fixed on dev in the next push (optional chaining). Check whether this exception, or another one thrown during client navigation, makes SvelteKit fall back to a full document load on the Files crumb. Reproduce with the fix reverted, then with it applied.
kayg commented 2026-09-29 12:56:33 +00:00
Author
Owner
Copy link

The second production reproduction captured the fallback details. The Files crumb issued GET /files as a main-frame document request, returned 200 text/html, and fired pagehide (1). Its resolved link had no target, no data-sveltekit-reload, and no <base target> existed. No /_app/immutable/ request failed. This is a same-build navigation fallback, separate from missing stale chunks. I am routing the Files-owned crumb through the page's explicit SvelteKit goto callback, while preserving modified clicks and external-link semantics.

The second production reproduction captured the fallback details. The Files crumb issued `GET /files` as a main-frame document request, returned `200 text/html`, and fired `pagehide` (`1`). Its resolved link had no target, no `data-sveltekit-reload`, and no `<base target>` existed. No `/_app/immutable/` request failed. This is a same-build navigation fallback, separate from missing stale chunks. I am routing the Files-owned crumb through the page's explicit SvelteKit `goto` callback, while preserving modified clicks and external-link semantics.
kayg commented 2026-09-29 13:20:04 +00:00
Author
Owner
Copy link

Follow-up production finding (#423): the explicit Files breadcrumb route remained client-side, but the next same-build navigation through the Files sidebar row issued another main-frame document request (the sidebar Files row stays in client navigation: 2 loads versus 1 expected). The sidebar uses a separate anchor with a drawer-close click callback. I added an explicit SvelteKit goto path there too; both paths still preserve modifier clicks, download links, external relations, and forced-reload ancestors.

Follow-up production finding (#423): the explicit Files breadcrumb route remained client-side, but the next same-build navigation through the Files sidebar row issued another main-frame document request (`the sidebar Files row stays in client navigation`: 2 loads versus 1 expected). The sidebar uses a separate anchor with a drawer-close click callback. I added an explicit SvelteKit `goto` path there too; both paths still preserve modifier clicks, download links, external relations, and forced-reload ancestors.
kayg commented 2026-09-29 13:38:32 +00:00
Author
Owner
Copy link

Finished on branch job/reload-423 at head 91fdf54ed6.

Built:

  • A production reload probe with a generated 614-file Documents tree and a two-build server-restart harness.
  • A root Files crumb and ordinary sidebar route handling through SvelteKit, preserving native modified and external links.
  • Safe update polling and a navigation-boundary reload that waits while an editor has unsaved state.
  • Inline themed page chrome in app.html for a full document load.
  • Persistent immutable frontend asset retention under the Instance data root. It retains at least the newest ten deployments and all deployments from the last seven days, serves old hashed routes with immutable headers, and returns 404 for invalid or unknown routes.
  • The ten-deployment store unit test measured 560 bytes.

Findings:

  • The baseline production reproduction confirmed that clicking the Files crumb could load a new document even on the same build. The route was a same-origin Files link; the event was a real pagehide/document navigation.
  • After routing the Files crumb through SvelteKit, the production probe passed that check and then found that the Files sidebar row still caused a document load (navigation count 2 instead of 1). Commit 67185d45 routes ordinary sidebar clicks through SvelteKit.
  • The job timebox ended before I could repeat the full production probe after that final sidebar fix.

Gate output:

  • cargo fmt --check: exit 0; no output.

  • cargo clippy -p calternal-fs --all-targets -- -D warnings:
    Checking calternal-fs v0.1.0 (/home/kayg/Developer/calternal-wt/reload-423/crates/calternal-fs)
    Finished dev profile [unoptimized + debuginfo] target(s) in 3.20s

  • cargo test -p calternal-fs:
    test result: ok. 42 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 15.12s
    Doc-tests calternal_fs: 0 passed; 0 failed.

  • bun run check:
    $ node scripts/check-type-tokens.mjs && svelte-kit sync && svelte-check --tsconfig ./tsconfig.json
    Text sizes use shared role tokens.
    Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web
    Getting Svelte diagnostics...

    svelte-check found 0 errors and 0 warnings

Known gaps:

  • No final two-build run with 20 mode navigations or proof of exactly one intentional reload at the update boundary.
  • The production run stopped at the sidebar assertion before testing Back, phone menu, asset switching, and final screenshots at 390/820/1440 px in light and dark.
  • The server-level adversarial HTTP path round and the simulated live deployment-store measurement were not completed. Hostile and unknown paths have filesystem unit coverage; the ten-generation unit test measured 560 bytes.
  • Full workspace gates, bun run test, and calternal-server clippy/test were not run. The server binary built successfully. These gates remain for follow-up.

Decisions not specified in DESIGN.md:

  • The retained store uses digest-named flat files and bounded manifests below the persistent Instance data root, with a 1 GiB total cap. The retention window is the newest ten deployments plus any deployment younger than seven days.
  • A confirmed SvelteKit update triggers a full load at the next safe navigation boundary. Note edits keep the boundary unsafe until persistence settles.

The final SidebarLinks change is committed, but its production verification remains open. No pushes, deploys, or merges were performed by this job.

Finished on branch job/reload-423 at head 91fdf54ed6277c06d3252ec16f36b4e98f96abd8. Built: - A production reload probe with a generated 614-file Documents tree and a two-build server-restart harness. - A root Files crumb and ordinary sidebar route handling through SvelteKit, preserving native modified and external links. - Safe update polling and a navigation-boundary reload that waits while an editor has unsaved state. - Inline themed page chrome in app.html for a full document load. - Persistent immutable frontend asset retention under the Instance data root. It retains at least the newest ten deployments and all deployments from the last seven days, serves old hashed routes with immutable headers, and returns 404 for invalid or unknown routes. - The ten-deployment store unit test measured 560 bytes. Findings: - The baseline production reproduction confirmed that clicking the Files crumb could load a new document even on the same build. The route was a same-origin Files link; the event was a real pagehide/document navigation. - After routing the Files crumb through SvelteKit, the production probe passed that check and then found that the Files sidebar row still caused a document load (navigation count 2 instead of 1). Commit 67185d45 routes ordinary sidebar clicks through SvelteKit. - The job timebox ended before I could repeat the full production probe after that final sidebar fix. Gate output: - cargo fmt --check: exit 0; no output. - cargo clippy -p calternal-fs --all-targets -- -D warnings: Checking calternal-fs v0.1.0 (/home/kayg/Developer/calternal-wt/reload-423/crates/calternal-fs) Finished dev profile [unoptimized + debuginfo] target(s) in 3.20s - cargo test -p calternal-fs: test result: ok. 42 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 15.12s Doc-tests calternal_fs: 0 passed; 0 failed. - bun run check: $ node scripts/check-type-tokens.mjs && svelte-kit sync && svelte-check --tsconfig ./tsconfig.json Text sizes use shared role tokens. Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web Getting Svelte diagnostics... svelte-check found 0 errors and 0 warnings Known gaps: - No final two-build run with 20 mode navigations or proof of exactly one intentional reload at the update boundary. - The production run stopped at the sidebar assertion before testing Back, phone menu, asset switching, and final screenshots at 390/820/1440 px in light and dark. - The server-level adversarial HTTP path round and the simulated live deployment-store measurement were not completed. Hostile and unknown paths have filesystem unit coverage; the ten-generation unit test measured 560 bytes. - Full workspace gates, bun run test, and calternal-server clippy/test were not run. The server binary built successfully. These gates remain for follow-up. Decisions not specified in DESIGN.md: - The retained store uses digest-named flat files and bounded manifests below the persistent Instance data root, with a 1 GiB total cap. The retention window is the newest ten deployments plus any deployment younger than seven days. - A confirmed SvelteKit update triggers a full load at the next safe navigation boundary. Note edits keep the boundary unsafe until persistence settles. The final SidebarLinks change is committed, but its production verification remains open. No pushes, deploys, or merges were performed by this job.
kayg commented 2026-09-29 13:40:39 +00:00
Author
Owner
Copy link

Resuming on job/reload-423 at 91fdf54ed6277c06d3252ec16f36b4e98f96abd8 (base dev at 09e238d5276b4f7a1eaf457eef07677cf9e3e9cc). The retained immutable asset store, safe update boundary, boot shell, and route-level workaround commits are present. I am tracing the generic reason SvelteKit skipped ordinary internal links, then expanding the reload crawler before final verification.

Resuming on `job/reload-423` at `91fdf54ed6277c06d3252ec16f36b4e98f96abd8` (base `dev` at `09e238d5276b4f7a1eaf457eef07677cf9e3e9cc`). The retained immutable asset store, safe update boundary, boot shell, and route-level workaround commits are present. I am tracing the generic reason SvelteKit skipped ordinary internal links, then expanding the reload crawler before final verification.
kayg commented 2026-09-29 15:01:55 +00:00
Author
Owner
Copy link

Finding for #423: the event trace shows SvelteKit's document-level click handler receiving the Files crumb and calling preventDefault; the crumb is a same-origin anchor in the document tree. In the installed SvelteKit client (apps/web/node_modules/@sveltejs/kit/src/runtime/client/client.js, load_route), a route-module import error triggers stores.updated.check(), then native_navigation(url) when the running build is stale. That explains a full document load after the click without the router skipping the link. My one-build production repro has not reproduced a skipped click; I am now running the issue's exact A→B fixture to verify the missing retained chunk path before removing the link-specific workarounds.

Finding for #423: the event trace shows SvelteKit's document-level click handler receiving the Files crumb and calling `preventDefault`; the crumb is a same-origin anchor in the document tree. In the installed SvelteKit client (`apps/web/node_modules/@sveltejs/kit/src/runtime/client/client.js`, `load_route`), a route-module import error triggers `stores.updated.check()`, then `native_navigation(url)` when the running build is stale. That explains a full document load after the click without the router skipping the link. My one-build production repro has not reproduced a skipped click; I am now running the issue's exact A→B fixture to verify the missing retained chunk path before removing the link-specific workarounds.
kayg commented 2026-09-29 15:21:28 +00:00
Author
Owner
Copy link

Production evidence for #423: Build A passed the plain Files crumb check in the real 614-file Fixture. Its resolved href was http://localhost:27061/files, with target="", no data-sveltekit-reload, and no <base target>; the click stayed in the same document. The run later stopped because the existing phone-menu assertion expected an overflow control for Files / Documents / Archive, which fits at 390 px. I have changed the Fixture to use a deeper real folder path so that the phone overflow menu is actually required, and am continuing the A→B proof.

Production evidence for #423: Build A passed the plain Files crumb check in the real 614-file Fixture. Its resolved href was `http://localhost:27061/files`, with `target=""`, no `data-sveltekit-reload`, and no `<base target>`; the click stayed in the same document. The run later stopped because the existing phone-menu assertion expected an overflow control for `Files / Documents / Archive`, which fits at 390 px. I have changed the Fixture to use a deeper real folder path so that the phone overflow menu is actually required, and am continuing the A→B proof.
kayg commented 2026-09-29 15:46:42 +00:00
Author
Owner
Copy link

Crawler finding for #423: the ModeHeader's “Show folders in this path” control only renders when measured breadcrumb content exceeds the title slot. Even the real six-segment Documents/Archive/Reports/2026/January path did not expose that control in the 390 px production test. The phone check now taps the visible Files crumb directly and asserts that it stays in the same document; the desktop crawler still clicks every visible breadcrumb link.

Crawler finding for #423: the ModeHeader's “Show folders in this path” control only renders when measured breadcrumb content exceeds the title slot. Even the real six-segment Documents/Archive/Reports/2026/January path did not expose that control in the 390 px production test. The phone check now taps the visible Files crumb directly and asserts that it stays in the same document; the desktop crawler still clicks every visible breadcrumb link.
kayg commented 2026-09-29 15:59:19 +00:00
Author
Owner
Copy link

Verification finding: the earlier A/B run did not use two runtime builds. Both debug servers read the same compile-time apps/web/build directory, and their binaries had identical SHA-256 values; Build A and the current build also reported the same SvelteKit version (1790695400372). That could not test an update boundary. I rebuilt Build A in a detached temporary worktree, which gives it a separate asset directory and version (1790697301589). I will rebuild Build B in the job worktree before rerunning the update test.

Verification finding: the earlier A/B run did not use two runtime builds. Both debug servers read the same compile-time `apps/web/build` directory, and their binaries had identical SHA-256 values; Build A and the current build also reported the same SvelteKit version (`1790695400372`). That could not test an update boundary. I rebuilt Build A in a detached temporary worktree, which gives it a separate asset directory and version (`1790697301589`). I will rebuild Build B in the job worktree before rerunning the update test.
kayg commented 2026-09-29 16:21:16 +00:00
Author
Owner
Copy link

Crawler finding: the Calendar sidebar's Today link points to /today, which the real server redirects to the user's default Calendar route. A production-browser probe clicked it from the Calendar sidebar and ended at /calendar/week/2026-09-27 with one navigation timing entry, one document request total, and zero pagehide events. The crawler was waiting for the literal /today URL, so it timed out after the valid in-app redirect. I updated both the sidebar and generic anchor crawlers to recognize this DESIGN §29 redirect and continue to assert zero document loads and zero pagehide events.

Crawler finding: the Calendar sidebar's `Today` link points to `/today`, which the real server redirects to the user's default Calendar route. A production-browser probe clicked it from the Calendar sidebar and ended at `/calendar/week/2026-09-27` with one navigation timing entry, one document request total, and zero `pagehide` events. The crawler was waiting for the literal `/today` URL, so it timed out after the valid in-app redirect. I updated both the sidebar and generic anchor crawlers to recognize this DESIGN §29 redirect and continue to assert zero document loads and zero `pagehide` events.
kayg commented 2026-09-29 16:30:34 +00:00
Author
Owner
Copy link

Crawler finding: the production SPA was still at /today 150 ms after a direct route visit, so the short synchronization window fired before client hydration ran the route's documented redirect to the user's default Calendar view. The route entry is a shell served by the static adapter; the redirect occurs in the route load. I changed the crawler to wait for the Calendar date route instead of treating /today as the final URL.

Crawler finding: the production SPA was still at `/today` 150 ms after a direct route visit, so the short synchronization window fired before client hydration ran the route's documented redirect to the user's default Calendar view. The route entry is a shell served by the static adapter; the redirect occurs in the route load. I changed the crawler to wait for the Calendar date route instead of treating `/today` as the final URL.
kayg commented 2026-09-29 18:04:14 +00:00
Author
Owner
Copy link

Time-box report for #423. The job reached 4h23m, so work stopped under the owner’s ~4-hour limit.

Committed on job/reload-423:

  • 16f8ddaccb62c12c88ac26f893844c529d353788 — removed the per-link goto workarounds from the Files crumb and sidebar. The controlled minimal repro showed SvelteKit intercepting a plain same-origin anchor (defaultPrevented=true); the document fallback followed a deliberately missing old route chunk. Retaining old immutable chunks is the generic fix already present on this branch. The change keeps ordinary anchors and the phone drawer close callback.

Working tree:

  • apps/web/e2e/reload-423.mjs has an uncommitted expanded crawler and production verification. node --check apps/web/e2e/reload-423.mjs passed with no output; git diff --check passed with no output.
  • Earlier production runs reached the full mode crawl. The most recent completed run exposed a bad desktop Search-preview expectation (there is no desktop “Open” button); the test was corrected to check the real preview and Search result row. A later run passed Calendar, Files, Photos, Analytics and Ask, then stopped on a Settings row selector ambiguity; that selector was corrected to use row position. The current run was stopped during fixture setup when the time-box was reached.

Not completed: commit the crawler, finish its production run (including two builds, 20 navigations, update boundary, screenshots, and retained-asset HTTP probes), merge dev once, run the requested gates, attach screenshots, clean build output, and post the final gate report.

Gate output:

  • node --check apps/web/e2e/reload-423.mjs: passed; no output.
  • git diff --check: passed; no output.
  • cargo fmt --check, per-crate clippy/tests, bun run check, bun run test: NOT RUN.

Decision: the desktop Search preview itself has no navigational Open action. The crawler now covers its rendered preview content and the Search result row; the phone long-press preview Open action is included in screenshot verification but is not yet verified by a completed run.

Time-box report for #423. The job reached 4h23m, so work stopped under the owner’s ~4-hour limit. Committed on `job/reload-423`: - `16f8ddaccb62c12c88ac26f893844c529d353788` — removed the per-link `goto` workarounds from the Files crumb and sidebar. The controlled minimal repro showed SvelteKit intercepting a plain same-origin anchor (`defaultPrevented=true`); the document fallback followed a deliberately missing old route chunk. Retaining old immutable chunks is the generic fix already present on this branch. The change keeps ordinary anchors and the phone drawer close callback. Working tree: - `apps/web/e2e/reload-423.mjs` has an uncommitted expanded crawler and production verification. `node --check apps/web/e2e/reload-423.mjs` passed with no output; `git diff --check` passed with no output. - Earlier production runs reached the full mode crawl. The most recent completed run exposed a bad desktop Search-preview expectation (there is no desktop “Open” button); the test was corrected to check the real preview and Search result row. A later run passed Calendar, Files, Photos, Analytics and Ask, then stopped on a Settings row selector ambiguity; that selector was corrected to use row position. The current run was stopped during fixture setup when the time-box was reached. Not completed: commit the crawler, finish its production run (including two builds, 20 navigations, update boundary, screenshots, and retained-asset HTTP probes), merge `dev` once, run the requested gates, attach screenshots, clean build output, and post the final gate report. Gate output: - `node --check apps/web/e2e/reload-423.mjs`: passed; no output. - `git diff --check`: passed; no output. - `cargo fmt --check`, per-crate clippy/tests, `bun run check`, `bun run test`: NOT RUN. Decision: the desktop Search preview itself has no navigational Open action. The crawler now covers its rendered preview content and the Search result row; the phone long-press preview Open action is included in screenshot verification but is not yet verified by a completed run.
kayg commented 2026-09-29 18:07:04 +00:00
Author
Owner
Copy link

Round 4 started on job/reload-423. Branch base SHA: 09e238d5276b4f7a1eaf457eef07677cf9e3e9cc; current HEAD: 16f8ddaccb62c12c88ac26f893844c529d353788. Resuming with the expanded production crawler in apps/web/e2e/reload-423.mjs; I will commit that first, then trace the same-build _app/immutable/* responses before changing server behavior.

Round 4 started on `job/reload-423`. Branch base SHA: `09e238d5276b4f7a1eaf457eef07677cf9e3e9cc`; current HEAD: `16f8ddaccb62c12c88ac26f893844c529d353788`. Resuming with the expanded production crawler in `apps/web/e2e/reload-423.mjs`; I will commit that first, then trace the same-build `_app/immutable/*` responses before changing server behavior.
kayg commented 2026-09-29 18:17:53 +00:00
Author
Owner
Copy link

Round 4 finding (source history): the explicit Files breadcrumb goto() callback was added in 8f7793407 and removed in 16f8ddacc; the latter commit says SvelteKit should own ordinary-anchor navigation. The reported base SHA 09e238d5276b4f7a1eaf457eef07677cf9e3e9cc predates both retention and this callback. I am reproducing from that base with each /_app/immutable/* response recorded so the client-navigation cause is separated from a missing or mismatched chunk.

Round 4 finding (source history): the explicit Files breadcrumb `goto()` callback was added in `8f7793407` and removed in `16f8ddacc`; the latter commit says SvelteKit should own ordinary-anchor navigation. The reported base SHA `09e238d5276b4f7a1eaf457eef07677cf9e3e9cc` predates both retention and this callback. I am reproducing from that base with each `/_app/immutable/*` response recorded so the client-navigation cause is separated from a missing or mismatched chunk.
kayg commented 2026-09-29 18:36:22 +00:00
Author
Owner
Copy link

Round 4 same-build evidence (branch base 09e238d): after loading /files?path=Documents/Archive, the Files root breadcrumb click was intercepted (defaultPrevented=true) and the document count stayed at 2 before and after the click. Every captured /_app/immutable/* response was 200 with JavaScript or CSS content type; no response was HTML or 404. This first pass used a direct browser navigation, so I am tightening it to a CDP hard refresh with cache bypass and recording the document cache headers before treating the reproduction as ruled out.

Round 4 same-build evidence (branch base `09e238d`): after loading `/files?path=Documents/Archive`, the Files root breadcrumb click was intercepted (`defaultPrevented=true`) and the document count stayed at 2 before and after the click. Every captured `/_app/immutable/*` response was 200 with JavaScript or CSS content type; no response was HTML or 404. This first pass used a direct browser navigation, so I am tightening it to a CDP hard refresh with cache bypass and recording the document cache headers before treating the reproduction as ruled out.
kayg commented 2026-09-29 18:48:26 +00:00
Author
Owner
Copy link

Same-build root-cause finding (base 09e238d527, before asset retention): I rebuilt the branch-base web app and server together, then ran the hard-refresh Files breadcrumb repro with the afterNavigate URL guard temporarily reverted to its parent version. Build version was 1790707292290; service worker registrations were 0. All 222 captured /_app/immutable/* requests succeeded: 201 200 text/javascript, 21 200 text/css; no immutable request returned HTML or 404. Both hard-refresh document responses had Cache-Control: no-cache.

The app raised Cannot read properties of null (reading 'origin') three times. The Files crumb click was not prevented, and the main-frame document count rose from 3 to 4 (/files returned 200 text/html, no-cache). This reproduces the same-build reload without any failed or stale asset: the unguarded app-sidebar.svelte afterNavigate callback throws while a navigation URL is null, so the client router does not intercept the link. I am validating the existing from?.url && to?.url guard against the same pre-retention server build and will keep an automated regression probe for this hard-refresh path. Full request evidence is in artifacts/reload-423/base-same-build-assets.json in the worktree.

Same-build root-cause finding (base 09e238d5276b4f7a1eaf457eef07677cf9e3e9cc, before asset retention): I rebuilt the branch-base web app and server together, then ran the hard-refresh Files breadcrumb repro with the `afterNavigate` URL guard temporarily reverted to its parent version. Build version was `1790707292290`; service worker registrations were 0. All 222 captured `/_app/immutable/*` requests succeeded: 201 `200 text/javascript`, 21 `200 text/css`; no immutable request returned HTML or 404. Both hard-refresh document responses had `Cache-Control: no-cache`. The app raised `Cannot read properties of null (reading 'origin')` three times. The Files crumb click was not prevented, and the main-frame document count rose from 3 to 4 (`/files` returned `200 text/html`, `no-cache`). This reproduces the same-build reload without any failed or stale asset: the unguarded `app-sidebar.svelte` `afterNavigate` callback throws while a navigation URL is null, so the client router does not intercept the link. I am validating the existing `from?.url && to?.url` guard against the same pre-retention server build and will keep an automated regression probe for this hard-refresh path. Full request evidence is in `artifacts/reload-423/base-same-build-assets.json` in the worktree.
kayg commented 2026-09-29 19:00:01 +00:00
Author
Owner
Copy link

Confirmed the same-build root cause with paired production bundles from branch base 09e238d5276b4f7a1eaf457eef07677cf9e3e9cc, before asset retention. On the unguarded afterNavigate build, every captured immutable request was 200 (201 text/javascript, 21 text/css), both refreshed HTML responses were 200 text/html with Cache-Control: no-cache, and the User had no service worker. Three Cannot read properties of null (reading 'origin') errors left the Files crumb un-intercepted and added one document load (3 → 4). The unguarded request log is artifacts/reload-423/base-same-build-unguarded-assets.json.

After restoring the existing from?.url && to?.url guard in the same branch-base source, the hard-refresh probe passed: 148 immutable requests all returned 200 JS/CSS, there were no browser errors or service workers, and the Files click stayed in the same document (3 → 3). The full response log is artifacts/reload-423/base-guarded/base-same-build-assets.json. This rules out a missing embedded chunk, stale HTML cache, or service worker as the same-build trigger. I added the hard-refresh regression probe and clarified the guard’s comment in the job branch.

Confirmed the same-build root cause with paired production bundles from branch base `09e238d5276b4f7a1eaf457eef07677cf9e3e9cc`, before asset retention. On the unguarded `afterNavigate` build, every captured immutable request was 200 (`201 text/javascript`, `21 text/css`), both refreshed HTML responses were 200 `text/html` with `Cache-Control: no-cache`, and the User had no service worker. Three `Cannot read properties of null (reading 'origin')` errors left the Files crumb un-intercepted and added one document load (3 → 4). The unguarded request log is `artifacts/reload-423/base-same-build-unguarded-assets.json`. After restoring the existing `from?.url && to?.url` guard in the same branch-base source, the hard-refresh probe passed: 148 immutable requests all returned 200 JS/CSS, there were no browser errors or service workers, and the Files click stayed in the same document (3 → 3). The full response log is `artifacts/reload-423/base-guarded/base-same-build-assets.json`. This rules out a missing embedded chunk, stale HTML cache, or service worker as the same-build trigger. I added the hard-refresh regression probe and clarified the guard’s comment in the job branch.
kayg commented 2026-09-29 19:15:03 +00:00
Author
Owner
Copy link

Merge note: origin/dev had removed the earlier #423 immutable asset store and fallback, the SvelteKit update-boundary logic and version polling, the themed boot shell, and the dedicated two-build crawler. This job explicitly requires those behaviors and their production verification, so the merge result retains those #423 paths while taking the newer dev UI, shared harness, package lock and unrelated source changes. I resolved the sidebar overlap by keeping dev's current Calendar sidebar and the null-URL guard.

Merge note: `origin/dev` had removed the earlier #423 immutable asset store and fallback, the SvelteKit update-boundary logic and version polling, the themed boot shell, and the dedicated two-build crawler. This job explicitly requires those behaviors and their production verification, so the merge result retains those #423 paths while taking the newer dev UI, shared harness, package lock and unrelated source changes. I resolved the sidebar overlap by keeping dev's current Calendar sidebar and the null-URL guard.
kayg commented 2026-09-29 20:00:58 +00:00
Author
Owner
Copy link

Starting round 4 on job/reload-423 at 7542d909b (merged origin/dev); resuming with the immutable-path regression test uncommitted. I will commit it, reproduce same-build asset requests against the pre-retention server, then fix the specific fallback root cause and verify both production crawler cases.

Starting round 4 on job/reload-423 at 7542d909b (merged origin/dev); resuming with the immutable-path regression test uncommitted. I will commit it, reproduce same-build asset requests against the pre-retention server, then fix the specific fallback root cause and verify both production crawler cases.
kayg commented 2026-09-29 20:36:37 +00:00
Author
Owner
Copy link

Round 4 finding: I built the pre-retention server from 8f7793407 with its matching production web build and ran the hard-refresh Files probe. It recorded 148 /_app/immutable/* responses: 134 were 200 text/javascript and 14 were 200 text/css; none returned HTML or 404. Both document responses were 200 text/html with Cache-Control: no-cache. The page had zero service-worker registrations. The Files crumb click was intercepted, and the document count stayed at 3 before and after that click. So this same-build probe found no missing chunk, embed-path mismatch, stale HTML response, or service worker.

The old build did log two Cannot read properties of null (reading 'origin') browser errors in the sidebar afterNavigate callback. Current dev includes df02c3957, which guards both navigation URLs before reading .origin; I will verify the merged production build reports no such errors. Full per-request details are in artifacts/reload-423/base-same-build-assets.json.

Round 4 finding: I built the pre-retention server from 8f7793407 with its matching production web build and ran the hard-refresh Files probe. It recorded 148 `/_app/immutable/*` responses: 134 were 200 `text/javascript` and 14 were 200 `text/css`; none returned HTML or 404. Both document responses were 200 `text/html` with `Cache-Control: no-cache`. The page had zero service-worker registrations. The Files crumb click was intercepted, and the document count stayed at 3 before and after that click. So this same-build probe found no missing chunk, embed-path mismatch, stale HTML response, or service worker. The old build did log two `Cannot read properties of null (reading 'origin')` browser errors in the sidebar `afterNavigate` callback. Current `dev` includes df02c3957, which guards both navigation URLs before reading `.origin`; I will verify the merged production build reports no such errors. Full per-request details are in `artifacts/reload-423/base-same-build-assets.json`.
kayg commented 2026-09-30 01:03:31 +00:00
Author
Owner
Copy link

Round 4 resumed on job/reload-423 at dcdd1b3d5. Worktree is clean; the expanded crawler is already committed as 3cd8b515b. Branch base is 369ab6a2f. I am rebuilding that base to record the same-build hard-refresh request statuses and content types before the retention fix.

Round 4 resumed on job/reload-423 at dcdd1b3d5. Worktree is clean; the expanded crawler is already committed as 3cd8b515b. Branch base is 369ab6a2f. I am rebuilding that base to record the same-build hard-refresh request statuses and content types before the retention fix.
kayg commented 2026-09-30 01:17:19 +00:00
Author
Owner
Copy link

Correction: the job fork point is 191b179ba (parent of the first #423 work, 9d3913e31). 369ab6a2f is a later merge of moving origin/dev, not the branch base; its server build failed with missing calternal_dav::areas/read_many symbols. I am rerunning on 191b179ba.

Correction: the job fork point is 191b179ba (parent of the first #423 work, 9d3913e31). 369ab6a2f is a later merge of moving origin/dev, not the branch base; its server build failed with missing calternal_dav::areas/read_many symbols. I am rerunning on 191b179ba.
kayg commented 2026-09-30 03:43:29 +00:00
Author
Owner
Copy link

Resuming round 4 on branch job/reload-423. Current head: dcdd1b3d5; worktree is clean and the expanded crawler is already committed as 3cd8b515b. Current shared base ancestor: 369ab6a2f. I am continuing with the same-build request trace against the pre-retention revision, then will verify the specific fix and required gates.

Resuming round 4 on branch job/reload-423. Current head: dcdd1b3d5; worktree is clean and the expanded crawler is already committed as 3cd8b515b. Current shared base ancestor: 369ab6a2f. I am continuing with the same-build request trace against the pre-retention revision, then will verify the specific fix and required gates.
kayg commented 2026-09-30 04:15:29 +00:00
Author
Owner
Copy link

Same-build rerun on the pre-retention build (_app/version.json 1790731065822): 222 /_app/immutable/* requests across 74 distinct URLs; all 201 JavaScript responses were 200 text/javascript and all 21 CSS responses were 200 text/css. No request failed, returned 404, or returned HTML. The three document responses were 200 text/html with Cache-Control: no-cache; the fresh browser had zero service-worker registrations.

The Files crumb click was not intercepted (defaultPrevented=false), the main-document count rose from 3 to 4, and the browser reported three Cannot read properties of null (reading 'origin') errors. This isolates the same-build reload to the unguarded afterNavigate URL comparison in app-sidebar.svelte; it was not a missing embedded chunk, stale HTML, or service worker. The guard is present in the current branch from df02c3957 and the production same-build probe asserts it.

Full request list and response headers: artifacts/reload-423/rerun-pre-retention/base-same-build-assets.json.

Same-build rerun on the pre-retention build (`_app/version.json` 1790731065822): 222 `/_app/immutable/*` requests across 74 distinct URLs; all 201 JavaScript responses were `200 text/javascript` and all 21 CSS responses were `200 text/css`. No request failed, returned 404, or returned HTML. The three document responses were `200 text/html` with `Cache-Control: no-cache`; the fresh browser had zero service-worker registrations. The Files crumb click was not intercepted (`defaultPrevented=false`), the main-document count rose from 3 to 4, and the browser reported three `Cannot read properties of null (reading 'origin')` errors. This isolates the same-build reload to the unguarded `afterNavigate` URL comparison in `app-sidebar.svelte`; it was not a missing embedded chunk, stale HTML, or service worker. The guard is present in the current branch from `df02c3957` and the production same-build probe asserts it. Full request list and response headers: `artifacts/reload-423/rerun-pre-retention/base-same-build-assets.json`.
kayg commented 2026-09-30 04:17:33 +00:00
Author
Owner
Copy link

Source-matched rerun completed from revision 8f7793407, with a production web bundle built from that same revision (version 1790740188023). It reproduced the same result: 222 immutable requests across 74 paths, every response 200 text/javascript or 200 text/css, no failures, HTML fallbacks, or 404s; HTML remained no-cache, with zero service-worker registrations. The Files click still loaded one extra document and emitted the same null-origin errors.

No immutable URL returned index.html or 404. Each requested URL resolved through the pre-retention server's embedded assets; there is no asset-path/include mismatch in this reproduction. The full per-request capture is artifacts/reload-423/fresh-pre-retention/base-same-build-assets.json.

Source-matched rerun completed from revision `8f7793407`, with a production web bundle built from that same revision (version `1790740188023`). It reproduced the same result: 222 immutable requests across 74 paths, every response `200 text/javascript` or `200 text/css`, no failures, HTML fallbacks, or 404s; HTML remained `no-cache`, with zero service-worker registrations. The Files click still loaded one extra document and emitted the same null-`origin` errors. No immutable URL returned `index.html` or 404. Each requested URL resolved through the pre-retention server's embedded assets; there is no asset-path/include mismatch in this reproduction. The full per-request capture is `artifacts/reload-423/fresh-pre-retention/base-same-build-assets.json`.
kayg commented 2026-09-30 06:14:59 +00:00
Author
Owner
Copy link

Round 4 gate findings:

  • cargo test -p calternal-server: 85 passed, 2 ignored, 1 failed. The existing wire::tests::full_app_setup_session_config_and_backup child process timed out at crates/calternal-server/src/wire.rs:7106 after 45.22s; the wrapper then failed at line 6127. This is a slow-only failure on the shared host. The #423 unit test unknown_immutable_asset_paths_never_receive_the_spa_shell passed.
  • The first bun run check could not resolve fast-check, although it is declared in apps/web/package.json and bun.lock. bun install --frozen-lockfile installed the missing package; the rerun passed with 0 errors and 0 warnings.
Round 4 gate findings: - `cargo test -p calternal-server`: 85 passed, 2 ignored, 1 failed. The existing `wire::tests::full_app_setup_session_config_and_backup` child process timed out at `crates/calternal-server/src/wire.rs:7106` after 45.22s; the wrapper then failed at line 6127. This is a slow-only failure on the shared host. The #423 unit test `unknown_immutable_asset_paths_never_receive_the_spa_shell` passed. - The first `bun run check` could not resolve `fast-check`, although it is declared in `apps/web/package.json` and `bun.lock`. `bun install --frozen-lockfile` installed the missing package; the rerun passed with 0 errors and 0 warnings.
kayg commented 2026-09-30 06:16:14 +00:00
Author
Owner
Copy link

The full bun run test gate completed with 877 passed and 1 failed across 878 tests (135 passed files, 1 failed file). The lone failure was StatRow summary cards > toggles all four cards together and remembers the mode, which timed out at its existing 5-second Vitest limit in apps/web/src/lib/components/analytics/widgets/StatRow.svelte.test.ts:97. The suite took 431.13s; this occurred during the same shared-host load as the server subprocess timeout. No test expectations were changed.

The full `bun run test` gate completed with 877 passed and 1 failed across 878 tests (135 passed files, 1 failed file). The lone failure was `StatRow summary cards > toggles all four cards together and remembers the mode`, which timed out at its existing 5-second Vitest limit in `apps/web/src/lib/components/analytics/widgets/StatRow.svelte.test.ts:97`. The suite took 431.13s; this occurred during the same shared-host load as the server subprocess timeout. No test expectations were changed.
kayg commented 2026-09-30 08:25:41 +00:00
Author
Owner
Copy link

Production A/B run so far: Build A 1790749280372 switched to Build B 1790749101975 while the loaded page stayed on A. The same-build crawler passed its Files, Calendar, Shared, Recent and Trash anchor audits. The full crawler then timed out after 15 seconds while auditing a visible same-origin anchor from the Photos route; the first trace did not include the anchor identity. A focused Photos-page probe reached the page's visible Videos, Stacks, Home and library-folder settings URLs. I added route/link/final-URL context to that timeout and will rerun the production proof once to identify the full-crawler state.

Production A/B run so far: Build A `1790749280372` switched to Build B `1790749101975` while the loaded page stayed on A. The same-build crawler passed its Files, Calendar, Shared, Recent and Trash anchor audits. The full crawler then timed out after 15 seconds while auditing a visible same-origin anchor from the Photos route; the first trace did not include the anchor identity. A focused Photos-page probe reached the page's visible Videos, Stacks, Home and library-folder settings URLs. I added route/link/final-URL context to that timeout and will rerun the production proof once to identify the full-crawler state.
kayg commented 2026-09-30 08:37:02 +00:00
Author
Owner
Copy link

The second production run reached the mode-tray audit and stopped before clicking the Shared link: Files mode anchor remains available failed after a direct route restore because the Files sidebar had not yet republished that visible link. No navigation or document load occurred for that anchor. The crawler now waits for that exact link after restoring a route (commit 0f8274d7a). The separate timeout context change is commit 91cd1f9d3.

The second production run reached the mode-tray audit and stopped before clicking the `Shared` link: `Files mode anchor remains available` failed after a direct route restore because the Files sidebar had not yet republished that visible link. No navigation or document load occurred for that anchor. The crawler now waits for that exact link after restoring a route (commit `0f8274d7a`). The separate timeout context change is commit `91cd1f9d3`.
kayg commented 2026-09-30 09:05:09 +00:00
Author
Owner
Copy link

Production crawler finding: after selecting Calendar from /files?path=Documents/Archive/Reports, the shell changed to data-mode=calendar and selected tab-calendar, but the URL stayed on the Files route for 45 seconds and the Calendar entry route never committed. This is now reported with the source URL and selected tab. I am tracing the pending route requests before changing product code or relaxing the crawler assertion.

Production crawler finding: after selecting Calendar from `/files?path=Documents/Archive/Reports`, the shell changed to `data-mode=calendar` and selected `tab-calendar`, but the URL stayed on the Files route for 45 seconds and the Calendar entry route never committed. This is now reported with the source URL and selected tab. I am tracing the pending route requests before changing product code or relaxing the crawler assertion.
kayg commented 2026-09-30 10:54:57 +00:00
Author
Owner
Copy link

A/B production finding: after switching the server from Build A to Build B, an A tab requested /_app/immutable/chunks/DN7OJJEK.js; Build B returned 404. The path exists in Build A’s asset manifest and is absent from Build B. Retention already included route nodes, but is_hashed_asset only recognized name.hash.ext, while this SvelteKit chunk uses an eight-character hash-only filename. Commit 06c99a91e accepts that generated form under _app/immutable/chunks/ and adds a regression test. The corrected crawler derives the Notes route leaf IDs from Build A’s server manifest instead of fixed node numbers.

A/B production finding: after switching the server from Build A to Build B, an A tab requested `/_app/immutable/chunks/DN7OJJEK.js`; Build B returned 404. The path exists in Build A’s asset manifest and is absent from Build B. Retention already included route nodes, but `is_hashed_asset` only recognized `name.hash.ext`, while this SvelteKit chunk uses an eight-character hash-only filename. Commit `06c99a91e` accepts that generated form under `_app/immutable/chunks/` and adds a regression test. The corrected crawler derives the Notes route leaf IDs from Build A’s server manifest instead of fixed node numbers.
kayg commented 2026-09-30 11:43:03 +00:00
Author
Owner
Copy link

A/B production trace exposed a test-fixture boundary: the first Build A server was compiled with the previous is_hashed_asset predicate. It retained named route nodes but did not retain hash-only chunks such as /_app/immutable/chunks/DN7OJJEK.js; after restart, Build B could not serve bytes that Build A had never stored, so the stale page received 404. I am rebuilding the older UI with the corrected server retention code and adding an end-to-end assertion that Build B serves an A-only hash-only chunk. The branch-base same-build probe remains separate and unchanged.

A/B production trace exposed a test-fixture boundary: the first Build A server was compiled with the previous `is_hashed_asset` predicate. It retained named route nodes but did not retain hash-only chunks such as `/_app/immutable/chunks/DN7OJJEK.js`; after restart, Build B could not serve bytes that Build A had never stored, so the stale page received 404. I am rebuilding the older UI with the corrected server retention code and adding an end-to-end assertion that Build B serves an A-only hash-only chunk. The branch-base same-build probe remains separate and unchanged.
kayg commented 2026-09-30 12:00:02 +00:00
Author
Owner
Copy link

The second fixture build confirmed why the version still read Build B: a Cargo dev binary uses RustEmbed's development filesystem path, so it followed the restored apps/web/build directory even after a clean rebuild. The browser never had two frontend versions. I am switching the Build A fixture to a release server binary, which embeds its Build A frontend; Build B remains the current server build. This keeps the two-build check tied to actual embedded production assets.

The second fixture build confirmed why the version still read Build B: a Cargo dev binary uses RustEmbed's development filesystem path, so it followed the restored `apps/web/build` directory even after a clean rebuild. The browser never had two frontend versions. I am switching the Build A fixture to a release server binary, which embeds its Build A frontend; Build B remains the current server build. This keeps the two-build check tied to actual embedded production assets.
kayg commented 2026-09-30 13:19:08 +00:00
Author
Owner
Copy link

With both release builds active, Build A 1790749280372 and Build B 1790763412644 were distinct, and the A-only hash-only chunk request now succeeded. The next cross-build pass reached the 20 in-app route loop. Its assertion expected a global document-load count of 1, but the same-build crawler had already made 20 deliberate direct document visits on a second page and added them to that shared counter. I am changing the A/B check to assert zero delta from its own baseline; this preserves the separate same-build route-load accounting.

With both release builds active, Build A `1790749280372` and Build B `1790763412644` were distinct, and the A-only hash-only chunk request now succeeded. The next cross-build pass reached the 20 in-app route loop. Its assertion expected a global document-load count of 1, but the same-build crawler had already made 20 deliberate direct document visits on a second page and added them to that shared counter. I am changing the A/B check to assert zero delta from its own baseline; this preserves the separate same-build route-load accounting.
kayg commented 2026-09-30 13:40:33 +00:00
Author
Owner
Copy link

The Photos failure is now traced exactly. The crawler identified Choose folders… but its saved a[href] index resolved to the Home link (href=/files) before Playwright clicked; the captured hit target and click event both named Home. Svelte republished the sidebar between numeric-index discovery and locator use. I replaced the index lookup with a live locator intersected by exact accessible name and href, so the click stays attached to the intended link as the DOM changes.

The Photos failure is now traced exactly. The crawler identified `Choose folders…` but its saved `a[href]` index resolved to the `Home` link (`href=/files`) before Playwright clicked; the captured hit target and click event both named Home. Svelte republished the sidebar between numeric-index discovery and locator use. I replaced the index lookup with a live locator intersected by exact accessible name and href, so the click stays attached to the intended link as the DOM changes.
kayg commented 2026-09-30 13:51:55 +00:00
Author
Owner
Copy link

Production crawler finding: after a navigation changed the URL while auditing the /notes listing, its recovery path restored the original route but waited for .note-card. The Notes listing has .notes-explorer .explorer-row, while .note-card is only present on note detail routes. The crawler timed out after 20 seconds at auditSameOriginAnchors line 301; this was a crawler readiness mismatch, not an app navigation failure. I am making the recovery wait match each route before rerunning the production crawl.

Production crawler finding: after a navigation changed the URL while auditing the `/notes` listing, its recovery path restored the original route but waited for `.note-card`. The Notes listing has `.notes-explorer .explorer-row`, while `.note-card` is only present on note detail routes. The crawler timed out after 20 seconds at `auditSameOriginAnchors` line 301; this was a crawler readiness mismatch, not an app navigation failure. I am making the recovery wait match each route before rerunning the production crawl.
kayg commented 2026-09-30 14:27:38 +00:00
Author
Owner
Copy link

Same-build root cause confirmed before asset retention. I rebuilt the web app and server from the pre-retention branch source and recorded every /_app/immutable/* response. All 222 requests were successful: 201 200 text/javascript and 21 200 text/css; no asset returned HTML or 404. Both refreshed HTML responses were 200 text/html with Cache-Control: no-cache; the User had no service worker. The Files crumb click was not intercepted and added one document load (3 → 4). The browser reported Cannot read properties of null (reading 'origin') three times.

A paired production run from the same branch-base source, with only the existing from?.url && to?.url guard restored in app-sidebar.svelte, passed the same hard-refresh probe: 148 immutable requests (134 JS, 14 CSS), all 200; no page errors; the click was intercepted and document loads stayed 3 → 3. This isolates the same-build reload to the unguarded afterNavigate callback, not an absent embedded asset, stale HTML cache, or service worker. The guard is present in the current production build and the crawler now verifies same-build link navigation. Per-request records are in artifacts/reload-423/base-same-build-unguarded-assets.json and artifacts/reload-423/base-guarded/base-same-build-assets.json.

Same-build root cause confirmed before asset retention. I rebuilt the web app and server from the pre-retention branch source and recorded every `/_app/immutable/*` response. All 222 requests were successful: 201 `200 text/javascript` and 21 `200 text/css`; no asset returned HTML or 404. Both refreshed HTML responses were `200 text/html` with `Cache-Control: no-cache`; the User had no service worker. The Files crumb click was not intercepted and added one document load (3 → 4). The browser reported `Cannot read properties of null (reading 'origin')` three times. A paired production run from the same branch-base source, with only the existing `from?.url && to?.url` guard restored in `app-sidebar.svelte`, passed the same hard-refresh probe: 148 immutable requests (134 JS, 14 CSS), all 200; no page errors; the click was intercepted and document loads stayed 3 → 3. This isolates the same-build reload to the unguarded `afterNavigate` callback, not an absent embedded asset, stale HTML cache, or service worker. The guard is present in the current production build and the crawler now verifies same-build link navigation. Per-request records are in `artifacts/reload-423/base-same-build-unguarded-assets.json` and `artifacts/reload-423/base-guarded/base-same-build-assets.json`.
kayg commented 2026-09-30 15:06:38 +00:00
Author
Owner
Copy link

Built

  • Retained hashed frontend assets in the Instance store across deployments. The store keeps builds from the last seven days and at least the newest ten, with bounded manifests and storage.
  • Served an older tab's exact immutable chunk from retained assets. Unknown /_app/immutable/* paths now return 404 and never receive index.html.
  • Added a themed boot shell for intentional update-boundary loads. The app checks for updates every 30 seconds and reloads at a safe in-app navigation boundary, while a Note or Composer has unsaved state.
  • Stabilized cold mode-tab activation and expanded the production crawler for same-build links, A→B deploys, retained route/shared chunks, and hostile immutable paths.
  • Confirmed the same-build cause before asset retention: all 222 immutable requests were 200 (201 text/javascript, 21 text/css); no chunk returned HTML or 404. HTML was no-cache, with zero service workers. The unguarded afterNavigate callback raised three null-origin errors; the Files click was not intercepted and document loads changed 3→4. In a paired build with the existing URL guard restored, all 148 requests were 200 (134 JS, 14 CSS), errors were zero, and document loads stayed 3→3. This rules out missing embedded files, stale HTML, and a service worker for the same-build reload. The guard is in the current build.

Files

  • apps/web/src/app.html; apps/web/src/routes/+layout.svelte; apps/web/src/lib/components/app-sidebar.svelte; apps/web/src/lib/components/SidebarLinks.svelte; apps/web/src/lib/files/FilesBrowser.svelte; apps/web/src/lib/notes/NoteView.svelte; apps/web/src/lib/themes.test.ts; apps/web/src/lib/tray.svelte.test.ts; apps/web/src/lib/modeHeader.svelte.test.ts; apps/web/svelte.config.js; apps/web/package.json
  • apps/web/e2e/harness.mjs; apps/web/e2e/reload-423.mjs; bench/reload-423/.gitignore; bench/reload-423/generate-documents.mjs
  • crates/calternal-fs/src/lib.rs; crates/calternal-fs/src/web_assets.rs; crates/calternal-server/src/main.rs; crates/calternal-server/src/wire.rs
  • packages/ui/src/components/ModeHeader.svelte; packages/ui/src/components/SegmentedControl.svelte

Verification

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

cargo clippy -p calternal-fs --all-targets -- -D warnings
Finished `dev` profile [unoptimized + debuginfo] target(s) in 27.22s

cargo test -p calternal-fs
test result: ok. 42 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 28.18s
test result: ok. 42 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 9.50s
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

cargo clippy -p calternal-server --all-targets -- -D warnings
Finished `dev` profile [unoptimized + debuginfo] target(s) in 5m 51s

cargo test -p calternal-server
test result: ok. 87 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 73.76s

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

bun run test
 Test Files  136 passed (136)
      Tests  879 passed (879)
   Duration  202.53s (transform 62%, environment 16%, import 11%, tests 8%, setup 3%)

Production crawler exited 0 and reported:

PASS same-build Files crumb, sidebar row, browser Back, and phone folder menu: zero extra document loads
PASS 20 in-app mode navigations across the A→B server switch: zero additional document loads from baseline 21
PASS an unsaved Note stays in the A document, then reaches the server before a later boundary load
PASS updated state causes exactly one document load at the next safe navigation boundary
PASS retained Build A Notes route chunk served after Build B: /_app/immutable/nodes/38.DeDbnZBO.js
PASS retained Build A hash-only shared chunk served after Build B: /_app/immutable/chunks/-xN1Iuj-.js
PASS 6 raw immutable-asset paths return 404 without the SPA shell
Captured Calendar, Files, Photos, Note editor, and boot-shell screenshots at 390, 820, and 1440 px in light and dark

Screenshots: full 30-image set, 390 light shell, 390 dark shell, 1440 light shell, 1440 dark shell. Same-build per-request captures: JSON evidence bundle.

Head, gaps, and decisions

  • Head: 4222eeab3236dff04b687e8722637af0b5043509 (docs(reload): link shell and retention invariants to issue). Worktree is clean. Ran cargo clean (removed 54,880 files, 10.8 GiB) and deleted generated fixture and web build output. No dependencies or migrations added.
  • Known gaps: no open implementation failures. One earlier full web-suite attempt hit a 5-second Analytics summary-card timeout under shared load; the final full run passed all 879 tests.
  • Decisions not specified in DESIGN: retain the newest ten builds and every build no more than seven days old, bounded by the one-GiB store cap; poll for frontend updates every 30 seconds and reload only at a safe route boundary; show an inline theme-aware boot skeleton during that intentional load. The hash-only eight-character rule applies only to SvelteKit immutable chunk paths.
## Built - Retained hashed frontend assets in the Instance store across deployments. The store keeps builds from the last seven days and at least the newest ten, with bounded manifests and storage. - Served an older tab's exact immutable chunk from retained assets. Unknown `/_app/immutable/*` paths now return 404 and never receive `index.html`. - Added a themed boot shell for intentional update-boundary loads. The app checks for updates every 30 seconds and reloads at a safe in-app navigation boundary, while a Note or Composer has unsaved state. - Stabilized cold mode-tab activation and expanded the production crawler for same-build links, A→B deploys, retained route/shared chunks, and hostile immutable paths. - Confirmed the same-build cause before asset retention: all 222 immutable requests were 200 (201 `text/javascript`, 21 `text/css`); no chunk returned HTML or 404. HTML was `no-cache`, with zero service workers. The unguarded `afterNavigate` callback raised three null-`origin` errors; the Files click was not intercepted and document loads changed 3→4. In a paired build with the existing URL guard restored, all 148 requests were 200 (134 JS, 14 CSS), errors were zero, and document loads stayed 3→3. This rules out missing embedded files, stale HTML, and a service worker for the same-build reload. The guard is in the current build. ## Files - `apps/web/src/app.html`; `apps/web/src/routes/+layout.svelte`; `apps/web/src/lib/components/app-sidebar.svelte`; `apps/web/src/lib/components/SidebarLinks.svelte`; `apps/web/src/lib/files/FilesBrowser.svelte`; `apps/web/src/lib/notes/NoteView.svelte`; `apps/web/src/lib/themes.test.ts`; `apps/web/src/lib/tray.svelte.test.ts`; `apps/web/src/lib/modeHeader.svelte.test.ts`; `apps/web/svelte.config.js`; `apps/web/package.json` - `apps/web/e2e/harness.mjs`; `apps/web/e2e/reload-423.mjs`; `bench/reload-423/.gitignore`; `bench/reload-423/generate-documents.mjs` - `crates/calternal-fs/src/lib.rs`; `crates/calternal-fs/src/web_assets.rs`; `crates/calternal-server/src/main.rs`; `crates/calternal-server/src/wire.rs` - `packages/ui/src/components/ModeHeader.svelte`; `packages/ui/src/components/SegmentedControl.svelte` ## Verification ```text cargo fmt --all -- --check (exit 0; no output) cargo clippy -p calternal-fs --all-targets -- -D warnings Finished `dev` profile [unoptimized + debuginfo] target(s) in 27.22s cargo test -p calternal-fs test result: ok. 42 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 28.18s test result: ok. 42 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 9.50s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s cargo clippy -p calternal-server --all-targets -- -D warnings Finished `dev` profile [unoptimized + debuginfo] target(s) in 5m 51s cargo test -p calternal-server test result: ok. 87 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 73.76s bun run check svelte-check found 0 errors and 0 warnings bun run test Test Files 136 passed (136) Tests 879 passed (879) Duration 202.53s (transform 62%, environment 16%, import 11%, tests 8%, setup 3%) ``` Production crawler exited 0 and reported: ```text PASS same-build Files crumb, sidebar row, browser Back, and phone folder menu: zero extra document loads PASS 20 in-app mode navigations across the A→B server switch: zero additional document loads from baseline 21 PASS an unsaved Note stays in the A document, then reaches the server before a later boundary load PASS updated state causes exactly one document load at the next safe navigation boundary PASS retained Build A Notes route chunk served after Build B: /_app/immutable/nodes/38.DeDbnZBO.js PASS retained Build A hash-only shared chunk served after Build B: /_app/immutable/chunks/-xN1Iuj-.js PASS 6 raw immutable-asset paths return 404 without the SPA shell Captured Calendar, Files, Photos, Note editor, and boot-shell screenshots at 390, 820, and 1440 px in light and dark ``` Screenshots: [full 30-image set](https://git.kayg.org/attachments/35ed5075-87ae-44d5-8f11-88e3b3d0c9a2), [390 light shell](https://git.kayg.org/attachments/cd467ea9-f4bf-42b5-8668-217550dcbf82), [390 dark shell](https://git.kayg.org/attachments/0f23f52a-9514-4bca-a6e7-ba94d4daaba7), [1440 light shell](https://git.kayg.org/attachments/c8972565-3cc3-4512-84d2-9655002f44d8), [1440 dark shell](https://git.kayg.org/attachments/f908aea2-1640-4fb9-acbb-865506f1b3c7). Same-build per-request captures: [JSON evidence bundle](https://git.kayg.org/attachments/432288e8-b62e-418a-9f57-9f2c32d84e40). ## Head, gaps, and decisions - Head: `4222eeab3236dff04b687e8722637af0b5043509` (`docs(reload): link shell and retention invariants to issue`). Worktree is clean. Ran `cargo clean` (removed 54,880 files, 10.8 GiB) and deleted generated fixture and web build output. No dependencies or migrations added. - Known gaps: no open implementation failures. One earlier full web-suite attempt hit a 5-second Analytics summary-card timeout under shared load; the final full run passed all 879 tests. - Decisions not specified in DESIGN: retain the newest ten builds and every build no more than seven days old, bounded by the one-GiB store cap; poll for frontend updates every 30 seconds and reload only at a safe route boundary; show an inline theme-aware boot skeleton during that intentional load. The hash-only eight-character rule applies only to SvelteKit immutable chunk paths.
kayg commented 2026-09-30 15:14:12 +00:00
Author
Owner
Copy link

Starting round 2 on job/reload-423. Base SHA: dfb5964a2f. I will add cold/warm route measurements and update-toast behavior, then run the requested web and per-crate Rust gates.

Starting round 2 on job/reload-423. Base SHA: dfb5964a2fcf13dc8b9a50a319eee09bc386f322. I will add cold/warm route measurements and update-toast behavior, then run the requested web and per-crate Rust gates.
kayg commented 2026-09-30 16:16:31 +00:00
Author
Owner
Copy link

Finding: the first found a missing handler in the merged shell () and five initial-prop capture warnings in Mail. I added the pointer-cancel handler, made the cached Inbox snapshot capture explicit, and reran the check: svelte-check now reports 0 errors and 0 warnings. The new route profile measures the seven requested views with cold, hard-refresh, Tab or Settings-link, deep-link, Back and Forward paths.

Finding: the first found a missing handler in the merged shell () and five initial-prop capture warnings in Mail. I added the pointer-cancel handler, made the cached Inbox snapshot capture explicit, and reran the check: svelte-check now reports 0 errors and 0 warnings. The new route profile measures the seven requested views with cold, hard-refresh, Tab or Settings-link, deep-link, Back and Forward paths.
kayg commented 2026-09-30 16:16:47 +00:00
Author
Owner
Copy link

Finding: the first bun run check found a missing cancelModePreload handler in the merged shell (apps/web/src/routes/+layout.svelte:735) and five initial-prop capture warnings in Mail. I added the pointer-cancel handler, made the cached Inbox snapshot capture explicit, and reran the check: svelte-check now reports 0 errors and 0 warnings. The new route profile measures the seven requested views with cold, hard-refresh, Tab or Settings-link, deep-link, Back and Forward paths.

Finding: the first bun run check found a missing cancelModePreload handler in the merged shell (apps/web/src/routes/+layout.svelte:735) and five initial-prop capture warnings in Mail. I added the pointer-cancel handler, made the cached Inbox snapshot capture explicit, and reran the check: svelte-check now reports 0 errors and 0 warnings. The new route profile measures the seven requested views with cold, hard-refresh, Tab or Settings-link, deep-link, Back and Forward paths.
kayg commented 2026-09-30 16:55:43 +00:00
Author
Owner
Copy link

Finding: the first route probe did not classify Calendar /today for first-meaningful-paint timing, and its cold Files path landed at a root containing only the Documents folder while the seeded rows were inside Documents. I fixed the route observer and now cold-load the stable Documents folder identity. Warm navigation also delays API GET responses by 300 ms and asserts that cached content appears first, before revalidation completes. No API contract changed.

Finding: the first route probe did not classify Calendar `/today` for first-meaningful-paint timing, and its cold Files path landed at a root containing only the Documents folder while the seeded rows were inside Documents. I fixed the route observer and now cold-load the stable Documents folder identity. Warm navigation also delays API GET responses by 300 ms and asserts that cached content appears first, before revalidation completes. No API contract changed.
kayg commented 2026-09-30 17:02:45 +00:00
Author
Owner
Copy link

Finding: the first cargo clippy -p calternal-server --all-targets -- -D warnings attempt stopped at RustEmbed because apps/web/build/ did not exist, then reported the expected missing embedded-asset methods. I am running the web production build before retrying the server gate; no Rust source diagnostic was emitted.

Finding: the first `cargo clippy -p calternal-server --all-targets -- -D warnings` attempt stopped at RustEmbed because `apps/web/build/` did not exist, then reported the expected missing embedded-asset methods. I am running the web production build before retrying the server gate; no Rust source diagnostic was emitted.
kayg commented 2026-09-30 17:34:47 +00:00
Author
Owner
Copy link

Progress: bun run check reports 0 errors and 0 warnings; bun run test passed 138 files / 906 tests. After building apps/web/build, cargo clippy -p calternal-server --all-targets -- -D warnings passed and cargo test -p calternal-server passed 87 tests with 2 ignored. The release server build is running for the production A→B proof and route profile.

Progress: `bun run check` reports 0 errors and 0 warnings; `bun run test` passed 138 files / 906 tests. After building `apps/web/build`, `cargo clippy -p calternal-server --all-targets -- -D warnings` passed and `cargo test -p calternal-server` passed 87 tests with 2 ignored. The release server build is running for the production A→B proof and route profile.
kayg commented 2026-09-30 18:14:25 +00:00
Author
Owner
Copy link

Evidence: three real production Build A→B reproductions committed the Calendar URL while the Files/Trash shell stayed visible. The browser request trace showed GET /api/v1/calendar/range pending, and the production server emitted no error. The mode selector awaited both route preparation and the full API preload before starting goto, so a slow Calendar data request delayed the route transition. Changed it to start navigation at activation and let real code/data preloads continue in parallel; a cold mode still shows its pending view until the route commits. Added the request/shell diagnostics to the E2E timeout for future route stalls.

Evidence: three real production Build A→B reproductions committed the Calendar URL while the Files/Trash shell stayed visible. The browser request trace showed `GET /api/v1/calendar/range` pending, and the production server emitted no error. The mode selector awaited both route preparation and the full API preload before starting `goto`, so a slow Calendar data request delayed the route transition. Changed it to start navigation at activation and let real code/data preloads continue in parallel; a cold mode still shows its pending view until the route commits. Added the request/shell diagnostics to the E2E timeout for future route stalls.
kayg commented 2026-09-30 18:27:50 +00:00
Author
Owner
Copy link

Follow-up diagnosis from the browser state: Calendar's /today entry commits through a same-mode redirect to /calendar/week/<date>. The layout's pending-header cleanup required an exact pathname match, so it kept the captured Files header after the Calendar route changed. Updated the cleanup to accept redirects when both paths resolve to the same registered mode. The Calendar range request in the trace belongs to its independent preload and can remain pending without blocking route navigation.

Follow-up diagnosis from the browser state: Calendar's `/today` entry commits through a same-mode redirect to `/calendar/week/<date>`. The layout's pending-header cleanup required an exact pathname match, so it kept the captured Files header after the Calendar route changed. Updated the cleanup to accept redirects when both paths resolve to the same registered mode. The Calendar range request in the trace belongs to its independent preload and can remain pending without blocking route navigation.
kayg commented 2026-09-30 18:55:34 +00:00
Author
Owner
Copy link

Evidence from --fallback-only: Build A serves the Files shell and /api/v1/plugins returns 200, but fallbackPage records cancelModePreload is not defined and has no [role=tab] elements. The same was true before restarting to Build B. This is a branch-base client defect from the missing callback that Build B already fixes. The full A→B harness needs a usable old shell, so I will add that callback only in the temporary Build A source used to generate the test binary; it is not a product change.

Evidence from `--fallback-only`: Build A serves the Files shell and `/api/v1/plugins` returns 200, but `fallbackPage` records `cancelModePreload is not defined` and has no `[role=tab]` elements. The same was true before restarting to Build B. This is a branch-base client defect from the missing callback that Build B already fixes. The full A→B harness needs a usable old shell, so I will add that callback only in the temporary Build A source used to generate the test binary; it is not a product change.
kayg commented 2026-09-30 19:17:02 +00:00
Author
Owner
Copy link

The isolated missing-chunk probe returns /notes in the same document after the Build A Notes module receives the simulated 404. Evidence: the browser recorded the old Notes node request, location.href became /notes, and no page errors were recorded; Playwright observed no document request. Updated the obsolete reload assertion to require the Notes surface to load without a document reload, matching #423's user-controlled refresh behavior. Build B's real old-node and hostile-path checks remain in probeImmutablePaths.

The isolated missing-chunk probe returns `/notes` in the same document after the Build A Notes module receives the simulated 404. Evidence: the browser recorded the old Notes node request, `location.href` became `/notes`, and no page errors were recorded; Playwright observed no document request. Updated the obsolete reload assertion to require the Notes surface to load without a document reload, matching #423's user-controlled refresh behavior. Build B's real old-node and hostile-path checks remain in `probeImmutablePaths`.
kayg commented 2026-09-30 19:57:44 +00:00
Author
Owner
Copy link

The full A→B crawl found that branch-base Build A (6c50a0f) can keep the Files header after its Calendar tab redirects from /today to /calendar/week/<date>: its older exact-path header matcher does not clear on that redirect. Build B handles the same-mode redirect, and its real-server crawler passes Calendar routes. I scoped the stale Build A asset-retention check to Files/Photos mode switches and the retained Note chunk; the current Build B Calendar behavior remains covered by the full route crawler. This is limited to the already-open legacy shell and cannot be repaired by changing the newly deployed Build B code.

The full A→B crawl found that branch-base Build A (6c50a0f) can keep the Files header after its Calendar tab redirects from `/today` to `/calendar/week/<date>`: its older exact-path header matcher does not clear on that redirect. Build B handles the same-mode redirect, and its real-server crawler passes Calendar routes. I scoped the stale Build A asset-retention check to Files/Photos mode switches and the retained Note chunk; the current Build B Calendar behavior remains covered by the full route crawler. This is limited to the already-open legacy shell and cannot be repaired by changing the newly deployed Build B code.
kayg commented 2026-09-30 20:00:58 +00:00
Author
Owner
Copy link

The first profile attempt rebuilt the production SPA and release server, then stopped before route measurement. bench/run.sh had hard-coded $ROOT/target/release/calternal-server, while this job uses the required preset CARGO_TARGET_DIR=/mnt/hdd/targets/jobs/reload-423; the built server was at $CARGO_TARGET_DIR/release/calternal-server. I changed the bench runner to use CARGO_TARGET_DIR with a worktree-target fallback and verified the configured release binary exists. The measured profile is being rerun now.

The first profile attempt rebuilt the production SPA and release server, then stopped before route measurement. `bench/run.sh` had hard-coded `$ROOT/target/release/calternal-server`, while this job uses the required preset `CARGO_TARGET_DIR=/mnt/hdd/targets/jobs/reload-423`; the built server was at `$CARGO_TARGET_DIR/release/calternal-server`. I changed the bench runner to use `CARGO_TARGET_DIR` with a worktree-target fallback and verified the configured release binary exists. The measured profile is being rerun now.
kayg commented 2026-09-30 20:09:10 +00:00
Author
Owner
Copy link

The next route-profile attempt launched the production server but failed while building the realistic Home: seedRealisticHome() calls assert.deepEqual() but route-perf.mjs did not import node:assert/strict (ReferenceError: assert is not defined, line 190). I added the missing import and verified the profile file parses. I am rerunning the profile from the committed head.

The next route-profile attempt launched the production server but failed while building the realistic Home: `seedRealisticHome()` calls `assert.deepEqual()` but `route-perf.mjs` did not import `node:assert/strict` (`ReferenceError: assert is not defined`, line 190). I added the missing import and verified the profile file parses. I am rerunning the profile from the committed head.
kayg commented 2026-09-30 20:17:42 +00:00
Author
Owner
Copy link

#423 round 2 report

Built

  • Warm mode selection navigates immediately while route and API preloads continue. Calendar same-mode redirects clear the captured old header.
  • Calendar, Mail, Money and Settings use cached data on warm navigation and revalidate after the cached first paint. Files retains the #522 loader path.
  • A newer version shows the shared “calternal has been updated” toast with a user-triggered Refresh. The test covers an A→B version change, unsaved Note and Composer protection, and restoration of the exact Note URL.
  • Added a production route profile for cold, hard-refresh, warm tab, in-app link, deep link, Back and Forward paths across Calendar, Files, Photos, Mail, Money, Analytics and Settings. The bench now honors CARGO_TARGET_DIR.

Files

apps/web/src/app.html, apps/web/svelte.config.js, apps/web/src/routes/+layout.svelte, apps/web/src/lib/navigation/modePreload.ts, apps/web/src/lib/notes/NoteView.svelte, apps/web/src/lib/mail/MailView.svelte, apps/web/src/lib/mail/inboxCache.ts, apps/web/src/lib/money/store.svelte.ts, apps/web/src/routes/money/[budget]/[month]/+page.svelte, apps/web/src/routes/settings/[...path]/+page.svelte, apps/web/src/routes/settings/api.svelte.ts, apps/web/e2e/reload-423.mjs, apps/web/e2e/route-perf.mjs, bench/run.sh, bench/record.py, bench/compare.py, bench/test_record.py, bench/test_compare.py.

Evidence and gates

  • Production Build A→B crawl passed against the real server. It covered the 614-file Home, current-build navigation through all requested route families, 20 legacy Files/Photos switches, retained Note and shared chunks, six hostile immutable-asset paths, and no-reload toast behavior.
  • Exact production crawl output: PASS 20 in-app Files/Photos mode navigations and retained Notes chunk across A→B: zero extra document loads from baseline 24; PASS A→B production update toast: no automatic reload, Note and Composer protection, exact deep link, and intentional Refresh; PASS 6 raw immutable-asset paths return 404 without the SPA shell.
  • Screenshots exist in the worktree at artifacts/reload-423/: toast, Calendar, Files, Photos, Note editor and boot shell at 390, 820 and 1440 px in light and dark. They are not attached to this comment yet.
  • bun run check had passed earlier in round 2, before the final E2E and bench-harness-only edits:
$ node scripts/check-type-tokens.mjs && node scripts/check-motion-tokens.mjs && svelte-kit sync && svelte-check --tsconfig ./tsconfig.json
Text sizes and UI shape values use shared role tokens.
UI transitions and animation options use shared motion tokens or documented exceptions.
Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web
Getting Svelte diagnostics...

svelte-check found 0 errors and 0 warnings
  • The earlier web unit run reported 138 files and 906 tests passed in 208.76s. Rust fmt/clippy/test gates also passed earlier in round 2 (calternal-fs: 44 core and 42 integration tests; calternal-server: 87 passed, 2 ignored). No Rust source changed in this round. These gates were not rerun after the final harness and bench edits.
  • The required route benchmark did not produce measurements. Its first attempt exposed and fixed a hard-coded target path; its second exposed and fixed a missing assertion import. The third profile was stopped before timing samples when the four-hour job cap elapsed. Therefore there are no cold/warm p50/p95 numbers or new docs/perf report.

Gaps and decisions

  • Remaining: rerun bench/run.sh --runs 3, record its results beside the baseline, rerun bun run check and bun run test, attach the screenshots to #423, then run cargo clean and remove apps/web/build. I stopped at the owner’s four-hour cap.
  • Local cold meaningful-paint budget is 5,000 ms, matching the route profile default; this still needs a successful measured run.
  • Build A predates the Calendar /today same-mode redirect fix. The current Build B crawler covers that redirect; the stale Build A asset-retention check uses non-redirecting Files/Photos routes.
  • The toast offers Refresh only; a Later action was optional in the issue prompt.

Head: 462038149b2861d5ceca7c92651d71c585e887ca.

#423 round 2 report ## Built - Warm mode selection navigates immediately while route and API preloads continue. Calendar same-mode redirects clear the captured old header. - Calendar, Mail, Money and Settings use cached data on warm navigation and revalidate after the cached first paint. Files retains the #522 loader path. - A newer version shows the shared “calternal has been updated” toast with a user-triggered Refresh. The test covers an A→B version change, unsaved Note and Composer protection, and restoration of the exact Note URL. - Added a production route profile for cold, hard-refresh, warm tab, in-app link, deep link, Back and Forward paths across Calendar, Files, Photos, Mail, Money, Analytics and Settings. The bench now honors `CARGO_TARGET_DIR`. ## Files `apps/web/src/app.html`, `apps/web/svelte.config.js`, `apps/web/src/routes/+layout.svelte`, `apps/web/src/lib/navigation/modePreload.ts`, `apps/web/src/lib/notes/NoteView.svelte`, `apps/web/src/lib/mail/MailView.svelte`, `apps/web/src/lib/mail/inboxCache.ts`, `apps/web/src/lib/money/store.svelte.ts`, `apps/web/src/routes/money/[budget]/[month]/+page.svelte`, `apps/web/src/routes/settings/[...path]/+page.svelte`, `apps/web/src/routes/settings/api.svelte.ts`, `apps/web/e2e/reload-423.mjs`, `apps/web/e2e/route-perf.mjs`, `bench/run.sh`, `bench/record.py`, `bench/compare.py`, `bench/test_record.py`, `bench/test_compare.py`. ## Evidence and gates - Production Build A→B crawl passed against the real server. It covered the 614-file Home, current-build navigation through all requested route families, 20 legacy Files/Photos switches, retained Note and shared chunks, six hostile immutable-asset paths, and no-reload toast behavior. - Exact production crawl output: `PASS 20 in-app Files/Photos mode navigations and retained Notes chunk across A→B: zero extra document loads from baseline 24`; `PASS A→B production update toast: no automatic reload, Note and Composer protection, exact deep link, and intentional Refresh`; `PASS 6 raw immutable-asset paths return 404 without the SPA shell`. - Screenshots exist in the worktree at `artifacts/reload-423/`: toast, Calendar, Files, Photos, Note editor and boot shell at 390, 820 and 1440 px in light and dark. They are not attached to this comment yet. - `bun run check` had passed earlier in round 2, before the final E2E and bench-harness-only edits: ```text $ node scripts/check-type-tokens.mjs && node scripts/check-motion-tokens.mjs && svelte-kit sync && svelte-check --tsconfig ./tsconfig.json Text sizes and UI shape values use shared role tokens. UI transitions and animation options use shared motion tokens or documented exceptions. Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web Getting Svelte diagnostics... svelte-check found 0 errors and 0 warnings ``` - The earlier web unit run reported 138 files and 906 tests passed in 208.76s. Rust fmt/clippy/test gates also passed earlier in round 2 (`calternal-fs`: 44 core and 42 integration tests; `calternal-server`: 87 passed, 2 ignored). No Rust source changed in this round. These gates were not rerun after the final harness and bench edits. - The required route benchmark did not produce measurements. Its first attempt exposed and fixed a hard-coded target path; its second exposed and fixed a missing assertion import. The third profile was stopped before timing samples when the four-hour job cap elapsed. Therefore there are no cold/warm p50/p95 numbers or new `docs/perf` report. ## Gaps and decisions - Remaining: rerun `bench/run.sh --runs 3`, record its results beside the baseline, rerun `bun run check` and `bun run test`, attach the screenshots to #423, then run `cargo clean` and remove `apps/web/build`. I stopped at the owner’s four-hour cap. - Local cold meaningful-paint budget is 5,000 ms, matching the route profile default; this still needs a successful measured run. - Build A predates the Calendar `/today` same-mode redirect fix. The current Build B crawler covers that redirect; the stale Build A asset-retention check uses non-redirecting Files/Photos routes. - The toast offers Refresh only; a Later action was optional in the issue prompt. Head: `462038149b2861d5ceca7c92651d71c585e887ca`.
kayg commented 2026-09-30 20:22:08 +00:00
Author
Owner
Copy link

Round 3 started on job/reload-423 at 462038149b (base dev: 9ecde429a7). I am completing the shared Calendar/Files/Photos/Mail/Money/Analytics/Settings cold, hard-refresh and warm benchmark on the locked perf VM, shortening the phone update toast to one line with Refresh and a normal Later dismiss, then recording results, running the requested web gates and cleaning build output.

Round 3 started on job/reload-423 at 462038149b2861d5ceca7c92651d71c585e887ca (base dev: 9ecde429a7e6f8b846211287ecd6b1475394db94). I am completing the shared Calendar/Files/Photos/Mail/Money/Analytics/Settings cold, hard-refresh and warm benchmark on the locked perf VM, shortening the phone update toast to one line with Refresh and a normal Later dismiss, then recording results, running the requested web gates and cleaning build output.
kayg commented 2026-09-30 20:39:03 +00:00
Author
Owner
Copy link

Screenshot harness finding: the new toast-only production run reached the real Files route but waited only for ; its setup had already created the real row, so the 30 s readiness wait expired before toast checks. I am changing readiness to accept either a real Files row or the real empty state and rerunning the capture.

Screenshot harness finding: the new toast-only production run reached the real Files route but waited only for ; its setup had already created the real row, so the 30 s readiness wait expired before toast checks. I am changing readiness to accept either a real Files row or the real empty state and rerunning the capture.
kayg commented 2026-09-30 20:39:20 +00:00
Author
Owner
Copy link

Correction to my previous finding: the screenshot-only run timed out waiting for the empty-folder marker because the fixture had created a visible Archive row. I will let readiness accept either that real row or the real empty state.

Correction to my previous finding: the screenshot-only run timed out waiting for the empty-folder marker because the fixture had created a visible Archive row. I will let readiness accept either that real row or the real empty state.
kayg commented 2026-09-30 21:11:55 +00:00
Author
Owner
Copy link

Finding after the required origin/dev merge: the resolved layout kept the incoming chrome but lost the existing updated.current hook. The production-build screenshot check then timed out for 30 seconds waiting for .cal-toast-label. I restored the #423 update hook alongside the merged layout; rebuild and screenshot recapture are next.

Finding after the required origin/dev merge: the resolved layout kept the incoming chrome but lost the existing updated.current hook. The production-build screenshot check then timed out for 30 seconds waiting for .cal-toast-label. I restored the #423 update hook alongside the merged layout; rebuild and screenshot recapture are next.
kayg commented 2026-09-30 21:28:16 +00:00
Author
Owner
Copy link

Perf setup finding on 2026-09-30: the shared release server returned HTTP 404 for POST /api/v1/money/budgets while seeding the real route Home, so the route measurements did not start. That binary predates the merged Money API. I am building the merged release server on the worktree host and will copy it to the perf VM; no compilation will run on the VM. The failed setup released /root/perf.lock and recorded its end load.

Perf setup finding on 2026-09-30: the shared release server returned HTTP 404 for POST /api/v1/money/budgets while seeding the real route Home, so the route measurements did not start. That binary predates the merged Money API. I am building the merged release server on the worktree host and will copy it to the perf VM; no compilation will run on the VM. The failed setup released /root/perf.lock and recorded its end load.
kayg commented 2026-09-30 21:44:46 +00:00
Author
Owner
Copy link

Perf setup finding on 2026-09-30: the current server build accepts Money fixture creation, then the shared route harness stops at setThemeContext with HTTP 422: auto_scheme.location is an unknown field; the merged API accepts only mode. No route timing was recorded and /root/perf.lock was released. I am updating the shared harness request to the merged Appearance contract before rerunning.

Perf setup finding on 2026-09-30: the current server build accepts Money fixture creation, then the shared route harness stops at setThemeContext with HTTP 422: auto_scheme.location is an unknown field; the merged API accepts only mode. No route timing was recorded and /root/perf.lock was released. I am updating the shared harness request to the merged Appearance contract before rerunning.
kayg commented 2026-09-30 21:48:57 +00:00
Author
Owner
Copy link

Fixed the Appearance helper mismatch uncovered by the perf run. The current API rejects the retired auto_scheme.location field with HTTP 422, so the shared E2E harness now sends only auto_scheme.mode in each theme helper. The fix is committed as 1fb1ef0c3; the benchmark is rerunning on the perf VM under /root/perf.lock with the current server and harness.

Fixed the Appearance helper mismatch uncovered by the perf run. The current API rejects the retired `auto_scheme.location` field with HTTP 422, so the shared E2E harness now sends only `auto_scheme.mode` in each theme helper. The fix is committed as `1fb1ef0c3`; the benchmark is rerunning on the perf VM under `/root/perf.lock` with the current server and harness.
kayg commented 2026-09-30 21:58:15 +00:00
Author
Owner
Copy link

The first locked route run passed its 390 px light cold and hard-refresh samples, then stopped while seeding warm routes: the test tried to use the Files tray tab before the fresh shell had finished exposing its plugin tabs. The shared profile now seeds its route caches with same-tab deep links, then measures actual tray switches separately. This keeps the route cache warm-up independent of asynchronous tab availability while retaining real warm mode-switch samples. Fix committed as 263f52f9f.

The first locked route run passed its 390 px light cold and hard-refresh samples, then stopped while seeding warm routes: the test tried to use the Files tray tab before the fresh shell had finished exposing its plugin tabs. The shared profile now seeds its route caches with same-tab deep links, then measures actual tray switches separately. This keeps the route cache warm-up independent of asynchronous tab availability while retaining real warm mode-switch samples. Fix committed as `263f52f9f`.
kayg commented 2026-09-30 22:02:20 +00:00
Author
Owner
Copy link

Follow-up to the warm-profile finding: a second cache setup loop also used a mode-tab click before collecting timed samples. It now primes the source route through a same-tab deep link as well. The measured tab-switch path remains unchanged; this removes only setup dependencies on asynchronous tab readiness. Committed as cf8be1672.

Follow-up to the warm-profile finding: a second cache setup loop also used a mode-tab click before collecting timed samples. It now primes the source route through a same-tab deep link as well. The measured tab-switch path remains unchanged; this removes only setup dependencies on asynchronous tab readiness. Committed as `cf8be1672`.
kayg commented 2026-09-30 22:07:01 +00:00
Author
Owner
Copy link

The next run reached warm sampling and showed why its setup still timed out: its final setup route was Settings, where the app hides the mode tray. The timed loop now navigates to its source view through a same-tab deep link, then measures the target mode-tab click. The back/forward cases keep their target route as the preceding history entry. Fix committed as 3c7f1380d.

The next run reached warm sampling and showed why its setup still timed out: its final setup route was Settings, where the app hides the mode tray. The timed loop now navigates to its source view through a same-tab deep link, then measures the target mode-tab click. The back/forward cases keep their target route as the preceding history entry. Fix committed as `3c7f1380d`.
kayg commented 2026-09-30 22:15:58 +00:00
Author
Owner
Copy link

The warm tab sample then reached Photos as its source and found that an item deep link does not expose the mode tray used by this measurement. The timed samples now start from the Files or Photos mode entry route. Photo-item deep links remain in the separate deep-link measurements. Committed as 2df1484d6.

The warm tab sample then reached Photos as its source and found that an item deep link does not expose the mode tray used by this measurement. The timed samples now start from the Files or Photos mode entry route. Photo-item deep links remain in the separate deep-link measurements. Committed as `2df1484d6`.
kayg commented 2026-09-30 22:25:39 +00:00
Author
Owner
Copy link

The Files warm sample timed out because Playwright waited for the full document load on the large folder. The shared route harness now disables that click auto-wait and waits for URL commit followed by the real route-ready marker, so timing still ends at visible route content. This supports both #423 and the larger #549 harness. Fix: 7279d12a8.

The Files warm sample timed out because Playwright waited for the full document load on the large folder. The shared route harness now disables that click auto-wait and waits for URL commit followed by the real route-ready marker, so timing still ends at visible route content. This supports both #423 and the larger #549 harness. Fix: 7279d12a8.
kayg commented 2026-09-30 22:38:19 +00:00
Author
Owner
Copy link

The locked final6 route profile completed the 390 px light matrix and the 390 px dark cold/hard-refresh matrix. It stopped during the third dark warm repetition: when returning from the large Files route, the Photos readiness marker did not become visible within 60 seconds. The VM one-minute load was 0.07 at start and 3.49 at exit; the run wrote no raw JSON. I am isolating this route/load interaction before collecting the full matrix.

The locked final6 route profile completed the 390 px light matrix and the 390 px dark cold/hard-refresh matrix. It stopped during the third dark warm repetition: when returning from the large Files route, the Photos readiness marker did not become visible within 60 seconds. The VM one-minute load was 0.07 at start and 3.49 at exit; the run wrote no raw JSON. I am isolating this route/load interaction before collecting the full matrix.
kayg commented 2026-09-30 23:20:36 +00:00
Author
Owner
Copy link

The local fallback profile timed out after 120 seconds while waiting for Photos content at the Files folder URL (/files?path=Files%2FBench%2F5k-folder). This came from warm setup reusing route.path after the Files route path had been rewritten to its large deep link for cold and hard-refresh samples. I am changing warm source setup to use explicit mode roots by default; #549 can select the deep Files source with PERF_ROUTE_FILES_SOURCE=deep. The perf VM remains occupied, and the local host load at this failure was 36.73. No completed raw profile was written.

The local fallback profile timed out after 120 seconds while waiting for Photos content at the Files folder URL (`/files?path=Files%2FBench%2F5k-folder`). This came from warm setup reusing `route.path` after the Files route path had been rewritten to its large deep link for cold and hard-refresh samples. I am changing warm source setup to use explicit mode roots by default; #549 can select the deep Files source with `PERF_ROUTE_FILES_SOURCE=deep`. The perf VM remains occupied, and the local host load at this failure was 36.73. No completed raw profile was written.
kayg commented 2026-10-01 00:21:15 +00:00
Author
Owner
Copy link

After the warm-source fix, the local fallback passed the 390 px and 820 px matrices and reached the 1440 px light warm Files sample. That sample stopped because its URL did not commit within the hard-coded 30-second wait. At the stop, local load was 18.95 (one minute) and 26.79 (five minutes); no raw JSON was written. I changed the URL-commit wait to use the route-ready timeout setting, which is 120 seconds for the next run. The perf VM is still locked by another profile and showed a one-minute load of 7.36.

After the warm-source fix, the local fallback passed the 390 px and 820 px matrices and reached the 1440 px light warm Files sample. That sample stopped because its URL did not commit within the hard-coded 30-second wait. At the stop, local load was 18.95 (one minute) and 26.79 (five minutes); no raw JSON was written. I changed the URL-commit wait to use the route-ready timeout setting, which is 120 seconds for the next run. The perf VM is still locked by another profile and showed a one-minute load of 7.36.
kayg commented 2026-10-01 00:51:33 +00:00
Author
Owner
Copy link

A full local rerun with the warm-source setting still timed out after 120 seconds while waiting for Photos; the browser had returned to /files?path=Files%2FBench%2F5k-folder. At failure, local load was 22.48 (one minute) and 27.01 (five minutes). The /files route can reuse the last selected folder, so I changed normal warm setup to use the explicit Files root (/files?path=) and to reach a visible Photos source through its real mode tab. Settings still uses a root link when the tray is hidden. #549 can select the deep Files source. node --check passed.

A full local rerun with the warm-source setting still timed out after 120 seconds while waiting for Photos; the browser had returned to `/files?path=Files%2FBench%2F5k-folder`. At failure, local load was 22.48 (one minute) and 27.01 (five minutes). The `/files` route can reuse the last selected folder, so I changed normal warm setup to use the explicit Files root (`/files?path=`) and to reach a visible Photos source through its real mode tab. Settings still uses a root link when the tray is hidden. #549 can select the deep Files source. `node --check` passed.
kayg commented 2026-10-01 00:58:40 +00:00
Author
Owner
Copy link

The focused 390 px dark profile completed the cold, hard-refresh and warm navigation checks for all seven routes, including the Files-to-Photos path. It then stopped in the separate mode-switch interaction sample: .timeline .tile matched 29 real Photos tiles, and Playwright rejected the strict locator wait. I am changing the interaction helper to wait for the first matching visible item. No route-readiness failure occurred in this run.

The focused 390 px dark profile completed the cold, hard-refresh and warm navigation checks for all seven routes, including the Files-to-Photos path. It then stopped in the separate mode-switch interaction sample: `.timeline .tile` matched 29 real Photos tiles, and Playwright rejected the strict locator wait. I am changing the interaction helper to wait for the first matching visible item. No route-readiness failure occurred in this run.
kayg commented 2026-10-01 01:23:56 +00:00
Author
Owner
Copy link

Round 3 report — reload-423 (#423)

Head SHA: a52229ec323ea6525c8a1353c49312a1476274b2 on job/reload-423. Worktree is clean. No push, deploy or merge.

Built: phone update toast now uses “Update available” on narrow screens, one Refresh action and normal dismiss for Later; wider screens retain “calternal has been updated”. The shared route harness now waits on URL commit and route content, starts warm Files samples at explicit /files?path=, and supports PERF_ROUTE_FILES_SOURCE=deep for #549. The performance report and raw local route sample are in docs/perf/2026-10-01-reload-423.md and docs/perf/runs/2026-10-01T005919Z-2d8427e79/.

Files touched include apps/web/e2e/{harness.mjs,reload-423.mjs,route-perf.mjs}, the update toast and mode-navigation components/stores/routes/tests under apps/web/src/, packages/ui/src/components/{ModeHeader,SegmentedControl}.svelte, crates/calternal-fs/src/{lib.rs,web_assets.rs}, crates/calternal-server/src/{main.rs,wire.rs}, bench/{run.sh,record.py,compare.py}, benchmark helpers/tests and the listed docs/perf/ files.

Benchmark limitation: the perf VM stayed locked by another job. At final check it showed load 4.06, 4.16, 4.07, above the one-minute gate. Per the single-tenant rule I used the local fallback. The archived sample has one run for all seven requested routes at 390 px dark only; it is not a full VM matrix and is not baseline-comparable. It records host load [15.63, 19.44, 23.37] before and [25.91, 23.90, 24.04] after. The 300 ms warm check and FCP observer produced assertion gaps recorded in raw JSON. A later focused run using a 3-second delay timed out waiting for the Photos URL after the mode click and remained on the Files folder URL under local load [13.39, 15.88, 19.26]; the earlier A→B crawl passed. This navigation needs another check on an available isolated host.

Visual evidence is attached to this issue for 390, 820 and 1440 px in light and dark. No baseline was changed.

Decisions not covered by DESIGN: use an explicit Files root for the normal warm route source; expose PERF_ROUTE_FILES_SOURCE=deep for #549’s large-folder case. Use the local single-profile result only as a labeled partial record because the VM lock was unavailable and the three-hour limit arrived.

Gates (verbatim output excerpts):

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

cargo clippy -p calternal-fs --all-targets -- -D warnings
Finished `dev` profile [unoptimized + debuginfo] target(s) in 13.61s

cargo test -p calternal-fs
45 passed (unit); 42 passed (storage); doc tests: 0

cargo clippy -p calternal-server --all-targets -- -D warnings
Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 27s

cargo test -p calternal-server
95 passed; 0 failed; 3 ignored; 0 measured; 0 filtered out; finished in 42.54s

bun run check
$ node scripts/check-type-tokens.mjs && node scripts/check-motion-tokens.mjs && svelte-kit sync && svelte-check --tsconfig ./tsconfig.json
Text sizes and UI shape values use shared role tokens.
UI transitions and animation options use shared motion tokens or documented exceptions.
Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web
Getting Svelte diagnostics...

svelte-check found 0 errors and 0 warnings

bun run test
Test Files  140 passed (140)
     Tests  917 passed (917)
  Start at  00:19:37
  Duration  186.15s (transform 55%, environment 17%, import 15%, tests 9%, setup 4%)

  Transform  |component| transforming modules took 368.79s · 48% of tracked time, re-done on every run
             persist transforms across runs with fsModuleCache: true
             learn more: https://vitest.dev/guide/improving-performance#caching-between-reruns

cargo clean
Removed 21489 files, 9.3GiB total

Cleanup: apps/web/build and apps/web/.svelte-kit removed. The Rust and web gates above passed before the final route-harness-only diagnostics and reporting changes; node --check, bash -n bench/run.sh and git diff --check passed for those changes.

Round 3 report — reload-423 (#423) Head SHA: `a52229ec323ea6525c8a1353c49312a1476274b2` on `job/reload-423`. Worktree is clean. No push, deploy or merge. Built: phone update toast now uses “Update available” on narrow screens, one Refresh action and normal dismiss for Later; wider screens retain “calternal has been updated”. The shared route harness now waits on URL commit and route content, starts warm Files samples at explicit `/files?path=`, and supports `PERF_ROUTE_FILES_SOURCE=deep` for #549. The performance report and raw local route sample are in [docs/perf/2026-10-01-reload-423.md](docs/perf/2026-10-01-reload-423.md) and `docs/perf/runs/2026-10-01T005919Z-2d8427e79/`. Files touched include `apps/web/e2e/{harness.mjs,reload-423.mjs,route-perf.mjs}`, the update toast and mode-navigation components/stores/routes/tests under `apps/web/src/`, `packages/ui/src/components/{ModeHeader,SegmentedControl}.svelte`, `crates/calternal-fs/src/{lib.rs,web_assets.rs}`, `crates/calternal-server/src/{main.rs,wire.rs}`, `bench/{run.sh,record.py,compare.py}`, benchmark helpers/tests and the listed `docs/perf/` files. Benchmark limitation: the perf VM stayed locked by another job. At final check it showed load `4.06, 4.16, 4.07`, above the one-minute gate. Per the single-tenant rule I used the local fallback. The archived sample has one run for all seven requested routes at 390 px dark only; it is not a full VM matrix and is not baseline-comparable. It records host load `[15.63, 19.44, 23.37]` before and `[25.91, 23.90, 24.04]` after. The 300 ms warm check and FCP observer produced assertion gaps recorded in raw JSON. A later focused run using a 3-second delay timed out waiting for the Photos URL after the mode click and remained on the Files folder URL under local load `[13.39, 15.88, 19.26]`; the earlier A→B crawl passed. This navigation needs another check on an available isolated host. Visual evidence is attached to this issue for 390, 820 and 1440 px in light and dark. No baseline was changed. Decisions not covered by DESIGN: use an explicit Files root for the normal warm route source; expose `PERF_ROUTE_FILES_SOURCE=deep` for #549’s large-folder case. Use the local single-profile result only as a labeled partial record because the VM lock was unavailable and the three-hour limit arrived. Gates (verbatim output excerpts): ```text cargo fmt --check (exit 0; no output) cargo clippy -p calternal-fs --all-targets -- -D warnings Finished `dev` profile [unoptimized + debuginfo] target(s) in 13.61s cargo test -p calternal-fs 45 passed (unit); 42 passed (storage); doc tests: 0 cargo clippy -p calternal-server --all-targets -- -D warnings Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 27s cargo test -p calternal-server 95 passed; 0 failed; 3 ignored; 0 measured; 0 filtered out; finished in 42.54s bun run check $ node scripts/check-type-tokens.mjs && node scripts/check-motion-tokens.mjs && svelte-kit sync && svelte-check --tsconfig ./tsconfig.json Text sizes and UI shape values use shared role tokens. UI transitions and animation options use shared motion tokens or documented exceptions. Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web Getting Svelte diagnostics... svelte-check found 0 errors and 0 warnings bun run test Test Files 140 passed (140) Tests 917 passed (917) Start at 00:19:37 Duration 186.15s (transform 55%, environment 17%, import 15%, tests 9%, setup 4%) Transform |component| transforming modules took 368.79s · 48% of tracked time, re-done on every run persist transforms across runs with fsModuleCache: true learn more: https://vitest.dev/guide/improving-performance#caching-between-reruns cargo clean Removed 21489 files, 9.3GiB total ``` Cleanup: `apps/web/build` and `apps/web/.svelte-kit` removed. The Rust and web gates above passed before the final route-harness-only diagnostics and reporting changes; `node --check`, `bash -n bench/run.sh` and `git diff --check` passed for those changes.
kayg commented 2026-10-01 08:02:03 +00:00
Author
Owner
Copy link

Owner update (2026-09-30), for traceability: after the root cause was found, the owner asked: "yeah please also test cold/warm navigations and that they should both feel instant. also we need a 'Refresh to update ' toast - word it in a user friendly way".

So the acceptance for this issue includes:

  • a cold and a warm navigation measurement across every Tab, both with no visible loading state (cached content first, then refresh; see also #549 and #527);
  • the update toast in plain words (current build: "calternal has been updated" with a Refresh action), never reloading during an unsaved edit.

The round-2 job comments above report both as built on job/reload-423. Check the toast wording against the "user-friendly names, no jargon" rule in review.

**Owner update (2026-09-30), for traceability:** after the root cause was found, the owner asked: "yeah please also test cold/warm navigations and that they should both feel instant. also we need a 'Refresh to update <action>' toast - word it in a user friendly way". So the acceptance for this issue includes: - a cold and a warm navigation measurement across every Tab, both with no visible loading state (cached content first, then refresh; see also #549 and #527); - the update toast in plain words (current build: "calternal has been updated" with a **Refresh** action), never reloading during an unsaved edit. The round-2 job comments above report both as built on `job/reload-423`. Check the toast wording against the "user-friendly names, no jargon" rule in review.
kayg commented 2026-10-01 23:21:28 +00:00
Author
Owner
Copy link

Started reload-423 on branch job/reload-423. Base HEAD: a52229ec32; origin/dev at start: 687ff70313. I am tracing the user-scoped caches and #555 browser test before editing.

Started reload-423 on branch job/reload-423. Base HEAD: a52229ec323ea6525c8a1353c49312a1476274b2; origin/dev at start: 687ff703136e71e89f8dfba139e93cd0788b25c1. I am tracing the user-scoped caches and #555 browser test before editing.
kayg commented 2026-10-01 23:56:57 +00:00
Author
Owner
Copy link

Source audit finding for #423: inboxCache.ts held one module-level Mail snapshot; MoneyStore held Budgets and month reports in process memory and used an untagged calternal.money.budget key; modePreload.ts keyed ready/in-flight routes only by mode. These could retain one User's cached data or readiness across a User change if an event or reload path was missed. I moved the persisted snapshots and readiness markers through userStorage, keyed the in-memory caches by the active User, and added a real cached Mail row to the #555 two-User browser scenario.

Source audit finding for #423: `inboxCache.ts` held one module-level Mail snapshot; `MoneyStore` held Budgets and month reports in process memory and used an untagged `calternal.money.budget` key; `modePreload.ts` keyed ready/in-flight routes only by mode. These could retain one User's cached data or readiness across a User change if an event or reload path was missed. I moved the persisted snapshots and readiness markers through `userStorage`, keyed the in-memory caches by the active User, and added a real cached Mail row to the #555 two-User browser scenario.
kayg commented 2026-10-02 00:00:48 +00:00
Author
Owner
Copy link

Finished #423 on branch job/reload-423.

Head SHA: 2399db841cf16ade3fbf47fcfab50578a3abe364

Commits:

  • 21d4b02a5 — merge origin/dev (includes #555 userStorage).
  • 2399db841 — scope warm caches to the active User.

Built:

  • Mail Inbox snapshots persist through userStorage, restore by User, and reject late requests after a User change. The #555 two-User browser test now paints an Alice Mail row from the production snapshot format before checking cleanup.
  • Money budgets and month reports use User-scoped userStorage; the in-memory Money and warm-route caches clear or change namespace with the active User.

Files changed by the cache fix:

  • apps/web/src/lib/mail/inboxCache.ts
  • apps/web/src/lib/money/store.svelte.ts
  • apps/web/src/lib/navigation/modePreload.ts
  • apps/web/e2e/user-storage-555.mjs
  • apps/web/src/lib/modeHeader.svelte.test.ts
  • apps/web/src/lib/userStorage-boot.test.ts
  • apps/web/src/routes/+layout.svelte

Gates (final output excerpts, verbatim):

bun run check

User browser caches use userStorage; only documented device/public-link exceptions remain.
Text sizes and UI shape values use shared role tokens.
UI transitions and animation options use shared motion tokens or documented exceptions.
Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web
Getting Svelte diagnostics...
svelte-check found 0 errors and 0 warnings

bun run test

Test Files  148 passed (148)
      Tests  1014 passed (1014)
   Start at  01:55:40
   Duration  57.08s (transform 42%, environment 23%, import 17%, tests 13%, setup 5%)

bun run build

> Using @sveltejs/adapter-static
  Wrote site to "build"
  ✔ done

Known gaps:

  • I did not run test:e2e:user-storage-555: another job had WebKit and Chromium processes active, and the host allows one browser at a time. The new real-row assertion is in the test.
  • I did not record a new performance sample for this cache-only round. The branch's existing bench/reload-423 profile remains available.

Decisions the design docs do not specify:

  • Keep the Money budget list and up to eight month reports in per-User local userStorage; retain the existing 30-second stale window.
  • Keep the bounded Mail Inbox page in per-User userStorage; retain the existing 2-second stale window and 50-row page.
  • Warm route readiness is tracked per User in memory and mirrored to userStorage. The SvelteKit route data itself is not restored across a document reload.

Cleanup: cargo clean reported Removed 1 file, 356B total; generated web build output was removed. Working tree is clean.

Finished #423 on branch `job/reload-423`. Head SHA: `2399db841cf16ade3fbf47fcfab50578a3abe364` Commits: - `21d4b02a5` — merge `origin/dev` (includes #555 `userStorage`). - `2399db841` — scope warm caches to the active User. Built: - Mail Inbox snapshots persist through `userStorage`, restore by User, and reject late requests after a User change. The #555 two-User browser test now paints an Alice Mail row from the production snapshot format before checking cleanup. - Money budgets and month reports use User-scoped `userStorage`; the in-memory Money and warm-route caches clear or change namespace with the active User. Files changed by the cache fix: - `apps/web/src/lib/mail/inboxCache.ts` - `apps/web/src/lib/money/store.svelte.ts` - `apps/web/src/lib/navigation/modePreload.ts` - `apps/web/e2e/user-storage-555.mjs` - `apps/web/src/lib/modeHeader.svelte.test.ts` - `apps/web/src/lib/userStorage-boot.test.ts` - `apps/web/src/routes/+layout.svelte` Gates (final output excerpts, verbatim): `bun run check` ``` User browser caches use userStorage; only documented device/public-link exceptions remain. Text sizes and UI shape values use shared role tokens. UI transitions and animation options use shared motion tokens or documented exceptions. Loading svelte-check in workspace: /home/kayg/Developer/calternal-wt/reload-423/apps/web Getting Svelte diagnostics... svelte-check found 0 errors and 0 warnings ``` `bun run test` ``` Test Files 148 passed (148) Tests 1014 passed (1014) Start at 01:55:40 Duration 57.08s (transform 42%, environment 23%, import 17%, tests 13%, setup 5%) ``` `bun run build` ``` > Using @sveltejs/adapter-static Wrote site to "build" ✔ done ``` Known gaps: - I did not run `test:e2e:user-storage-555`: another job had WebKit and Chromium processes active, and the host allows one browser at a time. The new real-row assertion is in the test. - I did not record a new performance sample for this cache-only round. The branch's existing `bench/reload-423` profile remains available. Decisions the design docs do not specify: - Keep the Money budget list and up to eight month reports in per-User local `userStorage`; retain the existing 30-second stale window. - Keep the bounded Mail Inbox page in per-User `userStorage`; retain the existing 2-second stale window and 50-row page. - Warm route readiness is tracked per User in memory and mirrored to `userStorage`. The SvelteKit route data itself is not restored across a document reload. Cleanup: `cargo clean` reported `Removed 1 file, 356B total`; generated web build output was removed. Working tree is clean.
kayg commented 2026-10-02 17:33:19 +00:00
Author
Owner
Copy link

This route has another stuck state when its lazy chunk import rejects: apps/web/src/routes/analytics/[period]/[date]/+page.svelte:53-58 leaves Dashboard null after a failed import, so line 67 keeps showing “Loading analytics” with no Retry or error state. Please include this route in the chunk-failure recovery check. A test can reject the Dashboard import and verify that Analytics shows a recovery action instead of a permanent skeleton.

This route has another stuck state when its lazy chunk import rejects: `apps/web/src/routes/analytics/[period]/[date]/+page.svelte:53-58` leaves `Dashboard` null after a failed import, so line 67 keeps showing “Loading analytics” with no Retry or error state. Please include this route in the chunk-failure recovery check. A test can reject the Dashboard import and verify that Analytics shows a recovery action instead of a permanent skeleton.
kayg commented 2026-10-02 17:39:52 +00:00
Author
Owner
Copy link

A second lazy-chunk failure point is the Composer panel. When composer.open becomes true, the app shell imports Composer.svelte with .then() but no rejection handler. If the chunk is missing, the panel stays absent and the opening action has no visible result or recovery action.

Evidence: apps/web/src/routes/+layout.svelte:65-72,915.

Please include the Composer and Analytics lazy imports in the chunk-failure recovery check. A test can reject the Composer import after the User opens it and verify a visible Retry path.

A second lazy-chunk failure point is the Composer panel. When `composer.open` becomes true, the app shell imports `Composer.svelte` with `.then()` but no rejection handler. If the chunk is missing, the panel stays absent and the opening action has no visible result or recovery action. Evidence: `apps/web/src/routes/+layout.svelte:65-72,915`. Please include the Composer and Analytics lazy imports in the chunk-failure recovery check. A test can reject the Composer import after the User opens it and verify a visible Retry path.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
wip/e2e-b2-1071
wip/e2e-b-1071
wip/draw4-1101
wip/draw3-1101
wip/draw2-1101
wip/draw-1101
wip/directory-1199-r
wip/directory-1199
wip/delete-1119
wip/collabrev-1197
wip/collabloss-1197
wip/cards2-1083
wip/cards-1083
wip/canvas-visual
wip/canvasvis2-976
wip/calhdr-1112
wip/calcards-1115
wip/browserfix
wip/blocks-1125
wip/allday-1107
wip/agenda-decks
wip/agenda-1086
wip/adv7c-1105
wip/txentry-1198
wip/trayicons2-1095
wip/trayicons-1095
wip/tagperf-1186
wip/sidebar3-1094
wip/rev2-webperf
wip/rev2-money-ident
job/adv-1202
wip/restyle-notes
wip/previewcard-1098
wip/palette2-1123
wip/palette-1093
wip/onboard2-1141
wip/onboard-1141.aborted-early
wip/onboard-1141
wip/nlpchip-1127
wip/morph-1104
wip/merge-round-7c5
wip/merge-round-7c4
job/notifloop-1194
wip/merge-round-7c3
wip/merge-round-7c2
wip/merge-round-7c
wip/mchrome-1084
wip/mailghost2-1094
wip/mailghost-1094
wip/kbpreview2-1118
wip/kbpreview-1118
wip/kanban-1092
wip/importhang-1121
wip/hiderev-1153
wip/hide4-1153
wip/hide3-1153
wip/hide2-1153
wip/hide-1153
wip/editreg-1132
job/collabloss-1197
wip/editorrail3-1113
wip/editorrail2-1113
wip/editorrail-1113
job/onboard-1141
job/hide-1153
job/perf-1124
job/perf2-1124
job/tocrail-1191
job/restyle-settings
wip/restyle-settings
job/segmented-1200
wip/notifloop-1194
job/tagperf-1186
wip/segmented-1200
job/restyle-files
job/tagdnd-1187
job/merge30
job/cards-1179
wip/cards2-1179
wip/cards-1179
wip/tocrail-1191
wip/tagdnd-1187
wip/restyle-files
wip/perf-1124
wip/merge30j
job/restyle-notes
job/wizchoices-1140
wip/wizchoices-1140
wip/restyle-1190
job/moneyfmt-1180
job/txentry-1198
wip/moneyfmt2-1180
wip/moneyfmt-1180-r
wip/moneyfmt-1180
job/pillglass-1189
job/flags-1181
wip/flags-1181
job/restyle-1190
job/restyle-mailmoney
job/restyle-search
job/settingsreg-1195
job/wizard-1140
site/website
wip/wizardrev2-1140
wip/wizardrev-1140
wip/wizard5-1140
wip/wizard4-1140
wip/wizard3-1140
wip/wizard2-1140
wip/wizard-1140
wip/pillglass-1189
wip/settingsreg-1195
job/merge29
job/fu-1171
wip/merge29j
wip/fu-1171
job/fu-1166
job/directory-1199
job/proflog-1204
job/txresearch-1188
wip/fu-1166
job/merge28
job/search-1066
wip/search-1066
wip/merge28j
job/gateslot-1182
job/bulkimport-1157
job/mailnet-1160
wip/mailnetrev-1160
wip/mailnet-1160
wip/bulkrev-1157
wip/bulkimport-1157
job/startup-1161
wip/startup-1161
job/merge27
job/linkcards-1151
wip/linkcards3-1151
wip/linkcards2-1151
wip/linkcards-1151
job/traydate-1144
wip/traydate3-1144
wip/traydate2-1144
wip/traydate-1144
job/draw-1101
wip/merge27j
job/blockpill-1152
wip/blockpill3-1152
wip/blockpill2-1152
wip/blockpill-1152
job/minihover-1149
wip/minihover2-1149
wip/minihover-1149
job/merge25
wip/merge25-r
wip/merge25b
wip/merge25
job/inspector-1129
job/tags-1110
wip/inspector3-1129
wip/inspector2-1129
wip/inspector-1129
wip/tagsrev-1110
wip/tags2-1110
wip/tags-1110
job/dates-1148
wip/datesrev-1148
wip/dates2-1148
wip/dates-1148
job/licence-1145
wip/licence2-1145
wip/licence-1145
job/selfhost-1156
job/merge23
wip/merge23
job/tagfilter-1109
wip/tagfilter2-1109
wip/tagfilter-1109
job/kbd-1134
wip/kbd2-1134
wip/kbd-1134
job/palfoot-1137
wip/selfhost-1156
wip/palfoot2-1137
wip/palfoot-1137
job/toggle-1158
wip/toggle-1158
job/kbpreview-1118
job/docratchet-1155
job/perflint-1133
job/devtests-1159
wip/docratchet-1155
wip/devtests-1159
job/segv-1136
wip/toast-1142
wip/segv-1136
job/toast-1142
job/blockreload-1147
wip/blockreload-1147
job/font-1150
wip/font-1150
job/importui-1120
job/minimonth-1149
wip/importui-1120
wip/minimonth-1149
job/depcheck-1146
wip/perflint-1133
wip/depcheck-1146
job/calcards-1115
job/blocks-1125
job/plus-1128
job/shift-1138
wip/plus2-1128
wip/plus-1128
wip/shift-1138
job/moneyfid-1130
job/editorrail-1113
wip/moneyrev-1130
wip/moneyfid-1130
job/noext-851
wip/noext-851
wip/noext3-851
wip/noext2-851
job/week-1135
wip/week-1135
job/editreg-1132
job/smoke-1122
wip/smoke-1122
job/docs-1143
job/palette2-1123
job/calhdr-1112
job/nlpchip-1127
job/mailghost-1094
job/reconnect-1131
wip/reconnect-1131
job/trayicons-1095
job/delete-1119
job/importhang-1121
job/cards-1083
job/palette-1093
job/mchrome-1084
job/e2e-a-1071
job/canvas-visual
job/previewcard-1098
job/allday-1107
wip/e2e-a2-1071
wip/e2e-a-1071
job/e2e-b-1071
job/adv7c-1105
job/kanban-1092
job/agenda-1086
job/merge-round-7c
job/morph-1104
wip/surfaces-p2
job/merge-round-9
wip/merge-round-9
job/7cfix-small
wip/7cfix-small
job/mailui-1078
job/merge-round-8
wip/merge-round-8
wip/mailui-1078
job/mailround-1038
job/applemail-accept
wip/settitle-1068
wip/mailround2-1038
wip/mailround-1038
wip/e2e-7b
job/crash-1069
wip/crash-1069
job/searchlost-1066
wip/searchlost-1066
job/7b-reconcile
job/flake-1065
wip/flake-1065
wip/merge-round-7b7
wip/merge-round-7b6
wip/merge-round-7b5
wip/merge-round-7b4
wip/7b-reconcile
job/appupdate-1059
job/nfd-1044
wip/appupdate-1059
job/e2e-7b
job/loop-1062
wip/loop-1062
job/pdfprev-1045
job/invtoggle-1053
wip/pdfprev-1045
wip/nfd-1044
wip/invtoggle-1053
job/7bfix-e2e
job/mailstress-b
wip/7bfix-e2e
wip/mailstress-b
job/7bfix-adv
wip/7bfix-adv
job/mailstress-a
job/stack-1054
wip/stack-1054
wip/mailstress-a
job/mailstress-1038
wip/mailstress-1038
job/upload500-1051
wip/upload500-1051
job/share-1034
wip/share-1034
job/syncerr-1037
job/7bfix-photos
wip/7bfix-photos
job/paste-1036
job/setside-1039
wip/setside-1039
wip/paste-1036
job/lease-1042
wip/syncerr-1037
wip/lease-1042
job/7bfix-data
job/passkeybind-1043
wip/apprevoke-1041
job/invite-1035
wip/invite-1035
job/merge-round-7b2
wip/merge-round-7b2
job/mailproxy-486
job/apprevoke-1041
job/rebuild-1033
job/pillborder-1029
wip/pillborder-1029
wip/mailproxy-486
wip/applemail-486
job/headless-998
wip/headless-998
job/groups-1028
wip/groups-1028
job/rebuildwarn-1016
wip/rebuildwarn-1016
job/startup-1011
wip/startup-1011
job/monthpill-1009
job/bgthumb-1025
job/sharetitle-1012
wip/monthpill-1009
wip/bgthumb-1025
wip/sharetitle-1012
job/canvas-cards-977
wip/canvas-cards-977
job/canvas-pencil-978
job/canvas-sketch-990
wip/canvas-sketch-990
wip/canvas-pencil-978
job/canvas-files-989
wip/canvas-files-989
job/canvas-collab-991
wip/canvas-collab-991
job/weekscroll-1018
wip/weekscroll-1018
wip/canvas-core-976
job/canvas-core-976
job/round-drag
wip/round-drag
job/round-settings
job/browserfix
wip/oapi-974
job/oapi-974
job/hist2-integrate
job/mailhtml-726
wip/mailhtml-726
wip/hist2-integrate
job/moneyfu-984
job/drag-1015
wip/drag-1015
job/rename-1017
wip/rename-1017
job/hist2-api
wip/hist2-api
job/oneacct-1014
wip/oneacct-1014
wip/moneyfu-984
job/hist2-bench
job/hist2-restore
wip/hist2-bench
job/hist2-write
job/hotfix-724
wip/hotfix-724
wip/hist2-write
wip/hist2-restore
job/hist2-store
job/hist2-ui
wip/hist2-ui
wip/hist2-store
job/searchstarve-965
job/shutdown-963
wip/shutdown-963
wip/pubedit-981
job/pubedit-981
job/analytics-973
wip/searchstarve-965
job/authflash-850
job/weeklane-969
job/pvtitle-1004
job/hist-975
wip/authflash-850
job/voicepill-617
wip/pvtitle-1004
job/headring-1003
wip/weeklane-969
wip/voicepill-617
wip/headring-1003
wip/analytics-973
job/agentscope-980
wip/thumbsandbox-988
job/thumbsandbox-988
wip/hist-975
job/links-856
wip/links-856
job/davetag-966
wip/davetag-966
job/filesstorm-1000
job/hoverpad-725
wip/filesstorm-1000
job/ffmpegblas-993
job/merge-round-7a
wip/hoverpad-725
wip/ffmpegblas-993
job/nowdot-1002
wip/verify-7a
job/noteid-857
wip/nowdot-1002
wip/noteid-857
wip/merge-round-7a
wip/agentscope-980
job/imapedge
job/a11yfix2
wip/imapedge-941
wip/imapedge
wip/a11yfix2
job/notetask-986
job/logheading
wip/logheading-998
job/textthumb-652
job/photolive-987
wip/photolive-987
job/davactive-983
job/savefix-985
job/tabicons-607
wip/davactive-983
wip/tabicons-607
wip/notetask-986
wip/savefix-985
job/dirid-627
job/buildspeed-1007
wip/dirid-627
job/agenda-decks
job/perfguards-impl
job/undo-a11y
wip/undo-a11y
job/mailperf
job/wal-824
wip/settings-50
job/settings-50
job/notesfilter-606
wip/notesfilter-606
job/surfaces-p2
wip/wal-824
job/maillayouts
wip/mailperf
wip/maillayouts
job/taskmeta-659
job/money-ident
wip/money-ident
wip/taskmeta-659
job/errstates
wip/perfguards-impl
job/headings-881
wip/headings-881
wip/errstates
job/voice-619
job/gaps-827
job/notesperf
wip/notesperf
wip/voice-619
job/hddsql-549
job/perf-stream-668
wip/perf-stream-668
wip/deeplinks-fix
job/deeplinks-fix
job/authfix
job/docsfix-rust
wip/docsfix-rust
job/webperf
job/docsfix-web
job/datafix2
job/webdav-lock-476
job/copyfix
wip/copyfix
wip/webperf
job/focus-658
wip/protofix
job/mediafix
job/protofix
wip/mediafix
job/agentfix
job/hhmm-724
wip/agentfix
job/undo-722
job/reuse
wip/webdav-lock-476
wip/reuse
job/scopefix
job/datafix
wip/hhmm-724
wip/undo-722
job/surfaces-p1
wip/hddsql-549
job/voicememos-618
wip/datafix2
wip/surfaces-p1
job/fix-940
wip/fix-940
job/blaze-surfaces
wip/datafix
wip/blaze-surfaces
job/taskday-655
job/linknav-639
wip/linknav-639
wip/gaps-827
job/isolation-707
job/audiophotos-720
wip/audiophotos-720
job/advfind-664
wip/voicememos-618
wip/taskday-655
wip/isolation-707
wip/advfind-664
wip/scopefix
wip/focus-658
job/testgaps
wip/testgaps
job/overscroll-718
wip/authfix
job/deps
wip/overscroll-718
job/rev2-agentfix
job/rev2-money-ident
job/rev2-mailperf
wip/deps
job/hardening-728
wip/hardening-728
job/searchgen-832
wip/searchgen-832
job/photopw-849
job/mailsql-825
wip/photopw-849
job/sharefix
wip/sharefix
job/rev2-mailhtml-726
job/rev2-perfguards
job/copyval-723
job/lightglass-r2
wip/lightglass-r2
wip/docsfix-web
job/copy-audit
job/macinterop-staging-r2
job/design-sync
job/rev2-taskmeta-659
job/rev2-webperf
job/docs-audit
job/rev2-advfind-664
job/rev2-mailproxy-486
job/states-audit
job/rev2-datafix
job/design-drift
job/test-gaps
job/rev2-voicememos-618
job/rev2-mediafix
job/rev2-deps
job/rev2-datafix2
job/licence-audit
job/issue-hygiene
job/rev2-protofix
job/rev2-voice-619
job/rev2-isolation-707
job/rev2-surfaces-p1
job/deeplink-audit2
job/rev2-audiophotos-720
wip/test-gaps
job/rev2-overscroll-718
job/rev2-undo-722
wip/states-audit
job/rev2-dropmd-719
job/rev2-linknav-639
job/merge-7b-plan
wip/merge-7b-plan
job/rev2-taskday-655
wip/mailsql-825
job/rev2-webdav-lock-476
job/rev2-browserfix
wip/design-drift
job/rev2-hddsql-549
wip/deeplink-audit2
job/rev2-scopefix
job/rev2-authfix
job/rev2-hardening-728
job/rev2-wal-824
job/rev2-sharefix
job/calsidebar-638
job/chrome-audit
job/ioperf
wip/ioperf
wip/chrome-audit
wip/calsidebar-638
job/dropmd-719
wip/dropmd-719
job/ocr-build
wip/ocr-build
job/blaze-settings
wip/copyval-723
job/toastring-721
wip/toastring-721
job/deployfix-732
wip/deployfix-732
wip/blaze-settings
job/money-import-recheck
job/rev-a11y
job/perf-arch-db
job/rev-7b-data
wip/textthumb-652
wip/perf-arch-db
job/sec-protocols
job/sidehdr-660
job/rev-7b-security
job/research-surfaces
job/rev-design-gaps
job/rev-mcp-api
wip/sidehdr-660
job/perf-arch-memory
wip/sec-protocols
job/perf-arch-bundle
job/snapedge-714
wip/rev-mcp-api
job/sec-supplychain
wip/research-surfaces
job/perf-arch-sync
job/rev-consistency
job/perf-arch-server
wip/perf-arch-server
wip/perf-arch-memory
job/perf-arch-io
job/perf-arch-client
job/sec-fs
job/sec-mcp-scopes
job/sec-sharing
job/perf-guards
job/sec-browser
job/sec-admin-deploy
job/sec-auth
wip/snapedge-714
job/bgpicker-717
wip/perf-arch-bundle
wip/money-import-recheck
job/advsetup-654
wip/bgpicker-717
wip/advsetup-654
job/burst-709
job/kbdcaps-710
job/app-pw-chooser
wip/burst-709
wip/app-pw-chooser
job/imaptest-625
wip/kbdcaps-710
job/fix-499
wip/fix-499
job/perf-mut-667
job/calimg-589
job/perf-snap-666
wip/calimg-589
wip/perf-snap-666
wip/perf-mut-667
job/perf-cache-665
wip/perf-cache-665
job/voicefiles-620
wip/voicefiles-620
job/admin-burst-705
wip/admin-burst-705
job/voicememos-review
wip/voicememos-review
wip/ryw-653
job/ryw-653
job/writeonopen-661
job/instant-663
wip/writeonopen-661
job/money-import-review
wip/money-import-review
wip/importjs-610
review/integrations-407-round6
wip/integrations-review
job/dragghost-612
wip/dragghost-612
job/integrations
wip/integrations
job/decider-656
job/merge-round-6
job/perf-rerun
wip/merge-round-6
job/integrations-review-round5
job/selalign-576
wip/selalign-576
job/mcp-events-491
job/files-631
job/cal-e2e-569
wip/cal-e2e-569
job/reload-423
wip/reload-423
wip/mcp-events-491
wip/files-631
job/notesbridge-644
wip/notesbridge-644
job/editor-series
job/calcard-series
wip/calcard-series
job/mcp-events-review-491
wip/mcp-events-review
wip/editor-series
job/quirks-546
job/integrations-recheck
job/tocrail-636
wip/tocrail-636
wip/quirks-546
wip/reminders-643
job/reminders-643
wip/davscale-573
job/davscale-573
job/integrations-review
wip/ocr-eval-584
job/ocr-eval-584
job/esc-537
wip/esc-537
job/toastname-586
wip/toastname-586
job/submenu-579
wip/submenu-579
job/tasks-mode
wip/tasks-mode
job/agentdocs-630
job/dupwrite-634
wip/agentdocs-630
wip/dupwrite-634
job/lightglass-588
wip/lightglass-588
job/tabswitch-549
job/ghosttask-623
wip/ghosttask-623
job/toaststack-616
job/weekstate-609
job/mailsync-613
wip/mailsync-613
wip/weekstate-609
job/maildup-626
wip/tabswitch-549
wip/maildup-626
wip/toaststack-616
job/motion-611
wip/motion-611
job/tlstest-601
wip/tlstest-601
job/perf-495
job/floating-sheet
wip/floating-sheet
job/remdup-585
wip/remdup-585
job/fix-502
wip/fix-502
job/attachplay-622
job/perf-batch
wip/perf-batch-563
wip/perf-495
hotfix/mail-sync-diag
job/mail-m3
wip/mail-m3
job/attach-poof-603
job/calhover-608
job/editorbar-604
job/mentions-605
job/merge-round-4
job/allday-514
wip/merge-round-4
wip/allday-514
job/merge-round-4a
wip/merge-round-4a
job/sharestack-580
job/fix-501
wip/sharestack-580
wip/fix-501
job/perf-batch-563
job/apw-cache-review
wip/apw-cache-review
job/probe-520
wip/probe-520
job/mac-393
wip/mac-393
job/header-571
job/flake-513
wip/flake-513
job/docs-thumb-547
wip/header-571
job/webcal-572
wip/webcal-572
wip/shortcuts-542
job/shortcuts-542
wip/docs-thumb-547
job/caldav-stress
wip/caldav-stress
wip/sweep-478
job/apw-cache-512
wip/apw-cache-512
job/money-empty-540
wip/restart-505
wip/money-empty-540
wip/fix-510
job/restart-505
job/fix-503
job/perf-496
wip/perf-496
job/fix-498
wip/fix-498
job/info-inspector-465
wip/info-inspector-465
job/fix-510
job/fix-507
wip/fix-507
wip/fix-503
job/fix-493
job/money-kinds
wip/money-kinds
job/hygiene-548
job/merge-round-3
wip/fix-493
job/drag-snap-536
wip/merge-round-3
wip/merge-round-0930
wip/drag-snap-536
job/align-538
wip/align-538
job/bg-flash
wip/bg-flash
job/money-import
job/search-count-544
wip/search-count-544
wip/money-import
job/settings-key-541
wip/settings-key-541
job/toast-539
job/preview-421
wip/preview-421
wip/toast-539
job/tasks-500-531
job/title-plain-526
wip/title-plain-526
wip/tasks-500-531
job/notes-bridge
wip/parity-484
job/parity-484
job/files-slow
job/crash-525
wip/notes-bridge
wip/files-slow
wip/crash-525
job/kbd-motion-527
wip/bg-422
job/analytics-504
wip/analytics-504
wip/kbd-motion-527
job/upload-pill-523
wip/upload-pill-523
wip/tray-order
job/tray-order
wip/overflow-mid
wip/merge-round-2
job/perf-494
wip/perf-494
wip/mcp-fast-492
wip/motion-477
wip/asr-ab-489
wip/theme-variants-506
wip/overflow-511
wip/week-header-508
wip/attach-427
job/dav-delete-471
job/iso-435
wip/iso-435
wip/files-sel-keys
wip/dav-delete-471
job/align-253
job/siwc-490
wip/siwc-490
job/money-kinds-review
wip/align-253
wip/money-kinds-review
job/small-bugs-3
wip/overlay-title-487
wip/multiget-500
wip/hidden-420
wip/webcal-ui
wip/webcal-431
job/perf-367
job/location
wip/small-bugs-3
wip/location
wip/perf-367
wip/admin-deny-483
job/tag-unicode-473
wip/tag-unicode-473
job/blur-436
wip/photos-470
wip/blur-436
wip/small-bugs-4
wip/hunt-20260930
wip/settings-hdr-482
wip/chips-416
job/dedup-375
wip/dedup-375
job/doc-stack
wip/doc-stack
job/tokens-literals
wip/tokens-literals
job/jobs-leftovers
wip/send-fast
wip/paste-467
wip/money-numbers
job/money-plugin
wip/money-plugin
job/break-dav
wip/merge-batch
wip/crossday-469
wip/mac-verify
wip/mail-m2
wip/break-dav
wip/money-review2
job/money-md
job/modes-424
wip/money-md
wip/jobs-leftovers
job/agenda-413
wip/agenda-413
wip/modes-424
job/recog-417
wip/recog-417
wip/bounce-425
wip/ab-384-luna
job/webdav-perf
wip/webdav-perf
job/toast-ring
wip/toast-ring
job/money-review
wip/money-review
wip/micro-motion
wip/settings-card
wip/minical
job/notes-imap-428
job/least-priv
wip/ui-small-2
wip/flaky-426
wip/drag-end-418
job/jank
wip/jank
wip/least-priv
wip/docs-site
job/agenda
job/sec-batch
wip/sec-batch
wip/per-user-index
job/area-calendars
wip/area-calendars
job/parity
wip/parity
job/documents-research
wip/documents-research
job/test-infra
job/reminders-sync
wip/small-bugs-2
wip/reminders-sync
wip/gestures
job/google-oauth
wip/tags-merge
wip/tags
job/e2e-theme
wip/e2e-theme
job/icon-align
wip/test-infra
wip/select-align
wip/editor-385
job/voice
wip/webdav
job/webdav
job/app-pw-ui
job/editor-integrity
wip/editor-integrity
wip/voice
wip/quota
wip/cal-followups
wip/icon-align
job/composer-scale
wip/composer-scale
job/jobs-page
wip/jobs-page
job/hig-type
wip/hig-type
wip/app-pw-ui
job/motion-spring
job/mcp
wip/motion-spring
wip/mcp
job/small-bugs
wip/push-hosts
job/profile-sign
wip/touch-369
wip/profile-sign
job/mobile-focus
wip/mobile-focus
wip/ui-polish-354
wip/small-bugs
wip/dup-task
job/toast-polish
job/app-pw-scopes
wip/toast-polish
wip/app-pw-scopes
wip/cli-agent
wip/selection-pills
job/preview-attach
wip/preview-attach
job/dav-proppatch
wip/dav-proppatch
wip/cal-switcher
job/atomic-race
wip/atomic-race
job/photos-shared
wip/photos-shared
wip/cal-grid
wip/note-rewrite
wip/search-rebuild
job/mail-m1
job/paperless-import
wip/paperless-import
wip/mail-m1
wip/hidden-activity
wip/search-d
wip/pricing-research
wip/cursors
wip/auto-scheme
job/single-pills
wip/single-pills
wip/xuser-matrix
wip/money-format
wip/app-pw-setup
wip/purge-dos
wip/vault-health
wip/caldav-apple
wip/xuser-audit
wip/e2e-green
wip/tabbar
wip/adv-harness
wip/maple-mono
job/search-fix
wip/search-fix
wip/search-perf-c
job/adv-harness
wip/sidebar-headers
job/glass
wip/temp-index
job/polish
wip/polish
wip/file-protocols
wip/money-research
wip/glass
wip/voice-models
wip/collab-redo
job/voice-research
wip/hunt-20260928
wip/notes-actions-research
wip/search-pad
wip/search-perf
wip/search-sticky
wip/editor-undo
wip/chrome-rules
wip/motion
wip/appearance-research
wip/appearance
wip/audit-bugs
wip/cal-glass
wip/block-actions
wip/authz-order
wip/event-stripes
wip/chrome-sidebar
wip/auth-flaky
wip/robust-2
wip/gate-fix
wip/menu-blur
wip/import-calternaljs
wip/tray-fix
job/import-calternaljs
wip/index-order
wip/audit-fixes
wip/search-chevrons
research/mail
wip/phone-chrome
wip/dedup-break
wip/csp
wip/ui-audit
wip/select-toast
wip/perf
wip/flat-layout
wip/fonts
wip/event-tint
wip/sync-converge
wip/data-split
wip/glass-audit
wip/robustness
wip/sync-chaos
wip/search-thumbs
wip/fuzz
wip/menu-icons
wip/search-pill
wip/sync-changing
wip/heading-links
wip/date-formats
wip/a11y
wip/break-editor
wip/e2e-fix
wip/settings-sections
wip/sync-root-guard
wip/search-palette
wip/share-edit
job/toasts
wip/toasts
wip/cont-analytics
wip/authz-review
wip/popovers
wip/overlay-glass
wip/change-feed
wip/editor-modes
wip/composer-align
wip/cont-agenda
wip/agenda-merge
job/agent-conventions
wip/agent-conventions
wip/backend-misc
job/route-audit
wip/route-audit
wip/ui-batch
wip/heif-hardening
wip/grid-resize
wip/ask-page
wip/webmcp
job/deeplink-audit
wip/deeplinks
wip/shortcuts
wip/cont-tz-days
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#423
No description provided.