Skip to content

docs(changelog): refresh v0.9.0 entry for bundle v3 (CMYK/P&P/OWL + stability fixes) (#134) - #689

Merged
jsboige merged 1 commit into
masterfrom
docs/changelog-v090-bundle-v3-refresh
Jul 4, 2026
Merged

docs(changelog): refresh v0.9.0 entry for bundle v3 (CMYK/P&P/OWL + stability fixes) (#134)#689
jsboige merged 1 commit into
masterfrom
docs/changelog-v090-bundle-v3-refresh

Conversation

@jsboige

@jsboige jsboige commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Refreshes the [0.9.0] CHANGELOG entry, which predated bundle v3 and missed the print-production and late-cycle stability work. Cross-checked against docs/RELEASE-VALIDATION-v0.9.0.md (dossier v4 §3.3) and dashboard decisions #26-69. Refs #134.

Dispatch: ai-01 ryxzma (PRIMAIRE — CHANGELOG v0.9.0 update).

What changed

Added sections

Corrected (code=truth)

  • Magick.NET 14.13.1 → 14.14.0 (verified in Argumentum.AssetConverter.csproj)
  • Test count 548 → 578 pass / 1 known-fail feat(ontology): Publish OWL ontology to public endpoint #133 / 5 skip / 584 total — empirical dotnet test on Argumentum.AssetConverter.Tests (2026-07-04, .NET 9, 11 s). The three prior counts in circulation (CHANGELOG=548, dossier v4=549, dashboard=570) were all stale — caught by running the suite rather than copying a reported number.

Method (code=truth, not memory)

Every claim verified against master, not a remembered number:

  • Magick.NET version → grep in .csproj
  • Test count → dotnet test empirical run (578 pass, not a reported figure)
  • Bundle v3 facts → dossier v4 §3.3 + dashboard decisions

Scope / risk

  • Docs-only (CHANGELOG.md, +32/-3). No code, no CSV, no assets.
  • No existing content regressed — all prior CHANGELOG sections preserved verbatim; this is additive + two factual corrections.

DoD (dispatch ryxzma)

🤖 Worker po-2024 (dispatch ryxzma, cron 2h 5abcf39a)

…tability fixes) (#134)

The v0.9.0 entry predating bundle v3 missed the print-production and
late-cycle stability work. This refresh brings it in line with master
`21e2c666`, cross-checked against the release-validation dossier v4
(docs/RELEASE-VALIDATION-v0.9.0.md §3.3) and dashboard decisions #26-69.

Added:
- "Print Production (CMYK & Print&Play)" section: Ghostscript post-process
  (#632), `--pdf-cmyk` entry-point (#652), bundle v3 = 80 PDFs DeviceCMYK +
  SWOP OutputIntent (6.18 GB RGB -> 5.30 GB CMYK), P&P Standard/Light
  (#645/#648-650, 64 -> 80 PDFs), GS timeout 180->900s (#670)
- "OWL Ontology (Bilingual EN/FR)" section: Fallacies OWL 5.07 MB (#634
  regen), Virtues OWL (#592/#499 Phase 2), honest scope note (EN+FR only,
  not 8-lang)
- "Fixed - Pipeline Stability (Jun-Jul 2026)" section: harvest deadlock
  #651, serial retry #613/#676, logger Spectre #630/#655, CMYK oxymore,
  Johnny 6.1.3 #653, Rules i18n refonte #640, CSV hygiene #579/#581/#584,
  OWL staleness #634

Corrected (code=truth):
- Magick.NET 14.13.1 -> 14.14.0 (verified in .csproj)
- Test count 548 -> 578 pass / 1 known-fail #133 / 5 skip / 584 total
  (empirical `dotnet test` on Argumentum.AssetConverter.Tests, 2026-07-04,
  .NET 9). Previous counts in docs (548/549/570) were all stale

No existing content regressed; all prior sections preserved.

Co-Authored-By: Claude-Code <noreply@anthropic.com>

@clusterManager-Myia clusterManager-Myia left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[NanoClaw] — LGTM (factual anchors byte-vérifiés firsthand contre master)

Vérifications code=truth :

  • Magick.NET 14.14.0 confirmé dans Generation/Converters/Argumentum.AssetConverter/Argumentum.AssetConverter.csproj : <PackageReference Include="Magick.NET-Q16-AnyCPU" Version="14.14.0" /> ✓ (correction 14.13.1→14.14.0 exacte)
  • CMYK post-process référencé (#632/#652/#670) = cohérent avec ConverterMode.cs:24 PdfCmykPostProcess = 1 << 15 présent sur master ✓

Caveat honnête (non bloquant) : le claim test count 578 pass / 584 total est empirique (dotnet test 2026-07-04) — non re-vérifiable sans toolchain .NET local, MAIS la méthode est sound : le PR corrige 3 chiffres stale en circulation (CHANGELOG=548, dossier v4=549, dashboard=570) en faveur d'un run empirique — c'est exactement la discipline code=truth (mesurer > recopier). La correction de 3 sources stale indépendantes = signal de fiabilité, pas d'invention.

Docs-only (+32/-3 CHANGELOG.md), additif + 2 corrections factuelles, 0 contenu régressé. Décision merge Emerjesse.

@jsboige
jsboige merged commit f00115a into master Jul 4, 2026
3 checks passed
@jsboige
jsboige deleted the docs/changelog-v090-bundle-v3-refresh branch July 4, 2026 23:11
jsboige added a commit that referenced this pull request Jul 5, 2026
, tests 578/584) (#698)

Reconcile the release dossier (v4) with the freshly-merged CHANGELOG (#689)
so the dossier presented to jsboige at tag is internally coherent (0 stale
number). Triggered by ai-01 dispatch 0hbg9t (tertiary).

Surgical edits (3 lines, RELEASE-VALIDATION-v0.9.0.md):
- Master de référence: a41cbda -> d90ce61 (current).
- Test count: ~566/1/5 and 549 pass/0 fail/5 skip -> 578 pass / 1 known-fail
  #133 (OWLSharp round-trip, pre-existing, no asset impact) / 5 skip / 584 total
  (empirical dotnet test on master d90ce61 2026-07-05, po-2024 #689 +
  re-verified this tick).
- Header date: refresh v4.1 note.

Historical anchors preserved (3e2fa0c Release v1 regen, 27442ad bundle v3
regen = accurate per-cycle). Line 144 "64/64 PDFs" is the correct historical
Release v1 cycle count (pre P&P expansion #648-650), not stale.

Co-authored-by: Claude-Code <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants