Last updated: March 22, 2026
This is the single source of truth for active, cross-doc follow-up work.
-
Worker-cache hardening
- Expand observability for cache hit/miss/write/prune behavior during full runs.
- Add edge-case coverage for cache key drift and stale-entry pruning.
- Verify long-run stability over repeated full-refresh runs.
-
Repeated-run benchmark baseline
- Capture before/after metrics for repeated full-refresh runs with cache enabled.
- Record duration deltas and cache-hit ratios in a reproducible benchmark note.
-
Published contract guardrails
- Keep
modules.json,modules.min.json,stats.json, andresult.mdstable while cache hardening evolves. - Treat contract-affecting changes as explicit review items in PRs.
- Keep
- Deterministic output enhancements
- Evaluate RFC 8785 canonical JSON serialization for stronger reproducibility guarantees.
- Evaluate timestamp normalization/stripping strategy where metadata timestamps reduce reproducibility value.
- Add new follow-up work here instead of creating per-document roadmap sections.
- When an item is complete, remove it here and reflect final behavior in the relevant reference docs.