GDP can isolate selected paths from an incoming unified diff and apply only that subset. The remaining fragment stays reviewable when it can be persisted safely, while partial apply and Move Back keep different evidence and verification boundaries from a full patch apply or rollback snapshot restore.
Apply only the selected patch paths
Incoming Patch Input can represent multiple changed paths. When only a subset is checked, GDP attempts to isolate a valid patch for exactly those selected paths before writing. If the selected fragment cannot be isolated safely, apply is blocked rather than guessing which hunks belong to the selection.
GDP prepares rollback protection for the fragment that is about to be applied. A successful selected-path write is recorded as partial_apply when the original incoming patch still contains other paths.
Partial apply is a real repository mutation, but it is not equivalent to proving that the original complete incoming patch was fully applied.
Keep the unapplied remainder durable
After a selected-path apply, GDP derives the remaining unified diff for the unselected paths and saves that remainder back into the repository-scoped Incoming queue. The visible review then continues from the fragment that has not yet been applied.
If saving that remainder fails, GDP's durable queue binding preserves the authoritative pre-apply review record rather than popping it as though the whole incoming item were finished. The controller blocks full verification release and reports manual reconciliation or rollback when it cannot prove a safe remaining state.
Do not resend the whole original patch merely because some paths remain visible.
Read current Git diff and Incoming state to distinguish applied selected paths from still-pending paths.
Full attached patch verification is not released by a partial_apply operation.
Continue only from the remaining fragment after the partial state is reconciled.
Use Move Back as fragment reversal, not snapshot rollback
GDP Apply History can move an applied patch fragment back to Incoming. Move Back uses the recorded applied fragment to reverse that fragment from the working tree and then places the forward fragment back into review so it can be reconsidered or reapplied later.
That is different from Rollback History. Move Back operates from apply-history fragment evidence; Rollback restores a pre-write GDP safety snapshot for its covered state.
Confirm you are operating on the same repository and current fragment identity.
A stale or cross-repository move-back target should fail closed rather than changing another repository.
After Move Back, verify both current Git state and the restored Incoming fragment.
Do not count Move Back itself as proof that a later reapply or verification succeeded.
Keep full verification tied to full-apply evidence
GDP's attached patch-verification activation is eligible for durable full apply operations such as apply_patch and apply_all. Partial apply, ZIP import, and drag/requeue-style recovery are intentionally not treated as the same full-apply verification boundary.
This prevents a successful subset operation from making the entire original patch look verified. Use exact Apply History, Incoming state, and check-run evidence to prove each step that actually completed.
If the remaining fragment is still queued, the original patch workflow is still incomplete even when every check run for the already-applied subset is green.
