docs(os-dev): the report comment opens with the seat signature, os-dev-report on line 2 (#27998)

<!-- claude-projects-attribution: {"github_login":"os-elon-musk"} -->
_Requested by **Elon** · [project
thread](https://claude.ai/code/project/chan_01WedDzV26nniwxv7jC88B9D?thread=cmsg_01WedDzV26nniwxv7jC88B9DWHWAYmZVGjAvyE1PE5yCN5)_

Fixes #27962

## What changes

`.claude/agents/os-dev.md` lines 17–18, the two sentences that place the
`os-dev-report` comment's lines. They now say the comment is written by
`scripts/pm/post-stamped.mjs`, line 1 is the seat signature, and line 2
is the plain-text `os-dev-report` marker. The rest of the file is
untouched; no recogniser changes (`post-stamped.mjs` and every
first-line reader already skip one leading signature line through
`stripSignatureLine` / `OS_DEV_REPORT_MARKER`).

## Why

Two governed texts contradicted each other. `os-dev.md:17` told a dev to
open the report comment with `os-dev-report` on line 1, while
`post-stamped.mjs` (the only sanctioned writer) refuses any body whose
first line is not the seat signature (`LANE#N · ACCOUNT · SESSION`).
Four devs reported the conflict; each dispatch paid a round trip. Triage
6516073129 ruled: signature on line 1, marker on line 2, name
`post-stamped.mjs` as the writer, no recogniser change.

## Verification

- `os-dev.md` stays at 402 lines (its skill-line-ratchet ceiling); both
replaced lines are 114 and 116 bytes.
- Readers accepting the line-2 form, measured on `origin/main`
`6d5c021d9`: `check-half-states.mjs` `OS_DEV_REPORT_MARKER` (optional
leading `SEAT_SIGNATURE_SOURCE` line), `check-handover.mjs`
`reportedStatus` (uses that marker), `check-prior-rulings.mjs`
`classifyRulingComment` (calls `stripSignatureLine`).
- Every gate family `node scripts/pm/dispatch-gates.mjs --commands`
derives for this path was run locally with exit codes recorded and
reconciled with `--ran`; the set is identical before and after the
commit. Results are in the `os-dev-report` comment on the card.

Clause-②: no
Metadata-protocol: none

## 维护者速读

- 改了什么:`os-dev.md` 第 17–18 行两句话,改为「报告评论由 `post-stamped.mjs` 写,首行席位签名,次行
`os-dev-report`」。
- 为什么改:原文说标记在首行,而唯一写入工具要求首行是签名,每次派发 dev 都要为此回一趟。
- 风险与回滚:纯规则文字,不碰任何识别器或门禁;回滚即 revert 这一个提交。
- 先看:diff 只有两行;对照 `scripts/pm/post-stamped.mjs` 头注「The first line is the
seat's signature」。
- 两分钟验证:`pnpm check:pm-skill-ratchet` 与 `pnpm check:pm-skill-id-lint`
绿;`wc -l .claude/agents/os-dev.md` 仍为 402。
- 需要你做的:暂无;契约复审(contract
review)欠席位出具,落地档位以登记册为准(`check-governed-merges.mjs --pr`)。

## Human Minimum

Each item is one rule from
[CONTRIBUTING.md › Human
Minimum](https://github.com/objectstack-ai/objectstack/blob/main/CONTRIBUTING.md#human-minimum),
which links the AGENTS.md text that states it.

- [x] 1. Schemas start as Zod; `packages/spec` holds no runtime logic.
(not touched)
- [x] 2. Every name I added uses the casing for its kind. (no names
added)
- [x] 3. No formatter ran; `pnpm lint` passes. (prose-only diff; derived
lint families green)
- [x] 4. One issue, one branch off an up-to-date `main`, one pull
request.
- [x] 5. A change that publishes carries a changeset, and both
declaration lines are filled in here and in the changeset. (nothing
publishes; `skip-changeset`)
- [x] 6. `packages/spec` touched: its generated artifacts are
regenerated and committed. (not touched)
- [x] 7. No hand edits to `content/docs/references/`,
`packages/*/CHANGELOG.md` or `content/docs/releases/`.
- [x] 8. Title, body and comments are in English. (the 维护者速读 block is
the sanctioned Chinese channel)
- [x] The *Before Submitting* list in CONTRIBUTING.md is done.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_016WV4czpd3gJLpqfxjS3KQc

Co-authored-by: Claude <noreply@anthropic.com>

Author: objectstack-fleet[bot]

.claude/agents/os-dev.md

@@ -14,8 +14,8 @@ model: opus
 
 你是 ObjectStack 开发 agent,由 PM 派发,恰好带一张 GitHub issue;无卡时派发令即卡并点名分支。
 交付物两件:该 issue 实现完毕并推成 draft PR,加下方的 JSON 报告;无卡则无 `Fixes #`,仅交终报。
-报告交付两次,GitHub 优先:同一段 JSON 先作 issue 评论,首行单独一行是纯文本 `os-dev-report`。
-⛔ 不用 HTML 注释写标记。再作为终报消息:PM 机械解析它,终报消息就是 JSON 本身。
+报告交付两次,GitHub 优先:同一段 JSON 先作 issue 评论,经 `post-stamped.mjs` 写:首行席位签名,
+次行纯文本 `os-dev-report`,⛔ 标记不用 HTML 注释。再作终报:PM 机械解析,终报即 JSON 本身。
 仓库根的 AGENTS.md 有约束力,第一次编辑前先读它。
 本文件只承载规则、查表数据与钩子无法机械强制的条款;教训写成自含规则,⛔ 不引卡号。
 引文只在原话本身即操作性判据处保留。