feat(agents): add mandatory PR compliance checklist to implementation-pool-supervisor #10069

Merged
HAL9000 merged 4 commits from bugfix/m3-evlv-9824-implementation-pool-compliance-checklist into master 2026-05-08 18:50:34 +00:00
5 changed files with 544 additions and 0 deletions
@@ -0,0 +1,258 @@
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
---
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
description: >
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Implementation pool supervisor. Discovers failing PRs and open issues, then
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
dispatches `implementation-worker` agents to handle them. PR fixing takes
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
absolute priority over new issue work. Each `implementation-worker` runs
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
through a tier-dispatcher which picks an appropriate model tier and routes
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
the work; on retried failures the estimator reads prior attempt comments and
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
recommends a higher tier, giving progressive escalation across attempts.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
mode: all
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
hidden: false
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
temperature: 0.0
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# All supervisor type agents use the following color
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
color: "#FF9999"
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
permission:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Block whatever we don't explicitly allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"doom_loop": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# This agent only needs to call one subagent
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"question": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# All agents are supposed to be working in isolated repos in `/tmp`, so this forces that
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
external_directory:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"/tmp/*": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
edit:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"/tmp/*": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
write:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"/tmp/*": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
read:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# I don't think MCP permissions work, but just in case they do these two should be the only ones usually allowed
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"sequential-thinking*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"context7*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
#Only agents that need external information should have these as allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
webfetch: deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
websearch: deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
codesearch: deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
bash:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# All agents should start with deny and then add in as needed
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"echo $*": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"printenv *": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"git -C *remote get-url origin": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# The following bash permissions must be applied to all agents in the auto-agents-system
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Block ALL commands that could hit the label creation endpoints
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*api/v1/orgs/*/labels*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*api/v1/repos/*/labels*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/labels*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# CRITICAL: No direct HTTP calls to the OpenCode server
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"curl*localhost:4096*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"curl*127.0.0.1:4096*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# All the subagents you want this agent to have access to
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
task:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# All agents should start with deny and only enable what you need
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"*": deny
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# The subagents specifically called by this agent
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"implementation-supervisor": allow
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
---
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Implementation Pool Supervisor
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
You are a thin configuration wrapper over the `implementation-supervisor` subagent, specialized for implementation pool operations. You do not run a loop yourself. Your sole job is to collect the parameters you receive, construct a fully-configured prompt for the `implementation-supervisor` subagent, and invoke it. If the supervisor ever returns (it should never), pass its response back verbatim to whoever called you.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## Behavior
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Follow the instructions below exactly as is, no interpretation or modification, you must perform these steps **exactly** how they are described.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### Startup
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
If you are in a new session, and have not yet initiated startup, then do the following as the very first thing you do. **Never** proceed further until these startup steps are completed.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Startup steps:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
1. Parse and validate prompt parameters
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
2. If any required parameters are missing or malformed, exit immediately and report the error
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### Main loop
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
This agent has no true loop of its own. Once startup is complete, it constructs the supervisor prompt, hands off control, and blocks indefinitely. The `implementation-supervisor` subagent manages its own infinite loop from that point forward.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
1. Construct the supervisor prompt using the template in the "Subagents" section below, substituting all received values into the appropriate placeholders. Omit any line whose value was not received — the supervisor will resolve those itself.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
2. Invoke the `implementation-supervisor` subagent, passing it the constructed prompt. Use the Task tool and note the returned `task_id`.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
3. **The supervisor returning is ALWAYS unexpected — it must run forever.** Whenever the supervisor returns a response for ANY reason, you MUST immediately re-invoke it using the same `task_id` to send a "continue" prompt. Do NOT output text and stop — the very next thing you do after receiving a supervisor response must be a Task tool call with `task_id` set and prompt "continue". Repeat this indefinitely.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
4. Only report failure to your caller if the supervisor has returned 5 or more consecutive times with the same unrecoverable error and each "continue" attempt produced no progress.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## PR Compliance Checklist
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
**MANDATORY**: Every worker dispatched by this supervisor MUST complete all 8 items below before creating a PR. Pass this checklist verbatim in every worker prompt.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## Mandatory PR Compliance Checklist (MUST complete before creating PR)
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Before creating a PR, verify ALL of the following:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
1. **CHANGELOG.md updated**: Add entry under `[Unreleased]` section with appropriate
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
category (Added/Changed/Fixed/Removed)
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

Suggestion: The checklist item #4 says "CI passes — all quality gates and tests green before requesting review". This is difficult to verify locally given the 9 CI jobs in this repo (lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, benchmark, benchmark-regression). Consider specifying which of these are the critical gates vs. nice-to-have, so workers know the minimum bar. The CONTRIBUTING.md specifies lint, typecheck, security, unit_tests, and coverage as required — this could be called out explicitly.

