git:20260904.70f3915 to git:20260904.76b0c0e

5 added, 0 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
description: Agent-authored GitHub comments must be blockquoted to distinguish them from the maintainer's own writing
alwaysApply: true
---
# Agent Voice on GitHub
All conversational RESPONSES an agent posts to GitHub on the maintainer's behalf — comments on existing issues and PRs, review bodies, discussion replies, close/reopen comments — MUST be wrapped in markdown blockquotes (`> ` prefixing every line, including blank lines within the quoted body). This is the maintainer's established convention (used on Discord as well) so readers can tell agent-authored responses from his own, and so responsibility for agent actions (closes, merges, verdicts) is auditable.
Bodies of NEW issues and PRs the agent opens are exempt — authorship is already clearly credited there. This policy is about responses in conversation.
+ Every blockquoted response MUST end with an attribution line as the last line of the quote, after a blank quoted line:
+
```markdown
❌ BAD
Confirmed and fixed in fc7e626f — thanks for the reproduction.
✅ GOOD
> Confirmed and fixed in fc7e626f — thanks for the reproduction.
>
> Root cause: derived stores fold drafts on the clone path...
+ >
+ > — *Claude via Cursor*
```
Rules of thumb:
- Code blocks inside the comment stay inside the blockquote (prefix the fences too: `> ```ts`).
+ - The attribution names the actual agent — model and/or product, e.g. `— *Claude via Cursor*` — the same way agents credit themselves on commits and PRs. Keep the `— *<agent>*` shape consistent so readers learn to recognize it.
- Applies to `gh issue comment`, `gh pr comment`, `gh pr review --body`, close/merge `--comment` bodies, and API-posted comment bodies.
- Does NOT apply to commit messages, changesets, PR/issue titles, labels, or code — only conversational bodies.
- If quoting someone else inside an agent comment, use a nested quote (`> >`).