docs(pm-dispatch): give domain:spec-tooling its table row — contested paths split by the "orbits the spec contract" criterion (#5469) - #6959
Merged
Conversation
…切分 (#5469) 维护者 2026-08-09 裁决:domain:spec-tooling(程序卡 #5163、座位贴 #6018)已实际 流通而表上无行 —— 补行登记。无争议面 packages/spec/scripts/** 与 packages/spec/docs/** 直列;与 devx 相交的 packages/lint / scripts/ / content/docs/** 三面按「是否围着 spec 契约转」切分,devx 行加对应备注, 「spec 一分为二」节同步记录裁决(一包两席 → 一包三席)。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BPWqbmEFU8gJepBJTHESXd
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
…,会静默卡发版 (#4898 门禁路线 2) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BPWqbmEFU8gJepBJTHESXd
hotlong
marked this pull request as ready for review
August 9, 2026 06:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #5469 — this lands the half that PR #6886 explicitly escalated instead of implementing: the
domain:spec-tooling/domain:devxboundary. The maintainer ruled on 2026-08-09 (in session, relayed to #5469 in a comment): criterion split. The lane gets its row; the three contested paths are divided by whether the work orbits the spec contract.What changed
.claude/skills/pm-dispatch/SKILL.md, docs-only:domain:spec-toolingrow in the domain table, afterspec-surface:packages/spec/scripts/**,packages/spec/docs/**— pathsdevxnever claimed (seat card [PM seat] domain:spec-tooling — 🟢 在任 (session_01AZgRyPVwi1jLb1mNNuUQ9o) #6018).packages/lint,scripts/,content/docs/**) are criterion-split withdevx: contract gates / generators / lint rules / error prose / the references pipeline route tospec-tooling; general dev tooling staysdevx. Ruling cited inline (2026-08-09, 域标签词表有两个未入表条目:domain:spec-tooling(在用,文件面与 devx 完全重叠)与domain:ui(一例,与repo:objectui重复) #5469).domain:spec-tooling)—— 整包移交待接收 #5163/[PM seat] domain:spec-tooling — 🟢 在任 (session_01AZgRyPVwi1jLb1mNNuUQ9o) #6018: ⛔ neverpackages/spec/src/**/*.zod.ts, never the strictness ledger.devxrow gains the matching carve-out note pointing at thespec-toolingrow.specsplit" section: "one package, two seats" corrected to three seats (semantic / text / machine face), and the boundary bullet now records the ruling so the row has a traceable origin, same as every other split in that section.Why now
The lane has been real for days while the table had no row: seat card #6018 occupied through a handover (9 PRs landed in one term), program card #5163, triage still applying the label (#6945 on 2026-08-09), 10+ open issues, two in flight. A lane statistics pass requested by the maintainer surfaced the gap; the maintainer then ruled the boundary question that #6886 had escalated.
Coordination with in-flight PR #6886
#6886 (session
session_01F8q5J1MQyocgtNspb15fSn, branchclaude/issue-5469-domain-label-vocabulary) adds thedomain:*roster and deliberately left the table row out because the three paths were unruled. That premise is now resolved, not contradicted: this PR adds only the row + boundary text and does not touch the roster section, so overlap is at most an adjacent-hunk rebase. A comment on #5469 records the ruling for that session to pick up.Gates
check:skill-frame-sync✓ (4 copies isomorphic, 3 axes — this change touches neither the frame nor the published mirror, which stays deliberately generalized per #5451 route B),check:skill-compatibility-version✓. Releases nothing →skip-changesetlabel per the Check Changeset gate's route 2; the empty-frontmatter changeset initially included was removed after the gate correctly rejected it as a real (and stalling, #4898) input to changesets/action.Generated by Claude Code