Bump to OCCT 8.0.1

Four mechanical binding edits; the bound Python surface is unchanged
(sigdiff compared the 7.9.3.1 dump against 8.0.1.1's in both directions
and found no class, member or constructor arity moved), so the app needs
no change.

- NCollection_Utf8String is gone; NCollection_String is the same UTF-8
  type. Python name kept, since the app imports it.
- Standard_Failure lost its Standard_Transient RTTI when it moved to
  deriving std::exception; ExceptionType() replaced DynamicType()->Name()
  and returns the same class names the exception dispatch keys on.
- FindKey gained a size_t overload beside the int one, so the plain
  member pointer is ambiguous; overload_cast picks the int form, which
  keeps the negative-index guard.
- StdPrs moved from TKService to TKV3d, so CMakeLists links both.

The byte-identity fixtures did NOT retire, contrary to the watchlist:
all six round-trip to the same digests under the new kernel, as do the
measurement, history and mesh-count blocks, so tests/data is untouched
and the app's content-addressed BREP payloads stay valid.

Gates: binding suite 83 passed, 138/138 symbols, sigdiff clean both
directions, ASAN clean, app suite 1798 passed / 1 skipped (unchanged),
sweep over 4486 parts with anchors_digest and every status unchanged,
-m perf 16% faster on the 32-feature chain.

README.md

@@ -7,14 +7,16 @@ backend uses — 138 symbols across 47 `OCP.*` modules, not all of OCCT.
 The package installs as a top-level `OCP`, so it is a drop-in replacement for
 `cadquery-ocp-novtk` and the app's 442 import sites stay untouched.
 
-Status: **coverage complete** — all 138 symbols the app imports, across 53
-bound modules, published as `7.9.3.1.dev5`. The app's full backend suite passes
-against it (1797 passed / 1 skipped, the same as the stock wheel), a sweep of
-the whole project store reproduces every part's geometry exactly (4486 parts;
-no change in statuses, volume, area, bbox, entity counts, triangles or anchor
-digests), and BREP serialisation stays byte-identical, which the pools and the
-content-addressed derive payloads depend on. The app is not swapped yet — that
-is the cutover, roadmap 10C.
+Status: **in production use** — all 138 symbols the app imports, across 53
+bound modules, published as `8.0.1.1` (OCCT 8.0.1). The app cut over on
+2026-08-10 at `7.9.3.1` and took the kernel bump on 2026-08-11; its full
+backend suite passes against both (1798 passed / 1 skipped, the same as the
+stock wheel it replaced), a sweep of the whole project store reproduces every
+part's geometry exactly (4486 parts; no change in statuses, volume, area,
+bbox, entity counts, triangles or anchor digests), and BREP serialisation
+stays byte-identical, which the pools and the content-addressed derive
+payloads depend on — across the kernel bump as well, so nothing stored had to
+be rewritten.
 
 Start with [docs/design.md](docs/design.md) for the decisions,
 [docs/building.md](docs/building.md) to build one, and
@@ -24,7 +26,7 @@ phase plan lives in the app repo at `docs-private/reference/roadmap.md`
 
 ## Why
 
-`cadquery-ocp` lags OCCT (it wraps 7.9.3; OCCT 8.0 shipped 2026-05), builds
+`cadquery-ocp` lags OCCT (it still wraps 7.9.3; we are on 8.0.1), builds
 Windows and macOS wheels we never use, and until recently forced a 638 MB VTK
 dependency into the image. So this exists for version velocity, footprint, and
 two defects that a binding we control prevents by construction:
@@ -54,7 +56,7 @@ production host (4 cores, and a kernel build is multi-hour). Wheels are built
 here on a dev box and published to the Gitea package registry.
 
 ```bash
-make image    # once, ~40 min: compiles OCCT 7.9.3 into the builder image
+make image    # once, ~40 min: compiles OCCT 8.0.1 into the builder image
 make dev      # inner loop: incremental compile + tests
 make wheel    # compile, stubs, auditwheel, self-containment smoke test
 make publish  # -> https://git.stroblme.de/api/packages/N3XD/pypi