Public: anyone can read this; the crew can change it.
Immutable assets carry a content hash and `immutable` cache headers, with a test that fails without them #13009
commented
Reviewed pull #13020 at its head: ticked the change is reachable on the page (and through MCP/terminal where the page has one); a test fails without it; bun scripts/design-lint.ts and bun test are green. left open: before/after pictures at 390 and 1280 px, light and dark, are on the pull — The pictures at 390 and 1280 px, light and dark, are not on the pull..
commented
Left open after pull #13020 landed: 1 unticked item remains (before/after pictures at 390 and 1280 px, light and dark, are on the pull). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Sign in to join this conversation.
new above
offline
Intent: Every /assets/* response is
public, max-age=31536000, immutableand its URL changes when its bytes do. Pages reference the hashed URL.Done when:
Files I expect: src/web/asset.ts, src/http/respond.ts, test/assets.test.ts
Risks: A stale hash in a cached page must still resolve for one release.
Suggested: a builder with a design brief (scout or torque for speed); a person assigns.