git checkout main >/dev/null
git pull --ff-only >/dev/null
为此切片创建实现分支。
完整实现并包含测试。
首先运行聚焦验证，然后运行更广泛的必要检查。
如果覆盖率或质量门失败，则在提交前添加测试。不要降低阈值。
阶段 4：交付切片
在实现完成且本地验证通过后：
调用 $commit-and-push。
调用 $enter-merge-queue。
等待合并完成（由 $enter-merge-queue 处理）。
在确认合并之前，不要开始下一个切片。
阶段 5：合并后更新
刷新工作区（通常由 $enter-merge-queue 处理）。
确认当前分支是 main 且是干净的。
将已合并的 PR 元数据附加到 completed_slices。
递增 iteration。
针对最新代码重新运行阶段 1 的侦察。
重复阶段 2-5 直至完成。
完成条件
当以下所有条件都为真时标记为完成：
Issue 检查列表项在代码中得到满足。
没有剩余的运行时引用指向已移除的遗留路径/代理助手（明确允许的例外情况除外）。
受影响的包的必需构建/测试通过。
没有剩余的非重叠高价值切片。
受阻条件
当发生以下任何情况时停止并报告：
在仍有已打开的 PR 处于活跃状态时，没有剩余的非重叠切片。
一个必需的切片在修复后仍连续 3 次 CI 失败。
合并冲突需要模糊的权衡，且无法安全解决。
Issue 需要用户产品决策，而这些决策无法推断。
反模式（切勿）
不要将不相关的清理工作捆绑到一个切片中。
不要为一个 Issue 并行打开多个活跃的 PR。
不要在回复评审线程时引用未推送的提交。
不要为了保持势头而跳过验证门。
不要在 PR 正文中使用自动关闭关键词。
推荐的循环骨架
LOAD/INIT STATE
RECON ISSUE + PR OVERLAP
WHILE NOT COMPLETE:
SELECT LARGEST NON-OVERLAPPING SLICE
IMPLEMENT + TEST
RUN $commit-and-push
RUN $enter-merge-queue
REFRESH + UPDATE STATE
FINAL ISSUE COMPLETION REPORT
After loading the issue, check whether its body is already in autopilot-friendly format. An autopilot-friendly issue has:
A ## Requirements section (or equivalent heading like ## Tasks, ## Checklist) with - [ ] checkbox items
Each requirement is clear, testable, and independently implementable
Enough granularity to decompose into slices
Skip normalization if the issue already has a requirements-style section with at least two - [ ] items.
If the issue body lacks structured requirements (e.g., plain prose, a single paragraph, or non-checkbox bullets), rewrite the body into autopilot-friendly format before proceeding:
Parse the existing body to extract intent, scope, and individual work items.
Rewrite into this structure:
## Summary
<one paragraph describing the goal and outcome>
## Context
<why this matters, impacted area, constraints>
## Requirements
- [ ] <clear, testable requirement 1>
- [ ] <clear, testable requirement 2>
- [ ] ...
## Implementation Notes
<initial approach, dependencies, or open questions>
Preserve the original issue body at the bottom under a collapsed details block:
<details>
<summary>Original issue body</summary>
<original body here>
</details>
Exclude slices whose candidate_files overlap with any open PR files.
Exclude slices with unclear done criteria.
Prefer slices that:
remove legacy paths/endpoints,
remove proxy layers,
remove obsolete dependencies,
unlock later deletions.
Pick the highest scoring remaining slice.
If no non-overlapping slice exists, set blocked_reason and stop.
Phase 3: Implement Slice
Ensure clean base:
git checkout main >/dev/null
git pull --ff-only >/dev/null
Create implementation branch for this slice.
Implement fully with tests.
Run focused validation first, then broader required checks.
If coverage or quality gates fail, add tests before commit. Do not lower thresholds.
Phase 4: Ship Slice
After implementation is complete and local validation passes:
Invoke $commit-and-push.
Invoke $enter-merge-queue.
Wait for merge completion (handled by $enter-merge-queue).
Do not start the next slice until merge is confirmed.
Phase 5: Post-Merge Update
Refresh workspace (normally handled by $enter-merge-queue).
Confirm current branch is main and clean.
Append merged PR metadata to completed_slices.
Increment iteration.
Re-run Phase 1 recon against latest code.
Repeat Phases 2-5 until done.
Completion Conditions
Mark complete when all are true:
Issue checklist items are satisfied in code.
No remaining runtime references to removed legacy paths/proxy helpers (except explicitly allowed exceptions).
Required builds/tests pass for touched packages.
No additional non-overlapping high-value slice remains.
Blocked Conditions
Stop and report when any occurs:
No non-overlapping slices remain while open PRs are still active.
A required slice repeatedly fails CI 3 times after fixes.
Merge conflicts require ambiguous tradeoffs and cannot be resolved safely.
The issue requires user product decisions that cannot be inferred.
Anti-Patterns (Never)
Do not bundle unrelated cleanup into one slice.
Do not open multiple active PRs for one issue in parallel.
Do not reply to review threads referencing unpushed commits.
Do not skip validation gates to keep momentum.
Do not use auto-close keywords in PR bodies.
Recommended Loop Skeleton
LOAD/INIT STATE
RECON ISSUE + PR OVERLAP
WHILE NOT COMPLETE:
SELECT LARGEST NON-OVERLAPPING SLICE
IMPLEMENT + TEST
RUN $commit-and-push
RUN $enter-merge-queue
REFRESH + UPDATE STATE
FINAL ISSUE COMPLETION REPORT
Issue #2540 Mapping Heuristic
For #2540-like migrations, prefer this order:
Remaining deproxy service slices with strongest boundaries.
Legacy routing/unmount deletion once deproxy dependencies are removed.
Client wrapper/type migration cleanup.
Final dependency removals and dead-code deletion.
Always re-check overlap against currently open PRs before each slice.
