From 58922e55c3e630f6e52d95c649006845c6a8b166 Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com> Date: Fri, 31 Jul 2026 14:53:07 -0400 Subject: [PATCH] Record the caching decision: content-hash filenames, then immutable Option A chosen. Noting explicitly that Option B should not ship as an interim step -- the two are not stackable, and a bounded max-age shipped now is the thing that never gets revisited. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01CMr9Yt8SYmZcfgrg3CV2G1 --- todo/TODO_2026-07-31_static-asset-caching.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/todo/TODO_2026-07-31_static-asset-caching.md b/todo/TODO_2026-07-31_static-asset-caching.md index 5db27d50..74d1d611 100644 --- a/todo/TODO_2026-07-31_static-asset-caching.md +++ b/todo/TODO_2026-07-31_static-asset-caching.md @@ -51,7 +51,10 @@ deploy verification; it does not rename assets or rewrite references. a deploy is picked up within ten minutes, and nothing can pin a user to a stale bundle. Choose this if hashing is not happening soon. -Decide A vs B before touching `vercel.json`; they are not stackable. +**DECIDED 2026-07-31: Option A.** Content-hash the filenames, then apply +`immutable`. Do not ship Option B as an interim step — the two are not +stackable, and a bounded `max-age` shipped now becomes the thing nobody +revisits. ## Also worth doing