docs: remove exploration leftovers (handover, audit, glossary)

CONTRIBUTING.md

@@ -86,8 +86,7 @@ them on a private corpus without copying it into the repository, are described i
   functions live in the one `utils/` folder of their module (`domain/document/utils/moddle.ts`,
   `domain/document/utils/fuzzy.ts`); a utils file holds no class and imports only other utils files and
   error classes. Outside the entries (`api.ts`, `index.ts`, `node.ts`, which keep the
-  package's public functions and delegate to the classes) there are no free functions. The
-  domain terms the classes are named after are in [GLOSSARY.md](GLOSSARY.md).
+  package's public functions and delegate to the classes) there are no free functions.
 - `test/`: the vitest suite. Its folders mirror the module folders of `src/`
   (`test/domain/batch/`, `test/adapters/in/cli/`, ...): a test sits with the module whose
   interface it exercises. Black-box tests through the entries and the CLI are in `test/e2e/`,

docs/.vitepress/config.ts

@@ -15,7 +15,7 @@ export default miragonDocs({
   footerMessage: "Released under the MIT License.",
 
   // Notes for maintainers, read on GitHub: not pages of the site.
-  srcExclude: ["releasing.md", "testing.md", "audit-2026-10.md"],
+  srcExclude: ["releasing.md", "testing.md"],
 
   nav: [
     {

docs/testing.md

@@ -31,9 +31,6 @@ rename flows as by default, and the fuzzer, the benchmark, the layout
 regression and the demo run the CLI without it (`CLI_ENV` in
 `tools/fuzz/lib/setup.mjs`). A test that needs it sets it for its own spawn.
 
-The audit that motivated this tooling is summarised in
-[audit-2026-10.md](audit-2026-10.md).
-
 ## Invariants
 
 The fuzzer and the property test check after every step
@@ -408,8 +405,7 @@ npx vitest run test/e2e/isomorphic.test.ts
   entry chunk is the output whose metafile `entryPoint` is the requested
   entry (esbuild gives every `import()` target an `entryPoint` too).
   esbuild itself never shows the hang (it puts shared modules into chunks
-  of their own); the check models what Rollup does, and the Vite run in
-  HANDOVER.md ("Profile rules on demand") proved it in Chrome.
+  of their own); the check models what Rollup does.
 - `test/e2e/isomorphic.test.ts` bundles `src/index.ts` the same way (no build
   needed), checks that the check sees a planted `node:fs` import and
   `process` read, and runs the bundle in a `vm` context without any Node
@@ -696,8 +692,7 @@ one message name at the same time.
 The other C7 regression tests (`test/domain/editing/c7-semantic.test.ts`,
 `test/domain/editing/c7-ext-structure.test.ts`, `test/e2e/camunda7.test.ts`,
 `test/domain/editing/c7-ops.test.ts`) run without engines; their engine evidence (deploy and run the CLI-built models, real
-customer files before and after edits) was collected outside the repository,
-see [audit-2026-10.md](audit-2026-10.md#camunda-7-audit-2026-10-09). When you
+customer files before and after edits) was collected outside the repository. When you
 change how vendor content is written, build a small model with the CLI, deploy
 it to a Camunda 7 compatible engine and run it (start, fetch-and-lock /
 complete, correlate), and run the real-file battery on your private corpus:

test/domain/diagram/incremental-audit.test.ts

@@ -1,6 +1,6 @@
 /**
  * Audit bugs of the incremental layout fixed with the layout
- * ergonomics package (docs/audit-2026-10.md):
+ * ergonomics package:
  *  - #41 a data object or annotation drawn in a lane follows the lane when
  *    the space tool moves it (it has no lane membership of its own)
  *  - #42 closing a strip inside a sub-process never puts a boundary event

test/e2e/fuzz.test.ts

@@ -63,8 +63,7 @@ const WALKS = [
 ];
 
 /**
- * Walks that currently hit open bugs of the 2026-10 audit (`bug` = the number
- * in the table of docs/audit-2026-10.md). They are expected to fail; when a fix
+ * Walks that currently hit open layout bugs (`bug` = the issue they reproduce). They are expected to fail; when a fix
  * makes one pass, vitest reports it and the walk moves into WALKS.
  */
 const KNOWN: Array<{ file: string; mode: Mode; seed: number; steps?: number; bug: string }> = [];