visual-recaplisted

# Visual Recap `/visual-recap` creates a visual plan built **from** a diff, not toward one. It is the reverse of forward planning: instead of describing the change you are about to make, you describe the change that was just made, at a higher altitude than line-by-line review. The same plan data model serves both directions — schema, API, file, and architecture changes become the same `data-model`, `api-endpoint`, `file-tree`, and `diagram` blocks a forward plan would use, only now they summarize work that exists. A reviewer scans the shape of the change before spending attention on the literal lines. ## Local-Files Privacy Mode Exception Use local-files privacy mode when the user explicitly asks for no DB writes, no hosted Plan database writes, no Plan MCP publish, fully local files, offline/private recaps, or when `AGENT_NATIVE_PLANS_MODE=local-files` is set. This is the only exception to the hosted publish rule below. In local-files mode: - Read the diff/stat/source context from local files and shell commands only. The existing `npx @agent-native/core@latest recap collect-diff`, `scan`, and `build-prompt --local-files` helpers are safe to use because they operate on local files and do not write to the Plan database. - Fetch/read the block catalog before writing structured MDX. Use `npx @agent-native/core@latest plan blocks --out plan-blocks.md` when the Plan MCP connector is not registered; it calls the public no-auth `get-plan-blocks` route and sends no r