A patch request, a successful preflight, and a queued item are different facts. GDP treats apply as a local-policy decision and fresh repository evidence as proof of what happened.
Diagnose before material work
Patch Doctor is a non-writing diagnosis layer. It can normalize common unified-diff formatting problems, identify stale context, and explain why a patch should be regenerated. It should fail clearly instead of guessing code intent.
Understand intake versus apply
The AI prepares a focused unified diff for the exact open repository.
GDP runs patch preflight before accepting the change into intake.
A safe candidate enters repository-scoped review or automation intake.
The selected local policy decides whether it waits for review or continues through eligible automation.
GDP records the actual repository outcome and linked verification evidence.
queued=true is not apply evidence. Do not call a change applied until fresh GDP state proves it.
Keep the change reviewable
Prefer small coherent patches over unrelated bulk edits.
Keep the exact target repository visible.
Attach focused verification when the change has a testable contract.
If a mutation outcome is uncertain, reconcile that exact operation before retrying it.
