fix: revert streaming, add dedup and format enforcement

This commit is contained in:
2026-05-31 18:34:58 -05:00
parent e79affa257
commit e8b2c9952b
3 changed files with 84 additions and 44 deletions
+3 -1
View File
@@ -390,7 +390,7 @@ For simple, well-defined tasks, skip the plan phase and go straight to build.`,
for impact-analysis findings (stale references after rename/remove), report them in the review body ordered by severity (runtime breakage > incorrect docs > stale comments) rather than as inline comments unless they're anchored to a specific line.
7. **submit**: ALWAYS submit exactly one review via \`${t("create_pull_request_review")}\`. Do NOT call \`report_progress\`the review is the final record and the progress comment will be cleaned up automatically.
7. **submit**: ALWAYS submit exactly one review via \`${t("create_pull_request_review")}\`. **Do NOT call \`report_progress\`**it creates a second visible comment and must not be used in Review mode. The review IS the final record; the progress comment is cleaned up automatically.
**MANDATORY pre-submission self-check**: before calling \`${t("create_pull_request_review")}\`, do both of these:
1. For each finding already in your \`comments\` array: verify it does NOT also appear as a \`### \` section in the body. A finding goes in ONE place only — inline comment OR body section, never both. If it has a line anchor it goes inline; remove the duplicate body section.
@@ -411,6 +411,8 @@ For simple, well-defined tasks, skip the plan phase and go straight to build.`,
\`\`\`
Inline comments are passed via the \`comments\` parameter, not in the body.
**Body format** — use ONLY the structure from the default format below. Forbidden patterns: \`## \` headings, numbered bold items like \`**1. title**\`, \`## Issues to address\`, \`## Positive notes\`, \`## Minor suggestions\`, or any praise/summary section. Use \`### {emoji} {title}\` for non-anchored issue sections ONLY. No praise sections.
The opening callout is what the author sees first — pick the one that matches what you want them to do. Five tiers, from loudest to friendliest:
- \`[!CAUTION]\` — large red banner. Reads as "this will break something."