chore(release): 0.8.0

Round 13 (the `.xml` core file type read as NISO-STS, and the PDF arm's
collision counter) and round 14 (a section the source DECLARES takes the
declared-structure route: `.xml` goes from 15 of 2 761 to 2 761 of 2 761
boundaries and from 23 to 2 761 concepts at the shipped defaults, hit@1/8/50
0/6 - 0/6 - 0/6 to 3/6 - 5/6 - 6/6) are both landed. This commit adds no
functionality: it sets the version, closes the CHANGELOG entry, and points
every install line at the new tag.

- `pyproject.toml` and `src/llm_ingestion_okf/__init__.py`: 0.7.0 -> 0.8.0.
  The second is the only line in `src/` this release touches. It is not a
  code change but the other half of the version, written without a `v`
  prefix, so a search for `v0.7.0` cannot find it;
  `test_packaging.py::test_the_declared_version_agrees_with_the_packaged_one`
  is what did. Left alone, the tag would report the previous release to every
  consumer that installs it.
- `CHANGELOG.md`: `[Unreleased]` becomes `[0.8.0] - 2026-09-10`, with a new
  empty `[Unreleased]` above it. The entries are round 13's and round 14's own
  words, unchanged. No compare link is added: this file has carried none since
  `[0.6.0]`, and inventing one here would be a claim about a URL nobody checked.
- The five install lines and the two prose lines naming the current tag move to
  `v0.8.0`. The tag history list gains a `v0.8.0` row as the current tag and
  KEEPS the `v0.7.0` row: that list states it is not install lines, so a
  rewrite would delete history rather than update it.
- README's test count was 1515, measured 2026-09-09; this tree measures 1575
  passed / 1 skipped with ruff 0.16.6. The surrounding sentence about the
  earlier figure is repaired too, because changing the date alone would have
  made it false.

`v0.7.0` stays on 1260fac. No lock change, no history rewrite in `docs/`.

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

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.0] — 2026-09-10
+
 ### Added
 
 - **A section the SOURCE DECLARES now takes the route declared structure takes,

README.md

@@ -9,7 +9,7 @@ call anywhere in the run path.
 Python 3.10+ and [uv](https://docs.astral.sh/uv/). One line:
 
 ```sh
-uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.7.0"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.0"
 ```
 
 ## Use it
@@ -59,11 +59,11 @@ Neither this package nor the guard it depends on is on a package index yet, so
 both install by direct reference. With uv, one command resolves both:
 
 ```sh
-uv pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.7.0"
+uv pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.0"
 ```
 
 uv resolves the guard on its own, because it reads the `[tool.uv.sources]`
-entry in the `pyproject.toml` **of the tag it is installing**, and `v0.7.0`
+entry in the `pyproject.toml` **of the tag it is installing**, and `v0.8.0`
 points that entry at `llm-ingestion-guard` `v1.3.0`. Use `uv tool install`
 instead of `uv pip install` when you want the `okf` command on `PATH` without an
 active virtualenv — that is the form the first screen shows.
@@ -74,10 +74,10 @@ With plain pip, the transitive git dependency does not resolve on its own —
 
 ```sh
 pip install "llm-ingestion-guard @ git+https://git.fromaitochitta.com/open/llm-ingestion-pipeline-security.git@v1.3.0"
-pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.7.0"
+pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.0"
 ```
 
-The guard tag is paired to the okf tag, not to this branch. `v0.7.0` declares
+The guard tag is paired to the okf tag, not to this branch. `v0.8.0` declares
 `llm-ingestion-guard>=1.2,<2.0`, which `v1.3.0` satisfies; the pairing above is
 read off that tag's own `[tool.uv.sources]`, not off this branch. Reading a pin
 off `main` and installing it against an older okf tag is the one combination
@@ -88,9 +88,14 @@ that fails.
 These are not install lines. They record what each earlier tag was, so a reader
 who meets one in an older document knows what they are looking at.
 
-- `v0.7.0` — the current tag: `okf project` builds the bundle `okf build`
-  builds (they were one flag apart before it), and the generated skill states
-  the question, hypothesis and document-task modes with relative paths.
+- `v0.8.0` — the current tag: `.xml` is a core file type, read as NISO-STS
+  through the stdlib parser, and a section the source DECLARES takes the
+  declared-structure route — one publisher's process code segments at 2 761 of
+  2 761 of its own declared sections at the shipped defaults. No other file
+  type changes one byte, measured on the bytes.
+- `v0.7.0` — `okf project` builds the bundle `okf build` builds (they were one
+  flag apart before it), and the generated skill states the question,
+  hypothesis and document-task modes with relative paths.
 - `v0.6.0` — the first tag carrying the `okf project`, `okf consume`,
   `okf check` and `okf skill` subcommands.
 - `v0.5.0a2` — a pre-release for the named OKF v0.2 pilot set only.
@@ -449,7 +454,7 @@ not need this repository — the first line installs the command, the second
 builds the bundle and writes a skill beside it, the third asks.
 
 ```sh
-uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.7.0"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.0"
 okf project ~/my-documents
 claude
 ```
@@ -759,10 +764,12 @@ From a checkout, the test suite runs with:
 .venv/bin/python -m pytest
 ```
 
-The suite is the verification surface for everything above: **1515 tests**,
-run on 2026-09-09 against this branch with the `[extract]` extra installed.
-(The figure published here until that day was 596, measured 2026-08-21 and
-never updated as the suite grew — a count is a measurement with a date on it.)
+The suite is the verification surface for everything above: **1575 tests**,
+run on 2026-09-10 against the `v0.8.0` release commit with the `[extract]`
+extra installed.
+(The figure stood at 596 until 2026-09-09 — measured 2026-08-21 and never
+updated as the suite grew — and at 1515 until this release: a count is a
+measurement with a date on it.)
 Without the extra the same suite skips the tests covering the parser path;
 that split was last counted on 2026-08-21 as 589 passed and 7 skipped and has
 **not** been re-measured since. The tests holding the fail-fast rejection for

llms.txt

@@ -6,7 +6,7 @@ Requires Python 3.10+ and [uv](https://docs.astral.sh/uv/). Neither this package
 nor the guard it depends on is on a package index yet; one command resolves both:
 
 ```sh
-uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.7.0"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.0"
 ```
 
 Then, in the folder you want to work from:

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "llm-ingestion-okf"
-version = "0.7.0"
+version = "0.8.0"
 description = "Shared OKF (Open Knowledge Format) ingestion library: spec-based connectors, bundle inbox, and external-bundle import, with security delegated to llm-ingestion-guard."
 readme = "README.md"
 license = "MIT"

src/llm_ingestion_okf/__init__.py

@@ -76,7 +76,7 @@ from .manifest import (
 )
 from .materialize import IngestResult, materialize_bundle
 
-__version__ = "0.7.0"
+__version__ = "0.8.0"
 
 __all__ = [
     "BlockedFile",