readings: MCP issue creation drops the trailing attribution footer block and eats `<…>` spans in titles — REST PATCH restores the body; file issues through REST or PATCH after

[claude]

Filed by the domain:skills seat (session session_019RfFHiRCSs3JXLK4cwcfox, os-steve) as a platform-readings candidate for the fifth readings increment (after the ceiling ruling on #15960). Self-triaged priority:p3, pm:blocked, governed (references/platform-readings.md).

Blocked-by: #15960

Measured

• Four cards this seat created today through the MCP issue_write create path (os-dev.md: the line-ratchet clause says "report blocked" where the dispatch protocol's measurement-first route is the ruled exception for a zero-headroom governed ledger — narrow the clause #15959, [Decision] platform-readings.md ceiling 359 → 362 for the fourth readings increment (PR #15955, red on the ratchet by design) #15960, core-rules.md digest owes one line for the two decision-frame rules PR #15946 lands (Governing text, protocol as baseline) #15961, objectui#7775) were all stored WITHOUT the trailing --- + _Generated by [Claude Code](https://claude.ai/code)_ block that was sent; the rest of each body was intact. The domain:cli seat measured the same on [finding] guard-main-checkout-bash.sh prints an escape hatch that cannot work as printed — OS_ALLOW_MAIN_EDITS=1 <cmd> is refused, because the hook reads its own environment, not the command's prefix #15971 and [finding] package-state/ENVIRONMENT.json is keyed by environment id under the machine-global home, so two projects on one machine share which packages are disabled #15969 (its 16:53Z comment on [finding] guard-main-checkout-bash.sh prints an escape hatch that cannot work as printed — OS_ALLOW_MAIN_EDITS=1 <cmd> is refused, because the hook reads its own environment, not the command's prefix #15971), while an identical block survived on a PR body created minutes apart.
• The title's angle-bracket span is eaten on the same path: [finding] guard-main-checkout-bash.sh prints an escape hatch that cannot work as printed — OS_ALLOW_MAIN_EDITS=1 <cmd> is refused, because the hook reads its own environment, not the command's prefix #15971 was sent as OS_ALLOW_MAIN_EDITS=1 <cmd> and stored without <cmd> (also seen earlier on rest-server.ts still describes the scoped URL family as /projects/:id/... in two docblocks, the spelling ADR-0006 D2 retired with no alias #15858).
• A REST PATCH /issues/{n} with the body re-sent plus the footer stored it verbatim and read back identical (the four cards above, 17:1xZ) — consistent with the existing reading that an issue-body PATCH appends nothing.

The rule to land (one or two lines, platform-readings.md 读数陷阱 write-side cluster)

• Issue creation through the MCP path drops the trailing footer block and any <…> span in the title: create issues through REST POST /issues, or read the stored body back and PATCH the footer on; spell title placeholders as NAME or :id, never <…>.

Dedup

Not a duplicate of the sanitizer lines already in the ledger (HTML-comment-shaped markers stripped; lone angle brackets survive in bodies): those describe body content, this is issue CREATION dropping a trailing block and a TITLE span. Searched the ledger for issue_write, 创建 issue, 标题 — no hit.

---

Generated by Claude Code

[claude]

Claim: PM loop round 8 (continued) — flight P, the FIFTH readings increment into references/platform-readings.md, one flight over four carriers: #15977 (the MCP-create footer drop and <…> title eating; REST restores), #16006 (the spec@objectui seat's measured platform facts of 2026-09-05), #16104 SECTION 1 ONLY (the spec seat's shift-end platform facts; sections 2–3 stay open on that card for their own split), and #15803 SECTION C ONLY (six platform facts; that card's section A stays in the decision box, its labels untouched). Every candidate fact is deduplicated against the ledger before it is written, split by carrier where two cards state one fact, and landed as one rule line in the section it belongs to. The file sits at 362/362 after PR #15955's ruled raise, so this PR opens RED on the line ratchet BY DESIGN with the ceiling untouched — the measured line count is what the seat presents to the maintainer as the next ceiling decision (the #15960 shape), together with the standing-rule question.
Session: session_019RfFHiRCSs3JXLK4cwcfox
Branch: claude/issue-15977-readings-increment-five
Worktree: objectstack-issue-15977
Domain: domain:skills
File surface: .claude/skills/pm-dispatch/references/platform-readings.md only. ⛔ Not the ratchet map (the ceiling is the maintainer's), not rest-channel.md.
Container & model: S, mode:subagent, opus — dispatch-gates.mjs --tier: no path-derived mandate on references/**; ledger prose, no contract move.
Clause-②: no
Serial: PR #15955 (flight L, 04b61b5f6a, the fourth increment + the ceiling raise) sits at the governed terminal on this same file; this flight branches from origin/main, writes below the fourth increment's lines, and proves git merge-tree --write-tree clean against 04b61b5f6a before opening its PR. GOVERNED (.claude/**) ⇒ draft PR, in-seat review, os-zhuang + hotlong, human merge, skip-changeset; at ACCEPT the seat adds needs-user-decision + the 维护者速读 and files the ceiling decision card.
The PR carries Fixes #15977.

---

Generated by Claude Code