Uh oh!
There was an error while loading. Please reload this page.
docs(pm-dispatch): extract incident case law into references/ — pure byte-identical move (#5925 item 7, #7341 PR B) - #7370
Merged
Conversation
…olicy, and 7 protocol batch items (#7341 PR A) Batch card #7341's protocol-text half, PR A of three: - #6644 L2: devs report at draft-PR time; the PM owns CI convergence, ready-flip and landing. Step-5 template clause + step-7 PM duty + os-dev.md Definition-of-done rewrite, with a per-card wait-for-CI override. - #7055: cleanup prescription drops --force — delete node_modules first, then unforced git worktree remove; a refusal means uncommitted work. - #7156: closed by the L2 clause (idle-poll prohibition at the role-file layer), with the measured cost cited in the reporting item. - Report-channel unification: every dev report also lands as an issue comment with the os-dev-report marker; the return message is an accelerator. Step-6 collection reads GitHub first, both modes. - Role-file precedence rule (unconditional clauses live in os-dev.md). - Triage classification comment gains an optional size/model suggestion line; executor may override with a stated reason. - Same-account scope-marking of shared-identity claim rituals. - [Decision] cards: every premise line carries its own re-check command. - Model tiering rewrite: floor sonnet, default opus, ceiling fable; mandatory claude-fable-5 for cards touching the PM skill; three maintainer rulings quoted verbatim as the authority block. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QrT21cGQfFVDWtVJysRtXo
…byte-identical move (#5925 item 7, #7341 PR B) Eight narrative blocks (9,941 bytes verbatim) leave the hot file for references/incidents.md and references/compile-surfaces.md; the main file keeps rule + one-line anchor + pointer at every cut point. SKILL.md: 3,098 -> 2,997 lines. incidents.md opens with the append-only note making it the default landing for future case law. Cut points re-derived from the post-PR-A file; every moved chunk verified byte-identical against the pre-move blob and absent from the post-move file (script-extracted, not retyped). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QrT21cGQfFVDWtVJysRtXo
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
…item 10) Maintainer ruling of 2026-08-10, quoted verbatim in the section: 「确认,M 及以上默认云卡,并进 #7341」. The 2026-08-07 heavy-card exception list becomes examples of the M+ class, not the trigger list; only S-grade mechanical cards stay mode:subagent. The three companion disciplines (subscribe on creation, issue-comment report authority, archive_session at terminal state) are named beside the new default. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QrT21cGQfFVDWtVJysRtXo
…341-pm-skill-batch-b
os-help
marked this pull request as ready for review
August 10, 2026 08:50
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Aug 10, 2026
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes#5925
Part of #7341
PR B of the three-PR #7341 batch. Stacked on PR A's branch (#7357) per the batch card's load-bearing ordering — the extraction's cut points are re-derived from the post-A file, so this diff shows A+B until A merges; the B-only commits are
c187173(the extraction) and merge724b810(propagating A's item-10 follow-up).What moved (pure move, byte-identical)
9,941 bytes of narrative moved verbatim into two new on-demand reference files; at every cut point the main file keeps the rule + a one-line anchor + a pointer naming the exact section:
references/incidents.md§定点文本两例实录domain:spec-toolinghistory — two superseded rulings + the 2026-08-09 refutation evidencereferences/compile-surfaces.mdreferences/incidents.mdopens with the append-only note: new case law lands there by default, existing entries are never rewritten, section titles are the pointer anchor texts — the main file's growth rate for narrative goes to zero (the #5925 ruling's stated intent).Numbers
724b810), the same pair reads 3,112 → 3,011 lines (236,095 → 227,397 bytes) — the extraction itself is unchanged; item 10 touches sections no chunk came fromincidents.md140 lines,compile-surfaces.md27 linesPurity discipline and its verification
Chunks were script-extracted, not retyped: an extraction script sliced each block out of the file by unique start/end anchors and wrote it to disk; the assembly script pasted those exact bytes into the reference files. A verification script then asserted, for every chunk: (1) contiguous byte-identical presence in the pre-move blob (PR A's HEAD), (2) contiguous presence in exactly one reference file, (3) absence from the post-move main file. 8/8 OK.
Kept-side adjustments (declared — these are the anchor/pointer lines, outside the moved bytes): each cut point's lead-in sentence had its dangling colon or "下表/见下" deixis re-pointed at the reference section; no moved byte was reworded. Two blocks were cut at sentence boundaries inside a paragraph (blocks 3 and 5), so the kept halves rejoin with a pointer sentence.
Deliberately NOT moved, per the "IF and only if the move can stay pure" condition: the Operational-notes bodies at large (rule and evidence interleave at sentence level — a pure move cannot separate them), and the step-5 two-blindness explainer (#6371/#6218), whose own governing sentence declares it the PM's step-7 review-question basis; moving it would have required rewriting that kept sentence's meaning, failing the pure-move test.
The line-count ratchet goes in PR C, not here: this PR is a pure move by discipline, and the ratchet is tooling + workflow wiring (C's class), which also lets the ceiling be set against the landed post-B count.
Maintainer authorization (verbatim, untranslated)
#5925 item 7's own approval (maintainer, 2026-08-06, recorded on #5925): 主文件留「规则 + 一行案例锚点」,只把长叙述案例抽到
references/incidents.md;纯搬移零改写;排在全部文本增补之后。The "单独成 PR" half was superseded by the 2026-08-10 batch directive above (recorded on #5925's claim-supersession comment); ordering-after-text-additions is honored via the A→B stack.Verification
node scripts/check-nul-bytes.mjs— OKpnpm check:skill-frame-sync— 4 copies isomorphic (the escalation frame stayed in main, untouched)pnpm check:skill-compatibility— 11 files reconciledpnpm check:agent-model-declared— os-dev.md → opus.claude/-only ⇒ no changeset;skip-changesetapplied.Generated by Claude Code