deliver

Provide the ticket, specification, or agreed plan as the authoritative request. The pipeline runs preflight, test-driven implementation in vertical slices, two independent read-only review passes, and the repository's final validation command before reporting a classified outcome.

Every actionable Required finding returns to implementation, including formatting, naming, and typing issues; review never edits files directly. After fixes, both review passes rerun, with at most two correction cycles before the pipeline stops and asks for conflict resolution.

Yes, a Godot profile loads automatically when project.godot, GDScript, or scene files are detected. It enforces typed GDScript, native documentation comments, scene authoring rules, and progressive Godot feedback including parsing, scene instantiation, and focused tests.

A missing validation command does not block implementation. If implementation and both reviews pass, the result is classified as Unverified, and the report names the missing validation interface plus the focused proof that did run.

No, commit and push authority defaults to false and is never inferred from repository guidance or earlier automation. Only an explicit instruction from the current user permits committing or pushing, and an explicit refusal always wins.