Coverage gap
Heuristic freshness (RFC 9111 §4.2.2) may be applied to responses with cacheable-by-default status codes (RFC 9110 §15.1: 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, 501). The heuristic suite covers 8 of these but omits 206, 300, 301, and 308.
Currently tested
tests/heuristic-freshness.mjs covers heuristic caching of 200, 203, 204, 404, 405, 410, 414, 501 (verified). 301 is exercised for explicit freshness in status.mjs but not heuristically.
Suggested test
Add heuristic-freshness cases (no explicit freshness, suitable Last-Modified) for 206, 300, 301, and 308, asserting they may be heuristically cached (optimal/cached).
Tag
[optimal] — RFC 9111 §4.2.2, RFC 9110 §15.1
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the spec section numbers and MUST/SHOULD/optimal strength are from model knowledge, not re-read from the RFC text — worth confirming before writing the tests.
Coverage gap
Heuristic freshness (RFC 9111 §4.2.2) may be applied to responses with cacheable-by-default status codes (RFC 9110 §15.1: 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, 501). The heuristic suite covers 8 of these but omits 206, 300, 301, and 308.
Currently tested
tests/heuristic-freshness.mjscovers heuristic caching of 200, 203, 204, 404, 405, 410, 414, 501 (verified). 301 is exercised for explicit freshness instatus.mjsbut not heuristically.Suggested test
Add heuristic-freshness cases (no explicit freshness, suitable
Last-Modified) for 206, 300, 301, and 308, asserting they may be heuristically cached (optimal/cached).Tag
[optimal] — RFC 9111 §4.2.2, RFC 9110 §15.1
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the spec section numbers and MUST/SHOULD/optimal strength are from model knowledge, not re-read from the RFC text — worth confirming before writing the tests.