Skip to content

MBTI-PDF-RESULT-SNAPSHOT-PARITY-REALIGN-08: realign snapshot print surface#1508

Merged
fermatmind merged 1 commit into
mainfrom
codex/mbti-pdf-snapshot-parity-realign-08
Jul 1, 2026
Merged

MBTI-PDF-RESULT-SNAPSHOT-PARITY-REALIGN-08: realign snapshot print surface#1508
fermatmind merged 1 commit into
mainfrom
codex/mbti-pdf-snapshot-parity-realign-08

Conversation

@fermatmind

Copy link
Copy Markdown
Owner

What changed

  • Bumped the MBTI result-page snapshot surface contract to mbti.result_page_snapshot.v4 on the frontend.
  • Removed the MBTI PDF-only summary shell from the result-page snapshot rendering path.
  • Restored snapshot print rendering to the real rich result tree: RichResultReport -> MbtiResultShell -> MbtiDesktopCloneShell.
  • Preserved server-prefetched snapshot content/status props for desktop clone content injection and fail-closed no-placeholder readiness.
  • Strengthened smoke/contract gates so snapshot PDFs reject the core-reading summary shell and require real result-page detail content.

Why

The snapshot export had drifted into a PDF-only core-reading summary shell. The user-facing goal is a result-page snapshot PDF that uses the real result page content tree, not a shortened summary renderer.

Validation

  • ./node_modules/.bin/vitest run tests/contracts/result-gotenberg-print-route.contract.test.ts tests/contracts/result-client-view-state.contract.test.tsx tests/contracts/mbti-result-page-pdf-smoke-quality-gate.contract.test.ts tests/contracts/result-private-print-chrome.contract.test.ts
  • ./node_modules/.bin/tsc --noEmit
  • git diff --check

Intentionally deferred

  • No deployment or server configuration changes.
  • No production artifact/cache cleanup.
  • No CMS, DB, queue, search, or indexing changes.
  • No final visual pagination polish.

@fermatmind fermatmind merged commit 005a0ae into main Jul 1, 2026
6 checks passed
@fermatmind fermatmind deleted the codex/mbti-pdf-snapshot-parity-realign-08 branch July 1, 2026 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant