[finding] check-clause2-carriers keeps two undecoration paths that disagree on 5 of 12 spellings — the retraction line strips a leading sigil / list marker / heading / underscore and the shared claim reading refuses them — both directions carry a live specimen, so converging is a protocol decision, not a cleanup

Filed by the domain:skills execution seat (session_01Gqi43smmqjJ5sUrhfoPeKu, seat post #7623) out of the #18764 round (PR #18824), from the dev's measurement the seat's dispatch reserved for the seat to route. ⛔ Filed bare: finding only, domain:* / type / priority are triage's (lane self-triage exception noted). ⛔ A decision-shaped card: the code pins the divergence as two jobs; the question is whether the protocol wants ONE definition of 「decorated」, and in which direction.

Dedupe words: undecorateRetractionLine vs markerMatches · two undecoration paths · leading sigil retraction · list item not a claim H20 · decorated open set · one thread two readings.

The reading, on PR #18824's head `984a93a17` (the same lines on `origin/main` `ad1f94e8ec` except the two claim tests PR #18824 moves)

scripts/pm/check-clause2-carriers.mjs reads two kinds of ownership line through two strippers:

retraction lines — undecorateRetractionLine (:1653 on main): strips [`*_] then every leading non-letter / non-digit run; used at :1700 on the prose retraction channel (PR fix(pm): a retracted claim leaves the governing-claim pool, so a withdrawn claim never governs #18770).
claim lines — since PR fix(pm): a decorated Claim: enters the governing-claim pool, through the sibling's one reading #18824, markerMatches(CLAIM_COMMENT_MARKER, body) imported from check-half-states.mjs :1261: the bare marker first, then undecorateProseLine per line under the MARKER_LIST_ITEM_PREFIX guard; the near-miss vocabulary OWNERSHIP_MARKER_NEAR_MISS_FORMS beside it.

The #18764 dev ran both over one fixture set (12 spellings, the retraction stripper extracted from the shipped text, not retyped) — 5 read DIFFERENTLY:

spelling	retraction path	shared claim path
`__Claim:__` (underscore emphasis)	true	false (a NAMED near miss)
`- Claim:` / `* Claim:` (list items)	true	false (H20 pins a list item as not a claim)
`🚨 Claim:` (leading sigil)	true	false
`## Claim:` (heading)	true	false
bare / `bold` / backticks / `>` / `> bold`	true	true
`Claim of ownership…` / `Claiming:`	false	false

Both directions are load-bearing today: the #18373 retraction the file's own battery replays opens 🚨 **撤回上一条认领… — narrowing the retraction stripper to the shared reading would stop reading the specimen PR #18770 landed for; widening the shared reading would make - Claim: a claim, which check-half-states.mjs' H20 pins as not one. PR #18824 pins the divergence in both directions (「the RETRACTION path still reads the sigil-led #18373 line」 / 「the SHARED reading does not strip a leading sigil」) so it cannot close silently.

The question for triage / the maintainer

A — one definition: the sibling's (undecorateProseLine + the near-miss vocabulary) is the protocol's definition of a decorated ownership line; the retraction channel adopts it, and the [finding] check-type-source-resolution's (via …) provenance annotation is FALSE for an include entry naming a bare directory — and that annotation is the doc-block's OWN test for which remedy limb an author is on #18373 shape (a sigil before the act) becomes a NAMED near miss with its own anchor row rather than a stripped prefix. Cost: one specimen the prose channel stops reading unless its anchor list learns the sigil form explicitly — which is the loud, declared direction.
B — two definitions on purpose: a retraction is prose (a sentence that OPENS with the act) and a claim is a directive line (a key at line start), so different tolerances are correct; the file states that, as PR fix(pm): a decorated Claim: enters the governing-claim pool, through the sibling's one reading #18824 now does. Cost: the next spelling replays 「one thread, two readings」 across the two channels.
C — widen the shared reading to the retraction stripper's tolerance: refused by H20 and by [finding] check-half-states' CLAIM_COMMENT_MARKER / RELEASE_COMMENT_MARKER anchor the bare word at line start, so a DECORATED **Release:** line is read as ABSENT — a real release record on #16529 is invisible to H2 / H47 / H66 #18680's own ruling that decoration is an open set answered by a named vocabulary, ⛔ not by a wider stripper.

The seat's view: A, on 防 AI 写错 (one declared vocabulary the reader is BUILT from, every form added with a fixture) and 项目长远合理性 (#18773 already asks whether a retraction should be a Release: line — if it must, the prose channel's tolerance question shrinks to nothing); B is the measured status quo and is acceptable until ruled; C is not.

⛔ Not measured

How many live retraction lines open with a sigil or a list marker (one specimen, [finding] check-type-source-resolution's (via …) provenance annotation is FALSE for an include entry naming a bare directory — and that annotation is the doc-block's OWN test for which remedy limb an author is on #18373; [finding] the governing-claim selector keeps a RETRACTED claim in the pool — a withdrawn claim outranks the live one, names a branch that does not exist, and the real claimant reads as SUPERSEDED #18719's dev found no second on that thread).

Refs: #18764 · PR #18824 · #18719 · PR #18770 · #18680 · PR #18756 · #18773 · scripts/pm/check-clause2-carriers.mjs undecorateRetractionLine · scripts/pm/check-half-states.mjs markerMatches / OWNERSHIP_MARKER_NEAR_MISS_FORMS

_{domain:skills execution seat · seat post #7623 · readings taken on PR #18824's head 984a93a17 and origin/main ad1f94e8ec}

Generated by Claude Code

Ruling: batch #156 item 4 · letter A (one definition of a decorated ownership line — the shared claim reading, undecorateProseLine plus the named near-miss vocabulary — and the retraction channel adopts it; the sigil-led #18373 shape becomes a named near-miss row, ⛔ not a stripped prefix) · maintainer 「同意」 2026-09-18T05:37Z

Director seat, summon #24, session_01Wj1HUjzyeiBQ8atRf1ZhaL. Presented in detail with the recommendation A; the maintainer agreed. Facts (this card; triage 5722477664): check-clause2-carriers.mjs reads retraction lines through undecorateRetractionLine (strips [`*_] then every leading non-letter/non-digit run) and claim lines through the shared markerMatches (bare marker first, undecorateProseLine under the list-item guard, the named near-miss vocabulary beside it, H20 pinning a list item as not a claim). Twelve spellings run through both: 5 disagree (__Claim:__, - Claim: / * Claim:, 🚨 Claim:, ## Claim:). Both directions carry a live specimen, so convergence is a protocol choice: #18680 already ruled that decoration is an open set answered by a named vocabulary, ⛔ not by a wider stripper.

Ruling — A

The protocol's definition of a decorated ownership line is the shared claim reading. The retraction channel adopts it; the 🚨-led [finding] check-type-source-resolution's (via …) provenance annotation is FALSE for an include entry naming a bare directory — and that annotation is the doc-block's OWN test for which remedy limb an author is on #18373 line becomes a named near-miss row with its own fixture, so the loud, declared direction keeps reading it. undecorateRetractionLine is deleted. With [finding] the protocol names Release: as the act that takes a card out of a seat's hands, but a claim RETRACTED before work starts is written as prose — the arbiter now reads that prose (PR #18770), and whether the protocol should REQUIRE the Release: spelling for a retraction is a governed-text question nobody has ruled #18773 A landing in the same round, the prose retraction channel itself retires, and this row's tolerance question shrinks to the Release: spelling.
⛔ B — 「one thread, two readings」 returns with the next spelling; ⛔ C — refused by H20 and by [finding] check-half-states' CLAIM_COMMENT_MARKER / RELEASE_COMMENT_MARKER anchor the bare word at line start, so a DECORATED **Release:** line is read as ABSENT — a real release record on #16529 is invisible to H2 / H47 / H66 #18680.
One skills round, one PR on check-clause2-carriers.mjs, together with [finding] the protocol names Release: as the act that takes a card out of a seat's hands, but a claim RETRACTED before work starts is written as prose — the arbiter now reads that prose (PR #18770), and whether the protocol should REQUIRE the Release: spelling for a retraction is a governed-text question nobody has ruled #18773 A and [finding] the #18828 triage's p1 escalation condition is MET — 12 open cards across both boards carry LIVE Claim: comments from two or more DIFFERENT authors with no retraction between them, and every reader prints the newer one green as a supersession; a cross-session ownership transfer has no reader #18862 b.

Four-facet reading: ① zero customers; ② one vocabulary the reader is built from, every form added with a fixture; ③ not scored — fleet-facing; ④ one stripper deleted.

Execution

needs-user-decision → pm:queue; domain:skills, priority:p2 stay. Governed script ⇒ the skills lane's at-tier review, human merge by the approver.

Generated by Claude Code

Claim: PM loop round 1 (skills seat, this seat's R1) — FOLD MEMBER of #18862
Session: session_01W5y9kRg1YtYaMQYExVLRc2
Branch: claude/issue-18862-claim-reader-one-spelling
Worktree: objectstack-issue-18862
Domain: domain:skills
Seat: domain:skills#1
File surface: scripts/pm/check-clause2-carriers.mjs (this card's share: one definition of a decorated ownership line — the shared claim reading — adopted by the retraction reading; undecorateRetractionLine deleted; the 🚨-led #18373 line a NAMED near-miss row with its own fixture)
Container & model: as the anchor — L, mode:subagent, model: fable
Clause-②: no
Thread-read: 5725677876
Ruling-ref: 5725677876 (batch #156 item 4, letter A)
Serial constraints cleared: as the anchor claim on #18862 (0 of 20 open PRs on the file at 2026-09-19T03:08Z; stale probe heads only).

The full claim (deliverables, fold admission, serial reading) is on the anchor #18862; this card closes with the anchor's PR (Fixes #18829 on it).

Generated by Claude Code

ACCEPT (fold) — delivered whole by PR #19169 (head 4cb58bcb01) under the #18862 anchor; the seat's review is on #18862 (ACCEPT) and on the PR thread (## Contract review 5739371777, PASS) · session_01W5y9kRg1YtYaMQYExVLRc2 · 2026-09-19T04:34Z. Ruling A implemented: one undecoration path (markerMatches), undecorateRetractionLine deleted (0 at the head, control undecorateProseLine 20), leading-sigil named with its fixture in OWNERSHIP_MARKER_NEAR_MISS_FORMS, the 12 spellings 5 → 0 disagreements, H20 held. Closes by keyword on landing; label and assignee residue at MERGED.

Generated by Claude Code

Landed — PR #19169 MERGED at 2026-09-19T05:02Z (squash e8667ee on origin/main; read back by content: undecorateRetractionLine 0 tree-wide against control undecorateProseLine, leading-sigil in OWNERSHIP_MARKER_NEAR_MISS_FORMS). domain:skills seat, session_01W5y9kRg1YtYaMQYExVLRc2 · 2026-09-19T05:09Z. Residue in this same act: pm:dispatched off (closed by keyword), assignee off.

Generated by Claude Code

feat(pm): name the two measured claim near-miss forms so the sweep so…

fix(pm): the claim reader reads one declared act — Release: through t…

Navigation Menu

Repository navigation

The reading, on PR #18824's head `984a93a17` (the same lines on `origin/main` `ad1f94e8ec` except the two claim tests PR #18824 moves)

The question for triage / the maintainer

⛔ Not measured

Ruling — A

Execution

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Description

The reading, on PR #18824's head 984a93a17 (the same lines on origin/main ad1f94e8ec except the two claim tests PR #18824 moves)

The question for triage / the maintainer

⛔ Not measured

Activity

hotlong commented on Sep 18, 2026

Ruling — A

Execution

os-tesla commented on Sep 19, 2026

os-tesla commented on Sep 19, 2026

os-tesla commented on Sep 19, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

The reading, on PR #18824's head `984a93a17` (the same lines on `origin/main` `ad1f94e8ec` except the two claim tests PR #18824 moves)