Repository navigation
skills(pm-dispatch): the NORTH-STAR p2/p3 dispatch gate reads repo-wide open P0/P1; maintainer ruling makes it read the lane's own queue #19980
Description
Activity
objectstack-fleet commented
on Sep 24, 2026 ContributorAuthorMore actions分诊首次定级:
priority:p2·tooling·domain:skills·pm:queue—— 把北极星第 3 条的判断范围从"整个产品仓"改成"本车道自己的队列",照维护者 14:08Z 的裁决落进规则文本Path:
docs/NORTH-STAR.md:114(「优先级」第 3 条,Tier H)+.claude/skills/pm-dispatch/references/execution-duties.md:45(取卡前置,Tier S)Triage: lands in the dispatch-gate rule text ⇒
domain:skills,tooling,priority:p2,pm:queue; rationale: a maintainer ruling (verbatim on the card) already changes how every lane reads rule 3 and is in effect under 「维护者裁决 > 北极星」, so nothing is blocked today — but the two texts every seat re-reads at each take still say "repo-wide open P0/P1", so seats that have not heard the ruling keep idling on p2 work;docs/NORTH-STAR.mdis Tier H, so the PR lands only on the maintainer's approval.分诊席(
session_01Tw7jnJinGHvoGSi8aFkhPJ,座位贴 #6015),2026-09-24T14:29Z。⛔ 不认领、不派发。本席读完了卡面(本卡尚无评论),并在main(2c1011b01b)上核对了两处原文。本席核对
docs/NORTH-STAR.md:114:「产品仓还有开放的 P0/P1 时,任何车道不派 p2/p3 的工具卡、契约卫生卡;……」,与卡面一致。execution-duties.md:45:「取卡前置 = … 产品仓开放 P0/P1 每次取卡现读」,与卡面一致。
定级说明
- p2:裁决已经生效,规则文本落后只影响没听到裁决的席位能否派 p2 工作,不会造成错误结果。
tooling+domain:skills:改的是派工规则文本,维护者也点名是 skills 卡。- 本卡按新裁决本身即可派发(skills 车道队列的 P0/P1 以取卡时现读为准)。
执行要点
- 卡面列的两个开放点(一个车道有多个席位时"本车道"怎么算;
pm:blocked/pm:on-hold的 P0/P1 算不算"在队列里"),实施者先提出写法,⛔ 不要自行定下,交维护者在 PR 上确认。 - "解锁产品 P0/P1 的仪器卡沿链继承优先级"这一句保持原样。
- 同一轮全文搜
产品仓开放 P0/P1/产品仓还有开放的 P0/P1,覆盖.claude/**、skills/**、docs/**,并报告命中数和对照查询。
Generated by Claude Code
- addedpriority:p2Medium: important, M3Medium: important, M3and removed
on Sep 24, 2026 objectstack-fleet commented
on Sep 24, 2026 ContributorAuthorMore actionsClaim: PM loop round 7
Session:session_01A22sUB3mUWs6M36VgfijBq
Branch:claude/issue-19980-lane-scoped-priority-gate
Worktree:objectstack-issue-19980
Domain:domain:skills
Seat:domain:skills#1
File surface:docs/NORTH-STAR.md(:114, 「优先级」 item 3 — Tier H, the maintainer merges) ·.claude/skills/pm-dispatch/references/execution-duties.md(:45 rewritten in place — 183 / 183, ratchet-neutral, ≤120 bytes) (stop on breach; explain in the report)
Container & model:S — two rule sentences rewritten in place so the P0/P1 reading is the lane's own queue; no gate, tool, workflow or allow rule change,mode:subagent,model: opus — dispatch-gates --tier --repo objectstack-ai/objectstack on the surface prints "no path-derived mandate: the surface hits none of the 3 declared glob(s) … floor sonnet · default opus · ceiling fable"
Clause-②: no
Thread-read: 5816120091
Serial constraints cleared: serial dispatch by the maintainer's word 「后续改为串行派发」 — the previous takes #19973 → PR #19993 (19af43d141, 16:19Z) and #19990 → PR #19997 MERGED at 2026-09-24T17:31Z (cc4ee77587) and closed out before this claim; no open PR touchesdocs/NORTH-STAR.mdorreferences/execution-duties.md(the 15 open PRs' head branches read at 2026-09-24T17:32Z); the newest landings on the surface arecc4ee77587(#19997, this seat —execution-duties.md:147 / :149, :45 untouched) and61170fa385(the last touch ofdocs/NORTH-STAR.mdonorigin/main) — both read.Take basis: category ③ — the maintainer's verbatim 「当前车道队列中如果已经没有 p0 p1,就应该可以派其他卡。这应该提交一个 skills 卡。」 (14:08Z, filed on the card by the
domain:spec@ objectui seat; in effect since spoken under 「维护者裁决 > 北极星」); triage 5816120091 gradedpriority:p2·toolingand routeddomain:skills. Rule 3 read under the ruling itself: this lane's queue holds no P0/P1 (#19980 is its only queue card). Tier H bycheck-governed-merges --teston the surface (docs/NORTH-STAR.md ×1, H;.claude/** ×1): the PR stays draft under the four-piece terminal for the maintainer's own merge, ⛔ never flipped ready or enqueued by this seat. The two open points the card and triage name (what 「本车道」 means for a multi-seat lane and a cross-repo lane; whetherpm:blocked/pm:on-holdP0/P1 count as "in the queue") are the implementer's proposal on the PR for the maintainer to confirm, ⛔ not ruled by this seat; the rule text itself mirrors the maintainer's words. Queue 0 after this take; in flight 1. Dispatched as a subagent of this session with this comment as its only claim.
Generated by Claude Code
objectstack-fleet commented
on Sep 24, 2026 ContributorAuthorMore actionsos-dev-report
{
"issue": 19980,
"status": "done",
"branch": "claude/issue-19980-lane-scoped-priority-gate",
"pr": "#20009",
"session": "session_01A22sUB3mUWs6M36VgfijBq",
"premise_still_valid": true,
"summary": "North-Star 「优先级」 item 3 now reads the lane's own queue, as the ruling says: 「3. 本车道队列还有开放的 P0/P1 时,该车道不派 p2/p3 的工具卡、契约卫生卡;解锁产品 P0/P1 的仪器卡沿链继承其优先级。」. Only the subject and the bar changed; the unlock-chain clause is byte-identical. execution-duties.md :45 was rewritten in place to 「本车道队列开放 P0/P1 每次取卡现读」 (183/183 lines, 111 B). The premise held on origin/main cc4ee77, but the dispatch assumption "only two readers" was FALSIFIED. The widened sweep found a third reader, triage-duties.md :64, the triage close predicate 「产品仓 P0/P1 开着时,无解锁对象的 p2/p3tooling卡同样关。」. It sits directly under 「定级按北极星「优先级」1–3 条」 in its origin f151ef2^ SKILL.md :370-374, and left repo-wide it would close at first touch the very p2/p3 tooling cards the ruling unlocks. Following the ruling's intent, it was rewritten in place to 「所入车道队列 P0/P1 开着时,…」 (120/120 lines, 87 B). That line is outside the claim's declared file surface (see deviations), and the PR offers it as a one-line revert. The two open points on the card are NOT decided in the rule text. They are proposals under 维护者速读 你要做的 ①②, with ③ flagging the triage line. PR 20009 is a draft, Tier H, labelled skip-changeset, and waits for the maintainer's merge. The assignee was os-zhuang on arrival and was not touched.",
"files_changed": [
"docs/NORTH-STAR.md :114 (+1/-1; Tier H)",
".claude/skills/pm-dispatch/references/execution-duties.md :45 (+1/-1; 183/183 lines; 105 → 111 B)",
".claude/skills/pm-dispatch/references/triage-duties.md :64 (+1/-1; 120/120 lines; 78 → 87 B)"
],
"gates": [
"all at head 1470ba8 (the change commit a0c50fb + a merge of origin/main 1f05ea4 that touches none of the 3 files); the union was run once at a0c50fb and re-run in full at 1470ba8, with each exit code captured before any pipe",
"pnpm check:pm-skill-ratchet :: exit 0 (execution-duties.md 183 lines ceiling 183 headroom 0; triage-duties.md 120 lines ceiling 120 headroom 0)",
"pnpm check:pm-skill-id-lint :: exit 0 (34 file(s) clean)",
"pnpm check:skill-frame-sync :: exit 0",
"pnpm check:doc-authoring :: exit 0",
"pnpm check:pm-governed-prose :: exit 0 (2 surfaces name all 6 registered governed surfaces)",
"pnpm check:nul-bytes :: exit 0 (9417 tracked text files, no raw control bytes)",
"node scripts/check-skills-token-ratchet.mjs :: exit 0 (54 authored bundle files within ceilings)",
"node scripts/pm/check-governed-merges.mjs --test docs/NORTH-STAR.md .claude/skills/pm-dispatch/references/execution-duties.md .claude/skills/pm-dispatch/references/triage-duties.md :: exit 3 = the GOVERNED reading (3 of 3 paths hit; landing tier H; .claude/** x2, docs/NORTH-STAR.md x1)",
"pnpm check:pm-governed-merges :: exit 0",
"pnpm check:pm-half-states :: exit 0 (4912 cases; NEW against the dispatch-time list, matched via triage-duties.md)",
"pnpm check:pm-settings-deny-roster :: exit 0 (artifact-roster family whose roster lives under .claude)",
"pnpm --filter @objectstack/lint run check:doc-formula-expressions :: exit 0. The first attempt exited 3 (PREREQUISITE NOT MET, nothing measured). It was re-run afterturbo run build --filter=@objectstack/formula --filter=@objectstack/lintunder os-verify-lock (VERDICT command-exit 0, at both heads)",
"node scripts/check-ci-filter-parity.mjs · node scripts/check-closing-keyword-parity.mjs (+ --self-test) · node scripts/check-comment-mask-corpus.mjs · node scripts/pm/check-harness-current.mjs --self-test :: exit 0 each",
"pnpm check:agent-test-spelling · check:cross-package-test-inputs · check:driver-memory-census · check:gitlink-declared · check:refd-timer-probe · check:watch-hint-literal :: exit 0 each",
"dispatch-gates --ran at 1470ba8: 19 derived famil(ies) accounted for, 19 run, 0 NOT-MEASURED (a DERIVED zero: all 19 recorded an exit code and none of them is 3)",
"CI on PR 20009 at report time: in_progress (33 check runs on 1470ba8: 11 success, 11 skipped, 11 in_progress); not waited on, per the dispatch contract"
],
"tests": "No code, no test and no package source changed, so there is no package build closure and no package test or typecheck to run. The measured verification is the gate union at head 1470ba8 (git rev-parse --short HEADafter the final commit), listed under gates. Reader sweep (git grep -F over .claude/, skills/, docs/, AGENTS.md, CLAUDE.md, content/docs/, scripts/pm/**; base cc4ee77 → head 1470ba8):产品仓开放 P0/P11→0;产品仓还有开放的 P0/P11→0;开放的 P0/P11→1 and开放 P0/P11→1 (same lines, new subject);产品仓3→0;P0/P1 开着1→1;本车道队列1→3;所入车道队列0→1. Controls:沿链继承2/2 and「优先级」4/4, unchanged. The English regex returned 7 hits, all unrelated. Pins elsewhere (取卡现读|无解锁对象|契约卫生卡|任何车道不派outside the 3 files) = 0. Siblings: objectui origin/main 8b1f066 has 0 hits; cloud origin/main c208a71 has 1 unrelated hit (ADR 0009 「按第 3 条分阶段」), the positive control. Byte checks: the stored PR body equals the sent body (12033 B, one session-URL footer); a self-scan of the body and the 3 files for control bytes returned exit 1 (none). NOT MEASURED, CI-only: the Test Core shard steps, the 4 type-check lanes, shard attestation and check-half-states --format=markdown --provenance. None has a local invocation, and no TypeScript is touched.",
"mcp_calls": "0",
"api_writes": "3 REST writes through the fleet-write relay (scripts/pm/, as objectstack-fleet[bot]), each one repository_dispatch plus its run: (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft PR 20009; run 36037852810, success); (2) label-write labels_add skip-changeset → POST /repos//issues/20009/labels (run 36037956642, success; the read-back matches: documentation, size/xs, skip-changeset); (3) post-stamped comment → POST /repos//issues/19980/comments (this report). Not counted: 3 git pushes (empty probe branch, the change commit, the pre-PR merge of main). Reads: REST GETs of the card and its comments, the open-PR list and file lists, the PR read-back and one check-runs read.",
"open_questions": [
{
"question": "What 「本车道」 means for a multi-seat lane and for a cross-repo lane.",
"options": [
"A: the open cards carrying that domain:X label in the repo the dispatching seat works. Seats of one lane in the same repo share that one queue; a cross-repo seat (e.g. domain:spec at objectui) reads only its own repo's same-named lane queue.",
"B: one queue per domain:X across every repo the lane spans, shared by all its seats."
],
"recommendation": "A, on four axes. Real need: the ruling came from the domain:spec at objectui seat idling while its own queue held 0 P0/P1 and objectstack held 4 P0 / 34 P1; B re-creates that coupling at lane scale. Long-term fit: A matches the per-seat reads the skill already uses (seat-lifecycle 读数三 本车道 pm:dispatched ∪ pm:queue; cross-repo-coordination 车道可分席 席号或域×仓). AI-error: A is the single label read execution-duties :9 already performs. Scope: no new tool or gate. Proposed on the PR for the maintainer's word, not written into the rule."
},
{
"question": "Whether pm:blocked / pm:on-hold P0/P1 count as 「在队列里」.",
"options": [
"A: count only cards the lane can take now (open, pm:queue, unassigned). In-flight pm:dispatched, pm:blocked, pm:on-hold and decision-box P0/P1 do not count.",
"B: count every open P0/P1 in the lane, whatever its state."
],
"recommendation": "A. Those cards cannot be dispatched, so counting them idles the lane: the very situation the ruling corrects. A blocked P0/P1 is already covered by the unchanged second half of item 3 (沿链继承), because the card that unblocks it inherits its priority. Proposed on the PR; if the maintainer wants B, it is a one-place change."
},
{
"question": "Keep the triage-side rewrite (triage-duties.md :64, the third reader the sweep found) or leave triage repo-wide.",
"options": [
"A: keep. Triage closes p2/p3 tooling cards without an unlock target only while the lane the card is routed into has open P0/P1.",
"B: revert that one line and change the dispatch side only."
],
"recommendation": "A. Under B, triage closes on first touch the same cards the ruling makes dispatchable, which defeats the ruling. The triage grade on this card (5816120091) already read it lane-scoped. Flagged as 你要做的 ③ on the PR; B is a one-line revert."
}
],
"deviations": [
"File surface expanded: .claude/skills/pm-dispatch/references/triage-duties.md :64 is not in the claim's File surface (5819005127 names NORTH-STAR.md and execution-duties.md). It is inside the card's own scope ("any other reader of the same rule"), falsifies the dispatch assumption that only two readers exist, and was rewritten per the ruling's intent. No open PR touches the file (16 open PRs' file lists read) and it is not a SINGLE_CLAIM_PATHS entry. OWED BY THE SEAT: add it to the claim's file surface (the dev writes no claim).",
"Pre-PR merge: origin/main 1f05ea4 (formula/objectql; disjoint from the 3 files) was merged into the branch before the PR opened, so the PR head is the merge commit 1470ba8. The whole gate union was re-run there, with formula and lint rebuilt first.",
"The dispatch-time gate list lackedpnpm check:pm-half-states, which is derived from the triage-duties.md path. It was run: exit 0.",
"Attribution: the harness reminder asks for a model-named Co-Authored-By trailer and a different PR footer. AGENTS.md prevails, so the commits carry the model-free pair (Claude-Session + Co-authored-by: Claude) and the PR body ends with the session-URL footer. Reported, not imitated."
],
"out_of_scope_findings": []
}
Generated by Claude Code
objectstack-fleet commented
on Sep 24, 2026 ContributorAuthorMore actionsACCEPT — os-dev-report 5819404372 (2026-09-24T18:00Z) reviewed against
references/review-checklist.mdby thedomain:skills#1seat (session_01A22sUB3mUWs6M36VgfijBq) at 2026-09-24T18:03Z. Tier H — this ACCEPT is piece ① of the four-piece terminal (SKILL.md 〈路径分叉〉): the PR stays draft for the maintainer's own merge; ⛔ this seat never flips it ready or enqueues it.Claim amendment (file surface): the claim 5819005127 named
docs/NORTH-STAR.mdandreferences/execution-duties.md. The dev's widened reader sweep (git grep -Fover.claude/**,skills/**,docs/**,AGENTS.md,CLAUDE.md,content/docs/**,scripts/pm/**, with controls) found a third reader the dispatch had missed:references/triage-duties.md:64, the triage close predicate 「产品仓 P0/P1 开着时,无解锁对象的 p2/p3tooling卡同样关」 — inside the card's own scope (「any other reader of the same rule」). The surface now readsdocs/NORTH-STAR.md:114 ·references/execution-duties.md:45 ·references/triage-duties.md:64 — all three rewritten in place, no line added (183 / 183, 120 / 120). No open PR touches the third file (the open PRs' file lists read by the dev; re-read by this seat at 2026-09-24T18:03Z).PR form: draft PR #20009 on
main, first lineFixes #19980,Clause-②: no; the only closing keyword in the body is that first line. Head1470ba822= the change commita0c50fb65+ a merge oforigin/main1f05ea4fbthat touches none of the three files (the maintainer's squash lands one commit). Labelsdocumentation·size/xs·skip-changeset(the dev's own write landed).Scope: +3/−3 over 3 files, all inside the amended surface; the unlock-chain clause 「解锁产品 P0/P1 的仪器卡沿链继承其优先级」 byte-identical; :45 111 bytes, :64 87 bytes, both ≤ 120;
docs/NORTH-STAR.mduntouched outside item 3's first clause. Reader sweep on the head:产品仓0 hits across the swept roots (3 on base), controls沿链继承2 / 2 and「优先级」4 / 4 unchanged; sibling repos 0 relevant hits.skip-changesetcorrect (nothing shipped).Rule text against the ruling: 「当前车道队列中如果已经没有 p0 p1,就应该可以派其他卡」 → NORTH-STAR item 3 「本车道队列还有开放的 P0/P1 时,该车道不派 p2/p3 的工具卡、契约卫生卡;…」; the execution-side precondition 「本车道队列开放 P0/P1 每次取卡现读」; the triage-side predicate 「所入车道队列 P0/P1 开着时,…」 (triage has no lane of its own, so 「所入」 — the lane the card is routed into). The two open points are ⛔ not encoded in the text; they stand as proposals under 你要做的 ① ②, with ③ flagging the triage line as a one-line revert if the maintainer wants the dispatch side only. As dispatched.
Open questions — this seat's answers (recorded here; the maintainer's word on the PR overrides): (i) 「本车道」 → A (the open cards carrying that
domain:*label in the repo the dispatching seat works; seats of one lane share that queue; a cross-repo seat reads its own repo's same-named lane) — the ruling came from exactly the coupling B would recreate; (ii) 「队列」 → A (only cards the lane can take now: open,pm:queue, unassigned; in-flight, blocked, on-hold and decision-box P0/P1 do not count — the unlock chain already carries a blocked P0/P1's priority); (iii) triage line → A, keep (under B triage would close on first touch the very cards the ruling makes dispatchable; the triage grade on this card already read it lane-scoped).Tests: rule text only; the report carries the derived gate union at
1470ba822(19 derived families, 19 run, 0 NOT-MEASURED; ratchet 183 / 183 and 120 / 120; id-lint 34 clean; frame-sync, doc-authoring, governed-prose, nul-bytes, skills-token-ratchet green;check-governed-merges --testexit 3 = the GOVERNED reading, Tier H;doc-formula-expressionsexit 3 first (unbuilt prerequisite) then 0 after the lock-guarded build).check-governed-merges --pr 20009from this seat: GOVERNED, Tier H (docs/NORTH-STAR.md ×1,.claude/** ×2), +3/−3. CI on the head at this ACCEPT: 16 success + 10 rostered skips, 3 in progress — the maintainer's merge reads it green at merge time; this seat lands only after an authorized APPROVED review, through the usual pre-landing checks.Deviations (four): the surface expansion — accepted and amended above; the pre-PR merge of
origin/main— accepted (disjoint, the union re-run at the merge head);pnpm check:pm-half-statesderived from the third path and run (exit 0) — noted; attribution per AGENTS.md — as required.Four-piece terminal from here: ②
needs-user-decisionon the PR + the final 「维护者速读」 comment (this seat's, from its own reading of the diff); ③ review requests toos-zhuangandhotlongon the draft PR; ④ the round report lists PR #20009 as awaiting a human merge. Landing after approval: pre-landing checks, clear the label, ready, auto-merge — or the maintainer's direct merge is itself the record.Four axes, one line each: business need — measured (a lane idled on p2 work with zero P0/P1 in its own queue while the repo held 4 P0 / 34 P1); long-term — the rule reads the unit the seat already reads at every take, no new part; AI-error — the three readers now say the same thing, so no seat or triage fire can close or hold what another dispatches; startup scope — three sentences, no gate, no tool.
Generated by Claude Code
objectstack-fleet commented
on Sep 24, 2026 ContributorAuthorMore actions收单注记 (holdover note) — the
domain:skills#1seatsession_01A22sUB3mUWs6M36VgfijBqsigns off at 2026-09-24T23:09Z on the maintainer's word 「你直接下班吧。」 with this card's PR #20009 approved by the maintainer (review 5311203607, 22:58Z), flipped ready and armed with auto-merge by them, and in the merge queue since 23:00:19Z (head1470ba822). The landing is the maintainer's; nothing is owed on it before MERGED.What is left, for the next seat or the half-state patrol (watcher = the next
domain:skillsseat):- On MERGED: the card closes by
Fixeson its own; thennode scripts/pm/label-write.mjs --issue 19980 --repo objectstack-ai/objectstack --remove pm:dispatched --unassign os-zhuang(the patrol'ssweep-closed-cards.mjs --writestrips thepm:*residue from a closed card on its own; the assignee needs the hand). Checkouts that readdocs/NORTH-STAR.md,execution-duties.mdortriage-duties.mdfast-forward. - If the queue ejects it:
merge-queue-triageposts the signature; handle it perlanding-operations.md:29–:34 — the maintainer's approval stays valid across a re-push (SKILL.md 〈路径分叉〉 「批准后再推亦不过期」). - The two open points (①「本车道」 for multi-seat / cross-repo lanes, ②「队列」 = takeable cards only) were proposed as A / A on the PR and not contradicted by the approval; read them as in force until the maintainer says otherwise.
Review judgement stays with the record: ACCEPT 5819456530 on this card, the final 「维护者速读」 5819470664 on the PR. ⛔ Nothing here is outsourced review.
Generated by Claude Code
- On MERGED: the card closes by
- added a commit that references this issue
on Sep 28, 2026
Filed by the
domain:spec@ objectui execution seat (sessionsession_01877XiBYSaRCk2CU7cMSg3S) at 2026-09-24T14:08Z, on the maintainer's instruction. ⛔ Not graded or routed; that is triage's job. The maintainer named the card class: "skills".Maintainer ruling (verbatim, from this seat's session, 2026-09-24T14:08Z)
(English: "If the current lane's queue has no p0/p1 left, other cards should be dispatchable. This should be filed as a skills card.")
What the text says today
docs/NORTH-STAR.md「优先级」 item 3 (line 114 onorigin/main): 「产品仓还有开放的 P0/P1 时,任何车道不派 p2/p3 的工具卡、契约卫生卡;解锁产品 P0/P1 的仪器卡沿链继承其优先级。」.claude/skills/pm-dispatch/references/execution-duties.md:45: 「取卡前置 =docs/NORTH-STAR.md「优先级」第 3 条:产品仓开放 P0/P1 每次取卡现读。」⇒ The gate reads repo-wide open P0/P1, across objectstack and objectui. At this reading, objectstack has 4 P0 / 34 P1 and objectui 0 P0 / 6 P1, while the
domain:spec@ objectui lane queue holds zero P0/P1. So the lane sat idle on p2 work that no P0/P1 in its own queue was competing with. That is the situation the ruling corrects.Asked change
Make the gate's reading lane-scoped: a lane may dispatch its p2/p3 tooling and contract-hygiene cards when its own queue has no open P0/P1. The unlock-chain inheritance clause stays as is. Surfaces to edit, all governed:
docs/NORTH-STAR.md「优先级」 item 3: the rule itself;.claude/skills/pm-dispatch/references/execution-duties.md:45: the take-card precondition that reads it;产品仓开放 P0/P1/产品仓还有开放的 P0/P1across.claude/**,skills/**anddocs/**; the seat's scan found only these two.docs/NORTH-STAR.mdis Tier H: the PR needs the maintainer's approval to land..claude/**is Tier S.Open points for triage and the implementer, not re-ruled here
domain:X#N), and for cross-repo lanes such asdomain:spec @ objectui: the ruling says 「当前车道队列」 (the current lane's queue).pm:blocked/pm:on-holdP0/P1 cards count as "in the queue".In effect now
The ruling applies from the moment it was given, per SKILL.md 优先级 「维护者裁决 > 北极星」. The
domain:spec@ objectui seat is dispatching under it now, with this card as the carrier.Dedupe: issues updated since 2026-09-01 (open and closed), 200 scanned, title and body matching
P0/P1 | rule 3 | 北极星门 | North-Star gatetogether withlane | gatein the title: 0.Generated by Claude Code