cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(cv): align preview pagination with native PDF

Browse Source
This commit is contained in:
cesnimda
2026-10-07 08:46:43 +02:00
parent 046dc304aa
commit efc9e7bdd4
182 changed files with 16092 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-5/READINESS_GATES.md
+4 -2
View File
@@ -59,9 +59,11 @@ This is separate integrity work, not authorization to start B07 or implement a c
## G-CV-RENDER — geometry, templates and real output
Successor: [P5-09 native corpus and measured results](p5-09-readiness/README.md#measured-corpus-and-results). Three bounded CSS/export/margin corrections restore the intended template/physical-page rules. **10/16 fixtures pass implemented measurements; six long-document fixtures fail materially. G-CV-RENDER remains open; P5-09 is NO-GO.** Native acquisition passing is not fidelity passing. A separate pagination repair and the remaining font/photo/wrapping qualifications are required; no renderer replacement is implicitly authorised.
Current successor: [pagination-fidelity repair](p5-09-pagination-readiness/README.md). Native preview fragmentation reuses renderer print rules/geometry; all 16 original fixtures pass the unchanged numerical oracle. PDF output and revision semantics are unchanged. The successor records the final P5-09 decision, full regression baseline and remaining deployment-font/photo/wrapped-line qualifications. Historical failures below are preserved, not waived.
The renderer is shared, but preview is not a byte-for-byte PDF rendering: `CvBuilderEditor.previewDocumentHtml` injects page padding, a pagination script and per-page transforms into server HTML. `CvCustomizeTab`, normalized settings and `ThemedCvRenderer` also influence layout. P4-03 proved keyboard access, not margin accuracy or document-theme fidelity.
Original readiness checkpoint: [native corpus and measured results](p5-09-readiness/README.md#measured-corpus-and-results). Three bounded CSS/export/margin corrections restored the intended template/physical-page rules. **10/16 passed; six long-document fixtures failed materially, keeping G-CV-RENDER open and P5-09 NO-GO at that checkpoint.** The successor above supplies the bounded repair. Native acquisition alone is never fidelity passing; broader qualifications and output truth remain explicit.
The renderer is shared, but preview is not a byte-for-byte PDF rendering. The old `CvBuilderEditor.previewDocumentHtml` estimated padding/breaks and cropped server HTML; the successor's `cvPreview.ts` uses native column fragmentation with the existing print rules and measured physical geometry. `CvCustomizeTab`, normalized settings and `ThemedCvRenderer` still influence layout. P4-03 proved keyboard access; the successor supplies the distinct numerical geometry/page-membership proof.
Before P5-09–14, obtain a dedicated rendering checkpoint, with corrections separately authorized if needed: