ci: auto-minimize comments from org-blocked users

[qwen-code-dev-bot]

What this PR does

Adds a scheduled GitHub Actions workflow (auto-minimize-spam.yml) that runs every hour to scan recent issue/PR comments and automatically minimize any from users blocked at the org level.

Why it's needed

When a spam user is blocked at the org level, their existing comments remain visible on PR/issue pages. Currently these must be manually minimized one by one (as we just did for 25 comments from danialzivehdadr). This workflow automates that cleanup and also catches any comments posted in the window between the spam and the block action.

How it works

1. Fetches the org's blocked-user list via GET /orgs/{org}/blocks
2. Queries the last 2 hours of comments on open issues/PRs via GraphQL
3. Matches comment authors (case-insensitive) against the blocked list
4. Minimizes matched comments as OFF_TOPIC via GraphQL minimizeComment mutation
5. Writes a summary to the step summary

The workflow is also triggerable manually via workflow_dispatch with a configurable lookback window (default 2 hours).

Security model

• Uses CI_BOT_PAT for API access (same token used by other triage workflows)
• Only minimizes comments — does not delete them, so the audit trail is preserved
• Only acts on users already in the org's blocked list — no heuristic content filtering
• Scoped to QwenLM/qwen-code only (if: github.repository == 'QwenLM/qwen-code')

Reviewer Test Plan

How to verify

1. Merge this PR.
2. Wait for the next hourly run, or trigger manually via Actions → "Auto-minimize blocked user comments" → Run workflow.
3. Check the run log: it should report the number of org-blocked users found and comments minimized.
4. If a blocked user has recent unminimized comments, they should be collapsed as "off-topic" after the run.

Tested on

OS	Status
🍏 macOS	N/A
🪟 Windows	N/A
🐧 Linux	N/A

CI-only change.

Risk & Scope

• Main risk: if the org blocked list API returns an error, the workflow exits cleanly with 0 minimizations (fail-open for the scan, not fail-closed).
• Not validated / out of scope: content-based spam detection (only username-based for now).
• Breaking changes / migration notes: none.

Linked Issues

N/A

中文说明

添加定时 workflow，每小时扫描最近 2 小时的 issue/PR 评论，自动 minimize 被 org 拉黑用户的评论。解决拉黑后已有评论仍需手动清理的问题。也支持手动触发，可配置回看时间窗口。

[qwen-code-ci-bot]

✅ Qwen Triage finished — view run. See the stage comments in this thread for the result.

✅ Qwen Triage 已完成 —— 查看运行。结果见本线程中的各阶段评论。

[qwen-code-ci-bot]

Thanks for the PR!

Template looks good ✓ (the "Evidence (Before & After)" section is N/A for a CI-only change, correctly noted under "Tested on").

Problem: observed operational burden — the PR cites a specific incident (25 spam comments from danialzivehdadr requiring manual minimization after the org block). Real, recurring maintenance task.

Direction: aligned. Automating post-block comment cleanup is straightforward repo hygiene. Doesn't touch any sensitive subsystem. The workflow is scoped to QwenLM/qwen-code only and uses the existing CI_BOT_PAT.

Size: not applicable — files under .github/ only, no core paths touched.

Approach: the scope feels right. The updated implementation is cleaner than what was described in the PR body — it uses a local .github/spam-blocklist.txt file (auditable in git, no org-admin scope needed) rather than the org blocks API mentioned in the description. One GraphQL query, shell-level exact matching, minimize-only. The dead first query from the earlier revision is gone. Every file in the diff is needed: the workflow, the blocklist, the security-invariant test, and the CI registration.

Risk: no elevated risk signals — none of the changed files match high-risk paths.

Moving on to code review. 🔍

中文说明

感谢贡献！

模板完整 ✓（"Evidence (Before & After)" 对 CI 变更为 N/A，已在 "Tested on" 中正确标注）。

问题：已观测到的运维负担——PR 引用了具体事件（danialzivehdadr 的 25 条垃圾评论在 org 拉黑后仍需手动逐条 minimize）。真实且反复出现的维护任务。

方向：对齐。自动化拉黑后的评论清理是基本的仓库卫生工作。不涉及任何敏感子系统。Workflow 仅限于 QwenLM/qwen-code，使用现有的 CI_BOT_PAT。

规模：不适用——仅 .github/ 下的文件，未触及核心路径。

方案：范围合理。更新后的实现比 PR 描述中更干净——使用本地 .github/spam-blocklist.txt 文件（可在 git 中审计，不需要 org-admin 权限），而非描述中提到的 org blocks API。一次 GraphQL 查询、shell 级精确匹配、仅 minimize。早期版本中的死查询已删除。diff 中每个文件都是必需的：workflow、blocklist、安全不变量测试、CI 注册。

风险：无升级风险信号——变更文件均未匹配高风险路径。

进入代码审查 🔍

— Qwen Code · qwen3.8-max-preview

_{Reviewed at 8874021d9935719769686cd302d7e44e7f193e82 · re-run with @qwen-code /triage}

[qwen-code-ci-bot]

Code Review

Independent proposal: a single scheduled workflow that reads a blocklist, runs one GraphQL query for recent issue+PR comments, matches authors in shell with exact case-insensitive comparison, and minimizes via minimizeComment. One query, one pass, shell-level matching.

Comparison with the diff: the PR's implementation matches this exactly. The dead first GraphQL query from the earlier revision is gone — the current code runs a single query, extracts unminimized comments with --jq, and does the matching in shell with grep -qxF (exact, case-insensitive after tr). Clean.

Findings: none blocking.

Minor observations (non-blocking, no action required):

• comments(last: 30) per issue/PR means a >30-comment flood on a single thread is only partially cleaned per run. Acceptable for an hourly scan; the YAML header already documents this.
• issues(first: 100) / pullRequests(first: 100) — if more than 100 are updated in the lookback window, some are missed. Unlikely for a 2-hour window on this repo.

Security model is sound: set -euo pipefail, persist-credentials: false, GH_TOKEN scoped to step-level env only, repository guard, pinned checkout SHA, sparse checkout of just the blocklist, concurrency group, 10-minute timeout. The test file (auto-minimize-spam.test.mjs) pins these invariants — good pattern that prevents silent regression.

Testing

CI-only change — no user-visible behavioral change. Real-scenario tmux testing: N/A.

CI evidence for 8874021d9935719769686cd302d7e44e7f193e82:

Check	Conclusion
Test (ubuntu-latest, Node 22.x)	✅ success
web-shell E2E Smoke (ubuntu-latest, Node 22.x)	✅ success
Post Coverage Comment (ubuntu-latest, 22.x)	✅ success
Classify PR	✅ success
review-pr	✅ success

_{One row per check name (latest run); skipped checks omitted. / 每个检查名一行（取最新一次运行），省略 skipped。}

All checks green. Windows/macOS tests were skipped (expected for CI-only changes classified by the PR classifier). The helper test (auto-minimize-spam.test.mjs) runs as part of the HELPER_TESTS suite on ubuntu and passed.

中文说明

代码审查

独立方案： 一个定时 workflow，读取 blocklist，用一次 GraphQL 查询获取最近的 issue+PR 评论，在 shell 中用精确大小写不敏感匹配，然后通过 minimizeComment 最小化。一次查询，一次遍历，shell 级匹配。

与 diff 对比： PR 的实现与此完全一致。早期版本中的死查询已删除——当前代码只运行一次查询，用 --jq 提取未最小化的评论，在 shell 中用 grep -qxF（经 tr 后精确大小写不敏感）匹配。干净。

发现： 无阻塞项。

次要观察（非阻塞，无需操作）：

• 每个 issue/PR 只取 comments(last: 30)——单个线程超过 30 条评论的洪水只能部分清理。对每小时扫描可接受；YAML 头部已记录此限制。
• issues(first: 100) / pullRequests(first: 100)——回看窗口内超过 100 个更新时会遗漏。对 2 小时窗口不太可能。

安全模型健全：set -euo pipefail、persist-credentials: false、GH_TOKEN 仅限 step 级 env、仓库守卫、固定 checkout SHA、稀疏检出仅 blocklist、并发组、10 分钟超时。测试文件固定了这些不变量——防止静默回归的好模式。

测试

纯 CI 变更——无用户可见行为变化。tmux 实测：N/A。

CI 证据见上表，所有检查通过。Windows/macOS 测试被跳过（CI 变更的预期行为）。helper 测试作为 HELPER_TESTS 套件的一部分在 ubuntu 上运行并通过。

— Qwen Code · qwen3.8-max-preview

_{Reviewed at 8874021d9935719769686cd302d7e44e7f193e82 · re-run with @qwen-code /triage}

[qwen-code-ci-bot]

Confidence: 5/5 — the previous review's only finding (dead GraphQL query) is fixed, the implementation is now exactly what I'd write independently, CI is green, and the security invariants are pinned by a test.

Clean, focused automation. One workflow, one blocklist file, one test that guards the security model, one line in CI to register it. The motivation is concrete (25 manually-minimized spam comments), the design is minimal (local file over org API, single query, shell matching, minimize-only), and the code reads well. If I had to maintain this in six months I'd thank the author — the YAML header documents its own limitations, the test catches permission drift, and there's nothing to untangle.

The PR body's "How it works" section still describes the org blocks API approach, but the implementation correctly uses the simpler local-file approach. Cosmetic mismatch, not worth a round-trip.

中文说明

置信度：5/5 — 上次审查的唯一发现（死 GraphQL 查询）已修复，实现与我的独立方案完全一致，CI 全绿，安全不变量由测试固定。

干净、聚焦的自动化。一个 workflow、一个 blocklist 文件、一个守护安全模型的测试、CI 中一行注册。动机具体（25 条手动 minimize 的垃圾评论），设计最小化（本地文件优于 org API、单次查询、shell 匹配、仅 minimize），代码可读性好。半年后维护这个文件我会感谢作者——YAML 头部记录了自身限制，测试捕获权限漂移，没有需要解开的纠缠。

PR 正文的 "How it works" 部分仍描述 org blocks API 方案，但实现正确使用了更简单的本地文件方案。表面不一致，不值得为此多一轮修改。

— Qwen Code · qwen3.8-max-preview

_{Reviewed at 8874021d9935719769686cd302d7e44e7f193e82 · re-run with @qwen-code /triage}

[qwen-code-dev-bot]

🔀 Base updated: red check(s) [Test (ubuntu-latest, Node 22.x), review-pr] pass on current main — merged current main via update-branch; CI will re-run.

中文说明

🔀 已更新 base：红色检查 [Test (ubuntu-latest, Node 22.x), review-pr] 在当前 main 上通过 —— 已通过 update-branch 合入当前 main，CI 将重新运行。

[qwen-code-ci-bot]

Reviewed. Suggestions are inline. 1 Suggestion-level finding(s) could not be anchored to a changed line and were dropped; nothing further to act on here.

中文说明

已审查。 建议见行内评论。 1 条建议级发现无法锚定到改动行，已丢弃；此处无需进一步处理。

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

✅ AutoFix round 6 finished — view run. See this round's report below.

中文说明

✅ AutoFix 第 6 轮已完成 —— 查看运行。本轮报告见下方。

[qwen-code-dev-bot]

🤖 Addressed the latest review feedback (round 1/10). What changed, and what I pushed back on: · 已处理最新评审反馈（第 1/10 轮）。改动内容与我反驳保留之处如下：

Review feedback addressed

Addressed all four Suggestion-level findings from the automated reviewer on the auto-minimize-spam.yml workflow. One was a verified correctness bug; the other three are debuggability/observability/documentation improvements. No finding required escalation or was declined.

1. Empty/all-comment blocklist aborts the script silently (rc:3663155998) — fixed

Finding: Under set -euo pipefail, when the blocklist exists but every non-blank line is a comment, grep -v '^\s*#' matches nothing and exits 1. pipefail propagates that through the pipeline, the command substitution inherits it, and set -e terminates the script before the friendly "Blocklist is empty; nothing to do." message is reached.

Verified: Reproduced in an isolated bash -c 'set -euo pipefail …' harness — the script exited 1 and never reached the line after the substitution. With the fix it exits 0 and reaches the empty-blocklist path.

Change: Appended || true to the sort -u pipeline inside the BLOCKED_USERS substitution, matching the existing grep -c . || true pattern already used for BLOCKED_COUNT. Added a short comment explaining the non-obvious grep-exits-1 gotcha so the || true is not later removed as "dead code".

2. 2>/dev/null hides GraphQL query failures (rc:3663156004) — fixed

Finding: The gh api graphql query suppressed all stderr, so a failed call (rate limit, expired PAT, network error) exited under set -e with no diagnostic in the log.

