Rewrite and move every published page's words to MDX

[RaviTejaKNTS]

Step 2d of dev-space/charts-and-content-in-code-plan.md: every published tool, directory, directory child page, and catalog now renders its words from content/*.mdx beside its route, rewritten in the current writing style. Titles, search text, and cards stay in the database and go out through the publisher after merge.

Pages

Family	Pages	Change
Tools	71	51 rewritten, 20 moved with their words unchanged (all KDP tools, KENP, print size, and five SaaS calculators)
Directories	14	Rewritten. /cli-apps, /self-host-apps, and /platform-fees words moved out of TSX and the database
Keyboard shortcut apps	218	Each has its own two-sentence intro
Platform fee categories	8	Own intro and a short guide with a worked example from the records
Catalogs	8	Rewritten. The domain catalog article moved from TSX to MDX

Out of scope: courses, site pages, unpublished pages (ad networks), and pagination.

Code

• Catalogs and fee categories map content by slug in content/index.ts. A published slug with no entry is an error.
• The keyboard shortcuts template, fee shell, catalog route, and shared hardware page take MDX instead of database Markdown.
• check-mdx.mjs checks MDX at any depth under content/.
• Record syncs (keyboard shortcuts, ad networks, hardware and Zigbee previews) only insert missing page rows and never overwrite titles, words, or search fields. The undocumented hardware --refresh is retired.

Facts corrected on live pages

• Availability pages named result labels the tools don't show.
• The transfer page called the 60-day rule a hard lock; registrars may refuse, not must.
• Drive reliability named a toggle that doesn't exist.
• The DNS lookup page said its DNSSEC line means validation; the tool never asks for that flag.
• The TLD directory said no tool can look up an ending without RDAP.

Checks

• npm run quality passes. check-mdx.mjs passes on all MDX files.
• Sol reviewed the code: ready, two P3 findings fixed in bb4769fa and confirmed.
• The 20 move-only tools match production text and search tags exactly.
• Still to do before merge: browser checks at desktop and mobile in both themes, and the content audit fixes.

After merge

Production publisher batches for titles, search text, and cards: tools and catalogs through stack127:tools:publish, directories and child pages through stack127:directories:publish with touch_reason where content changed. They run only after approval.

🤖 Generated with Claude Code