enterprise-harness

name	enterprise-harness
description	Use when enterprise work has been built and reviewed and needs a final mechanical ship gate before merge, install, or release-level signoff

Enterprise Harness

Final quality gate for enterprise work.

Treat the harness as a fail-closed evidence gate. Schema, query, and data-sensitive changes need live/integration DB proof; UI/PDF/file changes need headless browser proof; every changed runtime file needs code execution proof, E2E trace proof, or a documented non-runtime reason.

When To Use

• before merge
• before installation of generated skills
• before calling a change ship-ready

Required Behavior

Run the checks in final-gate-checks.md as a fresh pass over the resulting artifacts, not as a recap of what build or review already said.

Before harness starts, run the agent-bound harness gate in agent-stage-gates.md.

Output

Produce a compact PASS, FAIL, or WARN verdict with exact failing checks and the blocking reason.