[PM seat] security — 🟢 os-justin #29740

security#1 · os-justin · session_01QSeKYn5CmmdShCJifm6WYj

⚠️ Seat stub. Job description: .claude/skills/pm-dispatch/references/lanes/security.md (⛔ not copied here). Never-public rules: .claude/skills/pm-dispatch/references/security-findings.md. This is security seat 1. This post carries no finding, path, object name or mechanism, by rule.

Current PM — 🟢 os-justin

• Holder: os-justin (GET /user) · session_01QSeKYn5CmmdShCJifm6WYj (a direct session the maintainer summoned) · seated on the maintainer's order in that session, verbatim 「你是 security#1 座位」, once the lane charter landed (docs(pm-dispatch): the security lane — a security#1 seat owns every security finding; its charter, the Notify: security doorbell and the seat signature #29695, card pm-dispatch(security): a security#1 seat owns every security finding end to end — intake, the opaque advisory ledger, the no-card fix order, the rule-level review — and security-findings.md names it as the owner #29665).
• Mailbox: PR pm:mailbox — security#1 · os-justin #29743 (Mailbox-of: security#1 · os-justin), subscribed by the seated session; seat-online rung in triage's mailbox.
• Patrol: none. An on-demand seat for now; the maintainer is in session.
• Ledger rule: one row per advisory, opaque id · session · state, ⛔ no detail (lanes/security.md). Claims on advisory fixes live here, never in session memory.

Ledger

Standing orders (maintainer, this session, verbatim):

• 「目前的修复都关闭」 and 「你处理完的可以都先关闭」: once an advisory's fix merges, the seat closes it through the relay advisory_state and records it here.
• 「哪些高危要发布应该在我版本发布前决策吧」: before each version release, the seat puts a publish-or-not list to the maintainer, covering the closed advisories since the last release (high and moderate first), reviewed at CONTRACT_REVIEW_TIER first. Publishing is the maintainer's: they reopen and publish in the advisory UI, since the relay cannot move a closed advisory.
• 「同意,batch 调到 5」: the seat runs at most 5 slots at once.
• 「只记录,暂停派发」 (2026-11-04), lifted by 「可以继续派发」: the fourth and fifth decision batches are ruled and recorded in the seat's private notes, and dispatch has resumed.
• 「changeset 改写确认都同意」 (2026-11-05): a pending-changeset DELIBERATE CORRECTION lands on the seat's own record, as landing-operations.md already says (the ACCEPT quoting before and after, or the same-head at-tier PASS). The seat does not wait on the maintainer for it. Skills card: pm-dispatch skills: say who confirms a pending-changeset correction (the seat's record, never a maintainer wait) everywhere a dev or the gate is told to "get it confirmed", and keep PR bodies from narrating pre-fix behaviour on security fixes #30271.

Hot-file serial queue

⛔ Re-derive from live claims and each open PR's file list before every dispatch.

• None held as a lane: fixes land in their owning packages through no-card orders.
• .claude/skills/pm-dispatch/references/lanes/security.md and security-findings.md: pm/fleet-write: the relay publishes a security advisory on the maintainer's list: reopen, set the affected and patched versions, publish #30110 (dispatched) first, then pm-dispatch skills: the security seat's triage of a non-finding, its ledger states after the close-on-merge order, a release's contents read by ancestry, and the CI recoveries the relay leaves #30111 (filed, held until pm/fleet-write: the relay publishes a security advisory on the maintainer's list: reopen, set the affected and patched versions, publish #30110 merges).

Notes

• Write path: the relay (post-stamped.mjs, label-write.mjs, issue-create.mjs, fleet-write/dispatch.mjs). ⛔ No GitHub MCP writes. Advisory text is read only through the relay advisory_read.
• domain:skills#2 ([PM seat] domain:skills · seat 2 — ⏳ vacant #19287), held by this session for the security work's skills-lane cards, was handed back once they landed (clock-out brief 6598110373).