patrol: H4/H14/blocking-index read comment-level Blocked-by lines when the body carries none — the #8941 gauge fix

[os-warren]

实现卡,承接两处:#8941(追踪卡:解锁扫描/巡逻只读正文,而席位因 #8813 MCP 正文转义陷阱有意把 Blocked-by: 行停在评论里 —— 26/40 张 blocked 卡正文干净)与 #9948 的判据重校裁定(2026-08-19:残余 H14 行属量具错位,「修量具而非追假 stale」)。

Scope —— scripts/pm/check-half-states.mjs

H4、H14(双向)与 buildBlockingIndex 获得评论级回落读:当卡正文无 Blocked-by: 行时,读该卡晚于正文最后编辑的评论中的 Blocked-by: 行(读闭合规则照座位贴协议既例)。要点:

• 复用 PR feat(pm): H17 — render the on-hold trigger-file index on the patrol anchor #10041 刚落地的 commentCache 与候选门模式(H2/H17 同款):评论 fetch 只对「正文无行且状态相关」的卡发起 —— pm:blocked 卡(H4/索引边源)与 pm:blocking 卡(H14 stale 判定的辩方证据)。量具口径:普查测得 ~2/3 blocked 卡正文干净,fetch 上界即此集合。
• 解析复用 blockedByTargets(feat(pm): two report-only patrol predicates for the pm:blocking machinery — cache coherence both directions, and oldest-unclaimed age #9945 落地,首解析器);跨仓滤除/自引滤除照旧。
• H4 语义升级要诚实:正文无行但评论有行 ⇒ 不再报 H4(机器可读义务已尽,只是通道不同);正文评论皆无 ⇒ H4 照报。H4 的 finding 文本相应改写,说明两通道。
• H14 双向都吃全索引:stale 判定的「无人指向」必须先看过评论级边(Migrate the release toolchain to @changesets/cli v3 — one atomic PR carrying the bump, the pre-mode restructure, and the gates that model v2's semantics #9465/impersonate_user and set_user_role still 403 every platform admin — neither route is safely raw-mountable, and each blocks for a different reason #9968 假 stale 的实测形状进 fixture);missing 判定的目标集同源。
• 单卡 fetch 失败 = 该卡按「评论不可读」处理且不得因此判 stale(check:react-declaration-parity 是唯一没接进任何 workflow 的源码审计门禁,且无 MANIFEST 时静默 skip 退出 0 —— 它现在永远不可能红 #4690:读不到的证据不能当不存在的证据);摘要行报 comment fallback read on X of Y(照 H16/H17 先例)。全失败上抛 transport。
• 自测:正文行/评论行/两者皆有(正文优先?—— 不,并集,两通道都是真边)/皆无/评论不可读,每形状正负钉;Migrate the release toolchain to @changesets/cli v3 — one atomic PR carrying the bump, the pre-mode restructure, and the gates that model v2's semantics #9465、impersonate_user and set_user_role still 403 every platform admin — neither route is safely raw-mountable, and each blocks for a different reason #9968 的实测假 stale 形状做回归钉。

边界(不做)

⛔ 不让任何席位恢复正文重写(转义陷阱 #8813 另行跟踪);⛔ 不改 Restart-when:/Unlock-action: 读法(另卡);cloud 仓回填半边归 #8941/#9913 协调线。

Serial

热文件 check-half-states.mjs 被 PR #10041(H17,在队)占用 —— 串行在其合并之后,派发前重测(自测基线届时 414)。非治理面。Graded pm:queue, M(skills 座,own-lane,session ae0d8bd1-5667-5f58-8ff8-fa22ec154325)。

[os-warren]

Claim: session ae0d8bd1-5667-5f58-8ff8-fa22ec154325 · branch claude/issue-10061-comment-level-blockedby

串行解除:PR #10041(H17)已合并,check-half-states.mjs 空闲(自测基线 414,commentCache 机制已在树上)。折叠检查:队列无同文件第二卡 → 单卡。模型档:路径无强制(--tier 口径),report-only 量具修复 → opus。

---

Generated by Claude Code

[os-warren]

{
 "issue": 10061,
 "status": "done",
 "branch": "claude/issue-10061-comment-level-blockedby",
 "pr": "https://github.com/objectstack-ai/objectstack/pull/10075",
 "premise_still_valid": true,
 "summary": "H4, H14 (both directions) and buildBlockingIndex now read comment-level `Blocked-by:` lines. H4 judges both channels and either discharges the duty; buildBlockingIndex takes options.comments and UNIONs comment-borne refs with body ones (cross-repo/self-ref filtering unchanged, applied per-ref regardless of channel); H14's stale direction is judged against the full two-channel index. Fetches are gated by the exported needsBlockedByComments to body-clean pm:blocked / pm:blocking cards and share the existing commentCache, so a card costs one request across H2, H17 and this; total failure rethrows as transport via the shared h16DetailPassUnreadable, and a partial shortfall is stated by the summary line's third `read X of Y` pair. The two directions treat an incomplete index asymmetrically on purpose: stale (a claim about ABSENT evidence) is suspended when any gated fetch failed, while missing (a claim about evidence IN HAND) survives, since reading more sources can only add edges. DECLARED NARROWING: the seat-post read-closure cut-off (comments newer than the body's last edit) is NOT implemented -- REST carries no issue body-edit timestamp (GraphQL userContentEdits only; this file is REST-only by a standing operational note) and the one proxy in reach, updated_at, bumps when a comment is posted, so the cut-off would be false for every comment ever written and the fallback would read nothing while looking like it read. See open_questions.",
 "tests": "All on final commit 7ab290652 (tree clean; gate union re-derived on that HEAD). `node scripts/pm/dispatch-gates.mjs` with NO args, exit 0 -- 'change set derived from git -- 1 path(s) vs merge base a8509eba8', 6 families, all run. Verdict lines, each printed by the gate itself (exit codes captured by redirecting BEFORE any pipe): `pnpm check:pm-half-states` -> 'check-half-states self-test: 469 cases pass.' (baseline 414 -> 469, +55); `pnpm check:partof-closing-keyword` -> 'check-partof-closing-keyword self-test: 28 cases pass.'; `pnpm check:cross-package-test-inputs` -> 'OK: 12 package(s) read outside themselves, all declared, and turbo.json hashes every declared glob.'; `pnpm check:nul-bytes` -> 'check-nul-bytes: OK (scanned 6367 text file(s) -- 6367 tracked, 0 untracked-not-ignored; skipped 5 binary; no raw ASCII control bytes).' plus a manual grep -naP control-byte scan of the edited file (no match). The two `node scripts/...` rows in the derived list invoke the same scripts as their pnpm twins. Live sweep `node scripts/pm/check-half-states.mjs` exits 3 = 'PREREQUISITE NOT MET -- the token in the environment is not a valid GitHub credential' (transport-blocked container, expected; exit 3 is the CLASSIFIED verdict, not the unclassified 2, so the sweep path still loads and classifies). REVERSE VERIFICATION -- no build step exists for this artifact: node executes the script source directly, nothing resolves through a package dist/, so there is no stale-artifact hazard on either leg; every leg was ablated from the COMMITTED state and restored with `git checkout <branch> -- <path>`, and the restore leg was re-verified (469 pass, zero ABLATION markers left, `git status` clean). Directions predicted in writing first, all three held: (A) index union reverted to body-only -> predicted red on union-dependent rows with the two 'reads STALE against a body-only index' pins staying green; observed exit 1, and a direct probe through the exported functions showed edges at #9465 = null with #9465 reporting the stale sentence -- the measured false stale reproduced; after restore, edges = [9709,9828] and the row is null/clean. (B) H4 ignores commentBodies -> predicted red on the H4 comment-channel rows only, 8 rows named in advance; observed '8 of 469 case(s) failed', exactly those 8. (C) stale suspension removed -> predicted exactly one row; observed '1 of 469 case(s) failed' -- 'H14-A: stale is SUSPENDED when the index is known incomplete'. Self-test additions cover body-line / comment-line / both (union) / neither / comments-unreadable, positive and negative per shape, the gathering-policy gate, and the #9465/#9968 measured false-stale shapes as regression pins built from the REAL comment bodies on #9709/#9828/#9969/#9652, each pinned in both directions.",
 "labels_read_back": ["size/m", "skip-changeset"],
 "open_questions": [
 {
 "question": "The card specifies the comment fallback reads comments NEWER than the body's last edit, per the seat-post read-closure rule. That rule's own justification is that both timestamps are platform-stamped hard readings -- but only one of them is. A comment's created_at is on every REST row; an issue's body-edit time is on no REST payload at all (issues carry created_at/updated_at only, body edit history lives behind GraphQL userContentEdits, the timeline endpoint does not record body edits), and this file is REST-only by a standing operational note. How should the cut-off be handled?",
 "options": [
 "A -- ship without the cut-off (what this PR does): read the gated candidate's first comment page in full, and document the omission plus its direction analysis at the predicates. Errs only toward MORE evidence, which can clear an H4 row or an H14 stale row but can never invent a card's silence. Residual cost is a genuinely obsolete comment edge, which requires the source card to still be open, still labelled and still body-clean -- a state in which that source card is itself mis-stated.",
 "B -- implement the cut-off against issue.updated_at. Rejected: updated_at bumps when a comment is POSTED, so 'newer than the body's last edit' is false for every comment ever written; the fallback would read nothing while reporting that it read. An unfalsifiable check is worse than an absent one and is the shape this file exists to catch.",
 "C -- add a GraphQL read for lastEditedAt / userContentEdits. Buys the exact cut-off, and costs the file's REST-only operational note (the loop's hot path stays on the core quota) plus a second transport to classify in the prerequisite prober -- a real surface expansion for a boundary whose only measured benefit is suppressing obsolete edges nobody has observed.",
 "D -- narrow the gate instead: fetch only comments whose created_at is newer than the card's created_at. Vacuous (always true) -- listed only to record that it was considered and is not a cut-off."
 ],
 "recommendation": "A, shipped and declared. It is the only option that is both mechanizable under the file's stated constraints and directionally safe: the deviation can only clear false findings, which is precisely the #9948 recalibration this card implements, and it cannot manufacture one. C is the honest upgrade path if the maintainer decides the obsolete-edge case is worth a second transport -- worth a follow-up card only if such an edge is ever actually measured, since filing it now would be speculative surface. B is unsafe and should be recorded as rejected so nobody re-proposes it."
 }
 ],
 "out_of_scope_findings": []
}

---

Generated by Claude Code

[os-warren]

ACCEPT — PR #10075 复核通过,已 flip ready + auto-merge(显式 SQUASH)。

复核记录(session ae0d8bd1-5667-5f58-8ff8-fa22ec154325):

• 亲取全 diff。H4 三态输入设计(undefined 未询 / null 不可读 / string[] 已读)各配诚实句 —— 未询不冒领「评论为空」,不可读照报但注明第二通道未判(check:react-declaration-parity 是唯一没接进任何 workflow 的源码审计门禁,且无 MANIFEST 时静默 skip 退出 0 —— 它现在永远不可能红 #4690);presence 测试与 extractor 刻意分离的论证成立(Blocked-by: TBD 尽义务但不产边)✓。
• 并集索引:两通道皆真边,无优先序;跨仓/自引滤除按 ref 内容不按通道;Migrate the release toolchain to @changesets/cli v3 — one atomic PR carrying the bump, the pre-mode restructure, and the gates that model v2's semantics #9465/impersonate_user and set_user_role still 403 every platform admin — neither route is safely raw-mountable, and each blocks for a different reason #9968 两个实测假 stale 以真实评论体做回归钉,双向(body-only 红 / 双通道清)✓。
• 不完整索引的不对称处置是本单最好的设计:stale(对缺席证据的断言)在任一 gated fetch 失败时悬置,missing(对在手证据的断言)存活 —— 且摘要行第三对 read X of Y 在短缺时明说 stale 方向已悬置,静默板与拒判板不可混 ✓。
• 采集:needsBlockedByComments 导出钉住,共享 commentCache,H2/H17/本项一卡一取;pm:blocking 卡在 unscoped 才可见 ⇒ 第二遍采集的摆位正确 ✓。
• 声明降窄裁 A(照发):读闭合 cut-off 在 REST 下无从实现(issue 无 body-edit 时间戳;updated_at 代理会让 cut-off 对一切评论恒假 = 不可证伪的检查,B 正确拒绝并记录在案);无 cut-off 的误差方向只清假告警、不能捏造沉默 —— 恰是 request: run the pm:blocking derivation pass — cache measured at 0% coherence with the Blocked-by index (1 stale / 5 missing, 2026-08-19 census) #9948 重校要的方向。C(GraphQL)留作「若实测到过时边」的升级路径,现在不立卡 ✓。
• 自测 414→469,反向验证三腿(含 8 行提前点名)全中 ✓。

落地后:#8941 的本仓机械半闭环 —— 26/40 张评论停线的 blocked 卡从此对巡逻与解锁索引可见;cloud 回填半继续走 #9913 协调线。

---

Generated by Claude Code

[os-warren]

冻结锚点移交记录(skills 座,session ae0d8bd1-5667-5f58-8ff8-fa22ec154325):PR #10075 的冻结前提原挂在 #10071(registry.ts eslint 栈溢出 flake 根因卡),该卡已被 os-zhuang 关为 duplicate → 正主卡 #10030。截至本轮 #10030 仍开、pm:queue/domain:devx、无关联 PR、devx 队列无在班 PM —— 冻结维持,谓词不变,只换锚:#10030 有修复/止血落地 ⇒ 本卡 PR #10075 更新分支收割 → #10082 解锁。⛔ 期间不重触发 #10075 的 CI(停手线已在 #10071 第 5 击宣布)。flake 台账最新一击(第 6 击,PR #10038,run 32324337564)已记录并随 #10038 的 branch-update 重触发后合并收场。

---

Generated by Claude Code