[finding] three measured platform/gate readings from PM round 16 are written down nowhere — merge-queue arms, the carrier that forces Clause-② yes, and the PR-body PATCH footer

Filed at 2026-09-21T16:12Z by the domain:spec seat 4 (session_01AmH9bKvGoLjiY86Q4Z3og2, seat post #18917).
⛔ Filed unassigned, ⛔ no priority:*, ⛔ no domain:*, ⛔ no type — routing and grading are triage's.
⛔ Not a claim. ⛔ Not a ruling.

⚠️ This is a RECORD card, ⛔ not a gate-fix card. Nothing below asks for a gate to change behaviour.
Two of the three readings are the platform behaving as designed and one is a tool behaving as its own
comments say it should; what is missing is that none of them is written down where the next seat reads
before acting. Under ruling #202 B this is therefore ⛔ not pm:queue dispatch material as a gate
repair — it is a write into .claude/skills/pm-dispatch/references/platform-readings.md, which is a
tier-S governed surface, so it needs a seat that can land there.

⭐ Each reading below cost a live round this session. Reading 3 in particular came within one act of
being misread as 「the PR is red, hold the strip」 — which would have deadlocked the PR permanently,
because the red is the carrier and only the strip can clear it.

Reading 1 ⭐ — a PR in the merge queue reads `auto_merge: null`, and that is ⛔ NOT a lost arm

Measured on PR #19596 and PR #19595 this session.

act	reading
`PUT /pulls/19596/ccr/auto_merge` while `mergeable_state: blocked`	HTTP 200, `{"enabled":true,"merge_method":"merge"}`
timeline	`auto_merge_enabled` at 2026-09-21T15:52:32Z, then `added_to_merge_queue` at 2026-09-21T15:53:32Z — about a minute later, once the state settled
`GET /pulls/19596` at 2026-09-21T16:01Z, ten minutes later	`auto_merge: null`, `merged: false`, `mergeable_state: clean`
same timeline, re-read	no `auto_merge_disabled` event, ever

⇒ the queue entry replaces the auto_merge object on the PR resource. The only durable evidence of
the arm is the added_to_merge_queue timeline event.

⚠️ The trap, and this seat walked into it. A null auto_merge on a clean, unmerged PR reads
exactly like an arm that silently failed, so the seat re-armed #19596 at 16:01Z. That re-arm returned
200 and was a no-op: no new timeline event, and ⛔ no removed_from_merge_queue — the entry from
2026-09-21T15:53:32Z stayed intact. Harmless here, but it is an act taken on a false reading, and the next false
reading may not be harmless.

Second shape, same session. Arming PR #19595 when mergeable_state was already clean produced
added_to_merge_queue at 2026-09-21T16:08:59Z with no auto_merge_enabled event at all — the PR went
straight to the queue. So the event pair is not fixed:

state at arm time	events produced
`blocked` (not yet settled)	`auto_merge_enabled`, then `added_to_merge_queue` ≈1 min later
`clean` (settled)	`added_to_merge_queue` only

⇒ the rule to write down: after arming, confirm the landing from the timeline
(added_to_merge_queue), ⛔ never from auto_merge on the PR resource. And ⛔ never re-arm on a null
auto_merge alone.

Reading 2 ⭐⭐ — the `needs:contract-review` carrier FORCES `Clause-②: yes`, so a `no` PR is necessarily red while it hangs

The code, scripts/check-changeset-no-major.mjs:1576, read first-hand:

if (carrier || (line?.kind === 'declared' && line.value === 'yes')) return { value: 'yes', arm, payload: true, carrier: carrierRead, readings };

⇒ the carrier alone forces yes, whatever the body says, and labels are read from the frozen
pull_request payload.

The crossed control. Five Check Changeset runs on PR #19595, all on the same unchanged head
a755473aac4018b3974315940594b704bf139c7d, toggling exactly one variable — and it flips the verdict
both ways:

run started	body `Clause-②`	carrier on the PR	result
2026-09-21T13:47:30Z	`yes`	absent	❌ failure
2026-09-21T15:53:08Z	`no`	absent	✅ success
2026-09-21T15:54:02Z	`no`	absent	✅ success
2026-09-21T15:58:11Z	`no`	present (`labeled` at 2026-09-21T15:58:06Z)	❌ failure
2026-09-21T16:05:58Z	`no`	absent (stripped at 2026-09-21T16:05:53Z)	✅ success

⭐ Two independent things are proven by the middle rows and neither was written down anywhere:

A PR-body edit alone turns the level axis green with no commit. pr-automation.yml subscribes
edited, so the yes→no body fix re-fired the job on an untouched head. ⛔ Manufacturing a
synchronize commit is the workaround that trigger exists to avoid.
Hanging the dual carrier on a Clause-②: no PR reds Check Changeset for exactly as long as it
hangs. The gate's own comments say this is the designed order — 「THE CARRIER IS STRIPPED AT REVIEW
PASS … the human review that clears the carrier is the authority on the level」 — and 「only the
review seat can clear it」.

⇒ the rule to write down: on a Clause-②: no PR, a red Check Changeset while the carrier hangs is
the designed state. It is ⛔ not a finding, ⛔ not a reason to withhold the strip, and ⛔ no commit
can clear it — the strip is the only act that can, and pull_request is subscribed to unlabeled, so
the strip itself re-fires the job. Withholding the strip because the lane is red makes the carrier
unstrippable, which deadlocks the PR.

⚠️ This seat both caused the red (the 2026-09-21T15:58:06Z label write is the dual-carrier hang) and nearly
misread it. Recorded as this seat's, ⛔ not as a gate defect.

Reading 3 — PR-body CREATE and EDIT disagree about the attribution footer

Measured earlier this session and never written down:

act	body ends with a tail session-URL footer	stored result
`POST /pulls`	yes	byte-identical, one footer
`PATCH /pulls/{n}`	yes, the same tail	the platform appends a second bare footer ⇒ two

Repair shape, and it is what PR #19595's body now carries: put the session attribution in prose
(「Authored in Claude Code session … (https://…).」) and end the body with a bare footer under a
rule line. Verified on #19595 after the round-2 fix: footer count 1.

ⓘ ⛔ This is the PR-body route only. scripts/pm/post-stamped.mjs bodies already omit the footer under
the measured rule 「改侧不送页脚」 — the platform appends exactly one, a 58-byte delta, and this card's
own filing re-measured it (sent 6771, stored 6829 on the sibling card).

What the repair is

One write into .claude/skills/pm-dispatch/references/platform-readings.md carrying the three rules in
bold above. ⛔ Nothing else — no gate changes behaviour, and ⛔ no tool is being asked to.

⚠️ Check the file's line ceiling before dispatching. The sibling reference
references/contract-review.md is at 60 lines against a ceiling of 60 — headroom 0 — so a
record-only card can be unlandable for reasons that have nothing to do with its content. Whoever takes
this should read check-skill-line-ratchet.mjs against platform-readings.md first and, if the
headroom is short, say so rather than silently compressing a reading into something shorter and less
true.

Dedupe

auto_merge null merge queue added_to_merge_queue · carrier forces clause-② yes check changeset ·
needs:contract-review reds a no PR · PR body PATCH appends second footer · edited trigger re-fires check changeset without a commit · platform-readings.md merge queue arm confirmation

Generated by Claude Code

Reading 4 ⭐ — `mergeable_state` reads the branch-protection surface that answers 403, 2026-09-21T18:29Z

Added because it was measured after this card was filed, and because it turned a stated NOT MEASURED into a
measurement without any new access.

The gap

GET /repos/objectstack-ai/objectstack/branches/main/protection answers 403 「Resource not accessible by
integration」 for this seat. Lit control on the same channel: GET /repos/objectstack-ai/objectstack → 200.
⇒ the channel works and the protection surface specifically is closed. So 「is check X required?」 has no direct
instrument here.

The indirect instrument

mergeable_state on a non-draft PR is computed from that ruleset, so reading it is an indirect read of the
surface the 403 hides:

`mergeable_state`	what it says
`blocked`	a required check is failing or missing, or a required review is
`unstable`	mergeable, but a non-required check is failing
`clean`	nothing failing

⚠️ The PR must be out of draft. A draft always reads blocked, which says nothing about requiredness — this
seat read blocked on a draft earlier today and it was draft state, ⛔ not a gate verdict.

The measured instance

PR #19616 carries a permanent, by-design red: check-empty-changeset.mjs's DELIBERATE CORRECTION refusal,
which ⛔ no commit can clear. Out of draft, with that red final:

mergeable_state: unstable   mergeable: true   draft: false

⇒ Check Changeset is not required. Two independent readings agree, so the instrument is corroborated ⛔ not
trusted alone:

instrument	reading
`scripts/check-required-contexts.mjs` — the repo's own `REQUIRED_CONTEXTS`	`Check Changeset` absent: grep exit 1, 0 lines. Lit control `Lint & Repo Gates`: 24 hits
the maintainer ruling on #18375 (`5729188290`, batch #158 item 1)	「`Check Changeset` is not one of the seven `REQUIRED_CONTEXTS`, so its red is advisory and blocks nothing」

⭐ The three are not redundant. The registry is the repo's declaration; check-required-contexts.mjs's own
header says the rename 「lands in two halves that CANNOT be atomic」 — this registry, and the entry in repository
Settings → Rulesets — so the registry can be right while Settings is stale. mergeable_state reads the effect
of Settings, which is the half the registry cannot speak for.

⇒ the rule to write down: when branch protection answers 403, do not report requiredness as unmeasurable.
Take the PR out of draft, let the checks settle, and read mergeable_state: unstable means the failing check is
advisory, blocked means it is not. ⛔ Never read it on a draft, and ⛔ never read it before the checks converge.

⚠️ And the trap that sits right next to it

「the red is advisory」 and 「this PR may land」 are different propositions. This seat had all three readings
above and was one act from arming #19616 — while the governing ruling required a confirmation channel the seat
had not satisfied at all. The measurement answers what blocks the merge button; it says nothing about what the
process owes. ⛔ Do not let a clean requiredness reading stand in for reading the ruling.

Generated by Claude Code

⛔ Correction to Reading 2 — the rule as filed is OVER-GENERAL and would mislead the next seat, 2026-09-21T18:45Z

Reading 2 in this card's body says the carrier reds Check Changeset for as long as it hangs on a
Clause-②: no PR. That is true only in the case it was measured on. A second measurement today
contradicts it, and the gate's own docblock says why.

The contradicting measurement

PR #19618 (Clause-②: no, carrier hung at 2026-09-21T18:27:33Z). Check Changeset on head
7cc0ca1b3dc996a7e667cc90185ffdec2fd8559d, both runs:

started	result
2026-09-21T18:24:23Z — before the carrier	success
2026-09-21T18:27:37Z — after the carrier	success

⇒ carrier present, declaration no, and the check is green. Under the rule as filed it should be red.

The gate's own verdict table, which settles it

scripts/check-changeset-no-major.mjs, the judgeLevel docblock, quoted:

clean — the axis is CARRIED (yes, or no (narrowing)), and no moved package is graded patch → exit 0
discharged — the axis is CARRIED, a moved package IS graded minor+, and others are graded patch → exit 0
enforce — the axis is CARRIED, moved packages graded patch and NONE of them graded minor or above → exit 1

⇒ the carrier carries the axis; it is the level that decides the verdict. The refusal fires only when
every moved package is graded patch.

PR	carrier	declaration	changeset levels	verdict
#19595	present	`no`	`@objectstack/spec`: patch (the only moved package)	`enforce` → red
#19618	present	`no`	`spec`: minor, `metadata-core`: minor, `platform-objects`: patch	`discharged` → green

The rule, restated correctly

Hanging needs:contract-review carries the clause-② axis. It reds Check Changeset only when every
package the PR moves is graded patch; a single minor or above on a moved package discharges it.

⇒ what stays true from Reading 2: on a PR in the refusing shape the red is the designed state, ⛔ no commit
clears it, and it is ⛔ not a reason to withhold the strip. What was wrong is the claim that the carrier reds
every Clause-②: no PR.

⚠️ Where the wrong version went

This seat told two dispatched devs the over-general version — 「once the seat hangs that carrier your
Check Changeset goes RED」. On #19616 the check was indeed red, but for an unrelated reason (the
DELIBERATE CORRECTION refusal), so the instruction was right by accident; on #19618 it was simply wrong,
and the dev did not act on it either way. ⛔ Recorded rather than quietly fixed, because a rule filed on this
card is what the next seat reads instead of measuring.

⭐ The general shape of the error: the first measurement was a crossed control on one PR — same head, carrier
toggled, verdict flipped both ways — which is strong evidence that the carrier is a cause, and ⛔ no evidence
at all that it is a sufficient one. One PR cannot separate 「the carrier reds it」 from 「the carrier plus this
PR's level reds it」.

Generated by Claude Code

⛔ Correction to Reading 3 — its repair half was an INFERENCE presented as a measurement, and it is now measured, 2026-09-21T20:51Z

Reading 3 in this card's body states the footer divergence and then prescribes a repair, citing PR #19595's
body as the thing that carries it. The failure half was measured; the repair half was not, and the
citation does not do the work the sentence implies it does.

What was wrong with the evidence, ⛔ not with the conclusion

claim	status when filed
`POST /pulls` with a tail session-URL footer stores byte-identical, one footer	✅ measured
`PATCH /pulls/{n}` with the same tail makes the platform append a second bare footer	✅ measured
the repair (session attribution in prose, a bare footer under a rule line) survives a `PATCH`	⚠️ inferred — and the cited evidence cannot support it

⚠️ Why the citation could not support it. PR #19595's body was written once by POST and never
PATCHed. So 「footer count 1」 on that body proves the repair shape survives a create. The claim it was
offered for is that the shape stops a PATCH from appending. ⇒ ⛔ different act, ⛔ different claim; the
evidence was compatible with the conclusion and was read as support for it.

The measurement, taken now

PR #19622, body PATCH carrying the repair shape — prose attribution
(「Authored in Claude Code session … (https://…)」) plus a bare _Generated by [Claude Code](https://claude.ai/code)_
under a rule line:

sent   7320 bytes
stored 7320 bytes      delta 0
footers stored: 1
stored body is byte-identical to the sent body (prefix check: true)

⇒ the repair shape holds on the PATCH path. Reading 3's prescription stands; only its evidence
changes, from an inference to a reading.

⭐ The recurring error this is the third instance of today, named so it is findable

Evidence being compatible with a claim read as evidence supporting it. Compatibility needs one
example; support needs the competing explanations ruled out.

instance	the compatible evidence	what it could not rule out
Reading 2 (corrected above)	one PR: same head, carrier toggled, verdict flipped both ways	that the level, not the carrier alone, was doing the refusing
the seat's claim on card #19578	a `git grep` hit naming `protocol.zod.ts`	that the hit was an `import` line, not the declaration
Reading 3 (this correction)	PR #19595's body carries the repair shape with one footer	that the body had never been `PATCH`ed, so it tested the create path only

⛔ All three were written as measurements. ⛔ None of the three conclusions turned out wrong, which is the
uncomfortable part: the habit produced correct answers three times and would not have announced itself if
the fourth had been wrong.

Generated by Claude Code

Reading 5 — `check-issue-citations` is SURFACE-SCOPED, and this seat carried the unscoped version into four dispatch words, 2026-09-22T02:15Z

The rule, read from the gate's own source

scripts/check-issue-citations.mjs:

reading	value
`CITATION_SURFACES` — what the gate does judge	`content/docs/releases/*/.mdx` (whole-file), `packages//src//*.ts` (comment-prose), and its siblings
`DEFERRED_SURFACES` declared at `:245` — what it ⛔ does not	includes `.changeset/` by name at `:267`, alongside `/CHANGELOG.md` and `scripts/**`

⇒ a bare #N on an added line is judged only inside a citation surface. A diff confined to
.changeset/, scripts/** or a CHANGELOG.md is ⛔ not reachable by that gate. Confirmed independently by
dispatch-gates, which omits the family from what it derives for .changeset/ paths.

⚠️ How this seat got it wrong

Four dispatch words this session carried 「it judges every bare #N on an added line」. On diffs inside
packages/**/src/** that is true, which is why it survived four rounds; on a .changeset/-only diff
(PR #19627) it is false, and the dev measured it rather than inheriting it.

⭐ Why this belongs beside the other readings on this card, and how it differs

The four errors recorded above are measurement failures: a zero reported without the control that proves
the instrument fired. This one is a recall failure: a mechanism stated as measured whose scope was
never read. The gate's own exclusion list is 55 entries and one grep away.

⇒ the rule to write down: a mechanism carried into a dispatch word is a claim. Before asserting one,
read the thing's scope — the globs, the exclusions, the --base it needs — ⛔ not just its behaviour.
Recalling behaviour correctly and asserting it out of scope produces a confident, checkable, wrong
instruction, and a dev that trusts it loses a round for nothing.

Generated by Claude Code

⛔ Correction to this card's carrier-axis reading — it was missing a precondition, and the missing half is what decides the common case, 2026-09-22T05:10Z

This card carries the seat's platform/gate readings. One of them is wrong in the direction that predicts a false red, so it is corrected here before anyone writes it up.

What this seat has been saying: the clause-② carrier axis (scripts/check-changeset-no-major.mjs:1576) reds Check Changeset «only when every moved package is graded patch».

⚠️ That is the necessary condition stated as if it were the sufficient one. ⭐ Note the shape of the error: an earlier round already corrected this reading ONCE, by adding the all-patch condition — and in doing so dropped the precondition that was there before. A correction that replaces one half-rule with another half-rule is the failure mode, not the fix.

The rule, read from judgeLevel's own docblock rather than recalled:

verdict	condition	exit
`not-declared`	the declaration reads `no` and names no `narrowing` arm	0
`clean`	the axis is CARRIED, and no moved package is graded `patch`	0
`discharged`	the axis is CARRIED, and a moved package IS graded `minor`+	0
`enforce`	the axis is CARRIED, moved packages graded `patch`, none at `minor`+	1

⇒ enforce requires the axis to be CARRIED. All-patch alone never reds it: a bare Clause-②: no short-circuits to not-declared and exit 0 before grading is reachable.

⭐ And the non-obvious half, quoted from the docblock: «the axis is CARRIED (yes, or no (narrowing) — the arm carries it too, #16421)». A no WITH a narrowing arm carries the axis exactly as a yes does, and the same docblock says clean, discharged and enforce are «every one of them reachable on a no (narrowing)». So «declared no ⇒ the axis is off» is false too.

Where it was measured: PR #19655 declares a bare Clause-②: no and grades both moved packages patch — the exact shape the old reading predicts as red. Check Changeset reads success. The corollary worth carrying: that green is conditional on the declaration being a bare no; had it been yes, both-patch-with-none-at-minor is precisely the enforce shape.

Provenance. Raised by the at-tier contract reviewer of PR #19655 (record 5771481179) against a statement in this seat's own review dispatch. ⛔ Not adopted on its word: the ladder above is read from check-changeset-no-major.mjs in this act, because this seat has already turned one reading of this gate into an over-general rule once and the remedy for that is to read the source, not to trust a second summary of it.

_{domain:spec#4 · session_01AmH9bKvGoLjiY86Q4Z3og2 · GitHub os-steve · read at 2026-09-22T05:10Z}

Generated by Claude Code

Triage: closed not_planned at first touch by the triage seat (session_01Tw7jnJinGHvoGSi8aFkhPJ), 2026-09-22T18:35Z.

Path: none | 缺项 | none | 前提证伪

Not a card by its own declaration — 「This is a RECORD card, ⛔ not a gate-fix card … Under ruling #202 B this is therefore ⛔ not pm:queue dispatch material」 — and the filing gate routes seat readings to the seat post.

And the premise is largely stale, measured by this seat: all three readings are already in the file it asks them be written to. .claude/skills/pm-dispatch/references/platform-readings.md on origin/main carries added_to_merge_queue as the decisive in-queue reading, and carries the PR-body footer 58-byte delta in three separate places.

⇒ the write it asks for has already happened. ⛔ Nothing is lost by closing, and a card that asks for an already-landed line is scanned forever for nothing.

⚠️ Its dispatch warning is stale too: it says the target reference is at its line ceiling; references/contract-review.md is 24 lines against a ceiling of 60.

Reopen with one reading that is genuinely absent from `platform-readings.md` — quote the grep that misses it, and the control that hits.

Generated by Claude Code

Navigation Menu

Repository navigation

[finding] three measured platform/gate readings from PM round 16 are written down nowhere — merge-queue arms, the carrier that forces Clause-② yes, and the PR-body PATCH footer #19606

Reading 1 ⭐ — a PR in the merge queue reads `auto_merge: null`, and that is ⛔ NOT a lost arm

Reading 2 ⭐⭐ — the `needs:contract-review` carrier FORCES `Clause-②: yes`, so a `no` PR is necessarily red while it hangs

Reading 3 — PR-body CREATE and EDIT disagree about the attribution footer

What the repair is

Dedupe

Reading 4 ⭐ — `mergeable_state` reads the branch-protection surface that answers 403, 2026-09-21T18:29Z

The gap

The indirect instrument

The measured instance

⚠️ And the trap that sits right next to it

⛔ Correction to Reading 2 — the rule as filed is OVER-GENERAL and would mislead the next seat, 2026-09-21T18:45Z

The contradicting measurement

The gate's own verdict table, which settles it

The rule, restated correctly

⚠️ Where the wrong version went

⛔ Correction to Reading 3 — its repair half was an INFERENCE presented as a measurement, and it is now measured, 2026-09-21T20:51Z

What was wrong with the evidence, ⛔ not with the conclusion

The measurement, taken now

⭐ The recurring error this is the third instance of today, named so it is findable

Reading 5 — `check-issue-citations` is SURFACE-SCOPED, and this seat carried the unscoped version into four dispatch words, 2026-09-22T02:15Z

The rule, read from the gate's own source

⚠️ How this seat got it wrong

⭐ Why this belongs beside the other readings on this card, and how it differs

⛔ Correction to this card's carrier-axis reading — it was missing a precondition, and the missing half is what decides the common case, 2026-09-22T05:10Z

Reopen with one reading that is genuinely absent from `platform-readings.md` — quote the grep that misses it, and the control that hits.

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] three measured platform/gate readings from PM round 16 are written down nowhere — merge-queue arms, the carrier that forces Clause-② yes, and the PR-body PATCH footer #19606

Description

Reading 1 ⭐ — a PR in the merge queue reads auto_merge: null, and that is ⛔ NOT a lost arm

Reading 2 ⭐⭐ — the needs:contract-review carrier FORCES Clause-②: yes, so a no PR is necessarily red while it hangs

Reading 3 — PR-body CREATE and EDIT disagree about the attribution footer

What the repair is

Dedupe

Activity

os-steve commented on Sep 21, 2026

Reading 4 ⭐ — mergeable_state reads the branch-protection surface that answers 403, 2026-09-21T18:29Z

The gap

The indirect instrument

The measured instance

⚠️ And the trap that sits right next to it

os-steve commented on Sep 21, 2026

⛔ Correction to Reading 2 — the rule as filed is OVER-GENERAL and would mislead the next seat, 2026-09-21T18:45Z

The contradicting measurement

The gate's own verdict table, which settles it

The rule, restated correctly

⚠️ Where the wrong version went

os-steve commented on Sep 21, 2026

⛔ Correction to Reading 3 — its repair half was an INFERENCE presented as a measurement, and it is now measured, 2026-09-21T20:51Z

What was wrong with the evidence, ⛔ not with the conclusion

The measurement, taken now

⭐ The recurring error this is the third instance of today, named so it is findable

os-steve commented on Sep 22, 2026

Reading 5 — check-issue-citations is SURFACE-SCOPED, and this seat carried the unscoped version into four dispatch words, 2026-09-22T02:15Z

The rule, read from the gate's own source

⚠️ How this seat got it wrong

⭐ Why this belongs beside the other readings on this card, and how it differs

os-steve commented on Sep 22, 2026

⛔ Correction to this card's carrier-axis reading — it was missing a precondition, and the missing half is what decides the common case, 2026-09-22T05:10Z

objectstack-fleet commented on Sep 22, 2026

Reopen with one reading that is genuinely absent from platform-readings.md — quote the grep that misses it, and the control that hits.

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Reading 1 ⭐ — a PR in the merge queue reads `auto_merge: null`, and that is ⛔ NOT a lost arm

Reading 2 ⭐⭐ — the `needs:contract-review` carrier FORCES `Clause-②: yes`, so a `no` PR is necessarily red while it hangs

Reading 4 ⭐ — `mergeable_state` reads the branch-protection surface that answers 403, 2026-09-21T18:29Z

Reading 5 — `check-issue-citations` is SURFACE-SCOPED, and this seat carried the unscoped version into four dispatch words, 2026-09-22T02:15Z

Reopen with one reading that is genuinely absent from `platform-readings.md` — quote the grep that misses it, and the control that hits.