fix: gate reporting checkpoints in ultra-flow-route and release-route

[LeXwDeX]

Blocked by: LeXwDeX/OpenCode-GraphAgent#320 (runtime authoring enforcement; runtime-compat.json bump waits for the merged runtime SHA)

Problem

The runtime is about to reject report_to_parent checkpoints whose dependents are not gated by a condition on the checkpoint output (authoring-enforced; see runtime issue #320 and the 2026-08-17 incident where an ungated ultra flow ran to completion after every decision gate returned replan).

Audit of this repo's curations found exactly two affected shapes:

1. ultra-flow-route.yaml — all five checkpoint→stage edges ungated (cp-after-exploration→stage-design, cp-design-decision→stage-development, cp-after-development→stage-acceptance, cp-acceptance-decision→stage-release, cp-after-release→stage-summary). This template produced the incident graph.
2. release-route.yaml — release-execute depends on release-gate (report_to_parent: true) with no condition: the release would auto-execute the moment the human gate node settles, regardless of verdict.

Fix (grill-settled)

• Add condition gates on each checkpoint's verdict output (backward compatible — runs correctly on current and older runtimes, so this can land BEFORE the runtime PR).
• release-execute condition: proceed on the gate's accept-verdict (graph stays whole; human adjudication stays in the gate child session).
• After runtime #320 merges: bump runtime-compat.json to the merged full-runtime commit SHA and pass template-validation CI.

Acceptance

• Both YAMLs pass the new authoring validation (no ungated-checkpoint diagnostics) and template-validation CI
• Gate verdict vocabulary taken from each checkpoint's own output_schema/prompt (verify per file; do not invent verdicts)

[LeXwDeX]

Done: ultra-flow-route + release-route gated (PR #15, merge 35df8cd), runtime-compat bumped to b48dce469 with template validation green (PR #16).