Spec: OpenSCAD work needs vision, in nisse-dev or its own agent

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/Architecture-Build-Spec.md

@@ -1427,7 +1427,8 @@ The rest resolve when reached, not now.
     needs one model good enough as the dev executor and for ops' Home Assistant
     tool calls. The executor benchmark and the ops evaluation decide whether one
     exists. More agents are planned for other jobs, which makes one shared model
-    more valuable still, and some of them may add vision (next item).
+    more valuable still, and OpenSCAD and video work would add vision (next
+    item).
   - **Fallback: agents tag in and out.** If no single model fits, the agents
     coordinate their use of the host rather than interleave: an agent holds the
     host for a stretch of work on its model, then hands it over, so a swap happens
@@ -1435,9 +1436,11 @@ The rest resolve when reached, not now.
     groups), where VRAM allows, can reduce how often that's needed. How the
     hand-over works (a lease, a queue, or priority for ops alerts) is only worth
     designing if the preferred option fails.
-- **Parked: vision, for future agents.** More agents are planned for other kinds
-  of jobs, and some will need vision: checking OpenSCAD renders against a design,
-  or managing video files. Neither current agent needs it. The local candidates on
+- **Parked: vision.** OpenSCAD development needs it: the language describes 3D
+  parts, and the only way to check a change is to render it and look. That work
+  may belong to `nisse-dev` or, being different enough from ordinary code, to an
+  agent of its own; undecided. Video-file management, planned for a future
+  agent, needs it too. Ordinary code work doesn't. The local candidates on
   the 4090 host already accept images, and video as sampled frames, but the agent
   code is text-only. Building it will need tools that return images, image content
   in canonical events (A10) and both renderers, storage that keeps the durable log