pdf task-h

docs/implementation/task-h51-pdf-integrity-audit.md

@@ -0,0 +1,40 @@
+# Task H.5.1: PDF Integrity Audit & Payload Parity
+
+## Files Added
+
+- `scripts/audit-template-version-integrity.ts`
+- `scripts/audit-placeholder-integrity.ts`
+- `scripts/audit-payload-parity.ts`
+- `scripts/audit-approved-snapshot-parity.ts`
+- `scripts/generate-pdf-integrity-report.ts`
+- `docs/business/pdf-placeholder-registry.md`
+- `docs/implementation/task-h51-pdf-integrity-audit.md`
+
+## Files Modified
+
+- `package.json`
+- `scripts/generate-pdf-audit-report.ts`
+- `docs/implementation/pdf-parity-checklist.md`
+- `docs/business/pdf-mapping-registry.md`
+- `docs/implementation/technical-debt.md`
+- `scripts/pdf-audit-utils.ts`
+
+## Integrity Coverage
+
+- template-version integrity checks active template uniqueness, active version uniqueness, orphan mappings, and approved template-version references
+- placeholder integrity checks duplicate names, typo-like names, unmapped placeholders, dead mappings, and reserved dynamic topic names
+- payload parity computes SHA256 hashes for preview, generation, and computed snapshot payloads
+- approved snapshot parity compares stored snapshot payloads against computed snapshot payloads when they exist
+- integrity summary writes machine-readable artifacts into `artifacts/pdf-audit/`
+
+## Verification Result
+
+- `npx tsc --noEmit` passed
+- `npm run audit:pdf` runs the full H.5 + H.5.1 stack
+- current integrity result is expected to be `WARNING` when the audit fixture has not yet generated a persisted approved snapshot/artifact
+
+## Remaining Risks
+
+- stored approved snapshot parity still depends on generating a real approved PDF artifact for `QT-H5-AUDIT`
+- template field `line` is still treated as a tolerated designer-owned oddity rather than a normalized mapping field
+- the audit stack validates payload integrity and runtime parity, not screenshot-level pixel parity