idd-skill: Instructions file for GitHub Copilot

IDD — Merge Policy Handoff Phase (F2.5)

Read this file after idd-pre-merge.instructions.md (F2) satisfies all pre-merge conditions. It decides whether the current session can proceed to merge execution or must stop and hand off.

Before any mutating action in this phase, apply the claim revalidation gate. If an active claim exists, it must still use your current {claim-id}. If no active claim exists, continue only for the designated separate_merge_agent actor path or the fully_autonomous_merge policy path (see Step 1); all other paths must stop and report.

F2.5 — Resolve merge policy route

1. Confirm claim ownership context:
   • If an active claim exists, it must still use your current {claim-id}. If it is held by a different {claim-id} (even under the same agent ID), the claim was lost — report this and stop.
   • If no active claim exists, continue only for the designated separate_merge_agent actor path in step 5, or the fully_autonomous_merge policy path in step 6. Other paths must stop.
2. Read the repository's recorded merge policy from repository documentation that future IDD sessions read. If no policy is recorded, treat it as human_merge (distributed default).
3. If the recorded value is not one of fully_autonomous_merge, human_merge, or separate_merge_agent, treat it as an unknown merge policy: stop, post a hold comment, and request maintainer decision.
4. If the recorded policy is human_merge, stop before the final freshness fetch and before gh pr merge. After claim revalidation, post a concise handoff summary comment that includes:
   • PR number and branch
   • full F2 snapshot ({f2-head-SHA}, {f2-max-activity-updatedAt}, {f2-total-item-count}, {f2-latest-ci-completed-at|none})
   • the F2 readiness evidence
   • unresolved-thread count, advisory state, and CI state
   • active {claim-id}
   • merge command candidate: