generate-harness-dsl

# Generate Harness DSL Create a standalone Harness as Code v0.3 document and prove the execution contract with the package compiler and resolver. ## Workflow 1. Identify the host, the capabilities it must actually expose, and the real control owner. Use `session` for one host session. Use `state-machine` or `program` only when a selected adapter explicitly implements that mode. 2. Read [the DSL contract](references/dsl-contract.md). Start from [the minimal example](../../examples/minimal.harness); open [the standard example](../../examples/standard-coding.harness) when callable tools are required. 3. Generate one self-contained document unless the user requests a fragment. Include `language 0.3`, every referenced declaration, a concrete runtime, and a named deployment. Standard tools may remain implicit. 4. Run `scripts/validate.mjs`. Fix every compiler or resolution error and rerun. A compile-only state machine is not an executable Qoder or Pi deployment. 5. Return the DSL or saved file plus the harness id, deployment id, runtime, resolution status, and any execution boundary the selected adapter cannot satisfy. ## Authoring Rules - State only falsifiable requirements. Do not add permission, setting, degradation, binding, input/output-name, or runtime-execution syntax; v0.3 intentionally has none. - Match the requirement verb to its capability: `use skill`, `require tool`, or `connect mcp`. - Only the standard tool ids in the contract...