opencode-harness-loop

Use ONLY when a phase needs a tool that is not yet wired up — most often a headless browser to capture a screenshot for visual/perceptual verification of a UI. Synthesizes the MCP server on demand (in an isolated container), registers it in opencode.json, validates it, and notes credential placeholders. Not for MCPs already present in the manifest.

Use when creating, authoring, or optimizing an opencode skill (a SKILL.md procedure) — including when a phase keeps re-deriving the same how-to and you want to capture it. Guides an evaluation-driven workflow: interview, draft, generate trigger tests, install only the validated version.