#210: Markdown ZIP with frontmatter, imprint and manifest #269

Merged

fable-5 merged 2 commits from issue-210-zip-marking into main 2026-07-31 07:36:22 +02:00

Conversation 0 Commits 2 Files Changed 17 +539 -14

fable-5 commented 2026-07-31 07:14:10 +02:00

Collaborator

Copy Link

Implements #210 (M26): classified .md files carry YAML frontmatter + visible imprint top/bottom; manifest.json per archive (every file with level, highest level stated once; media inherits highest referencing page, fail-closed); importer strips exactly our wrapper and creates the page at least at the imported level (round-trip pinned by unit + e2e tests); foreign frontmatter and Obsidian vault modes untouched. Stacked on #268.

Implements #210 (M26): classified .md files carry YAML frontmatter + visible imprint top/bottom; manifest.json per archive (every file with level, highest level stated once; media inherits highest referencing page, fail-closed); importer strips exactly our wrapper and creates the page at least at the imported level (round-trip pinned by unit + e2e tests); foreign frontmatter and Obsidian vault modes untouched. Stacked on #268.

fable-5 added 4 commits 2026-07-31 07:14:11 +02:00

#207: print stylesheet with the classification on every printed sheet ... 809e071f14

First @media print support at all: page size/margins, navigation and
interactive chrome suppressed, break behaviour for headings, tables,
code blocks, figures and plugin blocks. The VS-NfD marking runs as
header AND footer on every sheet via a real-table PrintFrame whose
thead/tfoot browsers repeat per page — @page margin boxes are
unimplemented and position:fixed places unreliably in both engines
(verified empirically); on screen the table chain renders as plain
blocks, so nothing changes visually. Verified as PDF-from-browser in
Chromium 140 and Firefox 153 (2 markings on every page of a multi-page
document); the repeatable procedure is documented in
apps/web/e2e/README.md. Unclassified pages print without a marking.

Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

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

A classified page's PDF export carries its marking as a job option; the
renderer hands it to Gotenberg's Chromium header/footer templates, so it
repeats on every page — bold centered in the running header and next to
the existing page numbers in the footer. Unclassified pages send exactly
the pre-#208 forms (unchanged PDF, asserted by the fidelity smoke and a
lastMarking=null check). New real-Gotenberg fidelity test asserts the
marking appears twice on EVERY page of a multi-page render while the
document-level header keeps working.

Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

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

reference-vs-nfd.docx/.odt ship as derived binaries: the pinned pandoc's
default reference documents plus a header and footer with the marking —
part of the document's page setup, so it repeats on every page in Word
and LibreOffice and is not deletable body text. Source of truth is
scripts/gen-classified-reference-docs.mjs (wording from shared
classificationMarking(); maintenance documented in assets/README.md).
The converter passes reference docs to pandoc-server via in-request
files + reference-doc; the worker attaches them for marked docx/odt jobs
(job option {marking}, as in #208). Unclassified exports pass nothing
and are unchanged (pinned by fake-converter test). Fidelity suite
asserts against real pandoc 3.6 that marked outputs carry the
header/footer parts and unmarked ones do not; per-page repetition
verified via LibreOffice 25.8 headless PDF (5/5 pages, 2 markings each,
both formats). Word: quick manual look pending (sample files in the
workspace), procedure documented in assets/README.md.

Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

#210: mark the Markdown ZIP export with frontmatter, imprint and manifest ... 68497046e9

A classified page's .md carries the level in YAML frontmatter AND the
marking line at top and bottom; unclassified files are byte-identical to
before. Every pond archive (incl. the per-pond folders of the account
data export) ships a manifest.json listing each file with its level and
stating the highest level once at archive level — media inherits the
highest classification among the readable pages referencing it
(fail-closed). Round trip: the importer recognizes exactly our
frontmatter block, strips it plus the imprint lines, and creates the
page at least at the imported level (content must not escape its marking
by traveling through a ZIP) — pinned by unit and e2e round-trip tests.
Foreign frontmatter passes through unchanged; the Obsidian vault import
keeps its own frontmatter modes.

Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>

fable-5 referenced this pull request 2026-07-31 07:23:54 +02:00

#211: classification through feeds, public API, search, no-JS shell #270

fable-5 merged commit 68497046e9 into main 2026-07-31 07:36:22 +02:00

fable-5 referenced this pull request 2026-07-31 07:37:08 +02:00

#209: pandoc reference docs with classification header/footer (DOCX/ODT) #268

fable-5 referenced this pull request 2026-07-31 07:37:33 +02:00

[VS-NfD] Mark the Markdown ZIP export with frontmatter and a visible imprint #210

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

area:auth

  

area:docs

  

area:export

  

area:ops

  

area:storage

  

area:supply-chain

  

auth

Authentication, permissions, quotas

  

backend

API server (apps/api)

  

blocked

Blocked on external dependency/infrastructure

  

collab

Collaboration server (apps/collab)

  

deployment

Docker, CI/CD, hosting

  

docs

Documentation

  

effort:L

  

effort:M

  

effort:S

  

frontend

SPA (apps/web)

  

plugins

Plugin system and SDK

  

qa

Tests, fixtures, e2e

  

vs-nfd

  

vs-nfd:blocker

No Label

area:auth

area:docs

area:export

area:ops

area:storage

area:supply-chain

auth

backend

blocked

collab

deployment

docs

effort:L

effort:M

effort:S

frontend

plugins

qa

vs-nfd

vs-nfd:blocker

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stwaidele/dorfteich#269

No description provided.