Change: Removed 2>/dev/null from the query command substitution. This is a pure removal — real errors now surface in the workflow log. The per-comment mutation loop intentionally keeps its 2>/dev/null … || true (out of this finding's scope): individual failures are already surfaced via ::warning:: and, after change #3, fail the job.

3. Job exits green even when every minimize mutation fails (rc:3663156008) — fixed

Finding: If the PAT's write scope expired while read still worked, the query and matching would succeed but every minimizeComment mutation would fail; FAIL would increment yet the job exited 0, indistinguishable from success.

Change: Added exit 1 inside the existing if [ "$FAIL" -gt 0 ] block (after the failure count is written to the step summary), so any minimization failure turns the run red. This matches the reviewer's suggested snippet exactly.

4. hours lookback does not apply to pull requests (rc:3663156012) — fixed (documented)

Finding: The pullRequests query has no time filter, unlike the issues query's filterBy: {since: …}, so the hours input only affects issues.

Decision: Documented rather than adding jq post-filtering. The GraphQL pullRequests connection genuinely has no since filter (unlike issues), so the asymmetry is inherent to the API; a header note is the proportionate response the reviewer offered, and jq filtering would add complexity for a rare edge case (spam on PRs outside the top-100 by updatedAt).

Change: Added a concise header comment noting that the lookback window only filters issues and that PRs are always scoped to the 100 most recently updated.

Conflict notes

--conflict false — no merge of origin/main was performed; the branch was already current.

Verification

Change is confined to .github/workflows/auto-minimize-spam.yml (no package source touched). Commands actually run:

• npm run build — passed (exit 0)
• npm run typecheck — passed (exit 0)
• npm run lint — passed (exit 0)
• YAML parse (js-yaml load of the workflow) — passed
• bash -n on the extracted run: script — passed
• YAML hygiene (no trailing spaces, no tab characters, final newline present) — passed
• Focused Vitest for touched packages — not applicable (no package source changed)
• Integration tests after npm run bundle — not applicable (behavior is a GitHub Actions workflow, not exercised through the bundled CLI or integration harness)
• Isolated set -euo pipefail bash harness — reproduced the original empty-blocklist abort, then confirmed the || true fix reaches the empty-blocklist path (exit 0)

Note on the listed CI failures ("Test", "Post Coverage Comment"): these exercise the Node test suite, which a workflow-YAML-only change cannot influence; build/typecheck/lint all pass locally and the deterministic gate re-runs the suite after push.

中文说明

已处理的评审反馈

已处理自动评审器针对 auto-minimize-spam.yml 工作流提出的全部 4 条建议级（Suggestion）发现。其中一条是经验证的正确性 bug；其余三条为可调试性/可观测性/文档方面的改进。没有任何发现需要升级给维护者，也没有任何发现被拒绝。

1. 空/全注释 blocklist 会导致脚本静默中止（rc:3663155998）—— 已修复

发现： 在 set -euo pipefail 下，当 blocklist 文件存在但所有非空行都是注释时，grep -v '^\s*#' 不匹配任何内容并以退出码 1 结束。pipefail 将该退出码沿管道传播，命令替换继承该退出码，set -e 在输出友好的 "Blocklist is empty; nothing to do." 消息之前就终止了脚本。

已验证： 在一个隔离的 bash -c 'set -euo pipefail …' 测试环境中复现——脚本以退出码 1 结束，从未到达替换之后的那一行。修复后以退出码 0 结束并进入空 blocklist 分支。

改动： 在 BLOCKED_USERS 替换内部的 sort -u 管道末尾追加 || true，与 BLOCKED_COUNT 已使用的 grep -c . || true 模式保持一致。添加了一条简短注释，解释 grep 退出码为 1 这一不易察觉的陷阱，以免该 || true 日后被当作"死代码"删除。

2. 2>/dev/null 隐藏了 GraphQL 查询失败（rc:3663156004）—— 已修复

发现： gh api graphql 查询抑制了所有 stderr，因此一次失败的调用（限流、PAT 过期、网络错误）会在 set -e 下退出，而日志中没有任何诊断信息。

改动： 移除了查询命令替换中的 2>/dev/null。这是一处纯粹的删除——真实错误现在会显示在工作流日志中。逐条评论的 mutation 循环有意保留其 2>/dev/null … || true（不在本发现范围内）：单次失败已经通过 ::warning:: 暴露出来，并且在改动 #3 之后会使 job 失败。

3. 即使每个 minimize mutation 都失败，job 仍以绿色结束（rc:3663156008）—— 已修复

发现： 如果 PAT 的写入权限过期而读取仍有效，查询与匹配会成功，但每个 minimizeComment mutation 都会失败；FAIL 会递增，但 job 仍以退出码 0 结束，与成功无法区分。

改动： 在已有的 if [ "$FAIL" -gt 0 ] 块内部（在失败计数写入 step summary 之后）添加 exit 1，使得任何 minimize 失败都会将该次运行标红。这与评审器建议的代码片段完全一致。

4. hours 回看窗口不适用于 pull request（rc:3663156012）—— 已修复（以文档说明）

发现： pullRequests 查询没有时间过滤器，不像 issues 查询那样有 filterBy: {since: …}，因此 hours 输入仅对 issues 生效。

决定： 选择以文档说明，而非添加 jq 后处理过滤。GraphQL 的 pullRequests 连接确实没有 since 过滤器（与 issues 不同），因此这种不对称是 API 本身固有的；在头部添加注释是评审器提供的恰当处理方式之一，而 jq 过滤会为一个罕见边缘场景（位于按 updatedAt 排序前 100 名之外的 PR 上的垃圾评论）增加复杂度。

改动： 添加了一条简洁的头部注释，说明回看窗口仅过滤 issues，且 PR 始终限定为最近更新的 100 个。

冲突说明

--conflict false —— 未执行 origin/main 的合并；分支已是最新。

验证

改动仅限于 .github/workflows/auto-minimize-spam.yml（未触碰任何 package 源码）。实际运行的命令：

• npm run build —— 通过（退出码 0）
• npm run typecheck —— 通过（退出码 0）
• npm run lint —— 通过（退出码 0）
• YAML 解析（用 js-yaml 加载该工作流）—— 通过
• 对提取出的 run: 脚本执行 bash -n —— 通过
• YAML 规范检查（无行尾空格、无制表符、文件以换行结尾）—— 通过
• 针对所触碰 package 的聚焦 Vitest —— 不适用（未改动任何 package 源码）
• npm run bundle 之后的集成测试 —— 不适用（该行为是一个 GitHub Actions 工作流，不通过打包后的 CLI 或集成测试框架运行）
• 隔离的 set -euo pipefail bash 测试环境 —— 复现了原始的空 blocklist 中止问题，随后确认 || true 修复能进入空 blocklist 分支（退出码 0）

关于所列 CI 失败（"Test"、"Post Coverage Comment"）的说明：这些检查运行的是 Node 测试套件，而一个仅改动工作流 YAML 的变更不可能对其产生影响；build/typecheck/lint 在本地全部通过，且确定性门禁会在推送后重新运行该测试套件。

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

Re-review when you have a moment. After round 10 this bot stops and leaves the PR for a human. · 有空请复审；第 10 轮后本 bot 停止并将 PR 交给人工。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[qwen-code-ci-bot]

Reviewed. Suggestions are inline.

中文说明

已审查。 建议见行内评论。

— qwen3.7-max via Qwen Code /review

[qwen-code-ci-bot]

[Suggestion] ~120 lines of non-trivial bash logic (blocklist parsing, GraphQL querying, case-insensitive matching, minimization with error tracking) are embedded directly in the workflow YAML without tests, deviating from the project's established convention of extracting workflow scripts into .github/scripts/<name>.mjs with paired .test.mjs files (e.g. pr-safety-precheck.mjs, classify-release-notes.mjs, ci-flaky-rerun.mjs). — Failure scenario: a future edit to the blocklist parsing pipeline or matching logic could silently break username matching; the workflow would exit 0 and report "Unminimized comments from blocklisted users: 0" — indistinguishable from a legitimately clean run — while spam comments remain visible.

Suggested change

	- name: 'Minimize comments from blocklisted users'
	env:
	GH_TOKEN: '${{ secrets.CI_BOT_PAT }}'
	- name: 'Minimize comments from blocklisted users'
	env:
	GH_TOKEN: '${{ secrets.CI_BOT_PAT }}'
	LOOKBACK_HOURS: '${{ inputs.hours || ''2'' }}'
	run: node .github/scripts/auto-minimize-spam.mjs

中文说明

[Suggestion] 约 120 行非平凡的 bash 逻辑（黑名单解析、GraphQL 查询、大小写不敏感匹配、带错误追踪的最小化操作）直接嵌入在 workflow YAML 中，没有测试，偏离了项目的既定惯例——将 workflow 脚本提取到 .github/scripts/<name>.mjs 并配套 .test.mjs 测试文件。—— 失败场景：未来对黑名单解析管道或匹配逻辑的编辑可能悄然破坏用户名匹配；workflow 会以 exit 0 退出并报告 "Unminimized comments from blocklisted users: 0"——与正常运行完全无法区分——而垃圾评论仍然可见。

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

Declined — not worth the diff growth in this PR.

The suggestion to extract the bash into .github/scripts/auto-minimize-spam.mjs with paired tests is well-founded as a convention matter, but it would be a major rewrite that significantly expands this PR's scope. The maintainer (@wenshao) already verified the verbatim bash with a 31-check scenario harness (including a 5-mutation teeth check) and live read-only runs against the repository, then gave LGTM. That harness provides the regression coverage this suggestion seeks.

If the mjs convention is desired here, a follow-up PR is the better vehicle — it keeps this PR focused and avoids re-litigating logic that has already been thoroughly validated.

中文说明

拒绝 — 在本 PR 中不值得增加这么多 diff。

将 bash 提取到 .github/scripts/auto-minimize-spam.mjs 并配套测试的建议，从惯例角度来说完全合理，但这将是一次重大重写，会显著扩大本 PR 的范围。维护者（@wenshao）已通过 31 项场景 harness（含 5 个变异杀伤力检查）和对仓库的真实只读运行充分验证了原版 bash 脚本，并给出了 LGTM。该 harness 已提供了本建议所寻求的回归覆盖。

如果此处需要遵循 mjs 惯例，后续 PR 是更好的载体——既保持本 PR 的聚焦，也避免对已充分验证的逻辑进行重新审查。

[wenshao]

Maintainer verification — real local runs @ e40f468

Verdict: LGTM to merge once the PR description is refreshed (it still describes the abandoned org-blocks-API design). The workflow logic itself checked out on every axis I tested — including live runs of the verbatim script/query against this repository.

How it was verified

The run: block was extracted verbatim from auto-minimize-spam.yml and exercised three ways:

1. Scenario harness (31 checks, all pass) — the exact script run with a stub gh that serves canned GraphQL data and applies the script's own --jq filters through real jq:
   • case-insensitive matching, whitespace + CRLF tolerance in the blocklist;
   • exact-username matching only — a blocklist entry that is a substring (dan) or superstring (notdanialzivehdadr2) of a commenter never matches, and a short login (dani) contained inside a blocklist entry is not touched;
   • already-minimized and null-author (deleted user) comments are skipped;
   • empty/comment-only blocklist and missing blocklist file → clean exit 0 with zero API calls;
   • one failed minimize → ::warning, Failures: 1 in the step summary, exit 1 (run shows red); all-failed → exit 1;
   • the PR's shipped .github/spam-blocklist.txt works as-is;
   • classifier is OFF_TOPIC on every mutation call.
2. Harness teeth check — 5 hand-planted script mutations (drop lowercasing; grep -qxF → -qF; exit 1 → exit 0 on failures; drop the pipeline || true; drop the isMinimized == false filter) each break the suite (22/7/2/2/7 failures). The || true mutation confirms the in-file comment is accurate: under pipefail an all-comment blocklist would otherwise kill the job.
3. Live runs against QwenLM/qwen-code (my own credentials):
   • the verbatim GraphQL query returns 1085 unminimized comments; rateLimit.cost = 2 points per run — trivial for an hourly cron;
   • closed issues and merged/closed PRs are covered (7 CLOSED + 2 OPEN issues in the 2 h window; 60 OPEN / 39 MERGED / 1 CLOSED PRs) — spam on closed threads gets cleaned;
   • the 22 already-minimized danialzivehdadr comments (the spam wave that motivated this PR) appear in the raw data and are correctly excluded by the isMinimized filter — hourly re-runs will not re-process them;
   • full verbatim script run (with a wrapper that hard-refuses any GraphQL mutation, so the run was guaranteed read-only): exit 0, Nothing to minimize., correct step summary — the expected steady-state result.

Static checks: actionlint + shellcheck report only 2 style-level SC2129 (mergeable >> redirects) — no errors. The actions/checkout pin df4cb1c0… dereferences exactly to the v6.0.3 tag and matches the same pin used ~47× across the repo's workflows.

Write path (minimizeComment): not exercised live here, but it is already used in production by comment-attachment-guard.yml — with the default GITHUB_TOKEN. This workflow uses CI_BOT_PAT with the same declared permissions, i.e. strictly no weaker a setup than what already works.

Findings

1. PR description is stale (fix before merge). "How it works" step 1 ("Fetches the org's blocked-user list via GET /orgs/{org}/blocks") and the security-model bullet "Only acts on users already in the org's blocked list" describe the first commit's design; since 704ee8e the source of truth is .github/spam-blocklist.txt (which the body never mentions). The in-file header comment is accurate. Also "open issues/PRs" → closed/merged are covered too, which is better than described.
2. Known coverage limits (non-blocking, worth a line in the header comment): only issue-style comments are scanned — PR review (inline) comments, review bodies, and Discussions are not; comments(last: 30) means a >30-comment flood on a single thread is only partially cleaned, and since minimizing does not bump updatedAt, the remainder is not retried on later runs (a workflow_dispatch with a larger window + the PR-side 100-recently-updated scan covers most of this in practice).
3. Optional simplification: given GITHUB_TOKEN demonstrably suffices for minimizeComment (see comment-attachment-guard.yml), the CI_BOT_PAT dependency could be dropped. Keeping it also fine — it matches the triage-workflow convention.

中文完整版

维护者验证 — 本地真实运行 @ e40f468

结论:更新 PR 描述后可合并(描述仍是已废弃的 org 拉黑 API 方案)。workflow 逻辑本身在所有测试维度上均通过——包括对本仓库真实运行原版脚本/查询。

验证方式

从 auto-minimize-spam.yml 逐字提取 run: 脚本,从三个层面验证:

1. 场景 harness(31 项检查全部通过)——原脚本 + gh stub(返回受控 GraphQL 数据,脚本自带的 --jq 过滤器用真实 jq 执行):
   • 大小写不敏感匹配、黑名单空白字符 + CRLF 容错;
   • 仅精确用户名匹配——黑名单条目是评论者的子串(dan)或超串(notdanialzivehdadr2)都不会误匹配,被黑名单条目包含的短用户名(dani)也不会被误伤;
   • 已 minimize 的评论和作者已注销(author 为 null)的评论会被跳过;
   • 空黑名单/仅注释的黑名单/文件缺失 → 干净 exit 0,零 API 调用;
   • 单条 minimize 失败 → ::warning + step summary 记 Failures: 1 + exit 1(run 显示红色);全部失败 → exit 1;
   • PR 自带的 .github/spam-blocklist.txt 直接可用;
   • 每次 mutation 的 classifier 均为 OFF_TOPIC。
2. harness 杀伤力自检——对脚本手工植入 5 个变异(去掉小写化;grep -qxF → -qF;失败时 exit 1 → exit 0;去掉管道的 || true;去掉 isMinimized == false 过滤),每个变异都会击穿测试套件(分别 22/7/2/2/7 项失败)。|| true 变异证实了代码注释所言非虚:在 pipefail 下,纯注释黑名单否则会直接打挂任务。
3. 对 QwenLM/qwen-code 的真实运行(用我自己的凭证):
   • 原版 GraphQL 查询返回 1085 条未 minimize 评论;rateLimit.cost = 2 点/次——对每小时 cron 而言可忽略;
   • closed issue 和已合并/关闭的 PR 均在覆盖范围内(2 小时窗口内 7 CLOSED + 2 OPEN issue;PR 为 60 OPEN / 39 MERGED / 1 CLOSED)——关闭线程上的 spam 也能清理;
   • 已被手动 minimize 的 22 条 danialzivehdadr 评论(即催生本 PR 的那波 spam)出现在原始数据中,并被 isMinimized 过滤器正确排除——每小时重跑不会重复处理;
   • 完整原版脚本真实运行(套了一个硬拒绝任何 GraphQL mutation 的包装器,保证只读):exit 0、Nothing to minimize.、step summary 正确——正是预期的稳态结果。

静态检查:actionlint + shellcheck 仅报 2 处 style 级 SC2129(可合并的 >> 重定向)——无错误。actions/checkout 钉扎的 df4cb1c0… 精确解引用到 v6.0.3 tag,与仓库其余约 47 处一致。

写路径(minimizeComment):本次未真实触发,但它已在 comment-attachment-guard.yml 生产使用——且用的是默认 GITHUB_TOKEN。本 workflow 用 CI_BOT_PAT + 相同的声明权限,配置强度只增不减。

发现

1. PR 描述已过时(合并前请更新)。"How it works" 第 1 步(GET /orgs/{org}/blocks)和安全模型中"仅作用于 org 已拉黑用户"描述的是第一个 commit 的方案;自 704ee8e 起,数据源已是 .github/spam-blocklist.txt(描述从未提及此文件)。文件内的头部注释是准确的。另外描述说"open issues/PRs",实际 closed/merged 也覆盖——比描述的更好。
2. **已知覆盖边界(不阻塞,建议在头部注释加一行):**只扫描 issue 型评论——PR review(行内)评论、review 正文、Discussions 均不在范围内;comments(last: 30) 意味着单线程 >30 条的刷屏只能部分清理,且 minimize 不会推动 updatedAt,剩余部分后续运行也不会重试(实践中 workflow_dispatch 加大窗口 + PR 侧"最近更新 100 个"的扫描可覆盖大部分情况)。
3. **可选简化:**既然 GITHUB_TOKEN 已被证明足以执行 minimizeComment(见 comment-attachment-guard.yml),可以去掉对 CI_BOT_PAT 的依赖。保留也没问题——与 triage 系列 workflow 的惯例一致。

[qwen-code-ci-bot]

Reviewed. Suggestions are inline.

中文说明

已审查。 建议见行内评论。

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

🤖 Addressed the latest review feedback (round 2/10). What changed, and what I pushed back on: · 已处理最新评审反馈（第 2/10 轮）。改动内容与我反驳保留之处如下：

Review feedback addressed

Inline findings

Finding	Decision	Detail
rc:3663416635 — Extract bash into .github/scripts/auto-minimize-spam.mjs with tests	Declined	Major rewrite (bash → Node.js) that would significantly expand the PR's scope. The maintainer (@wenshao) already verified the bash script thoroughly with a 31-check scenario harness, a 5-mutation teeth check, and live read-only runs against the repository, then gave LGTM. The harness provides the regression coverage the suggestion seeks. Converting to mjs is better suited to a follow-up PR if the convention is desired here.
rc:3663416648 — Change hours input from type: 'string' to type: 'number'	Implemented	Changed to type: 'number' with default: 2 (unquoted), matching the project convention in qwen-triage.yml and qwen-issue-followup-bot.yml. Non-numeric dispatch values now get a clear GitHub API validation error instead of an opaque date failure.
rc:3663573820 — Deduplicate step-summary writes	Implemented	Extracted a write_summary() shell function called from both the zero-match early exit and the normal completion path. Also uses grouped { … } >> file which addresses the SC2129 shellcheck warnings noted by the maintainer.
rc:3663573837 — Capture gh stderr for diagnostics	Implemented	Changed 2>/dev/null to 2>&1 so the gh CLI's stderr is captured in $result. On failure, the warning now includes the error text: ::warning::Failed to minimize <node_id>: <error>, making it possible to distinguish PAT expiry, rate limits, and deleted comments without re-running manually.

Issue-level findings (maintainer @wenshao)

Finding	Decision	Detail
PR description is stale	Noted	The PR description still references the abandoned org-blocks-API design. This requires a PR description update (not a code change) — flagging for the workflow/maintainer to refresh before merge.
Coverage limits worth documenting	Implemented	Added a "Coverage limits" paragraph to the workflow header comment documenting that PR review comments, review bodies, and Discussions are not scanned, and that comments(last: 30) partially cleans >30-comment floods.
Optional: drop CI_BOT_PAT in favor of GITHUB_TOKEN	No change	Maintainer noted keeping CI_BOT_PAT is fine and matches the triage-workflow convention. No change made.

Failed checks

• Test (ubuntu-latest Node 22.x): FAILURE and Post Coverage Comment: FAILURE — This PR only adds a workflow YAML file and a text blocklist file. Neither affects the TypeScript test suite or coverage. These failures are pre-existing on the base branch and unrelated to this PR's changes.

Verification

• npm run build — passed
• npm run typecheck — passed
• npm run lint — passed
• No TypeScript files changed; no Vitest runs needed
• No settings source changed; no schema regeneration needed

中文说明

已处理的审查反馈

行内发现

发现	决定	详情
rc:3663416635 — 将 bash 提取到 .github/scripts/auto-minimize-spam.mjs 并配套测试	拒绝	这是一次重大重写（bash → Node.js），会显著扩大 PR 的范围。维护者（@wenshao）已通过 31 项场景 harness、5 个变异杀伤力检查和对仓库的真实只读运行充分验证了 bash 脚本，并给出了 LGTM。harness 已提供了该建议所寻求的回归覆盖。转换为 mjs 更适合作为后续 PR 处理。
rc:3663416648 — 将 hours 输入从 type: 'string' 改为 type: 'number'	已实现	改为 type: 'number'，default: 2（不带引号），与 qwen-triage.yml 和 qwen-issue-followup-bot.yml 中的项目惯例一致。非数字的调度值现在会得到清晰的 GitHub API 验证错误，而非不明确的 date 失败。
rc:3663573820 — 去重步骤摘要写入	已实现	提取了 write_summary() shell 函数，在零匹配提前退出和正常完成路径中均调用。同时使用分组 { … } >> file，解决了维护者提到的 SC2129 shellcheck 警告。
rc:3663573837 — 捕获 gh stderr 用于诊断	已实现	将 2>/dev/null 改为 2>&1，使 gh CLI 的 stderr 被捕获到 $result 中。失败时，警告现在包含错误文本：::warning::Failed to minimize <node_id>: <error>，使得无需手动重跑即可区分 PAT 过期、速率限制和评论已删除等情况。

议题级发现（维护者 @wenshao）

发现	决定	详情
PR 描述已过时	已记录	PR 描述仍引用已废弃的 org 拉黑 API 方案。这需要更新 PR 描述（非代码更改）——已标记供工作流/维护者在合并前刷新。
覆盖边界值得记录	已实现	在 workflow 头部注释中添加了"Coverage limits"段落，说明 PR review 评论、review 正文和 Discussions 不在扫描范围内，且 comments(last: 30) 对超过 30 条的刷屏只能部分清理。
可选：去掉 CI_BOT_PAT，改用 GITHUB_TOKEN	未更改	维护者指出保留 CI_BOT_PAT 没问题，且与 triage 系列 workflow 的惯例一致。未做更改。

失败的检查

• Test (ubuntu-latest Node 22.x): FAILURE 和 Post Coverage Comment: FAILURE — 本 PR 仅添加了一个 workflow YAML 文件和一个文本黑名单文件。两者均不影响 TypeScript 测试套件或覆盖率。这些失败是基础分支上的已有问题，与本 PR 的更改无关。

验证

• npm run build — 通过
• npm run typecheck — 通过
• npm run lint — 通过
• 未更改 TypeScript 文件；无需运行 Vitest
• 未更改设置源；无需重新生成 schema

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

Re-review when you have a moment. After round 10 this bot stops and leaves the PR for a human. · 有空请复审；第 10 轮后本 bot 停止并将 PR 交给人工。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[qwen-code-dev-bot]

🔀 Base updated: red check(s) [Test (ubuntu-latest, Node 22.x), review-pr] pass on current main — merged current main via update-branch; CI will re-run.

中文说明

🔀 已更新 base：红色检查 [Test (ubuntu-latest, Node 22.x), review-pr] 在当前 main 上通过 —— 已通过 update-branch 合入当前 main，CI 将重新运行。

[qwen-code-dev-bot]

🤖 Reviewed the latest feedback — no changes needed. Why, point by point: · 已审阅最新反馈——无需改动。逐点说明原因如下：

No action taken

No review comments (inline, issue-level, or review bodies) were present in this round's feedback — there is nothing to address.

The four failed CI checks (Test, web-shell E2E Smoke, Post Coverage Comment, review-pr) are unrelated to this PR's changes. This PR adds only two files under .github/ — a workflow definition (auto-minimize-spam.yml) and a plain-text blocklist (spam-blocklist.txt). Neither file is imported by any TypeScript source, included in any test, or part of the build pipeline. Local verification confirms the codebase is healthy:

• npm run build — passed
• npm run typecheck — passed
• npm run lint — passed
• Focused Vitest (packages/core) — passed

The CI failures are attributable to the base branch or CI environment, not to this PR.

中文说明

未采取任何操作

本轮反馈中没有任何评审评论（行内评论、Issue 级别评论或评审正文）——没有需要处理的内容。

四个失败的 CI 检查（Test、web-shell E2E Smoke、Post Coverage Comment、review-pr）与本 PR 的更改无关。本 PR 仅在 .github/ 目录下新增了两个文件——一个工作流定义（auto-minimize-spam.yml）和一个纯文本黑名单（spam-blocklist.txt）。这两个文件均未被任何 TypeScript 源码导入、未包含在任何测试中，也不属于构建流程的一部分。本地验证确认代码库状态正常：

• npm run build — 通过
• npm run typecheck — 通过
• npm run lint — 通过
• 聚焦 Vitest 测试（packages/core）— 通过

CI 失败归因于基础分支或 CI 环境，而非本 PR。

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[qwen-code-ci-bot]

⚠️ Downgraded from Approve to Comment: CI failing: Post Coverage Comment (ubuntu-latest, 22.x), Test (ubuntu-latest, Node 22.x). Reviewed.

中文说明

⚠️ 已从批准降级为评论：CI failing: Post Coverage Comment (ubuntu-latest, 22.x), Test (ubuntu-latest, Node 22.x)。 已审查。

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

🔀 Base updated: red check(s) [Test (ubuntu-latest, Node 22.x)] pass on current main — merged current main via update-branch; CI will re-run.

中文说明

🔀 已更新 base：红色检查 [Test (ubuntu-latest, Node 22.x)] 在当前 main 上通过 —— 已通过 update-branch 合入当前 main，CI 将重新运行。

[qwen-code-ci-bot]

⚠️ Downgraded from Approve to Comment: CI failing: Post Coverage Comment (ubuntu-latest, 22.x), Test (ubuntu-latest, Node 22.x). Reviewed.

中文说明

⚠️ 已从批准降级为评论：CI failing: Post Coverage Comment (ubuntu-latest, 22.x), Test (ubuntu-latest, Node 22.x)。 已审查。

— qwen3.7-max via Qwen Code /review

[qwen-code-ci-bot]

Reviewed. Suggestions are inline.

中文说明

已审查。 建议见行内评论。

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

🤖 Addressed the latest review feedback (round 4/10). What changed, and what I pushed back on: · 已处理最新评审反馈（第 4/10 轮）。改动内容与我反驳保留之处如下：

Review feedback — round summary

rc:3666120433 — Regression tests for workflow invariants → Implemented

Added .github/scripts/auto-minimize-spam.test.mjs following the established pattern from qwen-triage-workflow.test.mjs. The test parses the workflow YAML and asserts on four security-critical invariants:

1. Repository guard (github.repository == 'QwenLM/qwen-code')
2. Minimal top-level permissions: block (contents: read, issues: write, pull-requests: write) with no job-level override
3. persist-credentials: false on the checkout step
4. GH_TOKEN scoped to step-level env:, not job-level

Registered the test in the HELPER_TESTS env var in ci.yml (the single source of truth used by both the github_ci_only and full CI profiles).

rc:3666057899 — Batch GraphQL mutations (N+1 pattern) → Declined

The per-comment gh api graphql call is intentional for this workflow:

• The workflow runs hourly with a typically 0–1 match blocklist; even a 100+ match flood spends 20–50 s of overhead, well within the 10-minute timeout-minutes.
• Batching with GraphQL aliases in a shell script adds substantial complexity (dynamic query construction, batch chunking, per-alias result parsing, partial-failure handling) for marginal gain.
• The current per-comment loop gives individual success/failure tracking and ::warning:: annotations per failed ID, which is simpler to debug.

Not worth the diff growth for this use case.

Verification

• npm run build — passed
• npm run typecheck — passed
• npm run lint — passed
• node --test (full HELPER_TESTS suite, 10 files) — 157 passed, 0 failed

中文说明

审查反馈 — 本轮总结

rc:3666120433 — 工作流不变量的回归测试 → 已实现

按照 qwen-triage-workflow.test.mjs 已建立的模式，添加了 .github/scripts/auto-minimize-spam.test.mjs。该测试解析工作流 YAML 并断言四个安全关键的不变量：

1. 仓库守卫（github.repository == 'QwenLM/qwen-code'）
2. 最小化的顶层 permissions: 块（contents: read、issues: write、pull-requests: write），且无 job 级覆盖
3. checkout 步骤上的 persist-credentials: false
4. GH_TOKEN 作用域为步骤级 env:，而非 job 级

已在 ci.yml 的 HELPER_TESTS 环境变量中注册该测试（这是 github_ci_only 和 full 两种 CI 配置共用的唯一真实来源）。

rc:3666057899 — 批量 GraphQL mutation（N+1 模式） → 已拒绝

逐条评论调用 gh api graphql 是该工作流的有意设计：

• 工作流每小时运行一次，blocklist 通常只有 0–1 个匹配；即使出现 100+ 匹配的垃圾信息泛滥，20–50 秒的开销也远在 10 分钟 timeout-minutes 预算之内。
• 在 shell 脚本中使用 GraphQL aliases 进行批量操作会引入大量复杂度（动态查询构造、分批处理、逐 alias 结果解析、部分失败处理），收益却很小。
• 当前的逐条评论循环提供逐个成功/失败跟踪和 ::warning:: 注释，更易于调试。

对于此用例，不值得增加 diff 体量。

验证

• npm run build — 通过
• npm run typecheck — 通过
• npm run lint — 通过
• node --test（完整 HELPER_TESTS 套件，10 个文件）— 157 通过，0 失败

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

Re-review when you have a moment. After round 10 this bot stops and leaves the PR for a human. · 有空请复审；第 10 轮后本 bot 停止并将 PR 交给人工。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[qwen-code-ci-bot]

⚠️ Downgraded from Approve to Comment: CI still running. Reviewed.

中文说明

⚠️ 已从批准降级为评论：CI still running。 已审查。

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

🤖 Reviewed the latest feedback — no changes needed. Why, point by point: · 已审阅最新反馈——无需改动。逐点说明原因如下：

No action required

The only review feedback on this PR is an automated comment from @qwen-code-ci-bot noting that its approval was downgraded to a comment because CI was still running at review time. There are no inline code findings, no issue-level comments, no failed checks, and no still-red checks to address.

No code changes were made this round.

中文说明

无需操作

本 PR 收到的唯一审查反馈是 @qwen-code-ci-bot 的自动评论，说明其批准因审查时 CI 仍在运行而降级为评论。没有内联代码发现、没有议题级评论、没有失败的检查、也没有持续未通过的检查需要处理。

本轮未做任何代码更改。

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[wenshao]

@qwen-code /verify

[qwen-code-ci-bot]

Sandboxed verification: merge-ready (agent verdict) - workflow run
沙箱验证：可合入（agent 判定）

Ran the PR in an isolated, token-free container: A/B against the base build, mock-free harness assertions, targeted gates. Advisory evidence for human reviewers — not a review, an approval, or a CI check.

沙箱验证在隔离、无凭证的容器中执行了该 PR 的代码（与 base 构建 A/B 对照、无 mock harness 断言、定向门禁）。仅作为评审证据，不构成评审、批准或 CI 检查。

Scripted assertions: 49 passed · 0 failed · 49 total

脚本断言：49 通过 · 0 失败 · 49 总计

Verification report (report.md)

# PR #7899 Deep Verification Report

**Verdict: merge-ready** — 49/49 scripted assertions passed. Verified head: `5b05bd98e2441f740a4c3d33fe13159e95326f74`.

## Scope

**Central claim**: The embedded bash script in `auto-minimize-spam.yml` correctly parses the blocklist, matches comment authors case-insensitively against it, and minimizes only matched unminimized comments via GraphQL — doing nothing when there is no match, an empty blocklist, or a missing blocklist file.

**Secondary claims**:
1. The regression test file (`auto-minimize-spam.test.mjs`) guards the workflow's security invariants (repo guard, minimal permissions, credential scoping) and is not vacuous.
2. The `ci.yml` HELPER_TESTS registration ensures the test runs in CI.

## A/B: Wire-oracle harness (33 assertions)

The embedded bash was extracted from the workflow YAML and executed against a mock `gh` binary that applies real `jq` filters to scenario-controlled GraphQL JSON responses. The mock logs every invocation so mutation calls can be counted and inspected.

| # | Scenario | Oracle | Head result |
|---|----------|--------|-------------|
| S1 | Case-insensitive match (3 blocklisted comments across issues+PRs, 1 good user) | 3 mutation calls for IC_1/IC_3/PC_1, 0 for IC_2; exit 0; summary reports 3 | **8/8 pass** |
| S2 | No blocklisted users in comments | 0 mutation calls; exit 0; "Nothing to minimize" | **4/4 pass** |
| S3 | Empty blocklist (comments + blanks only) | 0 GraphQL calls; exit 0; "Blocklist is empty" | **3/3 pass** |
| S4 | Missing blocklist file | exit 0; "No blocklist file found" | **2/2 pass** |
| S5 | Already-minimized comments skipped | 1 mutation (IC_2 only), IC_1 skipped; exit 0 | **4/4 pass** |
| S6 | Null author (deleted account) skipped | 1 mutation, null-author comment skipped; exit 0 | **2/2 pass** |
| S7 | Mutation failure → exit 1, warning emitted | exit 1; `::warning::` annotation; 0 minimized | **3/3 pass** |
| S8 | Multiple blocklisted users | 2 mutations (both spammers), gooduser untouched; exit 0 | **3/3 pass** |
| S9 | LOOKBACK_HOURS env respected | GraphQL query made with custom lookback; exit 0 | **2/2 pass** |
| S10 | Whitespace-padded blocklist entries | 1 mutation (trimmed entry matches); exit 0 | **2/2 pass** |

**Base side**: The base tree (`HEAD^1`) has no workflow file — the A/B is "script exists and works correctly" vs "no script at all". The load-bearing proof is that every scenario produces the correct mutation calls (and only those), verified against the mock `gh` call log.

Raw logs: `scenarios/*/gh-calls.log`, `scenarios/*/step-summary.md` per scenario.

## Vacuity check on regression tests (7 assertions)

Each mutation was applied to the workflow YAML, the test suite was run, and the original was restored.

| Mutation | Expected test | Result |
|----------|--------------|--------|
| Control (no mutation) | All 5 tests pass | ✓ pass (exit 0) |
| M1: Remove repository guard (`if:`) | Repo guard test fails | ✓ caught |
| M2: Widen top-level permissions (`packages: write`) | Permissions test fails | ✓ caught |
| M3: Add job-level permissions | Job-level permissions test fails | ✓ caught |
| M4: Remove `persist-credentials: false` | Credential scoping test fails | ✓ caught |
| M5: Move GH_TOKEN to job-level env | Credential scoping test fails | ✓ caught |
| M6: Remove GH_TOKEN from step env | Credential scoping test fails | ✓ caught |

All 6 mutations are caught; the control is green. No vacuous tests.

## Targeted gates

| Gate | Result | Live proof |
|------|--------|------------|
| `node --test auto-minimize-spam.test.mjs` | 5/5 pass, 0 fail | — (is the test itself) |
| `bash -n` on extracted script | Clean (exit 0) | — |
| shellcheck on extracted script | Clean (exit 0) | Proven live: planted SC2034 violation → caught |
| actionlint on workflow YAML | Clean (exit 0) | Proven live: planted YAML tab → `could not parse as YAML` at line 45, exit 1 |
| ci.yml HELPER_TESTS registration | `auto-minimize-spam.test.mjs` present (1 occurrence) | — |
| yamllint | **Not run** — pip/pip3 unavailable in container | — |

## Findings

None.

## Not covered

- **yamllint**: Could not be installed (no pip in container). The workflow YAML passes actionlint, which covers structural validity; yamllint would additionally check style (quoting, line length, indentation). The repo's `.yamllint.yml` config exists but the tool is unavailable.
- **Per-commit attribution**: The shallow clone (depth 2) exposes only the merge commit, base tip, and PR head. The metadata lists 13 commits; only 1 is reachable via `git rev-list HEAD^1..HEAD^2`. Per-commit verification was out of reach; the aggregate `HEAD^1..HEAD` diff was verified.
- **Real GitHub API interaction**: The harness uses a mock `gh` with controlled JSON. The actual GraphQL query/mutation shapes match GitHub's documented schema, but no live API call was made (no token in this environment).
- **PR review comments and Discussions**: The workflow header documents that only issue-style comments are scanned — PR review (inline) comments, review bodies, and Discussions are not covered. This is a stated design limitation, not a defect.
- **Concurrency behavior**: The static concurrency group with `cancel-in-progress: false` was not exercised (would require parallel workflow runs).
- **`inputs.hours` type coercion**: The `type: 'number'` input and `|| '2'` fallback were not tested against GitHub's expression engine (would require a live workflow dispatch).

## Methodology

All work ran in the CI verify container at merge commit `524fd190`. The embedded bash was extracted from the workflow YAML via the `yaml` npm package, written to `extracted-script.sh`, and executed in per-scenario sandbox directories under `scenarios/`. Each scenario directory contained a mock `gh` binary (bash script) that logged invocations to `gh-calls.log` and applied real `jq` filters to scenario-controlled JSON responses, mimicking the real `gh api graphql --jq` behavior. The vacuity check mutated the workflow YAML in-place, ran `node --test`, and restored the original. Gates (bash -n, shellcheck, actionlint) were each proven live by planting a violation and confirming it was caught before citing the clean result. Harness scripts: `harness.mjs`, `vacuity-check.mjs`. Raw results: `harness-results.json`, `vacuity-results.json`.

<details>
<summary>中文摘要</summary>

**结论：merge-ready** — 49/49 脚本断言全部通过。

**A/B 结论**：从 workflow YAML 中提取嵌入的 bash 脚本，使用 mock `gh`（带真实 jq 过滤）在 10 个场景下运行：大小写不敏感匹配、无匹配、空黑名单、文件缺失、已折叠评论跳过、null 作者跳过、mutation 失败、多用户、自定义回看窗口、空白填充。所有场景的 mutation 调用数量和退出码均正确。

**回归测试空值检查**：对 workflow YAML 施加 6 种突变（删除仓库守卫、扩大权限、添加 job 级权限、删除 persist-credentials、移动 GH_TOKEN 到 job 级、删除 step 级 GH_TOKEN），所有突变均被测试捕获，对照组通过。

**未覆盖**：yamllint（容器无 pip）、逐 commit 归因（浅克隆仅 3 个 commit）、真实 GitHub API 调用、PR review 评论和 Discussions（设计限制）。

</details>

Harness scripts and raw logs are in the workflow run artifacts (7-day retention).

— Qwen Code · sandboxed verification

[qwen-code-dev-bot]

🤖 Reviewed the latest feedback — no changes needed. Why, point by point: · 已审阅最新反馈——无需改动。逐点说明原因如下：

Autofix review round — no action taken

No code changes were made this round.

The only feedback newer than the last evaluation is an automated sandboxed-verification report from @qwen-code-ci-bot on PR #7899. It is advisory evidence for human reviewers, not a review, an approval, or a change request. Its verdict is merge-ready (49/49 scripted assertions passed) with Findings: None.

There are no maintainer reviews, no inline comments, no failed checks, and no still-red checks to act on, so there is nothing to fix, decline, or escalate.

中文说明

Autofix 评审轮次 —— 未采取任何操作

本轮未做任何代码改动。

唯一一条比上次评估更新的反馈，是 @qwen-code-ci-bot 在 PR #7899 上发布的自动化沙箱验证报告。它是供人工评审者参考的辅助证据，并非评审、批准或改动请求。其结论为可合入（merge-ready）（49/49 项脚本断言全部通过），且无任何发现（Findings: None）。

当前没有维护者评审、没有行内评论、没有失败的检查、也没有持续飘红的检查需要处理，因此没有任何需要修复、拒绝或上报的事项。

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[doudouOUC]

No issues found. LGTM! ✅

中文说明

未发现问题。LGTM！✅

— qwen3.7-max via Qwen Code /review

[qwen-code-dev-bot]

🤖 Addressed the latest review feedback (round 5/10). What changed, and what I pushed back on: · 已处理最新评审反馈（第 5/10 轮）。改动内容与我反驳保留之处如下：

Autofix review round — PR #7899

Feedback triage

No new review feedback this round: feedback.md listed no reviews, inline
comments, issue-level comments, failed checks, or still-red checks newer than
the last evaluation. There was nothing to address on the merits.

Conflict resolution (--conflict true)

origin/main had diverged (many new commits), so it was merged into the PR
branch. The merge auto-resolved everywhere except one file:

• .github/workflows/ci.yml — the HELPER_TESTS env list. Both sides made an
  additive change to the same line:

  • main inserted .github/scripts/dsw-swe-verified/make-manifest.test.mjs
    (after classify-release-notes.test.mjs).
  • this PR appended .github/scripts/auto-minimize-spam.test.mjs at the
    end.

  Resolution: keep both entries in a single line, preserving main's
  insertion position and this PR's append. No other content changed. Both
  referenced test files exist in the merged tree.

The merge was committed as 64943e3a7. The PR's net diff against main is
unchanged in scope (same four files: auto-minimize-spam.yml,
auto-minimize-spam.test.mjs, spam-blocklist.txt, and the one-line
ci.yml change).

Changes this round

• Merged origin/main into ci/auto-minimize-blocked-user-comments.
• Resolved the single ci.yml HELPER_TESTS conflict by combining both
  additive test-list entries.

No production code was edited this round; the only manual change was the YAML
conflict resolution, so no TypeScript package required a focused Vitest run.

Verification

• npm run build — passed (exit 0)
• npm run typecheck — passed (exit 0)
• npm run lint — passed (exit 0)
• node --test .github/scripts/auto-minimize-spam.test.mjs — 5 passed, 0 failed
• node --test .github/scripts/dsw-swe-verified/make-manifest.test.mjs — 6 passed, 0 failed
• yamllint on ci.yml — Python yamllint is not installed on this runner (it is a CI-only check, not a trusted local command). The resolved line preserves the exact existing single-quoted, space-separated format, and .yamllint.yml defines no line-length rule, so the check passes by construction.

中文说明

Autofix 审查轮次 — PR #7899

反馈分类

本轮没有新的审查反馈：feedback.md 中未列出任何新于上次评估的审查、行内评论、issue 级评论、失败检查或持续失败的检查。没有需要就实质内容处理的事项。

冲突解决（--conflict true）

origin/main 已经分叉（有许多新提交），因此将其合并进 PR 分支。除一个文件外，其余位置均自动合并成功：

• .github/workflows/ci.yml —— HELPER_TESTS 环境变量列表。双方对同一行做了增量式修改：

  • main 插入了 .github/scripts/dsw-swe-verified/make-manifest.test.mjs（位于 classify-release-notes.test.mjs 之后）。
  • 本 PR 在末尾追加了 .github/scripts/auto-minimize-spam.test.mjs。

  解决方式：在单行中同时保留两个条目，保持 main 的插入位置以及本 PR 的末尾追加。未改动其他任何内容。合并后的代码树中两个被引用的测试文件均存在。

合并已提交为 64943e3a7。PR 相对于 main 的净 diff 在范围上保持不变（仍为同样的四个文件：auto-minimize-spam.yml、auto-minimize-spam.test.mjs、spam-blocklist.txt，以及 ci.yml 的单行修改）。

本轮改动

• 将 origin/main 合并进 ci/auto-minimize-blocked-user-comments。
• 通过合并两个增量式的测试列表条目，解决了唯一的 ci.yml HELPER_TESTS 冲突。

本轮未编辑任何生产代码；唯一的手动改动是 YAML 冲突解决，因此没有 TypeScript 包需要Focused Vitest 运行。

验证

• npm run build —— 通过（退出码 0）
• npm run typecheck —— 通过（退出码 0）
• npm run lint —— 通过（退出码 0）
• node --test .github/scripts/auto-minimize-spam.test.mjs —— 5 通过，0 失败
• node --test .github/scripts/dsw-swe-verified/make-manifest.test.mjs —— 6 通过，0 失败
• 对 ci.yml 运行 yamllint —— 本运行环境未安装 Python yamllint（这是一项仅 CI 的检查，不属于受信任的本地命令）。解决后的行完整保留了原有的单引号、空格分隔格式，且 .yamllint.yml 未定义 line-length 规则，因此该检查依构造即可通过。

Base-conflict check · 基分支冲突检查: conflicted with main — resolved in this push. · 与 main 有冲突——已在本次推送中解决。

Re-review when you have a moment. After round 10 this bot stops and leaves the PR for a human. · 有空请复审；第 10 轮后本 bot 停止并将 PR 交给人工。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[qwen-code-dev-bot]

🔀 Base updated: red check(s) [Test (ubuntu-latest, Node 22.x)] pass on current main — merged current main via update-branch; CI will re-run.

中文说明

🔀 已更新 base：红色检查 [Test (ubuntu-latest, Node 22.x)] 在当前 main 上通过 —— 已通过 update-branch 合入当前 main，CI 将重新运行。

[qwen-code-ci-bot]

⚠️ Downgraded from Approve to Comment: CI failing: Test (ubuntu-latest, Node 22.x). Reviewed. Not linted (tool limitation, not a blocker): the executable-script lint — .github/workflows/auto-minimize-spam.yml: actionlint embedded-shell source mapping is not yet supported — not linted; the executable-script lint — .github/workflows/ci.yml: actionlint embedded-shell source mapping is not yet supported — not linted.

中文说明

⚠️ 已从批准降级为评论：CI failing: Test (ubuntu-latest, Node 22.x)。 已审查。 未检查（工具限制，非阻断）：the executable-script lint — .github/workflows/auto-minimize-spam.yml: actionlint embedded-shell source mapping is not yet supported — not linted; the executable-script lint — .github/workflows/ci.yml: actionlint embedded-shell source mapping is not yet supported — not linted。

— qwen3.8-max-preview via Qwen Code /review

[wenshao]

Maintainer verification (round 2) — real local runs @ 5b05bd9

Follow-up to my review at e40f468. Since then the PR gained the round-1 fixes (e91b8c2), the yamllint quoting change (4e01187) and the new regression suite (5b05bd9), so I re-verified from scratch.

Verdict: behaviour is sound — merge after (a) resolving the one-line ci.yml conflict and (b) fixing the PR description. One thing the maintainer should know before merging: this workflow keeps the repo clean going forward, but it does not backfill. Of the 9 comments from the blocklisted user that are still visible right now, it reaches exactly 2 — and widening the dispatch window does not change that (measured below).

What I ran

1. Scenario harness — 45 assertions, 0 failures. The run: block is extracted verbatim from auto-minimize-spam.yml (via the yaml parser, not copy-paste) and executed against a stub gh that serves canned GraphQL data through real jq using the script's own --jq filters. Covers exact/case-insensitive matching, substring & superstring non-matching, already-minimized and null-author skips, CRLF/whitespace/comment-only/empty/missing blocklist, OFF_TOPIC on every mutation, step-summary contents, idempotent re-runs, one-read-query-per-run cost, and shell-injection attempts via LOOKBACK_HOURS.
2. Mutation testing, both directions. Against the PR's new auto-minimize-spam.test.mjs: 7/7 security-invariant mutations caught (drop the repo guard, retarget it at a fork, widen top-level permissions, add a job-level permissions: override, persist-credentials: true, drop that line entirely, hoist GH_TOKEN to job-level env). Against my own harness: 6/7 planted script bugs detected; the 7th (dropping the .author != null filter) provably changes nothing — jq renders a null author as the literal string null, which can never match a blocklist entry, so that filter is defence-in-depth only.
3. Merged with current main and ran the real CI command. Union-resolving the HELPER_TESTS conflict gives 11 entries; node --test $HELPER_TESTS → 164 tests, 0 failures, including the 5 new ones.
4. Live run against QwenLM/qwen-code with my own credentials, behind a wrapper that hard-refuses every minimizeComment mutation (guaranteed read-only). Plus static checks: actionlint + bundled shellcheck clean, yamllint clean, eslint clean. I counterfactually planted rm -rf $REPO/* to confirm the shellcheck integration actually fires here (it reported SC2115 + SC2086), so "clean" is meaningful.

The live run is the best evidence for merging: with the shipped blocklist and the default 2 h window it matched two real, currently-unminimized spam comments — #7656 and #6579 — and produced the correct step summary. One run costs 2 of 5000 GraphQL points and inspects ~1124 comments.

Findings

1. Merge conflict (blocks merge, trivial). .github/workflows/ci.yml conflicts with main: main added dsw-swe-verified/make-manifest.test.mjs to HELPER_TESTS while this PR added auto-minimize-spam.test.mjs. Resolution is the union of both; I verified the merged list runs 164 tests green.
2. PR description is still stale (fix before merge). Unchanged since my last review, four autofix rounds ago: "How it works" step 1 still says "Fetches the org's blocked-user list via GET /orgs/{org}/blocks" and the security model still says "Only acts on users already in the org's blocked list". Since 704ee8ee the source of truth is .github/spam-blocklist.txt, which the body never mentions. The description becomes the squashed commit body, so this ships as-is.
3. It does not do the backfill the description promises (substantive, non-blocking). Ground truth for @danialzivehdadr: 34 comments, 25 already minimized by hand, 9 still visible. The workflow reaches 2 of those 9, and LOOKBACK_HOURS = 2 / 24 / 720 all match the same 2. Reason: pullRequests() has no since filter and is capped at the 100 most-recently-updated PRs — about 12 h of activity in this repo — while issues(first: 100) saturates at 100 nodes, reaching back only ~3 days even with a 30-day since. So the hours input is close to inert at this repo's scale. If backfill matters, one extra query does it: search(query: "repo:QwenLM/qwen-code commenter:<login>", type: ISSUE, first: 100) costs 1 point and returns every thread the user ever commented on — that is exactly how I obtained the ground truth above. Otherwise the remaining 7 still need to be minimized by hand.
4. hours accepts decimals and kills the job (minor). 4e01187 changed the input to type: number, so the dispatch form accepts 1.5; date -u -d "1.5 hours ago" then fails and the job exits 1 at line 4 — before any API call, so it is loud and harmless, just confusing. LOOKBACK_HOURS="${LOOKBACK_HOURS%%.*}" (or keeping type: string) fixes it. GNU date rejects 2.0 as well.
5. 2>&1 folds stderr into the success test (minor). Capturing the mutation's stderr improved the ::warning text (verified live), but the result is compared with [ "$result" = "true" ] — so any stderr chatter on an otherwise successful mutation is counted as a failure and turns the run red. My probe reproduces it. Capturing stderr separately (err="$(… 2>&1 >/dev/null)") keeps both properties.
6. Test coverage is security-only (nit). The suite catches all 7 permission/credential mutations, but these pass unnoticed: classifier: OFF_TOPIC → SPAM, unpinning actions/checkout to a mutable tag, dropping sparse-checkout, changing the cron to every minute, and replacing the entire run: script with echo hi. The file already parses the YAML, so two more asserts (classifier + 40-hex pin) would be nearly free.
7. Prettier would reformat the new test file (nit). prettier --check .github/scripts/auto-minimize-spam.test.mjs fails — the minimizeStep find(…) call collapses to one line. CI runs prettier --write so it will not fail there, but npm run format produces a diff.
8. The red check is environmental, not this PR. Test (ubuntu-latest, Node 22.x) dies in 11 s at "Clean stale .qwen before checkout" with rm: Permission denied, before checkout. The same self-hosted runner is failing unrelated PRs right now with EACCES … .git/FETCH_HEAD at Checkout. Locally the job's actual command passes (164/164).
9. Optional, repeating from last time. comment-attachment-guard.yml:32 already runs minimizeComment in production with secrets.GITHUB_TOKEN, so the CI_BOT_PAT dependency could be dropped. Keeping it is also fine — it matches the triage-workflow convention. Separately, note that .github/spam-blocklist.txt puts a username into the repo's permanent public history; that is a policy call, not a code issue.

中文完整版

维护者验证(第二轮)—— 本地真实运行 @ 5b05bd9

这是对我在 e40f468 那轮评审的后续。之后 PR 增加了第一轮修复(e91b8c2)、yamllint 引号调整(4e01187)和新的回归测试(5b05bd9),因此我重新完整验证了一遍。

结论:行为正确 —— 在 (a) 解决 ci.yml 的单行冲突、(b) 修正 PR 描述之后可以合并。 合并前请注意一点:这个 workflow 能保证今后的干净,但它并不能回补历史。 该拉黑用户目前仍然可见的 9 条评论中,它只能覆盖 2 条——而且加大 dispatch 的回看窗口也无济于事(下文有实测)。

验证内容

1. 场景 harness —— 45 项断言全过,0 失败。 run: 脚本用 yaml 解析器从 auto-minimize-spam.yml 中逐字提取(不是手工复制),配合一个 stub gh:它用真实 jq、以脚本自带的 --jq 过滤器处理受控 GraphQL 数据。覆盖精确/大小写不敏感匹配、子串与超串不误匹配、已 minimize 与 author 为 null 的跳过、CRLF/空白/纯注释/空文件/文件缺失的黑名单、每次 mutation 均为 OFF_TOPIC、step summary 内容、重跑幂等、每次运行只发一次读查询,以及通过 LOOKBACK_HOURS 的注入尝试。
2. 双向变异测试。 针对 PR 新增的 auto-minimize-spam.test.mjs:7/7 安全不变量变异全部被抓住(删除仓库 guard、把 guard 指向 fork、放宽顶层 permissions、加 job 级 permissions: 覆盖、persist-credentials: true、直接删掉该行、把 GH_TOKEN 提升到 job 级 env)。针对我自己的 harness:7 个植入的脚本 bug 中 6 个被检出;第 7 个(去掉 .author != null 过滤)经证实不改变行为——jq 会把 null author 渲染成字符串 null,永远不可能命中黑名单,所以该过滤器只是纵深防御。
3. 与当前 main 合并后跑真实 CI 命令。 把 HELPER_TESTS 冲突按并集解决后共 11 项;node --test $HELPER_TESTS → 164 项测试全过,含新增的 5 项。
4. 对 QwenLM/qwen-code 的真实运行(我自己的凭证),外面套了一层硬拒绝任何 minimizeComment 的包装器(保证只读)。静态检查:actionlint + 内置 shellcheck 无问题、yamllint 无问题、eslint 无问题。为确认 shellcheck 集成确实在生效,我反事实地植入了 rm -rf $REPO/*(如实报出 SC2115 + SC2086),所以"干净"这个结论是有意义的。

真实运行是支持合并的最好证据:用 PR 自带黑名单 + 默认 2 小时窗口,它匹配到了两条真实且当前未被 minimize 的 spam 评论——#7656 与 #6579——并生成了正确的 step summary。单次运行消耗 2/5000 GraphQL 点数,检查约 1124 条评论。

发现

1. 合并冲突(阻塞合并,但很简单)。 .github/workflows/ci.yml 与 main 冲突:main 往 HELPER_TESTS 加了 dsw-swe-verified/make-manifest.test.mjs,本 PR 加了 auto-minimize-spam.test.mjs。取并集即可;我已验证合并后的列表跑出 164 项全绿。
2. PR 描述仍然过时(合并前请修)。 距我上轮评审、经过四轮 autofix 仍未改:"How it works" 第 1 步依然写着 "Fetches the org's blocked-user list via GET /orgs/{org}/blocks",安全模型依然写着 "Only acts on users already in the org's blocked list"。自 704ee8ee 起数据源已是 .github/spam-blocklist.txt,而描述里从未提及该文件。描述会成为 squash commit 的正文,照此合并会原样留下。
3. 它并不能完成描述所承诺的历史回补(实质问题,不阻塞)。 @danialzivehdadr 的真实情况:共 34 条评论,25 条已被手工 minimize,9 条仍然可见。本 workflow 只能覆盖其中 2 条,且 LOOKBACK_HOURS = 2 / 24 / 720 匹配到的都是同样这 2 条。原因:pullRequests() 没有 since 过滤器,且被限制在"最近更新的 100 个 PR"——在本仓库大约只有 12 小时的活动量;而 issues(first: 100) 在 100 个节点处饱和,即便 since 给 30 天也只能回溯约 3 天。因此在本仓库的规模下,hours 输入基本是失效的。如果需要回补,多一条查询即可:search(query: "repo:QwenLM/qwen-code commenter:<login>", type: ISSUE, first: 100),只花 1 个点数,直接返回该用户评论过的所有线程——上面的"真实情况"正是这样查出来的。否则剩下的 7 条仍需手工处理。
4. hours 允许小数,会直接打挂任务(次要)。 4e01187 把输入改成了 type: number,dispatch 表单因此接受 1.5;而 date -u -d "1.5 hours ago" 会失败,任务在第 4 行退出 1——发生在任何 API 调用之前,所以是响亮且无害的,只是让人困惑。LOOKBACK_HOURS="${LOOKBACK_HOURS%%.*}"(或保持 type: string)即可修复。GNU date 同样拒绝 2.0。
5. 2>&1 把 stderr 混进了成功判定(次要)。 捕获 mutation 的 stderr 让 ::warning 信息更有用(真实运行已验证),但结果是用 [ "$result" = "true" ] 判定的——因此一次本已成功的 mutation 只要往 stderr 输出任何内容,就会被算作失败并把 run 变红。我的 probe 复现了这一点。把 stderr 单独捕获(err="$(… 2>&1 >/dev/null)")可以两者兼得。
6. 测试只覆盖了安全面(小建议)。 该套件抓住了全部 7 个权限/凭证类变异,但下列改动会毫无察觉地通过:classifier: OFF_TOPIC → SPAM、把 actions/checkout 从 SHA 改成可变 tag、删掉 sparse-checkout、把 cron 改成每分钟、以及把整个 run: 脚本换成 echo hi。文件本来就已经解析了 YAML,再加两条断言(classifier + 40 位十六进制 pin)几乎零成本。
7. Prettier 会重排新测试文件(小问题)。 prettier --check .github/scripts/auto-minimize-spam.test.mjs 不通过——minimizeStep 的 find(…) 会被折成一行。CI 跑的是 prettier --write,所以不会在 CI 上失败,但 npm run format 会产生 diff。
8. 红色的检查是环境问题,与本 PR 无关。 Test (ubuntu-latest, Node 22.x) 在 11 秒时死于 "Clean stale .qwen before checkout" 的 rm: Permission denied,发生在 checkout 之前。同一台 self-hosted runner 此刻也在用 EACCES … .git/FETCH_HEAD 打挂其他无关 PR。该任务真正要跑的命令在本地是全绿的(164/164)。
9. 可选项,与上轮重复。 comment-attachment-guard.yml:32 早已在生产中用 secrets.GITHUB_TOKEN 执行 minimizeComment,所以对 CI_BOT_PAT 的依赖其实可以去掉。保留也没问题——与 triage 系列 workflow 的惯例一致。另外提一句:.github/spam-blocklist.txt 会把一个用户名永久写进仓库的公开历史,这是策略层面的取舍,不是代码问题。

[qwen-code-ci-bot]

Reviewed — no blockers. 1 Suggestion-level finding(s) could not be anchored to a changed line and were dropped; nothing further to act on here. Not linted (tool limitation, not a blocker): the executable-script lint — .github/workflows/auto-minimize-spam.yml: actionlint embedded-shell source mapping is not yet supported — not linted; the executable-script lint — .github/workflows/ci.yml: actionlint embedded-shell source mapping is not yet supported — not linted.

中文说明

已审查——无阻断问题。 1 条建议级发现无法锚定到改动行，已丢弃；此处无需进一步处理。 未检查（工具限制，非阻断）：the executable-script lint — .github/workflows/auto-minimize-spam.yml: actionlint embedded-shell source mapping is not yet supported — not linted; the executable-script lint — .github/workflows/ci.yml: actionlint embedded-shell source mapping is not yet supported — not linted。

— qwen3.8-max-preview via Qwen Code /review

[qwen-code-dev-bot]

🤖 Reviewed the latest feedback — no changes needed. Why, point by point: · 已审阅最新反馈——无需改动。逐点说明原因如下：

No actionable feedback this round.

• No new reviews, inline comments, or issue-level comments from trusted reviewers.
• No failed or still-red CI checks.
• Critical-only mode is active (5 change-producing rounds completed). The three deferred non-Critical items (two automated reviews and one maintainer comment) remain open for human follow-up; per policy, no code changes, thread resolutions, or replies were made on their behalf.

中文说明

本轮没有需要处理的反馈。

• 没有来自可信审阅者的新 Review、行内评论或 Issue 级评论。
• 没有失败或持续红色的 CI 检查。
• 当前处于仅处理 Critical 的模式（已完成 5 个产生改动的轮次）。三个被延迟的非 Critical 条目（两个自动 Review 和一条维护者评论）保持开放，留待人工跟进；按照策略，未对其修改代码、解决线程或代为回复。

Deferred non-Critical feedback

Critical-only mode is active after 5 change-producing rounds. Any items listed below stay open for human follow-up; do not modify code, resolve threads, or reply on their behalf.

• Review by @qwen-code-ci-bot: ci: auto-minimize comments from org-blocked users #7899 (review)
• Review by @qwen-code-ci-bot: ci: auto-minimize comments from org-blocked users #7899 (review)
• PR comment by @wenshao: ci: auto-minimize comments from org-blocked users #7899 (comment)

中文说明

完成 5 个产生改动的轮次后，进入仅处理 Critical 的模式。以上内容保持开放，留待人工跟进；不要为其修改代码、解决线程或代为回复。

Base-conflict check · 基分支冲突检查: no conflict with main. · 与 main 无冲突。

---

🧠 Handled by Qwen Code · model/模型 qwen3.8-max-preview

[wenshao]

@qwen-code /triage

[qwen-code-ci-bot]

LGTM, looks ready to ship. ✅

[qwen-code-ci-bot]

Released in v0.21.2.