release(0.4.0): the raise is breaking, so the number says so

okf answered the exposure question with a measured no — zero call sites for the
three capped surfaces anywhere in their src/, and their screen_output path
reaches only scan_output, which truncates. So the blast radius is zero and 0.3.5
would have hurt nobody.

It is still 0.4.0. Adding a raise to a previously total public function is
breaking under SemVer, and this file declares SemVer; a survey that comes back
clean tells you the upgrade is easy, not that the contract held. The version
number describes the change, not the luck of who happens to call it.

Cost, stated: 0.4.0 was penciled in for the axis separation. That moves to 0.5.0.
Tags are never moved, so the choice is made once.

README still advertises v0.3.4 — it is updated after a clean-venv install proves
the tag resolves, so the install block never points at something unproven.

src/llm_ingestion_guard/__init__.py

@@ -61,7 +61,7 @@ from .grounding import (
 )
 from . import okf
 
-__version__ = "0.3.4"
+__version__ = "0.4.0"
 
 
 # --- §6 bookends: the two library-side halves around the transform ---------