From 315b25869c26da1878684b4ee8b3033fdf4b5dae Mon Sep 17 00:00:00 2001 From: Arjit Jaiswal Date: Mon, 28 Sep 2026 18:14:12 -0400 Subject: [PATCH 1/2] docs: verify linked issue closure after merging --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 7a96bc3..2aa075e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -26,6 +26,7 @@ For repository changes, carry the work through validation, public PR review, and 2. Request Copilot review and use `address-copilot-review` to assess every finding, verify and push appropriate fixes, publish replies, and resolve addressed threads. Confirm replies are submitted rather than pending. If Copilot is unavailable or quota-limited, record that fact; do not treat it as an approval or wait indefinitely. 3. Run the project-local [verify-open-pstack skill](.agents/skills/verify-open-pstack/SKILL.md) against the final candidate. Complete the applicable installed-parent or maintenance checks above and record observed results in the PR. Revalidate behavior affected by review fixes. 4. Once required checks and applicable validation pass and review findings are addressed, squash merge the PR using a server-enforced expected-head SHA. Verify the resulting merge into `main`. +5. After merging, check linked issues, close those fully resolved by the PR, and verify their closed status on GitHub; leave issues with outstanding work open. Proceed autonomously through routine fixes and retries justified by evidence. Existing validation gates and explicit restrictions on credentials, spending, or other actions still apply. When a required check cannot run, document the concrete blocker, complete independent work, and leave the affected PR unmerged. Do not replace a missing live test with a unit-test or source-inspection claim. Tags, releases, and installation changes outside validation require their own task scope. From 92be5f85730520aaccc95d51306f873209f745a1 Mon Sep 17 00:00:00 2001 From: Arjit Jaiswal Date: Mon, 28 Sep 2026 18:14:38 -0400 Subject: [PATCH 2/2] docs: report issues left open after merge --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 2aa075e..899a43b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -26,7 +26,7 @@ For repository changes, carry the work through validation, public PR review, and 2. Request Copilot review and use `address-copilot-review` to assess every finding, verify and push appropriate fixes, publish replies, and resolve addressed threads. Confirm replies are submitted rather than pending. If Copilot is unavailable or quota-limited, record that fact; do not treat it as an approval or wait indefinitely. 3. Run the project-local [verify-open-pstack skill](.agents/skills/verify-open-pstack/SKILL.md) against the final candidate. Complete the applicable installed-parent or maintenance checks above and record observed results in the PR. Revalidate behavior affected by review fixes. 4. Once required checks and applicable validation pass and review findings are addressed, squash merge the PR using a server-enforced expected-head SHA. Verify the resulting merge into `main`. -5. After merging, check linked issues, close those fully resolved by the PR, and verify their closed status on GitHub; leave issues with outstanding work open. +5. After merging, check linked issues, close those fully resolved by the PR, and verify their closed status on GitHub; report any issue left open to the user with the reason and remaining work. Proceed autonomously through routine fixes and retries justified by evidence. Existing validation gates and explicit restrictions on credentials, spending, or other actions still apply. When a required check cannot run, document the concrete blocker, complete independent work, and leave the affected PR unmerged. Do not replace a missing live test with a unit-test or source-inspection claim. Tags, releases, and installation changes outside validation require their own task scope.