chore(release): 0.8.3

Tag K3-19 and K3-20 together: a NISO-STS document's own identity names
its directory and titles its sources entry, --frontmatter KEY=VALUE and
description from a section's first spec point, and the consume fix that
keeps a leading directory every concept id shares out of the first
fusion signal. K3-19 alone dropped the known-positive from rank 1 to not
delivered; K3-20 A is what makes the identity safe to ship.

Version 0.8.2 -> 0.8.3 in pyproject.toml, __init__.py and uv.lock (uv
lock changed that one line only). CHANGELOG [Unreleased] closed as
[0.8.3] with its five entries moved unchanged. Five install lines move to
@v0.8.3, the tag history gains a v0.8.3 row, and the suite count is
re-measured: 1668 collected, 1667 passed, 1 skipped.

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.3] — 2026-09-11
+
 ### Added
 
 - **`okf build --shell-parent` (K3-20), off by default.** A concept whose body

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.8.2"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.3"
 ```
 
 ## 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.8.2"
+uv pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.3"
 ```
 
 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.8.2`
+entry in the `pyproject.toml` **of the tag it is installing**, and `v0.8.3`
 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.8.2"
+pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.3"
 ```
 
-The guard tag is paired to the okf tag, not to this branch. `v0.8.2` declares
+The guard tag is paired to the okf tag, not to this branch. `v0.8.3` 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,7 +88,15 @@ 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.8.2` — the current tag: `okf check` refuses a skill and a payload that
+- `v0.8.3` — the current tag: a NISO-STS document's own `<doc-number>` names
+  its directory and titles its `sources` entry, `okf build --frontmatter
+  KEY=VALUE` stamps a key on every concept of a run, and an STS section's
+  `description` comes from its own first spec point. `okf consume` keeps a
+  leading directory every concept id shares out of its first fusion signal,
+  which is what keeps that identity from costing the answering section its
+  rank. `okf build --shell-parent` ships off; `okf check` still has sixteen
+  rules.
+- `v0.8.2` — `okf check` refuses a skill and a payload that
   name different bundles (`bundle_mismatch`, the checker's sixteenth rule;
   `v0.8.1` has fifteen), and a covered title no longer rises above a title
   that answers more of the question. No new command or flag; the shipped
@@ -549,7 +557,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.8.2"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.3"
 okf project ~/my-documents
 claude
 ```
@@ -873,16 +881,16 @@ From a checkout, the test suite runs with:
 .venv/bin/python -m pytest
 ```
 
-The suite is the verification surface for everything above: **1659 tests
-collected, 1658 passed and 1 skipped**, run on 2026-09-11 with the `[extract]`
+The suite is the verification surface for everything above: **1668 tests
+collected, 1667 passed and 1 skipped**, run on 2026-09-11 with the `[extract]`
 extra installed. Both numbers are given because they are two measurements: the
 figure published before the `v0.8.2` release was the PASSED count, and `pytest
 --collect-only -q` reported one more.
 (The figure stood at 596 until 2026-09-09 — measured 2026-08-21 and never
 updated as the suite grew — at 1515 until the `v0.8.0` release, at 1575
 through it, at 1582 through the `v0.8.1` release, at 1602 through the
-`v0.8.2` release, and at 1658 after K3-19: a count is a measurement with a
-date on it.)
+`v0.8.2` release, at 1658 after K3-19, and at 1667 after K3-20 and through
+the `v0.8.3` 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.8.2"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v0.8.3"
 ```
 
 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.8.2"
+version = "0.8.3"
 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.8.2"
+__version__ = "0.8.3"
 
 __all__ = [
     "BlockedFile",

uv.lock

@@ -547,7 +547,7 @@ source = { git = "https://git.fromaitochitta.com/open/llm-ingestion-pipeline-sec
 
 [[package]]
 name = "llm-ingestion-okf"
-version = "0.8.2"
+version = "0.8.3"
 source = { editable = "." }
 dependencies = [
     { name = "llm-ingestion-guard" },