You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seam-card queues have no named reader: repo:* seat probes never scan objectstack's repo:objectui/repo:cloud labeled cards — a routed p0 sat unclaimed for a day and a half #9063
Filed by the skills seat (session session_017TNzEetykdh7ceZGwuAPLq, 2026-08-16) after the maintainer's direct question in the live PM session (verbatim, untranslated): 「这个问题报了很久没有处理,是因为 objectui 项目经理不会再看 objectstack 仓库是吗?」— the answer is yes, and by protocol design rather than negligence.
Measured
The Console filterBuilder p0 (priority:p0 + target:v17, filed 2026-08-15 04:21) was triaged correctly within 29 minutes — settled seam placement, repo:objectui + pm:queue, dedup clean, fallback priced, p0 queue-jump noted. It then sat unclaimed ~36h.
The repo:objectui seat post's 范围 section reads, in full: 「objectui 全仓队列」. The objectstack seam-card queue (label:repo:objectui here) is not in its declared scan scope, and nothing else names it.
The pm-dispatch skill's seam-card rule (多仓协调 Add metamodel interfaces for ObjectQL/ObjectUI contract #1: seam cards stay in objectstack carrying repo:objectui/repo:cloud) presupposes the repo seat reads this queue — the triage comment on the p0 states that presupposition explicitly. Both sides executed their own text faithfully; the gap is between the texts.
This violates the skill's own invariant: 「一个标签存在,当且仅当有具名读者」— repo:objectui/repo:cloud on objectstack cards currently have none.
Deliverable (one PR, skills lane)
Give the seam queues a named reader, in the versioned protocol rather than seat-post prose: the repo:* seat's round-start probe (整车道一次读全) explicitly includes the objectstack seam query — list_issues on objectstack with the single label repo:<repo> (single-label per the OR-semantics trap row) — merged into the same candidate pool and priority ordering as the home-repo queue. Landing spot is the dev's call between the 多仓协调 rule in SKILL.md (one clause naming the reader) and references/seat-post-protocol.md (the repo-seat probe checklist); ratchet ceilings apply, fund by compression. The objectui/cloud seat posts' 范围 lines then update to match (one-line edits by their own seats, notified — not this PR's files).
Interim mitigation (already executed)
Cross-seat notice posted on the repo:objectui seat post naming the p0 and asking this shift to include the seam query until the protocol lands.
Constraints
.claude/skills/pm-dispatch/** ⇒ fable-mandatory (derive via --tier); ADR-class human merge; new text in Chinese, machine literals English; no issue numbers in operational text.
Filed by the skills seat (session
session_017TNzEetykdh7ceZGwuAPLq, 2026-08-16) after the maintainer's direct question in the live PM session (verbatim, untranslated): 「这个问题报了很久没有处理,是因为 objectui 项目经理不会再看 objectstack 仓库是吗?」— the answer is yes, and by protocol design rather than negligence.Measured
priority:p0+target:v17, filed 2026-08-15 04:21) was triaged correctly within 29 minutes — settled seam placement,repo:objectui+pm:queue, dedup clean, fallback priced, p0 queue-jump noted. It then sat unclaimed ~36h.repo:objectuiseat post's 范围 section reads, in full: 「objectui 全仓队列」. The objectstack seam-card queue (label:repo:objectuihere) is not in its declared scan scope, and nothing else names it.repo:objectui/repo:cloud) presupposes the repo seat reads this queue — the triage comment on the p0 states that presupposition explicitly. Both sides executed their own text faithfully; the gap is between the texts.repo:objectui/repo:cloudon objectstack cards currently have none.Deliverable (one PR, skills lane)
Give the seam queues a named reader, in the versioned protocol rather than seat-post prose: the
repo:*seat's round-start probe (整车道一次读全) explicitly includes the objectstack seam query —list_issueson objectstack with the single labelrepo:<repo>(single-label per the OR-semantics trap row) — merged into the same candidate pool and priority ordering as the home-repo queue. Landing spot is the dev's call between the 多仓协调 rule inSKILL.md(one clause naming the reader) andreferences/seat-post-protocol.md(the repo-seat probe checklist); ratchet ceilings apply, fund by compression. The objectui/cloud seat posts' 范围 lines then update to match (one-line edits by their own seats, notified — not this PR's files).Interim mitigation (already executed)
Cross-seat notice posted on the
repo:objectuiseat post naming the p0 and asking this shift to include the seam query until the protocol lands.Constraints
.claude/skills/pm-dispatch/**⇒ fable-mandatory (derive via--tier); ADR-class human merge; new text in Chinese, machine literals English; no issue numbers in operational text.