feat: rebuild the site around what FixMap actually does

[aryamthecodebreaker]

The site explained FixMap in abstractions and never showed a command or its output. --explain and verify were absent entirely, and the film note claimed v0.7.1 while v0.7.3 was published.

The browser demo was the weakest part: seven fabricated files whose textSample values were bags of keywords, arranged so every preset produced a clean win. A demo that cannot fail is not evidence of anything.

The demo now runs the real thing

buildReportFromRepo is extracted out of plan.ts, so report assembly no longer sits behind the filesystem scanner. browser.ts exports it alongside explainFile and verifyPlan. The page imports the same code the CLI runs and points it at a sample repository written like a real one — resolving imports, committed build output under dist/, an examples/ directory, a lockfile, a type declaration.

Three tabs walk the real workflow:

Tab	Shows
Plan	Ranked files with score, confidence and reasons; the test route; risk; diagnostics
Ask why	explainFile against any of the 16 files — all four statuses reachable
Verify	verifyPlan against four pretend diffs, including the one that exits non-zero

Picking dist/auth/reset-password.js in the second tab returns "Excluded: generated output for src/auth/reset-password.ts, which the next build overwrites. That file was ranked instead." — produced by the shipped code, not written into the page.

The default preset is the case FixMap handles worst

"Password reset emails never arrive" is a symptom with no symbol, and it ranks the email template above the file that sends the mail. The next preset adds sendMail and the ranking sharpens, with the reason visible on the row.

This is the documented failure mode. Showing it, next to its remedy, beats letting a user discover it alone on their own repository.

Also

• Anatomy section — one command and the four outputs it produces
• A card per command — plan, --explain, verify, mcp, plus the Action
• Six concrete reasons to use it, replacing three abstractions
• Version read from packages/cli/package.json so it cannot go stale again

Two accuracy fixes

The hero terminal listed output its own command does not produce — the shown ranking came from a different task string. It now prints the exact ranking, confidence labels included, that its command returns.

Mobile had genuine horizontal overflow: grid children default to min-width: auto, so wide <pre> blocks stretched the document to 674px inside a 375px viewport. They now scroll inside their own box.

Verification

• npm run ci green: 219 tests, all three benchmark suites byte-identical — the core refactor changed no behavior
• Exercised in a browser: every explain status, every verify scenario, the empty-report path, no console errors, no overflow at 375px or 1440px

🤖 Generated with Claude Code