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

pyproject.toml

@@ -22,7 +22,17 @@ classifiers = [
 # against a package index, and is satisfied today by the git+https tag
 # install documented in the README (a direct reference is an install-time
 # channel, not a dependency declaration).
-dependencies = ["llm-ingestion-guard>=0.3,<0.4"]
+#
+# Floor 1.2, not the 1.0.0 freeze: this library needs the flow-mapping
+# frontmatter support (`generated: { by: x, at: y }`) that landed in the
+# guard's 1.2.0, without which Door C fail-secures every concept carrying
+# it. Ceiling <2.0, not a narrower minor: the guard's own 1.0.0 release
+# promises no exported name is removed, renamed or given a different
+# meaning short of a 2.0.0 — calibration (severities, dispositions) is
+# explicitly free to move within 1.x under that same promise, so a tighter
+# ceiling here would claim a stability guarantee the guard does not need to
+# keep and we do not need to demand.
+dependencies = ["llm-ingestion-guard>=1.2,<2.0"]
 
 [project.optional-dependencies]
 # Binary file-type extraction parsers. OPT-IN ONLY: this extra pulls binary
@@ -94,10 +104,10 @@ ignore_missing_imports = true
 # both the failure and the two-command recovery).
 #
 # Either way the range above stays the pin, and the pin is per-tree: a wheel
-# built from THIS tree carries `Requires-Dist: llm-ingestion-guard<0.4,>=0.3`,
-# measured 2026-08-21 against the built wheel. The `<0.3,>=0.2` this comment
-# carried before was the `v0.4.0` tag's range — still true of that tag, never
+# built from THIS tree carries `Requires-Dist: llm-ingestion-guard<2.0,>=1.2`,
+# measured 2026-08-23 against the built wheel. The `<0.4,>=0.3` this comment
+# carried before was the `v0.3.4` tag's range — still true of that tag, never
 # true of this tree. Reading a range off one and installing it against the
 # other is the one combination that fails.
 [tool.uv.sources]
-llm-ingestion-guard = { git = "https://git.fromaitochitta.com/open/llm-ingestion-pipeline-security.git", tag = "v0.3.4" }
+llm-ingestion-guard = { git = "https://git.fromaitochitta.com/open/llm-ingestion-pipeline-security.git", tag = "v1.2.0" }