docs: viewer plan — Task 0c, Mantine 9.5.2 and the LLM docs path

[m4ttheweric]

Adds Task 0c to the chat viewer plan: upgrade Mantine 9.4.1 → 9.5.2 and, more to the point, give the agents building this UI a way to look Mantine up instead of recalling it.

The version is the small half. 9.5.2 is a minor already inside both repos' ^9.4.1 range, scoped to the eight @mantine/* packages (a bare bun update would drag vite, storybook, eslint and React along under one task's name) and gated by each repo's normal suite. No visual-regression apparatus for a minor.

The docs path is the point. Three artifacts, each covering a different failure:

• .mcp.json pinning @mantine/mcp-server@9.5.2 — it ships in lockstep with Mantine, so pinning it to the installed version is what makes the answers true rather than merely recent. Four tools: list_items, get_item_doc, get_item_props, search_docs.
• docs/mantine-llms.txt vendored (42 KB index) for sessions without MCP. llms-full.txt stays out at 4.1 MB — Mantine's guide still advertises ~1.8 MB.
• The instruction in AGENTS.md, which is what actually changes behaviour. Tooling nobody is told to use gets used by nobody.

Ordering: mantine-kit first, because create-cli scaffolds from git ls-files and copies the template's own package.json/bun.lock/AGENTS.md into every generated app — so whatever the template holds is what chat inherits at Task 1. Console follows and rebases onto Task 0b, which touches the same package.json.

Verification: two review rounds. The first caught that the new files would never reach a scaffold (untracked, and git commit -am doesn't add them), that the kit's bun run test is watch mode and would hang, and that the MCP check can't be run by the agent that writes the config. The second caught that the probe's version check was a comment rather than an assertion, that CLAUDE.md is a 15-byte pointer in both repos so the block belongs in AGENTS.md alone, and that the probe aborts on re-run.

Known and deliberately not fixed here: Task 0b's zero pixel drift gate is vacuous — console's parity capture renders static design mocks and never loads the app, so it cannot fail. That matters for 0b's extraction, not for this bump; flagged for Matt.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the implementation plan to include upgrading Mantine to version 9.5.2.
  • Added guidance for using offline Mantine documentation when working with component APIs.
  • Expanded prerequisite and scaffold verification steps, including dependency and documentation artifact checks.
  • Added packaging, formatting, validation, and coordination requirements.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 81f9e6e2-d66b-45d9-9204-2e4b6baefe96

📥 Commits

Reviewing files that changed from the base of the PR and between 8bbc299 and 4b2d78f.

📒 Files selected for processing (1)

• docs/superpowers/plans/2026-08-23-rt-chat-viewer.md

---

📝 Walkthrough

Walkthrough

The plan adds a Mantine 9.5.2 upgrade task, version-pinned MCP configuration, offline documentation, agent instructions, scoped validation, and scaffold propagation checks.

Changes

Mantine plan updates

Layer / File(s)	Summary
Repository prerequisites docs/superpowers/plans/2026-08-23-rt-chat-viewer.md	Task 0 now includes Mantine 9.5.2 upgrades, MCP configuration, offline documentation, API lookup instructions, package whitelists, validation gates, and coordination requirements.
Scaffold verification docs/superpowers/plans/2026-08-23-rt-chat-viewer.md	Task 1 now verifies Mantine ^9.5.2, .mcp.json, offline documentation, and the AGENTS.md lookup instruction.

Estimated code review effort: 1 (Trivial) | ~5 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/mantine-upgrade-task

---

_{Comment @coderabbitai help to get the list of available commands.}