chore(release): 0.8.1

A patch release carrying round 16's ranking rule and nothing else. No
behaviour changes in `src/`: the version string is the only line touched
there, and it is touched because it is the second half of the version --
`tests/test_packaging.py` holds `pyproject.toml`'s declaration and
`__init__.__version__` equal, and a tag whose package reports the previous
number lies to every consumer that installs it.

- `pyproject.toml` and `src/llm_ingestion_okf/__init__.py`: 0.8.0 -> 0.8.1.
- `CHANGELOG.md`: round 16's own entry closes as `[0.8.1]`, with a new empty
  `[Unreleased]` above it and no comparison link, because the file has
  published none since `[0.6.0]`. The entry gains one bullet it did not
  carry: the rule's MEASURED DOWNSIDE, reproduced here on a five-document
  folder -- a constructed known-negative question demotes the answering
  section from delivered rank 1 to rank 2 because a neighbouring concept
  titled with a single common process word has its WHOLE title accounted
  for. Written as a known limitation of short generic titles, not as a fix.
- The five install lines (`README.md` 4, `llms.txt` 1) move to `@v0.8.1`.
  Measured after: `okf.git@v0.8.0` 0 hits, `okf.git@v0.8.1` 5 hits as the
  known-positive control, and the two remaining bare `v0.8.0` occurrences
  are the tag-history row and the test-count history -- both are statements
  about the past and both stay.
- The tag-history list gains `v0.8.1` as the current tag and demotes the
  `v0.8.0` row to what it was; `v0.7.0` is untouched, and `docs/` is not
  rewritten at all.
- The test-count history sentence named the `v0.8.0` release as the last
  one and would have become false on this tag: it now records 1582 through
  `v0.8.1` as well. The published figures 1583 collected / 1582 passed /
  1 skipped were re-measured here and stand.

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.1] — 2026-09-10
+
 ### Added
 
 - **`--title-covered` (ON by default, opt out with `--no-title-covered`): a
@@ -60,6 +62,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     that one bundle, so "no regression" there means it never fires -- not that
     it fires harmlessly. Report:
     `docs/2026-09-10-k3-runde16-hele-tittelen-tar-ruten.md`.
+  - **A MEASURED DOWNSIDE, written as a known limitation and not as a fixed
+    defect: a SHORT, GENERIC title is covered in full by more questions than a
+    long one is.** On a five-document folder (26 concepts) a constructed
+    known-negative question demoted the answering section from delivered rank 1
+    to rank 2: a neighbouring concept titled with a single common process word
+    has its WHOLE title accounted for by that question, while the answering
+    section's longer title does not. The other seven delivered places did not
+    move. The repair is a later round's; nothing here narrows the rule, and the
+    opt-out is `--no-title-covered`.
 - `build_payload`'s signature defaults are now held equal to the consume CLI's
   argparse defaults by a test, for every same-named parameter. This is O6's
   defect in the other command: `cli.build` defaulted two flags `False` in the