Fix MBTI canonical result section registry

[fermatmind]

What changed

• Preserve canonical traits.at_difference and faq result projection sections.
• Add a contract test covering canonical ordering plus body and payload retention.

Why

Independent W1 MBTI result W9 QA found that these backend-authoritative section keys were silently filtered by the frontend projection registry. This isolated baseline repair removes that pre-existing renderer blocker before the result asset QA PR.

Validation

• pnpm typecheck
• pnpm lint
• pnpm test:contract (793 files, 4717 tests)
• NEXT_PUBLIC_API_URL=https://api.fermatmind.com NEXT_PUBLIC_SITE_URL=https://fermatmind.com pnpm build
• git diff --check
• changed-file scope validation

Deferred items

• W1 result asset QA artifacts and train metadata remain in EN-PARITY-W1-MBTI-RESULT-W9-QA-01.
• No CMS write, import, publication, activation, SEO runtime, sitemap, llms, indexability, staging wait, or production deployment is included.

Repository rule impact

No content authority or publishing ownership changes. The frontend continues to consume backend-authoritative result projection keys.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.