Coverage gap
status.mjs exercises explicit-freshness store/reuse (fresh + stale pairs) for a range of status codes but omits several, including cacheable-by-default and extension codes: 300, 405, 414, 451, 501.
Currently tested
status.mjs covers (explicit freshness) 200, 203, 204, 299, 301, 302, 303, 307, 308, 360, 400, 404, 410, 499, 500, 502, 503, 504, 599 (verified). Missing from the explicit-freshness path: 300, 405, 414, 451, 501.
Suggested test
Add status-<code>-fresh/-stale pairs for 300, 405, 414, 451, 501 — confirming each is storable/reusable with explicit freshness and revalidated/not reused once stale.
Tag
[optimal] (storage with explicit freshness applies regardless of default-cacheability) — RFC 9111 §3
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the cited codes/section are from model knowledge, not re-read from the RFC text — worth confirming before writing the tests.
Coverage gap
status.mjsexercises explicit-freshness store/reuse (fresh + stale pairs) for a range of status codes but omits several, including cacheable-by-default and extension codes: 300, 405, 414, 451, 501.Currently tested
status.mjscovers (explicit freshness) 200, 203, 204, 299, 301, 302, 303, 307, 308, 360, 400, 404, 410, 499, 500, 502, 503, 504, 599 (verified). Missing from the explicit-freshness path: 300, 405, 414, 451, 501.Suggested test
Add
status-<code>-fresh/-stalepairs for 300, 405, 414, 451, 501 — confirming each is storable/reusable with explicit freshness and revalidated/not reused once stale.Tag
[optimal] (storage with explicit freshness applies regardless of default-cacheability) — RFC 9111 §3
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the cited codes/section are from model knowledge, not re-read from the RFC text — worth confirming before writing the tests.