Marc-André Bombeck 120323d995 test(02-12.1): prove Vary on the serving path, not only the contents ...

Removing the Vary block left the disk-layer case green: it asserted what
is IN the cache, and the claim is what the cache will SERVE. On the
external-switch path nothing wipes those entries — the app never
initiated the switch — so Vary is the only thing between a cached
delegated response and the next request under another context.

- assert cache.match() hits under the stored context and misses under
  the new one; it fails when the Vary is removed
- correct the acceptance map and the client docblock to claim exactly
  what executes: no zero-entry count, no offline leg

2026-08-06 23:04:29 +02:00

..

__tests__

test(02-12.1): prove the record-session fence end to end

2026-08-06 19:33:15 +02:00

api-fetch.ts

feat(02-12.1): carry and verify the record context from the browser

2026-08-06 19:10:02 +02:00

localized-error.ts

release: v1.32.0 — hardening and scalability (#580)

2026-07-22 04:14:15 +02:00

optimistic-token.ts

feat(dashboard): configure Today highlights

2026-07-28 13:22:08 +02:00

read-error.ts

chore(release): v1.4.25

2026-05-14 23:49:32 +02:00

record-fence.ts

test(02-12.1): prove Vary on the serving path, not only the contents

2026-08-06 23:04:29 +02:00