build(deps): move the guard pin from >=0.3,<0.4 to >=1.2,<2.0

The operator's condition for revisiting the pin was met (v1.2.0 contains
the flow-mapping frontmatter fix, commit 5870483) and the operator has now
approved the move itself, dispatched as its own order because it changes
consumer-visible Requires-Dist and shifts golden-fixture admission.

Floor 1.2: this library needs the flow-mapping support (`generated: { by:
x, at: y }`) that landed there — without it Door C fail-secures every
concept carrying that stamp. Ceiling <2.0, not narrower: the guard's own
1.0.0 release freezes its exported surface until a 2.0.0, and explicitly
keeps calibration (severities, dispositions) free to move within 1.x, so a
tighter ceiling here would claim a stability guarantee neither side needs.

Re-measured through Door C against the guard's own default
(allow_reserved=True, matching how the earlier recommendation measured
it), over the 9 concept documents across all four Door-A goldens:
4/9 admitted at 0.3.4 -> 8/9 admitted at 1.2.0, confirming the number
already reported. The ninth (a `sources` block-list carrying `resource`)
stays refused by design (G30) and is not expected to move.

Failing-test-first: test_guard_adapter.py::test_guard_version_is_inside_the_pin
and test_packaging.py::test_the_only_runtime_dependency_is_the_security_boundary
were updated to the new pin first and confirmed red against the
still-installed 0.3.4, then `uv sync --extra extract` installed 1.2.0 and
both went green. Full suite (615), ruff and mypy --strict clean.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RxcxzNwpX1kDP53n1rLhM5

README.md

@@ -42,7 +42,7 @@ pip install "llm-ingestion-okf @ git+https://git.fromaitochitta.com/open/llm-ing
 
 The guard tag is paired to the okf tag, not to this branch: `v0.4.0` declares
 `llm-ingestion-guard>=0.2,<0.3`, which `v0.2.0` satisfies and later guard tags
-do not. `main` has since moved its own pin to `>=0.3,<0.4` (see
+do not. `main` has since moved its own pin to `>=1.2,<2.0` (see
 [Requirements](#requirements)); that pin reaches you in the next stable tag,
 not in the commands above. Reading a pin off this branch and installing it
 against `v0.4.0` is the one combination that fails.
@@ -75,7 +75,7 @@ bundle:
 
 Security is owned by the sibling package
 [`llm-ingestion-guard`](https://git.fromaitochitta.com/open/llm-ingestion-pipeline-security)
-(pinned `>=0.3,<0.4`). The division is strict:
+(pinned `>=1.2,<2.0`). The division is strict:
 
 - **guard** answers "is this content safe to persist?" — scan, sanitize,
   quarantine, fail-secure, provenance stamping.
@@ -239,7 +239,7 @@ structure from either.
 ## Requirements
 
 Python 3.10+, and exactly one runtime dependency — the security boundary,
-`llm-ingestion-guard>=0.3,<0.4`. Everything else is stdlib. The commands are
+`llm-ingestion-guard>=1.2,<2.0`. Everything else is stdlib. The commands are
 under [Install](#install); what follows is why they look the way they do.
 
 From a checkout, the test suite runs with:
@@ -259,7 +259,7 @@ clone rather than a `pip install`.
 A git URL is a PEP 508 direct reference and pins one exact tag, so it is an
 install-time *channel*, not the pin: the range above stays the declared
 dependency — a wheel built from this branch carries `Requires-Dist:
-llm-ingestion-guard<0.4,>=0.3`, measured 2026-08-10 — and resolves normally
+llm-ingestion-guard<2.0,>=1.2`, measured 2026-08-23 — and resolves normally
 once the package index exists. A wheel built from a *tag* carries that tag's
 range instead, which is why the install commands pair tag with tag.