# R016 Plan Review — Step 7: Replace duplicate prose

Decision: REQUEST CHANGES

I read `PROMPT.md`, the current `STATUS.md`, and spot-checked the files Step 7 will touch (`README.md`, `web/layouts/index.html`, and `web/README.md`). The Step 7 plan has the right core actions, but it should be tightened before implementation so this step does not leave another stale catalog statement on the landing page.

## Blocking plan adjustment

1. **Include the remaining hardcoded landing-page catalog count/prose, not just chips.**  
   `web/layouts/index.html` already renders featured chips through `{{ partial "tool-chips.html" . }}` from Step 4, so there may be no `<span class="tool">` chips left to remove. However, the same landing page still has a hand-maintained catalog claim at `web/layouts/index.html:54`: `~25 MCP tools`, while the generated `web/data/tools.json` currently contains 40 entries. If Step 7 only checks for hardcoded chip spans, it can leave a known stale catalog count in place, which conflicts with TP-051's source-of-truth goal.

   Please revise the Step 7 plan to explicitly handle this line. Preferred options:
   - render the count from `len site.Data.tools` if the copy needs a number; or
   - remove the numeric claim and point users to the generated tool reference.

## Implementation notes once revised

- In `README.md`, replace only the hand-maintained bullet list under `## MCP tool catalog` / `Currently implemented tools:` with a short paragraph and the canonical link to `https://icuvisor.app/reference/tools/`. Keep the following `## MCP resources`, `## MCP prompts`, and later toolset/delete-mode explanatory sections intact.
- In `web/layouts/index.html`, keep using the shared `tool-chips.html` partial and do not reintroduce a curated HTML chip list. If a generated count is used, make Hugo fail clearly when `web/data/tools.json` is missing, consistent with the existing partial behavior.
- In `web/README.md`, add a concise note that `web/data/tools.json` is generated by `make docs-tools` / `cmd/gendocs` and should not be hand-edited.
- No additional `CHANGELOG.md` change appears necessary for Step 7 because Step 6 already recorded the generated-catalog/docs-source-of-truth change, unless the implementation makes a separate user-visible documentation change worth calling out.
