v2.0.3 — every tool at its current release

The October 2026 edition, re-measured on every tool at its current release. No figure moved; the versions, one count and one list of upstream drift did.

📄 SemOps-Manual-v2.0.3-A4.pdf (124 pages, A4)
📓 SemOps-Manual-v2.0.3-notebooks.zip: the three runnable notebooks, unchanged
🌐 Web edition, built from the same sources

Measured against: suite 0.25.0, extension 0.17.1, DSL 0.16.1, engine 0.3.4, HOLOS 0.26.0, tarka 0.2.1, between 13 October and 3 November 2026.

What moved

• Suite 0.24.3 → 0.25.0. It adds --severity-policy and --stringency, which set how strict each check is at each stage of a project, applied to finished findings. Every figure the manual quotes is the same on 0.25.0.
• Extension 0.16.3 → 0.17.1. It reads the same severity policies, and bundles holos-wasm-node 0.26.0. The suite's repository now locks holosdb 0.26.0 too, so Chapter 7's "the version is the same on both sides" holds again.
• tarka 0.2.0 → 0.2.1.
• The testing repository reports 166 passed, 10 skipped: one test more than the 165 first recorded, from tests it has gained since.
• Upstream drift (§14.4). The testing README's fixture count was corrected on 23 October. The same day the suite retired its develop branch, so the manual's eleven links into it were dead. They now go to main, and every target exists there.

evidence/

256 claims:

• 179 reproduced by 105 distinct runs, all passing;
• 123 quotations checked word for word;
• 1649 links resolving.

The runs used fresh clones of the testing repository at 31bda0d and the suite at v0.25.0. All three notebooks run with no errors on suite 0.25.0, shacl 0.3.4 and holosdb 0.26.0.

Full changelog: v2.0.2...v2.0.3