signalproof-build-spawn-debug

Define a bounded envelope with objective, allowed surfaces, automated gates, and STOP conditions, then iterate build, challenge, and debug cycles. Each retry against the same failure requires materially new evidence or a changed condition, otherwise the loop stops.

It is a coordinator that composes build, role-separated challenge, debug, verification, and learning steps for UI defects. Automated gates run first, and the human receives a USER UI TEST handoff only after all machine-verifiable checks pass.

Each failure gets a fingerprint with attempt count, ruled-out causes, and last material change. A new chat, filename, or cosmetic edit does not reset the identity, and three unsuccessful corrections against the same failure class route to investigation or STOP.

No. Invocation explicitly excludes production release, deployment, direct protected-main mutation, privilege escalation, and canonical ledger changes. Human UI PASS only authorizes the stated acceptance gate, not downstream release actions.

It stops when current Git state is unknown, the same-failure retry limit is reached, required verification is unavailable, an excluded authority class is needed, or recovery is no longer credible. A new attempt requires materially new evidence or a changed condition.