STAGING-STATE: reconcile against the host, and close DIV-005 as recorded backwards

DIV-005 is withdrawn. It claimed requirements-cad.txt declared a CAD dependency set that was not installed. Verified in CT 100 today: cadquery and OCP both import from the venv. build123d does not, and correctly so - requirements-cad.txt names it as a viable alternative on the same OCCT kernel, not as an installed package. The file declares one requirement, cadquery greater-or-equal 2.4, and it is satisfied. The manifest and the container agree.

The false statement was in HANDOFF section 5, which said no CAD kernel is installed and that cadquery, OCP and build123d are all absent. True when written on 19 AUG, carried forward by hand for three weeks. STAGING-STATE section 5 recorded cadquery 2.8.0 in the venv for the same period. Two documents, each stating it as fact, disagreeing, and neither noticing.

The entry was recorded backwards: it named the manifest as diverging from the container when the container matched the manifest and a third document was wrong about both. Its evidence was a session record rather than an observation, which is why it carried do-not-close, and that marking is the only reason this was checked instead of acted on. The index note is corrected from three-of-six to two-of-six.

A roadmap item was deprioritised on the same false premise. HANDOFF section 4 listed STEP export as needing a CAD kernel that was not installed. It is installed.

STAGING-STATE section 5 opened with a transcribed repository block: HEAD at the seed commit c7e32d8, tests 3 passed and 236 skipped, and absent the Shapely port itself. All three were true on 18 AUG and none after 20 AUG, while the checklist directly below was kept current. Facts three weeks apart in one section, the maintained half lending credibility to the stale half. Removed rather than corrected. One line in it was still accurate - the venv cadquery 2.8.0 - and it was the only correct statement about the CAD kernel in the repository when it was deleted.

Section 3a said Kane Fabric is where SASE, HOA Diagnostics, the Mechanical Compiler and other SASE-consuming projects are implemented. Nothing here is implemented on Kane Fabric. Each project has its own FQDN and container and they share the bridge, the hub and the proxy. SASE was used and never defined anywhere in this repository. Section 3a also said no interface between the two projects exists and none is assumed; IDENTITY-CONTRACT.md specifies one.

Section 4 gave AllowedIPs on the hub peer entry for srv-b as 10.110.0.0/22, four paragraphs after correctly giving it as 10.110.0.12/32. The 22 is srv-b own AllowedIPs for the hub, recorded in section 1. The two ends of one tunnel were conflated, in the paragraph describing the security boundary. WORK-ORDER-004 section 0 settles it: all twenty peers carry a 32.

Also: the toolchain image box is ticked, verified present in CT 100. The baseline result is marked overdue against DIV-006. The Shapely port gates nothing. HANDOFF rewrap owed from 61b8f1e is applied.

Read-only verification was run before writing, per PROCESS section 2. Had it not been, this commit would have deleted the one true CAD statement and left the false one standing. Suite 643 passed, oracle intact. Documentation only.

docs/HANDOFF.md

@@ -170,11 +170,12 @@ internet → WireGuard → `srv-b` → containers. Containers cannot reach the h
 LAN and cannot send mail.
 
 `ct-baseline.sh` is read-only, runs any time, exits non-zero on divergence.
-Installed at `/usr/local/sbin/`. **Last run 2026-08-18: 62 passed, 0 failed —
-which predates the DNAT rule and the placeholder service replacement, both of
-which `PROCESS.md` §9a names as requiring a run. Overdue. See DIV-006.** **A property it
-does not check is not part of the standard** — that is what makes conformance
-terminate rather than recur.
+Installed at `/usr/local/sbin/`. **Last run 2026-08-18: 62 passed, 0 failed.**
+That predates the DNAT rule and the placeholder service replacement, both of
+which `PROCESS.md` §9a names as requiring a run, so it is overdue — see DIV-006.
+
+**A property it does not check is not part of the standard** — that is what
+makes conformance terminate rather than recur.
 
 **Settled decisions. Do not reopen any of these:**
 
@@ -350,8 +351,10 @@ Roadmap items — read `ROADMAP.md` before starting any:
   persist anything or show a bill of materials. `payload["defaults"]` is sent to
   the browser and nothing reads it — dead weight, and it is what made a
   verification grep lie on 11 SEP.
-- STEP export. Needs a CAD kernel and none is installed in CT 100 (§5).
-  STL needs none — a member is prismatic by definition. See §5.
+- STEP export. **The kernel is installed** — `cadquery` and `OCP` both import in
+  CT 100, verified 2026-09-13. This item sat low on the list partly because §5
+  said no kernel was present; it is closer than that implied. STL needs none —
+  a member is prismatic by definition. See §5.
 - `mechcomp-worker.service`. `src/mechcomp/worker/` is still a 36-byte stub and
   nothing needs a worker yet.
 - Nodes (non-prismatic) and panels (sheet). No representation exists for either.
@@ -439,9 +442,22 @@ Shapely 2.1.2 on GEOS 3.13.1 — keep these in step, boolean results on
 near-degenerate geometry can shift between GEOS releases. numpy 2.4.6. Shapely is
 in `requirements-base.txt`, the 2D path's own dependency set.
 
-**No CAD kernel is installed in CT 100.** `cadquery`, `OCP` and `build123d` are
-all absent, though `requirements-cad.txt` says it is installed by default. That
-is the strictest environment for developing the 2D path.
+**A CAD kernel is installed in CT 100.** `cadquery` and `OCP` both import from
+the venv — verified 2026-09-13 by `importlib.util.find_spec` under
+`/var/www/mechcomp/venv/bin/python`. `build123d` does not, and correctly so:
+`requirements-cad.txt` names it as a viable alternative on the same OCCT kernel,
+not as an installed package. The file declares one requirement, `cadquery>=2.4`,
+and it is satisfied.
+
+An earlier version of this paragraph said all three were absent. That was true
+when written on 19 AUG and was carried forward by hand for three weeks, while
+`STAGING-STATE.md` §5 recorded `cadquery 2.8.0` in the venv for the same period.
+Two documents, each stating it as fact, disagreeing. See DIV-005.
+
+**The 2D path must still import no CAD kernel**, and that is asserted by test —
+`ACCEPTANCE.md` E-8. Separability is enforced by the suite, not by the kernel
+being absent, and `requirements-cad.txt` says so itself: the suite must pass
+with that file absent.
 
 **STL export does not need one, and an earlier version of this section implied
 it did.** A member here is prismatic by definition — a 2D section swept along a