)]}'
{
  "log": [
    {
      "commit": "74a84c56047f3463f9086fcffad5c62f402e047e",
      "tree": "49487eff2a2d139daf8c575068e893fec1808467",
      "parents": [
        "08f530770994cbab31406c538fa18fcd7e5e6d81"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 16 06:08:42 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 16 06:08:42 2026 +0200"
      },
      "message": "Die Umnummerierungs-Kaskade war keine Grenze, sondern drei Mängel\n\nDie mehrschrittige Umnummerierungssequenz galt bislang als wesenseigene Grenze:\nIhre Folgeänderungen gingen in den Abschnitt „Manuell prüfen“, im bayerischen\nBelegfall drei von 154 Anweisungen (48. a) ee), 48. a) gg), 48. b) cc), sämtlich\naus der Neunummerierung des Bußgeldkatalogs in Art. 56 BayJG). Die Prüfung gegen\ndie amtliche Nachfassung zeigt, dass es keine Grenze war, sondern drei\nvoneinander unabhängige Mängel. Erst die Diagnose vor jeder Änderung — die\nBegründungen der drei Fälle ausgeben — hat sie getrennt; die Vermutung, alles\nsei eine Frage der Reihenfolge, traf nur auf einen von ihnen zu.\n\nGeordnet werden nun Schritte statt Befehle (BefehlAnwender). Ein Verbund aus\nUmnummerierung und Begleitänderung trägt zwei gegenläufige zeitliche Ansprüche:\nDie Umnummerierung gehört vor denjenigen, der ihre Bezeichnung neu besetzt, die\nBegleitänderung an ihre Stelle im Dokument, denn sie setzt die vorangegangenen\nPunkte als vollzogen voraus. Bisher setzte sich der erste Anspruch für die ganze\nEinheit durch. Bei gg) — „Die bisherige Nr. 11 wird Nr. 12 und die Angabe\n„schriftliche“ wird gestrichen“ — stand die Angabe vorgezogen noch zweimal im\nArtikel und war zu Recht mehrdeutig; an ihrer Dokumentstelle hat ee) die zweite\nFundstelle längst ersetzt. Die Befehlsliste wird dazu vor der Anwendung zu\nSchritten aufgefaltet (je Teilbefehl einer); protokolliert wird unverändert je\nBefehl, ein Verbund gilt nur als angewandt, wenn jeder Teil gegriffen hat.\n\nDie Ordnungsregel selbst bleibt wörtlich dieselbe („wer eine Bezeichnung räumt,\nkommt vor dem, der sie neu besetzt“), wird aber erst jetzt vollständig\ndurchgesetzt. Bisher rückte ein Befehl nur einmal vor seinen ersten\nKollisionspartner; auf Schritten zerreißt das die Ketten — von „Nr. 15 wird\nNr. 16“, „Nrn. 13 und 14 werden Nrn. 14 und 15“, „nach Nr. 12 wird Nr. 13\neingefügt“ zog die Einfügung nur das letzte Glied vor sich her. An die Stelle\ntritt eine Tiefensuche auf der Dokumentordnung: vor jedem Schritt erst rekursiv\nseine Räumer, eine ringförmige Abhängigkeit bricht ab. Kein Kahn mit „frühester\nbereiter Knoten“ — der zieht unbeteiligte Schritte vor und bricht genau die\nBegleitänderung wieder.\n\nDie beiden übrigen Mängel lagen anderswo:\n\n* Das Muster der lokativen Klausel (BefehlErkenner) schloss mit einer\n  Wortgrenze. Hinter einem abgekürzten Bezeichnungswort steht aber schon der\n  Abkürzungspunkt, und zwischen ihm und dem Leerzeichen liegt keine Wortgrenze;\n  der Klausel entging deshalb jede Kurzform („in Abs. 2 …“, „in Buchst. b …“).\n  Die unabgekürzten Formen trafen zu, weshalb es nie auffiel.\n\n* Der StellenAufloeser verlangte hinter der Aufzählungsmarke Text auf derselben\n  Zeile. Eine Einheit, die sich vollständig in ihre Untergliederung ergießt,\n  führt ihre Marke allein (Art. 56 Abs. 2 Nr. 12 BayJG, darunter nur die\n  Buchstaben a und b) und galt als nicht auffindbar.\n\nDer bayerische Belegfall steht damit auf 154 angewandten Anweisungen ohne Rest\n(zuvor 151), die Ausschussfassung der Beschlussempfehlung zum GEG auf 68 statt\n67 — dort greift nun eine Bereichs-Umnummerierung in § 108, die vorher nur ihr\nerstes Glied vorziehen konnte; § 108 liegt jedoch in der bekannten Zone, in der\ndas Beispiel-XML eine andere Fassung ist als die vorausgesetzte, taugt also\nnicht als Beleg. Belegt ist die Ordnung an Art. 29a und Art. 56 BayJG und an den\nKaskaden des WDR-Gesetzes. Alle übrigen Bezugszahlen des Bundes und der Länder\nsind unverändert; 304 Prüfungen laufen durch.\n\nDer Akzeptanztest hält zwei Mängel fest, die er nicht behebt. Beide bestanden\nschon zuvor, was ein Lauf gegen den Ausgangsstand belegt:\n\n* Der Block aus „Nach Nr. 4 werden die folgenden Nrn. 5 bis 7 eingefügt“ tritt\n  an das Ende des Absatzes statt hinter die Nr. 4, und der leere Platzhalter\n  „7. (aufgehoben)“ der Altfassung bleibt zwischen den Nrn. 9 und 10 stehen.\n  Dass jede Anweisung greift, heißt eben nicht, dass die Norm in allem der\n  amtlichen Nachfassung gleicht; der Test sagt das ausdrücklich.\n\n* Die Heilung doppelter Leerzeichen nach einer Streichung wirkt auf den\n  gesamten Zieltext und verkürzt dabei die Einrückung der Aufzählungszeilen.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: Id61babe60226d27b5c05ff971927d61713b01781\n"
    },
    {
      "commit": "2b1841e17533543d1cb15220ca86a2a37c853daf",
      "tree": "01b940cb06c5abc36704d2d4853343ee7b38ce02",
      "parents": [
        "5700bbcb89186e432c5c7dd232b61c052de8e784"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Aug 15 10:51:11 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Aug 15 10:51:11 2026 +0200"
      },
      "message": "Die Web-App rechnet im Browser statt auf dem Server\n\nBisher lief die Weboberfläche auf einem JDK-HttpServer: Uploads landeten als\ntemporäre Dateien auf dem Server, die Synopse entstand dort. Das kostete\nBetrieb (systemd, Reverse Proxy, Rate-Limiting, Timeouts) und verlangte ein\nDatenschutzversprechen, das nur zusicherbar, nicht nachprüfbar war — gerade\nEntwurfstexte verließen den Rechner der Nutzer:innen.\n\nNeu übersetzt `./mvnw -Pwasm package` dieselbe Pipeline mit GraalVM Web Image\n(`native-image --tool:svm-wasm`) nach WebAssembly, PDFBox eingeschlossen.\nAusgeliefert werden nur noch statische Dateien; gerechnet wird im Browser.\nDie erzeugte Synopse ist byteweise identisch mit der der Befehlszeile\n(SHA-256 verglichen für IfSG 48/27/21 und BayJG 151/3/54).\n\nDie Befehlszeile bleibt unberührt: `./mvnw package` erzeugt unverändert das\nJAR, alle Optionen und Meldungstexte sind gleich, das Wasm-Profil ist rein\nadditiv und verlangt Oracle GraalVM 25.1+ (die CE hat kein Web Image).\n\nPortabilitätsschnitt (nützt beiden Fassungen):\n\n* `Quelle` (Name + Bytes) ersetzt `Path` in der Pipeline; nur die\n  Befehlszeile kennt noch ein Dateisystem. Der Name trägt genau den\n  bisherigen `getFileName()`-Text, damit Warnungen und Quellenzeile\n  wortgleich bleiben.\n\n* `DateiTyp` erkennt PDF/XML/Klartext an den Signaturbytes. Tika entfällt —\n  eine schwergewichtige Abhängigkeit samt ServiceLoader- und\n  XML-Konfiguration weniger, was der Wasm-Übersetzung unmittelbar zugutekommt.\n\nVier Eigenheiten von Web Image, die der Quelltext jeweils an Ort und Stelle\nvermerkt:\n\n* `java.util.zip.Inflater` ist nicht angebunden (GR-65205), ohne Inflate ist\n  kein PDF lesbar. `InflaterErsatz` substituiert ihn durch jzlib.\n\n* Typisierte JS-Felder lassen sich nicht nach `byte[]` umsetzen\n  („byteArrayHub is not defined“); der Dateiinhalt wandert als Base64.\n\n* JULs Standardformatter ruft `StackWalker`, den es dort nicht gibt.\n\n* Im Worker fehlt `document.currentScript`, worauf die Laufzeit das\n  Wasm-Modul neben `worker.js` sucht; die VM wird deshalb mit ausdrücklichem\n  Pfad ein zweites Mal gestartet.\n\nDie Reachability-Metadaten stammen aus einem Lauf des Tracing-Agents über die\nPipeline; die PDFBox- und FontBox-Ressourcen sind als Globs ergänzt, sonst\nscheitern PDFs an „Could not find referenced cmap stream Identity-H“.\n\nEntfallen: WebMain, UploadHandler, StaticHandler, Multipart und die\nsystemd-Unit. Die nginx-Vorlage liefert jetzt statische Dateien aus, und die\nDatenschutzseite sagt, was nun stimmt: Die Dateien verlassen den Rechner\nnicht.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I38faf2ac0f764d601f080d4276babe4747773683\n"
    },
    {
      "commit": "7235b34eeb6ff331c152116cbe4df846d7476110",
      "tree": "febb373089f624511a484316642bad31519ed5ca",
      "parents": [
        "7b455cd43149834ccd2163b4e5d197809bd34a37"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Fri Aug 14 18:58:25 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Fri Aug 14 18:58:25 2026 +0200"
      },
      "message": "Quellformate jenseits des verkündeten Gesetzes\n\nBisher nahm ÄndGgner nur verkündete Artikelgesetze und Gesetzentwürfe an, ohne\nden Unterschied zu kennen. Dokumente, die einen Entwurf ändern statt ein\nGesetz, lieferten still null Befehle.\n\nNeu:\n\n* Dokumentart-Erkennung aus dem Rohtext (DokumentErkenner, DokumentArt,\n  DokumentKopf) — vor der Bereinigung, weil gerade die Drucksachenköpfe als\n  Kolumnentitel wegfallen. Erkannt wird nie am Dateinamen: Die Beispieldaten\n  enthalten eine Datei namens Beschlussempfehlung, die in Wahrheit ein\n  Entschließungsantrag ist. Dokumente ohne Befehle erzeugen jetzt eine\n  benannte Warnung statt stiller Leere.\n\n* Änderungsanträge (AenderungsantragParser, EntwurfsPatcher): Der Antrag wird\n  auf den Entwurfstext angewandt, der geänderte Entwurf danach wie gewohnt auf\n  das Stammgesetz — eine komponierte Synopse. Drucksachen- und Gesetzesstellen\n  bleiben getrennte Typen; die Zuordnung Antrag→Entwurf läuft über die\n  Drucksachennummer, nicht über die Argumentreihenfolge. Der 1910 Zeilen große\n  BefehlAnwender bleibt unberührt.\n\n* Beschlussempfehlungen werden erkannt und mit Begründung übergangen, die den\n  brauchbaren Entwurf beim Namen nennt. Die Spaltentrennung der\n  Zusammenstellung ist gebaut (FontgroessenFilter.Spalte, koordinatenbasiert\n  am Steg) und belegt: Die linke Spalte ergibt Befehl für Befehl den\n  Regierungsentwurf. Die rechte Spalte bleibt bewusst offen — sie vermerkt\n  „unverändert“ auch zeilenweise innerhalb zitierter Blöcke, ihre\n  Anführungszeichen gehen daher nicht auf; nötig ist die zeilenweise Zuordnung\n  beider Spalten über die gemeinsame Grundlinie.\n\nDie Synopse kennzeichnet eine Entwurfsfassung als solche.\n\n296 Tests grün (vorher 269); alle gepinnten Akzeptanzzahlen unverändert.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I0001d25fcbd9969fc06eea675edc4326ce2e02f9\n"
    },
    {
      "commit": "7b455cd43149834ccd2163b4e5d197809bd34a37",
      "tree": "5194dad78446c9631da454a523f122f9de46057c",
      "parents": [
        "5b2e6ef635026a62e23fe5ea6df2c85d839ff78c"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 09 08:33:37 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 09 08:33:37 2026 +0200"
      },
      "message": "Add a public web front end alongside the CLI\n\nExtracts the CLI pipeline into a reusable Pipeline class and exposes it\nvia a dependency-free JDK HttpServer (upload form, bounded worker pool\nwith 503 on overload, per-request size/time limits, no persisted\nuploads), plus nginx/systemd deploy templates and Impressum/Datenschutz\nplaceholders for public operation.\n\nChange-Id: I6e8e7afa3c4b1082cdf9e82da0fae0b5b49470ad\n"
    },
    {
      "commit": "5b2e6ef635026a62e23fe5ea6df2c85d839ff78c",
      "tree": "6c7af175312d929ea698a6567ba8f2fd3367abc4",
      "parents": [
        "a201e83e59562e0e662196a616ff746cdaddd74e"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 02 20:01:37 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 02 20:01:37 2026 +0200"
      },
      "message": "Add Hesse as an extraction and recognition case\n\nThe Hesse GVBl issue 5/2026 amends the ordinance on traffic-law\ncompetences. All 21 commands of its article 1 are now recognised.\n\nThe blocked letterspacing that was expected to be the hard part turns\nout to affect only the signature block, not a single command. What did\nneed work was three other things: the running GVBl footer and the\nmasthead remainder are now stripped as page furniture, and so is the\nheading\u0027s asterisk footnote (\"* Ändert FFN 61-60\"), which sits at the\nfoot of a page between two enumeration items and stuck to the command\nabove it.\n\nTwo command forms are new, both general rather than Hessian: \"am Ende\"\nmay be absent from a punctuation replacement — the definite article then\nrequires the unit to carry exactly one such mark, which the applier\nchecks — and the object after \"durch\" may be elided in the form without\na location, as it already could in the form with one. Where a\npunctuation replacement follows a renumbering in the same sentence it\nbinds to the renumbered unit: unlike a word operation it has no\ndistinguishing target text, so resolving it norm-wide would be useless.\n\nA full acceptance test stays out of reach: hessenrecht.hessen.de is the\nsame login-only juris application as the Schleswig-Holstein and Berlin\nportals. Checking landesrecht-bw.de too, that now covers all four\nportals that could have supplied an annex-bearing statute, so the\nLandesRechtTextParser\u0027s missing annex headings will need a stem from\nrecht.nrw.de instead.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: Ief04164ee25653345a011f3ffbbfaa6df1f5c64b\n"
    },
    {
      "commit": "a201e83e59562e0e662196a616ff746cdaddd74e",
      "tree": "bebd570c3098f8793d9d6f3442bbb50433374917",
      "parents": [
        "bac648b8fc06dfffaf67cf283f73fa2572e67575"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 02 19:45:34 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Aug 02 19:45:34 2026 +0200"
      },
      "message": "Close the NRW issue: 17. RÄStV-AusfG as a fourth acceptance case\n\nArticle 4 of the 22nd Broadcasting Amendment Act recasts § 1 of the act\nimplementing the 17th Broadcasting Amendment Treaty. Both the pre- and\nthe post-amendment consolidated version are served by recht.nrw.de, so\nthis closes the last open article of GV. NRW. 7/2026.\n\nNo production code needed changing: the article carries its single\ncommand without an enumeration item, and the recast quote contains\nnested quotation marks — both are already handled. The result matches\nthe official version of 1 April 2026 character for character, including\nits editorial placeholders.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: If63606d113f2801f0c9e82350215443da8e8be8b\n"
    },
    {
      "commit": "bac648b8fc06dfffaf67cf283f73fa2572e67575",
      "tree": "e2e4387451deabb37b5f80ed42e06bd17b3127d9",
      "parents": [
        "5f30f566873c313b554f087c0f7e132efa54d64a"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Tue Jul 28 07:51:09 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Tue Jul 28 07:51:09 2026 +0200"
      },
      "message": "Run the NRW mass test: WDR-Gesetz and LMG NRW\n\nThe 22nd Rundfunkänderungsgesetz amends five laws in one gazette issue.\nArticle 3 (TMZ-Gesetz) was already an acceptance case; this adds the two\nbig ones — Article 1 (WDR-Gesetz, 101 commands across 31 norms) and\nArticle 2 (LMG NRW, 18 commands). Both stem versions come from\nrecht.nrw.de, whose URLs address a version by its date of entry into\nforce, so the results could be checked norm by norm against the official\n1 April 2026 consolidations.\n\nApplying them turned up work at every layer:\n\nOrder of application. Renumbering always refers to the original count,\nnot to the state after the preceding items, so a cascade („Absatz 3 wird\nAbsatz 4“, „Absatz 4 wird Absatz 5“, …) applied in document order leaves\nthe law carrying two units of the same name. BefehlAnwender now derives,\nfor each command, which designations it vacates and which it newly\noccupies, and pulls a vacating command ahead of the first one it\ncollides with. That single rule subsumes the previous §-only special\ncase, orders a cascade descending, and — inside a Sammelbefehl too —\nkeeps a range renumbering from colliding with itself. Bayern\u0027s Art. 29a\nsequence now resolves as well (5 manual residues down to 3).\n\nRenumbering an enumeration item. Unlike an Absatz, a Nummer carries its\ndesignation as a marker in the text; the applier silently reported\nsuccess without touching it. It now rewrites the marker and lets a\nstruck placeholder with the target designation give way.\n\nSentence splitting. Gazette citations („(BGBl. I S. 1982)“) and\nline-initial enumeration markers were splitting sentences, so Satz\nlocators pointed into the wrong place; a sentence may also open with §.\n\nCommand language: „wie folgt neu gefasst“ and the missing „wird“, a\nsplit location („In Absatz 2 wird Satz 1 wie folgt gefasst“), an\ninsertion behind a location prefix, the standalone „Der Punkt am Ende\nwird durch … ersetzt“, „Dem Wortlaut des Absatzes 3 …“, the verb frame\n„Es werden ersetzt:“ whose items carry only the location, coordination\nat „sowie“ and before a punctuation clause, and a stray closing quote at\nthe end of a sentence.\n\nStem format: LandesRechtTextParser reads an „Inhaltsübersicht“ line as\nthe norm of that name (which is what the Angabe commands address) and\nrecognises keyword-less Roman section headings.\n\nEverything the two acceptance tests do not apply is named: one command\nin the WDR-Gesetz whose „Punkt am Ende des Satzes“ is not unambiguous in\na two-sentence Nummer. The remaining differences from the official\nconsolidations are places where the official text itself departs from\nthe command wording; SOURCES lists them.\n\nChange-Id: I261cf89cd5820f7597bc5db734f322d94b84828e\n"
    },
    {
      "commit": "5f30f566873c313b554f087c0f7e132efa54d64a",
      "tree": "4f6c33a0a1e9a6b2b1ad29bffef4defd0990fef2",
      "parents": [
        "79b88e0a8cb4dfc9c33fe219045f3da7f64256c4"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Tue Jul 28 06:00:16 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Tue Jul 28 06:00:16 2026 +0200"
      },
      "message": "Recognise word-anchored insertions; close quotes at the next item\n\nThe documented next step was the word-anchored structural insertion\n(\"Vor den Wörtern „Aus dem Bereich Verkehr:“ wird folgender Absatz 5\neingefügt\", Berlin Artikel 1 Nr. 2 b) bb)). StrukturEinfuegung now\ncarries an optional WortAnker, the recogniser has a pattern for the form\n— placed before STRUKTUR_EINFUEGUNG, which bails out of recognition\nentirely when the StellenParser cannot read \"den Wörtern «0»\" — and the\napplier positions the new unit at the anchor line instead of a structural\nboundary.\n\nTwo blockers turned up next to it, both measured on the corpus rather\nthan assumed:\n\nThe command was not cleanly recognisable at all. Its closing quotation\nmark is missing in the official text, so the quote swallowed items cc)\nand c); an anchor alone would have made the command look applicable with\na huge foreign quote as its payload. The docs called a boundary at\nenumeration markers impossible, and that holds for the unguarded form: a\nquoted amendment provision carries command language itself. Guarded by\nfour conditions together — the article\u0027s quotation marks demonstrably do\nnot balance, the next line\u0027s marker is at the same or a shallower level\nthan the one the quote opened on, that line carries command language, and\nclosing here leaves the rest of the article balanced — it fires exactly\ntwice in the whole sample corpus, both times where the missing mark\nbelongs: Berlin before cc), and GV. NRW. Artikel 2 before 12. Without the\nguards it also fires inside quoted amendment provisions in the BayJG and\nGModG documents; the balance gate rules those out.\n\nThe GV.-NRW. gazette encodes part of its umlauts decomposed (u + U+0308,\n79 places, dozens of them \"eingefügt:\"/\"angefügt:\"). Invisible in the\ntext, but a different word to every command pattern, so those commands\ncould never match. TextBereiniger now normalises to NFC first — not\nNFKC, which would flatten the official sentence numbers ¹²³ and take\nSatzTeiler and Superskript their basis. Every other sample document,\nevery gii-XML stem and every hand-kept plain-text stem is already NFC, so\nthe pinned figures stay bit-identical.\n\nBerlin Artikel 1 is thereby fully recognised (6 of 6 commands, none\nunknown). One pinned statement changed for a stated reason: the NRW\nacceptance test asserted the article-heading warning, which is now\npreempted by the item boundary inside Artikel 2 — Nr. 12 survives\ninstead of being swallowed. 241 tests green.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: Ic579bec6fecc2495a61b3dcf87c9ad71b42f34ae\n"
    },
    {
      "commit": "79b88e0a8cb4dfc9c33fe219045f3da7f64256c4",
      "tree": "7f2fd3a3fd78b463d001ae7e2f81c70affdd6bfd",
      "parents": [
        "2cfea0076b43001569565c2f625afa42901282cd"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 13:33:09 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 13:33:09 2026 +0200"
      },
      "message": "Limit the juris dead-end claim to what was actually checked\n\nOnly the Schleswig-Holstein and Berlin portals were probed. Stating the\nsame for Baden-Württemberg, Hesse, Thuringia and Lower Saxony would have\ninvited a future session to skip an attempt that might well succeed.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I0fecfff43b4cb941eb973d2c7805a0eee0029781\n"
    },
    {
      "commit": "2cfea0076b43001569565c2f625afa42901282cd",
      "tree": "f2dfc99525473ea5af1c02b20521fa9680ae5265",
      "parents": [
        "81777013dfa582053489efea874e84379f1f0805"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 13:32:26 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 13:32:26 2026 +0200"
      },
      "message": "Bring the documentation up to the current state\n\nThe README still described state law as Bavaria-only, six Länder later.\nThe sample-data overview grew a section on how to obtain the pre-\namendment stems per portal — which of the three routes works, and that\nthe juris state portals are a dead end — and a short prioritised \"where\nto continue\", so the next session does not have to re-derive it.\n\nCorrected while writing it: the regression figures are not all pinned\nthe same way. UWG, AGG and ProdHaftG pin \"nothing left manual\", BayJG\npins 154 commands and names its five renumbering residues, and the state\ncases pin full application. Saying \"UWG 19/0, GEG 66/53, …\" would have\ndescribed observations, not what the tests actually assert.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: Ie247e9626e789e628d537bede735923d5b67d14b\n"
    },
    {
      "commit": "81777013dfa582053489efea874e84379f1f0805",
      "tree": "83f227c65b91152d4a8aaca67d418da04d601e9e",
      "parents": [
        "c86a73a6e1da7dd28076054936458b850eda2947"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 08:53:10 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 08:53:10 2026 +0200"
      },
      "message": "Support unnumbered named Anlagen; strip control characters\n\nInvestigating \"Anlagen as amendment target\" corrected the diagnosis from\nyesterday: Anlagen are supported. In gii-XML they are norms of their own\n(\"Anlage 8\", \"Anhang\"), Stelle.anlagenEnbez() resolves them, and the GEG\nsample applies annex-targeted commands — only two of its fifty manual\nentries touch annexes, both for content reasons.\n\nWhat actually failed in Berlin was narrower, and is fixed:\n\n  * A law with a single annex names it after the provision it belongs to\n    (\"Die Anlage zu § 2 Absatz 4 Satz 1\"). StellenParser demanded a\n    number after \"Anlage\" and rejected the phrase, so the article\u0027s frame\n    command went unrecognised and its items lost their context. The\n    annex now carries the designation \"Anlage\", like \"Anhang\". The naming\n    suffix is skipped deliberately: read along, the \"§ 2\" inside it would\n    become the target and the wrong norm would be amended.\n\n  * C0 control characters are now stripped. Berlin\u0027s enumeration indent\n    carries a U+0007 that sits invisibly in front of the command and made\n    its start-of-line anchor miss.\n\n  * Command verbs torn apart by a stray space in the official typesetting\n    (\"ein gefügt\" for \"eingefügt\") are rejoined, restricted to sequences\n    that are not valid German word order.\n\nThree of Article 1\u0027s four commands are now recognised. The fourth places\nthe new unit by a word anchor (\"Vor den Wörtern … wird folgender Absatz 5\neingefügt\"), which StrukturEinfuegung cannot express; that and the\ninability of the plain-text stem format to carry an Anlage at all are\nrecorded in Landesrecht-Beispiele.adoc.\n\n231 tests green; all pinned figures unchanged.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: Ic5804bf343dd5d8ce435c07b8f882ca0372890d2\n"
    },
    {
      "commit": "c86a73a6e1da7dd28076054936458b850eda2947",
      "tree": "179aa5b90857750bbaf41b20a401985206b6817f",
      "parents": [
        "83ba9f0db3462a4c2d5122ba836f646b055156ca"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 08:02:10 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 26 08:02:10 2026 +0200"
      },
      "message": "Berlin column spike: stream order already reads correctly\n\nThe plan assumed the two-column Berlin gazette would need x-coordinate\ncolumn detection. It does not: the content stream already emits the left\ncolumn fully before the right one, so commands come out in reading order.\nThe test pins that finding.\n\nWhat does go wrong there is different, and two parts of it are fixed:\n\n  * The article\u0027s amendment formula carries its own target (\"§ 2 Satz 1\n    des Gesetzes zur Errichtung … wird wie folgt geändert\"), but the\n    following items never inherited it. The pattern\u0027s leading \\b could\n    never match before \"§\" — a non-word character needs a word character\n    in front of it — so the paragraph branch was dead code and only the\n    Bavarian \"Art.\" branch ever fired.\n\n  * The running page header is not a line of its own; it sits inside the\n    body text of the following column, so it has to be cut out rather\n    than dropped as a column title.\n\nTwo blockers remain and are recorded rather than papered over: Article 1\namends an *Anlage* with its own numbering, which the model does not carry\n(the same gap that shelved Baden-Württemberg), and full-width frames\n(title block, imprint) sit elsewhere in the stream than on the page,\nwhich would need a real XY-cut. Stems are unobtainable either way —\ngesetze.berlin.de is an authenticated juris app like the Schleswig-\nHolstein portal.\n\n229 tests green; all pinned figures unchanged.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I4619dbe96a023d61104d7107a9a34533123d1bc5\n"
    },
    {
      "commit": "83ba9f0db3462a4c2d5122ba836f646b055156ca",
      "tree": "82b786836898972cf1291f2b8739098f762e3baf",
      "parents": [
        "35e90f4ab0f9b40d4752c9b8cba57c9452a8189f"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 25 10:35:45 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 25 10:35:45 2026 +0200"
      },
      "message": "Support the two Lower Saxony insertion forms; NEFG now applies fully\n\nThe NEFG acceptance case left two commands as \"check manually\". Both are\nnow supported, so Lower Saxony applies 7 of 7 with no remainder.\n\n  * Lower Saxony cites inserted paragraphs with a space before the sub\n    number (\"§ 2 a\"); the rest of German legal usage writes \"§ 2a\", which\n    is what the Stelle and level parsers expect. TextBereiniger now pulls\n    the form together, leaving enumeration markers of the amendment act\n    alone (\"… nach § 8 c) In Absatz 2 …\").\n\n  * \"In Kapitel 4 wird nach § 12 der folgende neue § 13 angefügt\" — the\n    division only names the section the new paragraph lands in; the\n    anchor governs the position, as in the plain form. The optional\n    \"neue\" is now accepted in both.\n\nApplying that insertion needed one more thing: the paragraph it creates\nis only vacated by the *following* command (\"Der bisherige § 13 wird\n§ 14\"), so in document order the two collided and the insertion was\nrejected. \"Bisherig\" denotes the state before the amendment, so the\nrenumbering logically precedes the reoccupation and is now pulled ahead.\nThe log still lists commands in the order of the amendment act.\n\n226 tests green; all other pinned figures unchanged.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I0e2ea5b0389f8002157eeb8471800da51febe739\n"
    },
    {
      "commit": "35e90f4ab0f9b40d4752c9b8cba57c9452a8189f",
      "tree": "271b8ce1f0537bc8546e3939d99df6e47d79369b",
      "parents": [
        "519c1e7b769c37769d1b5d1ffd6e13566b26c86d"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 25 10:00:36 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 25 10:00:36 2026 +0200"
      },
      "message": "Add North Rhine-Westphalia TMZ-Gesetz acceptance case\n\nArticle 3 of the 22. Rundfunkänderungsgesetz (GV. NRW. 2026 S. 202) amends\nthe Telemedienzuständigkeitsgesetz. All four commands apply cleanly, and\nthe result matches the official consolidated version of 1 April 2026.\n\nrecht.nrw.de turned out to be the one remaining state portal that serves\nconsolidated laws as server-rendered HTML, with the version history\nencoded in the URL date prefix — so the pre-amendment stem (27 Apr 2022)\nwas directly obtainable.\n\nTwo fixes were needed:\n\n  * LandesRechtTextParser read the parenthesised title suffix wholly as\n    the abbreviation. State laws routinely carry both short title and\n    abbreviation there (\"(Telemedienzuständigkeitsgesetz – TMZ-Gesetz)\"),\n    and the amendment act cites the short title, so article selection\n    never matched. The parser now splits at the dash.\n\n  * ZitatExtraktor swallowed the rest of the document when a closing\n    quotation mark is missing in the official text (Article 2 no. 11\n    here), which hid Articles 3 to 5 entirely. An amendment act never\n    quotes across an article heading, so an open quotation is now closed\n    before a bare \"Artikel N\" line, with a warning. Quoted paragraphs are\n    unaffected: Bavarian norm heads read \"Art. N\".\n\n223 tests green; all previously pinned figures unchanged.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I78470075d9be2433966b821b6fe1e21808996c46\n"
    },
    {
      "commit": "519c1e7b769c37769d1b5d1ffd6e13566b26c86d",
      "tree": "59c8deaa1e34c3464801e9337fc2a92a15af307d",
      "parents": [
        "43e91612875de3cc6e7466eee56023ab55cefd89"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 25 09:11:56 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 25 09:11:56 2026 +0200"
      },
      "message": "Add Schleswig-Holstein extraction case and three cleanup fixes\n\nThe GVOBl. Schl.-H. amendment act (Kommunalrecht, 2026/27) brings three\nconventions the tool had not seen:\n\n  * a running two-line page header that sits between articles and glued\n    itself onto the following article heading,\n  * superscript footnote markers on article headings (\"Artikel 1 ¹)\"),\n    which defeated the article split, and\n  * ragged-right typesetting, where the geometric margin detection finds\n    no alignment cluster and reports full lines as hard line ends, so a\n    trailing hyphen was never joined.\n\nAll three are fixed in TextBereiniger; the hyphen rule now trusts the\nextractor\u0027s trailing-space signal over the geometric class.\n\nA full acceptance test is not possible: the Schleswig-Holstein law portal\nserves document bodies only through an authenticated API, and the last\nfreely archived consolidated Gemeindeordnung (14 Nov 2022) predates the\namended § 34a. The new test therefore covers everything up to and\nincluding command recognition; the blocker is recorded in\nLandesrecht-Beispiele.adoc.\n\n219 tests green; Bund/Bayern/Sachsen/Niedersachsen figures unchanged.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I9b3ab8a756372504b51c4d410b491fded255da96\n"
    },
    {
      "commit": "43e91612875de3cc6e7466eee56023ab55cefd89",
      "tree": "867f602cd8b00a320987cde8947778deaa7efa45",
      "parents": [
        "3f81addcfbeae7aabcdd823340397f66e394f02f"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Fri Jul 24 22:29:35 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Fri Jul 24 22:29:35 2026 +0200"
      },
      "message": "Add Lower Saxony NEFG acceptance case and two parser robustness fixes\n\nSecond §-structured Landesrecht case for wave six: the Lower Saxony ELER Support\nAct (NEFG, unchanged since 2022, derived from the two-column Nds. GVBl 2022 No. 33)\nplus the amending act of 28 Jan 2026 (Nds. GVBl 2026 No. 10). Five of seven\ncommands apply — both \"erhält folgende Fassung\" re-enactments (§ 1(1), § 2), the\ncitation replacement in § 1(5), the words insertion in § 6(1), and the § 13 → § 14\nrenumbering.\n\n- LandesRechtTextParser: a norm head no longer accepts a title ending in a full\n  stop, so a cross-reference sentence at line start (\"§ 7 GAPInVeKoSG findet\n  entsprechend Anwendung.\") is not misread as a norm head \"§ 7\" (which had made the\n  monotonicity check swallow the norms in between).\n- TextBereiniger: strip the Lower Saxony GVBl running footer and publisher line.\n  The footer sat between two enumerated items and otherwise attached to the\n  preceding re-enactment quote, defeating its end-of-sentence anchor.\n- Add sampledata/Niedersachsen/NEFG-alt.txt and EndToEndTest.nefgAcceptance.\n\nTwo insertion forms remain documented residues (manuell prüfen): inserting a\n§-block with a space-separated sub-number (\"§ 2 a\") and a chapter-scoped §-block\ninsertion (\"In Kapitel 4 wird nach § 12 … angefügt\").\n\n221 tests green; federal, Bavarian and Saxon pinned numbers unchanged.\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\nChange-Id: Ie23eee1f596ec8eecc6a73f6ce585a22e73ec6c9\n"
    },
    {
      "commit": "3f81addcfbeae7aabcdd823340397f66e394f02f",
      "tree": "cfc08069f1da4bff2c8f1b67de85e70defad2fa2",
      "parents": [
        "c2b57decf3d57d4808dd37723c562b8e001cc342"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Fri Jul 24 05:34:32 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Fri Jul 24 05:34:32 2026 +0200"
      },
      "message": "Add Saxony SächsBeamtVG acceptance case (first non-Bavarian Landesrecht)\n\nComplete the first §-structured Landesrecht acceptance case for wave six: the\nSaxon Civil Servants\u0027 Pension Act (SächsBeamtVG) in its 1 Feb 2025 version plus\nthe amending act of 13 April 2026 (SächsGVBl. S. 134). All five commands are\nrecognised and applied without residue — the amount replacements in § 47 and the\nre-enactment of § 80(1) sentence 2.\n\n- LandesRechtTextParser: recognise arabic, keyword-first structural headings\n  (\"Abschnitt 1\", \"Unterabschnitt 2\", \"Teil 3\") via GLIEDERUNG_ARABISCH, in\n  addition to Bavaria\u0027s roman \"I. Abschnitt\" form. Bavaria behaviour unchanged.\n- TextBereiniger: strip the footer of revosax full-text output (REVOSAX_FUSS,\n  \"https://…revosax… Fassung vom … Seite N von M\").\n- Add the consolidated pre-amendment stem as canonical plaintext\n  (sampledata/Sachsen/SaechsBeamtVG-alt.txt, derived from the archived revosax\n  full text) and EndToEndTest.saechsBeamtVgAcceptance (5 applied, 0 manual).\n\n220 tests green; federal and Bavarian pinned numbers unchanged.\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\nChange-Id: I8e878bc9506f24028cf643a873de000f3d066d64\n"
    },
    {
      "commit": "ab7ac577eedaffabf087a84786bebe9a8904c365",
      "tree": "0efb32b59b2cf6470e1d09c748ce32ff1698c79a",
      "parents": [
        "65eff08b32a0f00ff0f5e4bda3fe5793f631ed64"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 19 09:25:55 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 19 09:25:55 2026 +0200"
      },
      "message": "Add Landesrecht amendment samples from eight further Länder\n\nCollect real amendment gazettes/ordinances from Berlin, Schleswig-Holstein,\nHessen, Niedersachsen (two hefts), Baden-Württemberg, Nordrhein-Westfalen,\nSachsen and Thüringen as candidates for a further enhancement wave, plus an\n.adoc overview. Unlike Bavaria (Art./§ inversion) these Länder use § in their\nstem laws; the new test dimensions are PDF layout (Berlin two-column, Hessen\nletter-spacing) and command idioms (\"erhält folgende Fassung\", superscript\nArtikel footnote markers, amtliche Satznummern in a § context). Only the\namendment documents are included so far; the consolidated stem versions and\nRheinland-Pfalz remain open.\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\nChange-Id: I0e3e761763038abda144266381cf59f8d8f3bf78\n"
    },
    {
      "commit": "65eff08b32a0f00ff0f5e4bda3fe5793f631ed64",
      "tree": "1d101859b51c80bc117ec72a871933575ed8b2f3",
      "parents": [
        "f20828ffd8ea9d554566636a9c53a3abd57507c5"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sat Jul 18 12:24:32 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Jul 19 09:00:01 2026 +0200"
      },
      "message": "Support Bavarian state law (BayJG) with Art./§ inversion and superscripts\n\nExtend ÄndGgner from federal-only to Bavarian state law. Bavarian base\nlaws are structured in Artikel while their amending acts are structured\nin Paragraphen (inverted from the Bund); official sentence numbers and\nfootnote markers are carried as Unicode superscripts (¹²³, ⁶)).\n\n- Generalise Stelle.Paragraph to carry a sigil (\"§\" or \"Art.\") and route\n  it through recogniser, applier and resolver (bit-identical Bund output).\n- Superscript pipeline: geometric detection in FontgroessenFilter\n  (SuperskriptModus BEHALTEN), Superskript util, exact sentence splitting\n  in SatzTeiler, label-based sentence resolution.\n- BayRechtLoader/BayRechtTextParser for gesetze-bayern.de PDF/plaintext.\n- §-structured amending acts, GVBl/Landtag column titles, non-breaking\n  spaces, the GVBl continuation quote; Bavarian command forms (footnote\n  aufhebung, Satznummerierung streichung, Wortlaut forms, Halbsatz,\n  gapping chains).\n\nAcceptance (EndToEndTest.bayJgGvblAcceptance): the pre-2026 BayJG\nfassung (BayJG-alt.txt, reconstructed from Wayback single-article\nsnapshots) with GVBl 6/2026 §§ 1-2 applied — 154 commands, 0 unknown,\n149 applied automatically, 5 pinned residuals (follow-up edits inside\ntwo multi-step renumbering sequences in Art. 29a and Art. 56).\n\nApplication-side fixes surfaced by the acceptance run (all Bund-safe):\nsentence-start superscript before §; sentence boundaries \u003d {0} ∪ {each\nnumber ≥ 2}; gapping scope inheritance for bare word operations;\nfootnote definition lines hidden from word operations; absatz aufhebung\nmarks \"(weggefallen)\" keeping its number, and absatz renumbering\noverwrites an empty placeholder (weggefallen/gegenstandslos) target.\n\n211 tests green (mvnw verify); federal reference numbers unchanged.\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\nChange-Id: Iebae4c17ca90755c5fd36251362042f3d5796fd0\n"
    },
    {
      "commit": "91a57498aa4acf266d0ab255aa06c18527846eec",
      "tree": "5c53b08a64f87f924f9d59c6feafde500fbb9427",
      "parents": [
        "8ae49729ee18a102d503324f2be49c35694b244a"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Mon Jul 13 21:33:09 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Mon Jul 13 21:33:09 2026 +0200"
      },
      "message": "Add AGG, BayJG, GEG, ProdHaftG, and UWG sample data.\n\nFive new datasets with provenance in SOURCES files:\n\n* UWG: 3. UWGAendG (BGBl. 2026 I Nr. 43) in the new digital BGBl\n  format, plus drafts.\n* GEG: the 2023 \"Heizungsgesetz\" (BGBl. 2023 I Nr. 280, new format)\n  and the pending GModG 2026 drafts.\n* AGG: 2. AGGAendG drafts (RefE/RegE/BT-Drs 21/6178) -- the base XML\n  predates the bill, so this dataset produces real diffs -- and the\n  official BMJV synopsis as ground truth.\n* ProdHaftG: product-liability modernization drafts (Artikel 1 is a\n  replacement act, Artikel 2 amends the old law), with official\n  synopsis.\n* BayJG: Bavarian hunting-law amendment (GVBl. 2026 S. 113) -- state\n  law is not yet supported by the tool; kept for future work.\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I8c33b6a19178f73cece9c9da99c713009016e578\n"
    },
    {
      "commit": "99962fb4aff2a11074b7179b71ed5a5f0cdbc8e4",
      "tree": "58caa90e2a27e50e9e6b6ce13488278860903b03",
      "parents": [
        "58e19982f25ae6433d7837454bb54b8edc37589c"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Mon Jul 13 21:32:24 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Mon Jul 13 21:32:24 2026 +0200"
      },
      "message": "Add IfSG sample data.\n\nThe Infektionsschutzgesetz as gii-norm XML, EPUB, and PDF (consolidated\nas of 2020-11-20, i.e. already including the Art. 1 changes below), the\nDrittes Bevoelkerungsschutzgesetz (BGBl. I 2020 S. 2397) as published,\nand the Bundestag/Bundesrat drafting documents, with provenance URLs in\nSOURCES.  Used by the end-to-end smoke test.\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I1221734ea3e3dab705151421774151438be1b337\n"
    },
    {
      "commit": "1b9bfb1bfed11593e08cde8bb072dbfb5980b740",
      "tree": "984c268931d2d5567551a4cb1a50f9c735a2a3f1",
      "parents": [
        "545aeb6e25386121b414e6aa0cae0a96758cf3c8"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Mon Jul 13 07:08:31 2026 +0200"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Mon Jul 13 07:08:31 2026 +0200"
      },
      "message": "Modernize build: Java 21, Tika 3, PDFBox 3, JUnit 5.\n\nBump all dependencies and plugins to current versions.  Replace the\ntika-parsers bundle with a direct PDFBox dependency (we need\nPDFTextStripper control), add java-diff-utils for the synopsis diff,\nand add JUnit 5 with AssertJ for testing.  Drop unused dependencies\n(tess4j, Lanterna, term4j, sqlite-jdbc, imageio codecs, annotation\nlibraries) in favour of jspecify.  Regenerate the Maven wrapper with\nthe official plugin (Takari is dead) and remove the vestigial Ant\nwrapper and Tika configuration.\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I0e1813b3967027cbb0bb978591d345ce138fa0a0\n"
    },
    {
      "commit": "545aeb6e25386121b414e6aa0cae0a96758cf3c8",
      "tree": "6cb998430e9c461c283ff7d692d0b14aad2a541d",
      "parents": [
        "1d92ac8fbb6c5c3a3be7bf477fef9251dcd3dfe2"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Dec 06 15:16:22 2020 +0100"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Sun Dec 06 19:24:02 2020 +0100"
      },
      "message": "Configure Tika correctly.\n\nWith the new configuration, Tika can now extract text from PDFs and\nXML documents.\n\nAlso configures logging for the application.\n\nChange-Id: I7a89c2b232ed4e220665dd335a5f5a0cc3ef2994\n"
    }
  ]
}