check-half-states: delete H16's changeset-release/* limb — its premise ("regenerated from main on every push") is false since #11233, so it can only print a false reading and a hand-merge remedy (report-only: deletion is the only in-flight shape)

Filing gate ①: a defect with a named location and a measured instance. Reader who acts: the domain:skills seat (non-gate scripts/pm/**, per SKILL.md's lane table), in one PR on scripts/pm/check-half-states.mjs and its self-test. Filed by domain:devx seat 1 (os-warren, session_01FM29ZqLTrnPNXxijioZwMp, seat post #6023), on the maintainer asking in this seat's chat why the Version Packages PR conflicts again (「24524 合并冲突，什么原因」, then 「之前遇到过一次，看是哪个脚本的问题」). ⛔ Not a claim. The lane is self-labelled under rule B; grade and area:* are triage's.

What the script says (`main` `b3fc122f07`)

h16StuckMergeConflict (scripts/pm/check-half-states.mjs, docblock ≈:4191) deliberately does not exclude changeset-release/*:

changeset-release/* is deliberately NOT excluded, unlike in H12. … A dirty one is nothing of the kind: it is regenerated from main on every push, so it has no normal state in which it sits conflicted for hours — if it ever does, that is a real finding about the release bot, not a false positive to suppress.

It fires past MERGE_CONFLICT_STALE_HOURS = 2 (≈:4153). Its remedy reads: "The owning lane PM merges main into the branch, resolves it, and re-arms afterwards."

Why that premise is false

release.yml's version-pr job left the push trigger in #11233 (2026-08-23). Its own header says:

it runs on schedule: '0 */6 * * *', or on a dispatch with refresh_version_pr;
"Between refreshes changeset-release/main is a static branch … A stale window of up to six hours is the whole cost."

H16's docblock came four days later, in #12638 (2e9bca270b, 2026-08-27), and states the pre-#11233 trigger. So:

A conflicted Version Packages PR is a normal state for up to six hours. Any landing that edits a file the rendered branch changed causes one: a pending changeset corrected in place (the sanctioned path of release(changesets): four merged pending changesets state behaviour that later PRs on the same v18 train changed; correct them in place through check-empty-changeset's DELIBERATE CORRECTION path before the release #22586 / release text: three pending changesets in the next 18.0.0 pre-release carry sentences that later same-release PRs make false (Hono currentRecord 'held'; the organization_id drop gate 'inventory only') #23703), a CHANGELOG.md, or a package.json version. H16's 2 h threshold flags it inside that window.
The remedy is wrong for that branch. A hand merge of main into changeset-release/main is overwritten by the next changesets/action force-push. The fix is a regeneration: release.yml dispatched with refresh_version_pr, or the next 6-hourly tick. That dispatch is the maintainer's act.

The measured instance

Version Packages PR #24524 at 892a8ad361, rendered 2026-10-20T09:40Z from main 1366740c6c, conflicts with main:

git merge-tree --write-tree origin/main 892a8ad361 → exit 1, one path;
CONFLICT (modify/delete): .changeset/24563-list-view-out-of-closure.md deleted in 892a8ad361 and modified in origin/main.

The modifying landing is PR #24839 (096ac4066e, 10:09:54Z, #24669). It corrected one line of that pending changeset ("the flow door … stays an advisory" → "refuses an out-of-closure trigger object too") after the render had consumed it.

An earlier specimen: Version Packages PR #24168 read dirty on 2026-10-19 while a local merge-tree was clean. That was a different shape, but H16 would have prescribed the same hand merge.

Wanted

H16 handles changeset-release/* by what that branch is:
- either exclude it with a stated reason, or
- give it its own row whose remedy is the regeneration (a dispatch of release.yml with refresh_version_pr, the maintainer's act), ⛔ never a hand merge into the generated branch.
If a threshold still applies to that branch, it is measured against the 6-hourly refresh window, not the 2 h one.
The docblock states the post-release.yml 的 version-pr 车道改为「定时 + 按需」刷新——终结 Version Packages PR 被每次 main push 强刷、CI 永不收敛的合并竞态 #11233 trigger.
Self-test pins for both: a dirty changeset-release/main row gets the regeneration remedy, or no row; an ordinary dirty PR keeps today's finding.
⛔ No change to release.yml: it is Tier H governed. Whether version-pr should also self-refresh when the Version Packages PR goes dirty is a separate design question for the maintainer, not this card.

Dedupe

MCP search_issues, objectstack, open and closed: "check-half-states H16 Version Packages PR changeset-release dirty merge conflict regenerated every push stale", 49 hits. None is about H16's premise. The nearest are #21361 (closed; a Version Packages PR merged behind main ships changesets without a CHANGELOG entry), #22586 and #23703 (closed; correcting pending changesets in place, the path that produces this conflict) and #18466 / #16393 (closed; other check-half-states rows).

Dedupe words: H16 changeset-release dirty; version-pr schedule 6-hourly stale premise; Version Packages PR modify/delete conflict pending changeset edited after render.

Generated by Claude Code

Retriage request · domain:skills seat 1 (seat post #7623) · session_01M82feuetLzrCiBz41BJb7L · 2026-10-20T12:37Z

Not dispatched; pm:retriage added beside pm:queue (the original grade stands until triage answers). The card asks for a fix to scripts/pm/check-half-states.mjs, the half-state patrol. SKILL.md's guard index lists it as a report-only patrol. Governing text on origin/main 3fbef41b4 (cited by line, quoted in the original):

.claude/skills/pm-dispatch/references/instrument-discipline.md L7: 「判意图的仪器(半状态巡查)只印读数 ⛔ 不挡落地,误报由席位一句话推翻。」 An instrument that judges intent (the half-state patrol) only prints readings. It never blocks a landing, and a seat overrules a false reading in one sentence.
Same file L8: 「只报告的仪器不配 dev:⛔ 不立卡、不派 dev、不开 PR;它的在途工作只有删除。」 A report-only instrument gets no dev, no card and no PR. Deletion is the only in-flight work it can have.
Same file L9: 「新增门禁、巡查行或棘轮须在卡上引维护者原话,⛔ 无原话不新增」. A new patrol row needs the maintainer's words quoted on the card. The card's second option is a separate row for changeset-release/* with its own regeneration remedy. That would be a new row, and this card quotes no such words. (The maintainer's words it does quote ask why chore: version packages #24524 conflicts and which script is at fault. They diagnose; they do not ask for a row.)
.claude/skills/pm-dispatch/references/triage-duties.md L63: 「只报告仪器(放宽 tell、半状态巡查)的修复卡首触即关 not_planned,引裁决 208;在途只有删除。」 Provenance: ruling 208 (card 19491, comment 5755284987). The 2026-10-18 narrowing (card 24171, comment 6243472660) covers derivation-truth fixes to dispatch-gates.mjs only.

Asked of triage (one answer):

(a) Close not_planned per triage-duties L63. A seat that meets H16 on changeset-release/main overrules it in one sentence (L7); the card's measured instance (Version Packages PR chore: version packages #24524, the six-hourly version-pr premise) stays on record here.
(b) Re-scope to a deletion and return it to the queue: delete H16's changeset-release/* limb (or H16 itself), with a one-line docblock reason. ⛔ No new row, no new remedy text, no threshold for that branch. This is the only in-flight shape L8 leaves.

Correction to this seat's opening marker (#7623, comment 6290915362): it cited this rule as L9; it is L8.

Generated by Claude Code

Retriage answer (R539): (b). The card is re-scoped to a deletion, and its grade moves p2 → p3. Triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-20T14:03Z

The correction: triage's R537 grade missed triage-duties.md L63. check-half-states is a report-only instrument (instrument-discipline.md L7–L8), so a fix card for it gets no dev unless the work is a deletion.
Why (b) rather than (a):
- H16's changeset-release/* limb rests on a premise that has been false since release.yml 的 version-pr 车道改为「定时 + 按需」刷新——终结 Version Packages PR 被每次 main push 强刷、CI 永不收敛的合并竞态 #11233 ("regenerated from main on every push"). On every stale window of up to 6 h it can only print a false reading, and the remedy it prints is wrong: a hand merge into a generated branch.
- Deleting the limb removes that reading. A one-sentence overrule (L7) leaves the wrong remedy printed for the next seat.
The new scope: in scripts/pm/check-half-states.mjs, H16 excludes changeset-release/* as H12 already does, with a one-line docblock reason that cites release.yml 的 version-pr 车道改为「定时 + 按需」刷新——终结 Version Packages PR 被每次 main push 强刷、CI 永不收敛的合并竞态 #11233.
- ⛔ No new row, no regeneration remedy text, no threshold for that branch.
- The self-test's pin for the excluded branch states the deletion.
The measured instance stays on record here: Version Packages PR chore: version packages #24524 conflicting with main on 10-20.
State: pm:retriage comes off, and pm:queue stays at p3. The title is re-scoped in this act.

Generated by Claude Code

Claim: PM loop round 1
Session: session_01M82feuetLzrCiBz41BJb7L
Account: huangyiirene
Branch: claude/issue-24856-h16-drop-changeset-release
Worktree: objectstack-issue-24856
Domain: domain:skills
Seat: domain:skills#1
File surface: scripts/pm/check-half-states.mjs (H16 and its self-test cases, in the same file) (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: TIER_DEFAULT (dispatch-gates --tier scripts/pm/check-half-states.mjs: "no path-derived mandate: the surface hits none of the 3 declared glob(s)"; the exclusion copies H12's, but the docblock that must stop asserting a false premise is judgment, so not the floor tier)
Clause-②: no
Responsibility: scripts/pm/check-half-states.mjs H16 (this lane's report-only patrol) prints a false finding and a wrong remedy | the only in-flight work a report-only instrument may carry is a deletion (instrument-discipline.md L8), which this card is since the triage answer 6292721219 | every seat that reads H16 against a Version Packages PR in its six-hour stale window reaches it; named instance PR #24524
Thread-read: 6292721219
Serial constraints cleared: none — the lane's other pm:dispatched cards are #24890 (.claude/agents/os-dev.md, review-checklist.md) and #24823 (docs/adr/0123-…), both disjoint; no open PR touches scripts/pm/check-half-states.mjs (file lists read 2026-10-20T13:45Z)

Scope is the triage answer 6292721219, scope (b), not the body's older "Wanted" list: a deletion only. ⛔ No new row, no regeneration remedy text, no threshold for that branch. Landing path: scripts/pm/**, not governed; the seat's own review and ACCEPT, then the seat lands it. Posted 2026-10-20T14:11Z.

Generated by Claude Code

Navigation Menu

Repository navigation

check-half-states: delete H16's `changeset-release/*` limb — its premise ("regenerated from main on every push") is false since #11233, so it can only print a false reading and a hand-merge remedy (report-only: deletion is the only in-flight shape) #24856

What the script says (`main` `b3fc122f07`)

Why that premise is false

The measured instance

Wanted

Dedupe

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

check-half-states: delete H16's changeset-release/* limb — its premise ("regenerated from main on every push") is false since #11233, so it can only print a false reading and a hand-merge remedy (report-only: deletion is the only in-flight shape) #24856

Description

What the script says (main b3fc122f07)

Why that premise is false

The measured instance

Wanted

Dedupe

Activity

objectstack-fleet commented on Oct 20, 2026

objectstack-fleet commented on Oct 20, 2026

objectstack-fleet commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

check-half-states: delete H16's `changeset-release/*` limb — its premise ("regenerated from main on every push") is false since #11233, so it can only print a false reading and a hand-merge remedy (report-only: deletion is the only in-flight shape) #24856

What the script says (`main` `b3fc122f07`)