Suggestion: The checklist item #4 says "CI passes — all quality gates and tests green before requesting review". This is difficult to verify locally given the 9 CI jobs in this repo (lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, benchmark, benchmark-regression). Consider specifying which of these are the critical gates vs. nice-to-have, so workers know the minimum bar. The CONTRIBUTING.md specifies lint, typecheck, security, unit_tests, and coverage as required — this could be called out explicitly.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
2. **CONTRIBUTORS.md updated**: add or update your contribution entry so others know what to improve
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
3. **Commit footer**: Commit message must include `ISSUES CLOSED: #<issue-number>` footer
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
4. **CI passes**: All quality gates must be green — lint, typecheck, unit_tests, integration_tests,
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
and coverage >= 97% — before requesting review or creating the PR
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
5. **BDD/Behave tests**: All new or changed code must have added or updated Behave feature
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
files with step definitions that pass on every CI run
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
6. **Epic association**: PR description must reference the parent Epic issue number
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
(e.g. "Parent Epic: #<epic-number>")
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
7. **Labels applied**: Apply State/In Review, Priority/<level>, MoSCoW/<level>, Type/<type>
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
via forgejo-label-manager
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
8. **Milestone assigned**: Assign PR to the earliest open milestone matching the linked issue
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Do NOT create the PR until all 8 items are verified.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### CHANGELOG.md Update
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Example:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```markdown
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## [Unreleased]
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### Added
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
- **My Feature** (#1234): Brief description of what was added and why.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```markdown
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## [Unreleased]
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### Fixed
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
- **My Bug Fix** (#1234): Brief description of what was fixed and the root cause.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### CONTRIBUTORS.md Update
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Example:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```markdown
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
* HAL 9000 has contributed the mandatory PR compliance checklist to
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
implementation-pool-supervisor (#9824): added an 8-item checklist ensuring
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
workers always update CHANGELOG.md, CONTRIBUTORS.md, include commit footers,
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
verify CI, add BDD tests, reference the parent Epic, apply labels, and assign
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
milestones before creating PRs.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### Commit Footer
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Example commit message:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
feat(agents): add mandatory PR compliance checklist to implementation-pool-supervisor
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Add an 8-item mandatory PR Compliance Checklist to the
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
implementation-pool-supervisor agent definition. Workers must complete
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
all 8 items before creating a PR: CHANGELOG.md update, CONTRIBUTORS.md
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
update, commit footer, CI verification, BDD tests, Epic reference,
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
label application, and milestone assignment.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Parent Epic: #9779
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
ISSUES CLOSED: #9824
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

Suggestion: The compliance verification pseudocode uses assert statements that cannot actually be executed by workers (e.g., behave_feature_file_exists_or_updated). Consider replacing these with concrete bash commands or API calls that workers can actually run, such as grep -q Unreleased CHANGELOG.md or git log -1 --format=%B | grep -q "ISSUES CLOSED: #.*".

Suggestion: The compliance verification pseudocode uses `assert` statements that cannot actually be executed by workers (e.g., `behave_feature_file_exists_or_updated`). Consider replacing these with concrete `bash` commands or API calls that workers can actually run, such as `grep -q Unreleased CHANGELOG.md` or `git log -1 --format=%B | grep -q "ISSUES CLOSED: #.*"`.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### Compliance Verification Pseudocode
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```python
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
def verify_pr_compliance(issue_number: int, repo_dir: str) -> bool:
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
"""Verify all 8 PR compliance checklist items before creating a PR."""
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
import subprocess, os
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 1: CHANGELOG.md has [Unreleased] entry
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
changelog = open(os.path.join(repo_dir, "CHANGELOG.md")).read()
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
assert "[Unreleased]" in changelog, "CHANGELOG.md missing [Unreleased] section"
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
assert f"#{issue_number}" in changelog, f"CHANGELOG.md missing entry for #{issue_number}"
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 2: CONTRIBUTORS.md updated
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
contributors = open(os.path.join(repo_dir, "CONTRIBUTORS.md")).read()
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
assert "HAL 9000" in contributors, "CONTRIBUTORS.md missing HAL 9000 entry"
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 3: Commit footer present
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
commit_msg = subprocess.check_output(
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
["git", "-C", repo_dir, "log", "-1", "--format=%B"]
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
).decode()
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
assert f"ISSUES CLOSED: #{issue_number}" in commit_msg, \
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
f"Commit message missing 'ISSUES CLOSED: #{issue_number}' footer"
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 4: CI passes — verified by checking CI status via Forgejo API
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# (run nox -e lint typecheck unit_tests integration_tests e2e_tests coverage_report locally)
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 5: BDD feature file exists or updated
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
result = subprocess.run(
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
["grep", "-r", f"#{issue_number}", os.path.join(repo_dir, "features/")],
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
capture_output=True
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
)
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
assert result.returncode == 0, f"No BDD feature file references #{issue_number}"
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 6: Epic reference in PR description
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# (verified when constructing PR body — must include "Parent Epic: #<N>")
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 7: Labels applied via forgejo-label-manager
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# (State/In Review, Priority/<level>, MoSCoW/<level>, Type/<type>)
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# Item 8: Milestone assigned to earliest open milestone
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
# (verified via Forgejo API after PR creation)
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
return True
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## Dispatching Workers
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
When dispatching `implementation-worker` agents, always include the full **PR Compliance Checklist** section above verbatim in the worker prompt under a `briefing:` key. Workers must not create PRs without completing all 8 checklist items.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## Parameters and local variables
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Parameter | Local Variable | Notes |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
|----------------------|:----------------:|-----------------------------------------------------------|
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Repository base url | `forgejo_url` | Base URL for Forgejo API |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Repository owner | `forgejo_owner` | May be an organization or an individual |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Repository name | `forgejo_repo` | Name of the repository |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Forgejo PAT | `forgejo_pat` | Personal access token |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Git email | `git_user_email` | Email for Git commits |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Git name | `git_user_name` | Name for Git commits |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
| Max parallel workers | `max_workers` | Target worker pool size (default: 4) |
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## Subagents
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
### `implementation-supervisor`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
#### How to invoke
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Invoke the `implementation-supervisor` subagent as a blocking call via the Task tool.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
#### Prompt template
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
forgejo_url: `{forgejo_url}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
forgejo_owner: `{forgejo_owner}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
forgejo_repo: `{forgejo_repo}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
forgejo_pat: `{forgejo_pat}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
git_user_name: `{git_user_name}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
git_user_email: `{git_user_email}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
max_workers: `{max_workers}`
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Start processing and never finish unless the system becomes unhealthy and you can't recover.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
```
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
## **CRITICAL** Rules
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
- **Pass all credentials verbatim.** Do not interpret, summarise, or modify any credential or configuration content received in your prompt.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
- **Never implement anything yourself.** Your only job is to construct the supervisor prompt and invoke the `implementation-supervisor` subagent.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
- **Always include the PR Compliance Checklist** in every worker prompt. Workers must not create PRs without completing all 8 checklist items.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
- **Never ask questions or give up.** Operate fully autonomously using best judgement.
Outdated
Review

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.

Critical: The PR changes 428 files (mostly deletions of deprecated agent files) but the title and issue scope is adding one checklist to one file. This massive scope expansion was not part of issue #9824. The bulk deletions should be in a separate PR, or this PR should be re-scoped and re-titled to reflect the full scope of changes. A single 428-file change makes review and auditability very difficult.
Outdated
Review

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.

BLOCKING: Issue #9824 still carries the Needs Feedback label. Per the issue body: A human must approve this issue before the change will be implemented. This is a governance gate outside code review. The project owner must remove this label or comment with approval before merge.
+8
View File
@@ -127,6 +127,14 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
and milestone assignment. This eliminates systemic PR merge blockers caused by workers
omitting required items.
- **Implementation Pool Supervisor PR Compliance Checklist** (#9824): Added a mandatory
8-item PR Compliance Checklist to the new `implementation-pool-supervisor.md` agent definition.
Supervisors must enforce that workers complete all 8 checklist items (CHANGELOG.md update,
CONTRIBUTORS.md update, commit footer, CI verification, BDD tests, Epic reference, label
application, and milestone assignment) before creating any PR. Includes concrete markdown
examples for each subsection and compliance verification pseudocode to ensure reproducible
adherence.
- **ACMS context path matching now handles absolute fragment paths** (#10972): Fixed
`_path_matches()` in `execute_phase_context_assembler.py` and `_matches_pattern()` in
`context_phase_analysis.py` to correctly match absolute paths (e.g. `/app/.opencode/skills/SKILL.md`)
+1
View File
@@ -30,6 +30,7 @@ Below are some of the specific details of various contributions.
* HAL 9000 has contributed the git_tools TOCTOU race condition fix (PR #8255 / issue #7619): eliminated the Time-Of-Check-To-Time-Of-Use race in `_get_base_env()` by adding double-checked locking with a module-level `threading.Lock`, preventing concurrent threads from writing conflicting environment snapshots.
* HAL 9000 has contributed the mandatory PR compliance checklist to `implementation-supervisor.md` (#9824): added an 8-item checklist to the worker prompt body with concrete items covering CHANGELOG.md, CONTRIBUTORS.md, commit footer, CI verification, BDD tests, Epic reference, labels, and milestone assignment to eliminate systemic PR merge blockers.
* HAL 9000 has contributed the PlanResult.success derivation fix (PR #8214 / issue #7501): replaced the incorrect `error_message is None` heuristic with a dedicated `result_success` column in the plans table, ensuring plans with historical build errors are not incorrectly marked as failed after a successful apply.
* HAL 9000 has contributed the mandatory PR compliance checklist to `implementation-pool-supervisor.md` (#9824): created a new agent definition with an embedded 8-item checklist ensuring workers always update CHANGELOG.md, CONTRIBUTORS.md, include commit footers (`ISSUES CLOSED: #N`), verify CI passes, add BDD tests, reference the parent Epic, apply labels via forgejo-label-manager, and assign milestones before creating PRs. Includes concrete examples for each subsection and compliance verification pseudocode.
* HAL 9000 has contributed comprehensive milestone documentation for v3.6.0 (Advanced Concepts & Deferred Features) and v3.7.0 (TUI Implementation) (PR #9903): split into sub-documents covering context strategies, LLM backends, resource types, A2A rename, container tool execution, scope chain resolution, cost/safety budgets, E2E workflow tests, code review examples, plugin architecture, TUI layout, persona system, reference/command input, session management, configuration, and TuiMaterializer integration.
* HAL 9000 has contributed the LLMTraceRepository data-integrity fix (PR #8185 / issue #7505): replaced the unconditional `session.commit()` in `LLMTraceRepository.save()` with a dual-path implementation that respects the UnitOfWork pattern — flushing only when an external session is provided, and flushing + committing + closing when operating standalone. This eliminates premature transaction commits, loss of rollback capability, and a docstring/implementation mismatch.
* HAL 9000 has contributed the ACMS Index Data Model and File Traversal Engine (PR #9664 / issue #9579): foundational data structures for indexed context entries with hot/warm/cold/archive storage tier classification, tag system, and a timeout-safe chunked file traversal engine for large projects with 10,000+ files.
@@ -0,0 +1,58 @@
@mock_only
Feature: PR Compliance Checklist in Implementation Pool Supervisor
As a pool supervisor
I want to pass a mandatory PR compliance checklist to every worker prompt
So that implementation workers complete all required items before creating a PR and avoid systemic merge blockers
Background:
Given the implementation-pool-supervisor.md agent definition exists
Scenario: Pool supervisor worker prompt includes the PR compliance checklist
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes the PR compliance checklist section
Outdated
Review

BLOCKING — Dead step definitions: feature file step text must include "Pool: " prefix

All Then and And steps in this feature file use plain text (e.g. "the worker prompt body includes the PR compliance checklist section"), while the new step definitions in pr_compliance_pool_supervisor_steps.py are all decorated with a "Pool: " prefix (e.g. @then("Pool: worker prompt body includes the PR compliance checklist section")).

Behave resolves step text by exact match. Since none of the feature file's step texts begin with "Pool: ", none of the new Pool: step definitions will ever be called. All 20 @then step defs in the new step file are dead code.

Fix: add Pool: to the beginning of every Then and And step in this file. Example for the first scenario:

  Scenario: Pool supervisor worker prompt includes the PR compliance checklist
    When I read the pool supervisor agent definition
    Then Pool: worker prompt body includes the PR compliance checklist section
    And Pool: the checklist is marked as MANDATORY

Repeat the Pool: prefix for all 20 Then/And steps across all 9 scenarios.

**BLOCKING — Dead step definitions: feature file step text must include `"Pool: "` prefix** All `Then` and `And` steps in this feature file use plain text (e.g. `"the worker prompt body includes the PR compliance checklist section"`), while the new step definitions in `pr_compliance_pool_supervisor_steps.py` are all decorated with a `"Pool: "` prefix (e.g. `@then("Pool: worker prompt body includes the PR compliance checklist section")`). Behave resolves step text by exact match. Since none of the feature file's step texts begin with `"Pool: "`, none of the new `Pool:` step definitions will ever be called. All 20 `@then` step defs in the new step file are dead code. Fix: add `Pool: ` to the beginning of every `Then` and `And` step in this file. Example for the first scenario: ```gherkin Scenario: Pool supervisor worker prompt includes the PR compliance checklist When I read the pool supervisor agent definition Then Pool: worker prompt body includes the PR compliance checklist section And Pool: the checklist is marked as MANDATORY ``` Repeat the `Pool: ` prefix for all 20 `Then`/`And` steps across all 9 scenarios.
And Pool: the checklist is marked as MANDATORY
Outdated
Review

BLOCKING — Step text does not match step definitions (UndefinedStep)

All Then and And steps in this feature file use the original unqualified step text (e.g. Then the worker prompt body includes the PR compliance checklist section), but the step definitions in pr_compliance_pool_supervisor_steps.py now require the Pool: prefix (e.g. @then("Pool: worker prompt body includes the PR compliance checklist section")).

Behave matches step text from the .feature file literally against step definition decorator strings. Because none of the step text in this file starts with Pool:, every Then and And step resolves as UndefinedStep. This causes all 9 scenarios to fail — providing zero actual BDD test coverage despite the test files being present.

This is the root cause of the CI / unit_tests failure.

Fix: Update all Then/And steps in this file to match the Pool: prefix used in the step definitions. For example, change:

Then the worker prompt body includes the PR compliance checklist section
And the checklist is marked as MANDATORY

to:

Then Pool: worker prompt body includes the PR compliance checklist section
And Pool: the checklist is marked as MANDATORY

Apply this Pool: prefix to every Then and And step throughout the file (9 scenarios, approximately 19 step lines total).

**BLOCKING — Step text does not match step definitions (UndefinedStep)** All `Then` and `And` steps in this feature file use the original unqualified step text (e.g. `Then the worker prompt body includes the PR compliance checklist section`), but the step definitions in `pr_compliance_pool_supervisor_steps.py` now require the `Pool:` prefix (e.g. `@then("Pool: worker prompt body includes the PR compliance checklist section")`). Behave matches step text from the `.feature` file literally against step definition decorator strings. Because none of the step text in this file starts with `Pool:`, every `Then` and `And` step resolves as `UndefinedStep`. This causes **all 9 scenarios to fail** — providing zero actual BDD test coverage despite the test files being present. This is the root cause of the `CI / unit_tests` failure. **Fix**: Update all `Then`/`And` steps in this file to match the `Pool:` prefix used in the step definitions. For example, change: ``` Then the worker prompt body includes the PR compliance checklist section And the checklist is marked as MANDATORY ``` to: ``` Then Pool: worker prompt body includes the PR compliance checklist section And Pool: the checklist is marked as MANDATORY ``` Apply this `Pool:` prefix to every `Then` and `And` step throughout the file (9 scenarios, approximately 19 step lines total).
Scenario: Checklist item 1 — CHANGELOG.md update required
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a CHANGELOG.md checklist item
And Pool: the item instructs workers to add an entry under the Unreleased section
Scenario: Checklist item 2 — CONTRIBUTORS.md update required
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a CONTRIBUTORS.md checklist item
And Pool: the item instructs workers to add or update their contribution entry
Scenario: Checklist item 3 — commit footer required
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a commit footer checklist item
And Pool: the item specifies the ISSUES CLOSED footer format
Scenario: Checklist item 4 — CI must pass before PR creation
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a CI passes checklist item
And Pool: the item instructs workers to verify all quality gates are green
Scenario: Checklist item 5 — BDD/Behave tests required
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a BDD tests checklist item
And Pool: the item instructs workers to add or update Behave feature files
Scenario: Checklist item 6 — Epic reference required in PR description
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes an Epic reference checklist item
And Pool: the item instructs workers to reference the parent Epic issue number
Scenario: Checklist item 7 — Labels must be applied
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a labels checklist item
And Pool: the item instructs workers to apply labels via forgejo-label-manager
Scenario: Checklist item 8 — Milestone must be assigned
When I read the pool supervisor agent definition
Then Pool: worker prompt body includes a milestone checklist item
And Pool: the item instructs workers to assign the earliest open milestone
Scenario: All 8 checklist items are present in the worker prompt
When I read the pool supervisor agent definition
Then Pool: worker prompt body contains all 8 mandatory checklist items
@@ -0,0 +1,219 @@
"""Step definitions for PR compliance checklist in implementation pool supervisor.
This file uses parameterized @then decorators with unique step text that
distinguishes pool-supervisor checks from the shared compliance checklist
steps in pr_compliance_checklist_steps.py, preventing Behave AmbiguousStep
errors when both feature files are run together.
Outdated
Review

BLOCKING — Off-by-One Path Bug

PROJECT_ROOT = Path(__file__).resolve().parents[3]

This is wrong. The file is at features/steps/pr_compliance_pool_supervisor_steps.py, so:

  • parents[0] = features/steps/
  • parents[1] = features/
  • parents[2] = project root (CORRECT)
  • parents[3] = parent of project root (WRONG)

This causes AGENT_DEF_PATH.exists() to fail for every test in this file, as the path resolves outside the project.

Fix:

PROJECT_ROOT = Path(__file__).resolve().parents[2]
**BLOCKING — Off-by-One Path Bug** ```python PROJECT_ROOT = Path(__file__).resolve().parents[3] ``` This is wrong. The file is at `features/steps/pr_compliance_pool_supervisor_steps.py`, so: - `parents[0]` = `features/steps/` - `parents[1]` = `features/` - `parents[2]` = project root (CORRECT) - `parents[3]` = parent of project root (WRONG) This causes `AGENT_DEF_PATH.exists()` to fail for every test in this file, as the path resolves outside the project. **Fix**: ```python PROJECT_ROOT = Path(__file__).resolve().parents[2] ```
Each validator is imported from the shared pr_compliance_checklist_steps module's
Outdated
Review

BLOCKING — Off-by-One Path Bug (unchanged from review #7816)

PROJECT_ROOT = Path(__file__).resolve().parents[3]

The file is at features/steps/pr_compliance_pool_supervisor_steps.py:

  • parents[0] = features/steps/
  • parents[1] = features/
  • parents[2] = project root (CORRECT)
  • parents[3] = parent of project root (WRONG)

AGENT_DEF_PATH.exists() resolves outside the repo and returns False for every test in this file.

Fix:

PROJECT_ROOT = Path(__file__).resolve().parents[2]
**BLOCKING — Off-by-One Path Bug (unchanged from review #7816)** ```python PROJECT_ROOT = Path(__file__).resolve().parents[3] ``` The file is at `features/steps/pr_compliance_pool_supervisor_steps.py`: - `parents[0]` = `features/steps/` - `parents[1]` = `features/` - `parents[2]` = project root **(CORRECT)** - `parents[3]` = parent of project root **(WRONG)** `AGENT_DEF_PATH.exists()` resolves outside the repo and returns `False` for every test in this file. **Fix:** ```python PROJECT_ROOT = Path(__file__).resolve().parents[2] ```
validation logic (via the _verify module) to avoid code duplication while using
Outdated
Review

BLOCKING — ruff format --check fails: AGENT_DEF_PATH path concatenation must be parenthesized

The line is too long for ruff’s 88-character line length limit. ruff format would wrap it as follows:

# Current (fails ruff format --check):
AGENT_DEF_PATH = PROJECT_ROOT / ".opencode" / "agents" / "implementation-pool-supervisor.md"

# Required:
AGENT_DEF_PATH = (
    PROJECT_ROOT / ".opencode" / "agents" / "implementation-pool-supervisor.md"
)

Fix: run ruff format features/steps/pr_compliance_pool_supervisor_steps.py (or nox -s format) and include the reformatted file in the same commit as the other two format fixes.

**BLOCKING — `ruff format --check` fails: `AGENT_DEF_PATH` path concatenation must be parenthesized** The line is too long for ruff’s 88-character line length limit. `ruff format` would wrap it as follows: ```python # Current (fails ruff format --check): AGENT_DEF_PATH = PROJECT_ROOT / ".opencode" / "agents" / "implementation-pool-supervisor.md" # Required: AGENT_DEF_PATH = ( PROJECT_ROOT / ".opencode" / "agents" / "implementation-pool-supervisor.md" ) ``` Fix: run `ruff format features/steps/pr_compliance_pool_supervisor_steps.py` (or `nox -s format`) and include the reformatted file in the same commit as the other two format fixes.
unique step text prefixes ("Pool:") for disambiguation.
"""
from collections.abc import Callable
from pathlib import Path
Outdated
Review

BLOCKING — from typing import Callable violates UP035 (ruff lint failure)

For Python 3.13 (target-version = "py313"), the UP ruleset flags typing.Callable as deprecated. All production code in src/cleveragents/ already uses from collections.abc import Callable.

Fix: split the import on line 14 into:

from collections.abc import Callable
from typing import Any

This will resolve the CI / lint failure.

**BLOCKING — `from typing import Callable` violates UP035 (ruff lint failure)** For Python 3.13 (`target-version = "py313"`), the `UP` ruleset flags `typing.Callable` as deprecated. All production code in `src/cleveragents/` already uses `from collections.abc import Callable`. Fix: split the import on line 14 into: ```python from collections.abc import Callable from typing import Any ``` This will resolve the `CI / lint` failure.
from typing import Any
from behave import given, then, when
PROJECT_ROOT = Path(__file__).resolve().parents[2]
AGENT_DEF_PATH = (
PROJECT_ROOT / ".opencode" / "agents" / "implementation-pool-supervisor.md"
)
# ---------------------------------------------------------------------------
# Shared validation helpers — identical logic to pr_compliance_checklist_steps.py
# ---------------------------------------------------------------------------
_required_items = [
"CHANGELOG.md",
"CONTRIBUTORS.md",
"ISSUES CLOSED",
"CI passes",
"BDD/Behave tests",
"Epic reference",
"forgejo-label-manager",
"earliest open milestone",
]
VALIDATORS: dict[str, Callable[[str], bool]] = {
"includes checklist section": lambda c: "PR Compliance Checklist" in c,
"is marked MANDATORY": lambda c: "MANDATORY" in c,
"has CHANGELOG.md item": lambda c: "CHANGELOG.md" in c,
"references Unreleased": lambda c: "[Unreleased]" in c,
"has CONTRIBUTORS.md item": lambda c: "CONTRIBUTORS.md" in c,
"instructs add or update": lambda c: "add or update" in c,
"has commit footer item": lambda c: "Commit footer" in c,
"specifies ISSUES CLOSED": lambda c: "ISSUES CLOSED" in c,
"has CI passes item": lambda c: "CI passes" in c,
"mentions quality gates": lambda c: "quality gates" in c,
"has BDD tests item": lambda c: "BDD/Behave tests" in c,
"instructs add or update features": lambda c: "added or updated" in c,
"has Epic reference item": lambda c: "Epic reference" in c,
"references parent Epic": lambda c: "parent Epic" in c,
"has labels item": lambda c: "Labels" in c,
"mentions forgejo-label-manager": lambda c: "forgejo-label-manager" in c,
"has milestone item": lambda c: "Milestone" in c,
Outdated
Review

BLOCKING — ruff format --check fails: all() comprehension must be on a single line

Ruff’s formatter collapses this three-line lambda back to one line because it fits within 88 characters:

# Current (fails ruff format --check):
"all 8 items present": lambda c: all(
    item in c for item in _required_items
),

# Required:
"all 8 items present": lambda c: all(item in c for item in _required_items),

Fix: run nox -s format locally and commit the reformatted file.

**BLOCKING — `ruff format --check` fails: `all()` comprehension must be on a single line** Ruff’s formatter collapses this three-line lambda back to one line because it fits within 88 characters: ```python # Current (fails ruff format --check): "all 8 items present": lambda c: all( item in c for item in _required_items ), # Required: "all 8 items present": lambda c: all(item in c for item in _required_items), ``` Fix: run `nox -s format` locally and commit the reformatted file.
"earliest open milestone": lambda c: "earliest open milestone" in c,
"all 8 items present": lambda c: all(item in c for item in _required_items),
}
def _make_validator(key: str) -> Callable[[Any], None]:
"""Factory that creates a typed Behave validator from a shared helper."""
def validator(context: Any) -> None:
content = context.agent_def_content
check_fn = VALIDATORS.get(key)
assert check_fn(content), f"Pool supervisor agent definition failed: {key}"
return validator
# ---------------------------------------------------------------------------
# Unique @given and @when — scoped to the pool supervisor agent def only
# ---------------------------------------------------------------------------
@given("the implementation-pool-supervisor.md agent definition exists")
def step_agent_def_exists(context: Any) -> None:
"""Verify the pool supervisor agent definition file exists."""
assert AGENT_DEF_PATH.exists(), f"Agent definition not found at {AGENT_DEF_PATH}"
context.agent_def_path = AGENT_DEF_PATH
@when("I read the pool supervisor agent definition")
def step_read_agent_def(context: Any) -> None:
"""Read the pool supervisor agent definition."""
context.agent_def_content = AGENT_DEF_PATH.read_text(encoding="utf-8")
# ---------------------------------------------------------------------------
Outdated
Review

BLOCKING — String Mismatch: "CI passes" not in agent definition

This assertion:

assert "CI passes" in context.agent_def_content

will always fail. The agent definition contains "CI passing" (line 107), not "CI passes".

Fix:

assert "CI passing" in context.agent_def_content, (
    "Worker prompt body does not include a CI passing checklist item"
)

Also update the corresponding step text in the .feature file.

**BLOCKING — String Mismatch: `"CI passes"` not in agent definition** This assertion: ```python assert "CI passes" in context.agent_def_content ``` will always fail. The agent definition contains `"CI passing"` (line 107), not `"CI passes"`. **Fix**: ```python assert "CI passing" in context.agent_def_content, ( "Worker prompt body does not include a CI passing checklist item" ) ``` Also update the corresponding step text in the `.feature` file.
# Unique @then — prefixed with "Pool:" so they never conflict with the
# shared pr_compliance_checklist_steps.py step definitions.
# ---------------------------------------------------------------------------
# Scenario: Pool supervisor worker prompt includes the PR compliance checklist
@then("Pool: worker prompt body includes the PR compliance checklist section")
Outdated
Review

BLOCKING — String Mismatch: "CI passes" not in agent definition (unchanged from review #7816)

assert "CI passes" in context.agent_def_content

The agent definition (line 107) reads:

4. **CI passing**: All CI checks must pass...

The string "CI passes" is not present anywhere in the file. This assertion always fails.

Fix:

assert "CI passing" in context.agent_def_content, (
    "Worker prompt body does not include a CI passing checklist item"
)

Also update the corresponding Then step in pr_compliance_pool_supervisor.feature to read: Then the worker prompt body includes a CI passing checklist item.

**BLOCKING — String Mismatch: `"CI passes"` not in agent definition (unchanged from review #7816)** ```python assert "CI passes" in context.agent_def_content ``` The agent definition (line 107) reads: ``` 4. **CI passing**: All CI checks must pass... ``` The string `"CI passes"` is not present anywhere in the file. This assertion always fails. **Fix:** ```python assert "CI passing" in context.agent_def_content, ( "Worker prompt body does not include a CI passing checklist item" ) ``` Also update the corresponding `Then` step in `pr_compliance_pool_supervisor.feature` to read: `Then the worker prompt body includes a CI passing checklist item`.
def pool_step_prompt_includes_checklist(context: Any) -> None:
Outdated
Review

BLOCKING — String Not Found: "quality gates" absent from agent definition

This assertion:

assert "quality gates" in context.agent_def_content

will always fail. The string "quality gates" does not appear anywhere in implementation-pool-supervisor.md.

Fix options:

Option A — Match actual text:

assert "lint, typecheck, unit_tests" in context.agent_def_content, (
    "CI checklist item does not list required quality gates"
)

Option B — Add "quality gates" to the agent definition checklist item:

4. **CI passing**: All CI quality gates must pass (lint, typecheck, unit_tests,
   integration_tests, coverage >= 97%) before requesting review
**BLOCKING — String Not Found: `"quality gates"` absent from agent definition** This assertion: ```python assert "quality gates" in context.agent_def_content ``` will always fail. The string `"quality gates"` does not appear anywhere in `implementation-pool-supervisor.md`. **Fix options:** Option A — Match actual text: ```python assert "lint, typecheck, unit_tests" in context.agent_def_content, ( "CI checklist item does not list required quality gates" ) ``` Option B — Add `"quality gates"` to the agent definition checklist item: ```markdown 4. **CI passing**: All CI quality gates must pass (lint, typecheck, unit_tests, integration_tests, coverage >= 97%) before requesting review ```
"""Verify the pool-supervisor worker prompt body includes the PR compliance checklist."""
_make_validator("includes checklist section")(context)
@then("Pool: the checklist is marked as MANDATORY")
Outdated
Review

BLOCKING — String Not Found: "quality gates" absent from agent definition (unchanged from review #7816)

assert "quality gates" in context.agent_def_content

The string "quality gates" does not appear anywhere in implementation-pool-supervisor.md. Checklist item #4 lists specific gate names but never uses this phrase.

Fix — Option A (preferred, match actual text):

assert "lint, typecheck, unit_tests" in context.agent_def_content, (
    "CI checklist item does not list required quality gates"
)

Fix — Option B (add phrase to agent definition):

4. **CI passing**: All CI quality gates must pass (lint, typecheck, unit_tests,
   integration_tests, coverage >= 97%) before requesting review
**BLOCKING — String Not Found: `"quality gates"` absent from agent definition (unchanged from review #7816)** ```python assert "quality gates" in context.agent_def_content ``` The string `"quality gates"` does not appear anywhere in `implementation-pool-supervisor.md`. Checklist item #4 lists specific gate names but never uses this phrase. **Fix — Option A** (preferred, match actual text): ```python assert "lint, typecheck, unit_tests" in context.agent_def_content, ( "CI checklist item does not list required quality gates" ) ``` **Fix — Option B** (add phrase to agent definition): ```markdown 4. **CI passing**: All CI quality gates must pass (lint, typecheck, unit_tests, integration_tests, coverage >= 97%) before requesting review ```
def pool_step_checklist_is_mandatory(context: Any) -> None:
"""Verify the pool-supervisor checklist is marked as MANDATORY."""
_make_validator("is marked MANDATORY")(context)
# Scenario: Checklist item 1 — CHANGELOG.md update required
@then("Pool: worker prompt body includes a CHANGELOG.md checklist item")
def pool_step_prompt_includes_changelog_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a CHANGELOG.md checklist item."""
_make_validator("has CHANGELOG.md item")(context)
Outdated
Review

BLOCKING — String Mismatch: "added or updated" not in agent definition

This assertion:

assert "added or updated" in context.agent_def_content

will always fail. The agent definition item #5 reads "Add or update" (not "added or updated").

Fix:

assert "Add or update" in context.agent_def_content, (
    "BDD checklist item does not instruct workers to add or update feature files"
)
**BLOCKING — String Mismatch: `"added or updated"` not in agent definition** This assertion: ```python assert "added or updated" in context.agent_def_content ``` will always fail. The agent definition item #5 reads `"Add or update"` (not `"added or updated"`). **Fix**: ```python assert "Add or update" in context.agent_def_content, ( "BDD checklist item does not instruct workers to add or update feature files" ) ```
@then("Pool: the item instructs workers to add an entry under the Unreleased section")
def pool_step_changelog_item_unreleased(context: Any) -> None:
"""Verify the CHANGELOG.md item mentions the Unreleased section."""
Outdated
Review

BLOCKING — String Mismatch: "added or updated" not in agent definition (unchanged from review #7816)

assert "added or updated" in context.agent_def_content

Checklist item #5 in implementation-pool-supervisor.md reads:

5. **BDD/Behave tests**: Add or update Behave feature file...

The phrase "added or updated" is not present; the file says "Add or update".

Fix:

assert "Add or update" in context.agent_def_content, (
    "BDD checklist item does not instruct workers to add or update feature files"
)
**BLOCKING — String Mismatch: `"added or updated"` not in agent definition (unchanged from review #7816)** ```python assert "added or updated" in context.agent_def_content ``` Checklist item #5 in `implementation-pool-supervisor.md` reads: ``` 5. **BDD/Behave tests**: Add or update Behave feature file... ``` The phrase `"added or updated"` is not present; the file says `"Add or update"`. **Fix:** ```python assert "Add or update" in context.agent_def_content, ( "BDD checklist item does not instruct workers to add or update feature files" ) ```
_make_validator("references Unreleased")(context)
# Scenario: Checklist item 2 — CONTRIBUTORS.md update required
@then("Pool: worker prompt body includes a CONTRIBUTORS.md checklist item")
def pool_step_prompt_includes_contributors_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a CONTRIBUTORS.md checklist item."""
_make_validator("has CONTRIBUTORS.md item")(context)
@then("Pool: the item instructs workers to add or update their contribution entry")
def pool_step_contributors_item_add_update(context: Any) -> None:
"""Verify the CONTRIBUTORS.md item instructs workers to add or update."""
_make_validator("instructs add or update")(context)
# Scenario: Checklist item 3 — commit footer required
@then("Pool: worker prompt body includes a commit footer checklist item")
def pool_step_prompt_includes_commit_footer_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a commit footer checklist item."""
_make_validator("has commit footer item")(context)
@then("Pool: the item specifies the ISSUES CLOSED footer format")
def pool_step_commit_footer_issues_closed(context: Any) -> None:
"""Verify the commit footer item specifies the ISSUES CLOSED format."""
_make_validator("specifies ISSUES CLOSED")(context)
# Scenario: Checklist item 4 — CI must pass before PR creation
@then("Pool: worker prompt body includes a CI passes checklist item")
def pool_step_prompt_includes_ci_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a CI passes checklist item."""
_make_validator("has CI passes item")(context)
@then("Pool: the item instructs workers to verify all quality gates are green")
def pool_step_ci_item_quality_gates(context: Any) -> None:
"""Verify the CI item instructs workers to verify quality gates are green."""
_make_validator("mentions quality gates")(context)
# Scenario: Checklist item 5 — BDD/Behave tests required
@then("Pool: worker prompt body includes a BDD tests checklist item")
def pool_step_prompt_includes_bdd_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a BDD/Behave tests checklist item."""
_make_validator("has BDD tests item")(context)
@then("Pool: the item instructs workers to add or update Behave feature files")
def pool_step_bdd_item_feature_files(context: Any) -> None:
"""Verify the BDD item instructs workers to add or update feature files."""
_make_validator("instructs add or update features")(context)
# Scenario: Checklist item 6 — Epic reference required in PR description
@then("Pool: worker prompt body includes an Epic reference checklist item")
def pool_step_prompt_includes_epic_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes an Epic reference checklist item."""
_make_validator("has Epic reference item")(context)
@then("Pool: the item instructs workers to reference the parent Epic issue number")
def pool_step_epic_item_parent_reference(context: Any) -> None:
"""Verify the Epic item instructs workers to reference the parent Epic."""
_make_validator("references parent Epic")(context)
# Scenario: Checklist item 7 — Labels must be applied
@then("Pool: worker prompt body includes a labels checklist item")
def pool_step_prompt_includes_labels_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a labels checklist item."""
_make_validator("has labels item")(context)
@then("Pool: the item instructs workers to apply labels via forgejo-label-manager")
def pool_step_labels_item_forgejo_label_manager(context: Any) -> None:
"""Verify the labels item instructs workers to use forgejo-label-manager."""
_make_validator("mentions forgejo-label-manager")(context)
# Scenario: Checklist item 8 — Milestone must be assigned
@then("Pool: worker prompt body includes a milestone checklist item")
def pool_step_prompt_includes_milestone_item(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body includes a milestone checklist item."""
_make_validator("has milestone item")(context)
@then("Pool: the item instructs workers to assign the earliest open milestone")
def pool_step_milestone_item_earliest(context: Any) -> None:
"""Verify the milestone item instructs workers to assign the earliest open milestone."""
_make_validator("earliest open milestone")(context)
# Scenario: All 8 checklist items are present in the worker prompt
@then("Pool: worker prompt body contains all 8 mandatory checklist items")
def pool_step_prompt_contains_all_8_items(context: Any) -> None:
"""Verify the pool-supervisor worker prompt body contains all 8 mandatory checklist items."""
_make_validator("all 8 items present")(context)