Follow-up to #33 / PR #34. Reviewer items deferred from the documentation-improvements PR because they're own-scope:
1. Memoize feature isn't visible in any demo
`forge`'s `memoize` config knob is a real, useful feature; nothing on the main demo or the kit pages exercises it visually. The config-options table in the README mentions it, but a reader can't see what memoization buys until they go read `llms.txt` or instrument it themselves.
Possible surfaces:
- A small "call this 1000 times; cold vs cached" benchmark widget on the home page.
- A memoize toggle on the existing ArPeeGee shop sliders with a visible call-count + cache-hit-rate readout.
- A dedicated mini-demo section on the home page (alongside CoreApi and ArPeeGee).
2. Mutation-survivor + per-file mutation breakdown could live in TESTING.md
`llms.txt` currently absorbs the per-file mutation score breakdown and the survivor-classification policy. `review-the-nit` flagged this as contributor-process content that belongs in a `TESTING.md` (or absorbed into `CONTRIBUTING.md` / `EXTENDING.md`) rather than the agent-orientation doc. Optional reorganization; doesn't affect the public API.
Follow-up to #33 / PR #34. Reviewer items deferred from the documentation-improvements PR because they're own-scope:
1. Memoize feature isn't visible in any demo
`forge`'s `memoize` config knob is a real, useful feature; nothing on the main demo or the kit pages exercises it visually. The config-options table in the README mentions it, but a reader can't see what memoization buys until they go read `llms.txt` or instrument it themselves.
Possible surfaces:
2. Mutation-survivor + per-file mutation breakdown could live in TESTING.md
`llms.txt` currently absorbs the per-file mutation score breakdown and the survivor-classification policy. `review-the-nit` flagged this as contributor-process content that belongs in a `TESTING.md` (or absorbed into `CONTRIBUTING.md` / `EXTENDING.md`) rather than the agent-orientation doc. Optional reorganization; doesn't affect the public API.