Govern task context and advance execution pointer

docs/status/M16-GAP-00015.md

@@ -0,0 +1,25 @@
+# M16-GAP-00015 Status
+
+status: done
+task: MetaBall data-block LOCAL_EXACT slice
+updated: 2026-08-19 America/New_York
+
+scope: Blender 5.2 MetaBall element metadata: point count, element positions, radii and anisotropic scale values.
+
+evidence:
+
+- `tools/web/generated/M16-GAP-00015.py` generated one `WebGapMetaBall` data-block with two deterministic elements and a linked object.
+- Desktop report reopened after save and matched exactly: two elements at `[-0.65, 0, 0.4]` and `[0.65, 0, 0.4]`, radii 0.75/0.55 and scales 1.1/0.9/1.2 and 0.8/1.05/0.95.
+- WASM/Main opened the same fixture with `geometryStatus=available`, matched both elements and pointCount, and save/reopen matched the full non-mesh snapshot exactly.
+- A truncated malformed Blend submitted to an already loaded Main was rejected and the original snapshot remained unchanged.
+- `build_blender_5.2.0/bin/blender -b --factory-startup --python tools/web/generated/M16-GAP-00015.py -- tests/files/web/generated/M16-GAP-00015-datablock-MetaBall.blend` exited 0.
+- `npm --prefix web run test:generated-gap -- --task M16-GAP-00015` exited 0.
+- `node tools/web/check-generated-gap.mjs --task M16-GAP-00015` exited 0.
+
+artifacts: `tests/golden/M16-GAP-00015/manifest.json` contains SHA-256 for the parent manifest, fixture, generator, desktop/Web checkers, reader/protocol/runtime and both reports.
+
+knownRisk: This closes one `datablock:MetaBall` metadata slice only. MetaBall editing/evaluation commands and all other generated gaps remain separate tasks.
+
+rollback: remove this task's fixture, checker, reports, manifest, status and context; restore `M16-GAP-00014` as the queue tail without editing its successful evidence.
+
+nextTask: `M16-GAP-00016`