[VS-NfD] Put the classification into the Gotenberg PDF header/footer template #208

New Issue

fable-5 · 2026-07-30T01:43:42+02:00

fable-5 commented

2026-07-30 01:43:42 +02:00

Plan reference: 20-massnahmenplan.md -> P1-2 (output channels)
ADR: ADR 0022
Effort: S (1 AT)
Depends on: #204

Context

Server-side PDF is the export an authority is most likely to file or
forward, so it must be marked per page rather than once at the top.

Current state

apps/api/src/import-export/pdf-html.ts builds the export HTML: a
document-level <header class="pdf-header"> with pond name and title
(:76–79) plus print CSS for page size and breaks (:30–31, :69–71).
This header appears once, not per page.
Page numbers already come from Gotenberg's footer (:31), so the
per-page mechanism exists and is the place to extend.
Renderer: apps/api/src/import-export/gotenberg.renderer.ts.

Acceptance criteria

Classification is rendered in Gotenberg's header and footer template
so it appears on every page of the PDF, next to the existing page
numbers.
The document-level header keeps working; unclassified pages produce
an unchanged PDF (asserted against the existing PDF fidelity
snapshots).
Fidelity test extended per the repo's fixture-first process
(fixtures/README.md): fixture first, snapshot regenerated only with
the pinned tool version, committed together.
Documented in #228.

Out of scope

DOCX/ODT (#209) and browser print (#207).

**Plan reference:** `20-massnahmenplan.md` -> P1-2 (output channels) **ADR:** ADR 0022 **Effort:** S (1 AT) **Depends on:** #204 ## Context Server-side PDF is the export an authority is most likely to file or forward, so it must be marked per page rather than once at the top. ## Current state - `apps/api/src/import-export/pdf-html.ts` builds the export HTML: a document-level `<header class="pdf-header">` with pond name and title (`:76–79`) plus print CSS for page size and breaks (`:30–31`, `:69–71`). This header appears **once**, not per page. - Page numbers already come from Gotenberg's footer (`:31`), so the per-page mechanism exists and is the place to extend. - Renderer: `apps/api/src/import-export/gotenberg.renderer.ts`. ## Acceptance criteria - [ ] Classification is rendered in Gotenberg's header and footer template so it appears on every page of the PDF, next to the existing page numbers. - [ ] The document-level header keeps working; unclassified pages produce an unchanged PDF (asserted against the existing PDF fidelity snapshots). - [ ] Fidelity test extended per the repo's fixture-first process (`fixtures/README.md`): fixture first, snapshot regenerated only with the pinned tool version, committed together. - [ ] Documented in #228. ## Out of scope DOCX/ODT (#209) and browser print (#207).

fable-5 added this to the M26 — VS-NfD: classification metadata milestone 2026-07-30 01:43:42 +02:00

fable-5 added the

labels 2026-07-30 01:43:42 +02:00

fable-5 referenced this issue

2026-07-31 06:55:53 +02:00

#208: classification in the Gotenberg PDF header/footer #267

fable-5 referenced this issue from a commit

2026-07-31 06:55:54 +02:00

#208: VS-NfD marking in the Gotenberg per-page header and footer

fable-5 referenced this issue from a commit

2026-07-31 07:09:50 +02:00

#209: pandoc reference documents carry the VS-NfD marking for DOCX/ODT

fable-5 commented

2026-07-31 07:24:53 +02:00

Done in PR #267 (commit c2df7c0, CI runs 548+549 green, fast-forward merged on Stefan's standing merge instruction).

Evidence:

Classified PDF exports carry the marking via Gotenberg's per-page header/footer templates: bold centered running header + marking next to the existing page numbers in the footer, on EVERY page.
The marking travels as conversion-job option {marking} (set only for classified pages); the worker hands it to the renderer.
Unclassified pages send exactly the pre-#208 forms - unchanged PDF, pinned by the fidelity smoke (no marking anywhere) and a lastMarking=null unit assertion.
New real-Gotenberg fidelity test (pinned gotenberg:8): multi-page marked render shows the marking twice on every page while the document-level header keeps working - verified locally, runs in the CI fidelity gate.
Doc convention recorded on #228.

Done in PR #267 (commit c2df7c0, CI runs 548+549 green, fast-forward merged on Stefan's standing merge instruction). Evidence: - Classified PDF exports carry the marking via Gotenberg's per-page header/footer templates: bold centered running header + marking next to the existing page numbers in the footer, on EVERY page. - The marking travels as conversion-job option {marking} (set only for classified pages); the worker hands it to the renderer. - Unclassified pages send exactly the pre-#208 forms - unchanged PDF, pinned by the fidelity smoke (no marking anywhere) and a lastMarking=null unit assertion. - New real-Gotenberg fidelity test (pinned gotenberg:8): multi-page marked render shows the marking twice on every page while the document-level header keeps working - verified locally, runs in the CI fidelity gate. - Doc convention recorded on #228.

fable-5 closed this issue

2026-07-31 07:24:54 +02:00

fable-5 referenced this issue

2026-07-31 07:38:10 +02:00

[VS-NfD] Write the security documentation (architecture, data flows, network plan, ports, trust boundaries) #228

Sign in to join this conversation.