chore(release): prepare 1.1.1 — version sync and changelog

Patch release. It adds no capability over 1.1.0 and changes no package
behaviour. What changes is that the fixtures, tests, tools and documents use
generic, fictitious examples. Help text reworded in `okf build --assets`,
`--pdf-outline` and the `okf quality --fasit` provenance line, and the
`--fasit` bar is written as the round share 999/1000.

The version is synced in pyproject.toml, src/llm_ingestion_okf/__init__.py,
uv.lock (uv lock --check clean), README (install lines and the tag list) and
CHANGELOG. No tag: the operator tags.

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

README.md

@@ -10,7 +10,7 @@ types](#supported-file-types) lists each one with the evidence behind it.
 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@v1.1.0"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v1.1.1"
 ```
 
 ## Use it
@@ -209,11 +209,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[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v1.1.0"
+uv pip install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v1.1.1"
 ```
 
 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 `v1.1.0`
+entry in the `pyproject.toml` **of the tag it is installing**, and `v1.1.1`
 points that entry at `llm-ingestion-guard` `v1.4.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.
@@ -224,10 +224,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.4.0"
-pip install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v1.1.0"
+pip install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v1.1.1"
 ```
 
-The guard tag is paired to the okf tag, not to this branch. `v1.1.0` declares
+The guard tag is paired to the okf tag, not to this branch. `v1.1.1` declares
 `llm-ingestion-guard>=1.2,<2.0`, which `v1.4.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
@@ -238,7 +238,10 @@ 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.
 
-- `v1.1.0` — the current tag. The reading side: BM25 ranking on passages and
+- `v1.1.1` — the current tag. No capability over `v1.1.0`: sector-specific
+  example material in fixtures, tests, tools and documents is replaced by
+  generic, fictitious examples. See the CHANGELOG.
+- `v1.1.0` — the reading side: BM25 ranking on passages and
   titles, several sub-questions in one call, a map per bundle, a signal for
   weak coverage, and one generic skill plus the server as the standard way in
   over a whole folder of bundles. The payload contract is `okf-consumption/2`,
@@ -1273,7 +1276,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@v1.1.0"
+uv tool install "llm-ingestion-okf[extract] @ git+https://git.fromaitochitta.com/open/llm-ingestion-okf.git@v1.1.1"
 okf project ~/my-documents
 claude
 ```