Repository navigation
Description
Parent
Refs #15703
Source: #15730 (blind classification under rules revision 5, #15730 comment 6950077480), cut item 5 of 47 in its filing order.
Depends on
- none open. The route this cut follows is in place: Add the ecosystem-resolution contract, its decision record and the review rule #15706 (ecosystem-resolution contract and review rule), Add the whole-page sensitivity-control clause to the four cut-proof rules #15707 (sensitivity-control clause), Cut the per-language property pages from testing:write as the pilot #15709 (the pilot cut), all closed.
- Add a language-neutral rule to the type-discipline contract for values that share a primitive #15840 (closed): the type-discipline contract already carries the language-neutral rule the TypeScript page held.
Blocks #15732 (the portability gate widens only after every cut lands).
Outcome
planning ships no model-read tool, library or command choice outside ADR 0101's named exceptions: the 6 rows below are cut (R11 6).
#15730's filing order names this cut ahead of the rest: "planning's TypeScript idioms page with the type-discipline contract's sentence".
Demo: on main after the merge, each listed row's cited text is gone or replaced by generic text at a routing site, and the pull request body lists every row id with what happened to it.
Row count (bulk-mutation standard): 6 rows. The pull request states this number and lists each row.
Rows to cut
Paths are repository-relative; line numbers are as read at 5b66a7fa and may have moved. Kind is the inventory kind (K2 detection table, K3 bundled value, K4 tool guidance, K5 tool pointer, K7 example).
| Row | Rule | Kind | Cited at | Fact the classifier matched | Notes |
|---|---|---|---|---|---|
| F0317 | R11 | K2 | plugins/planning/skills/design/SKILL.md:214-221 |
design SKILL.md:214-221 is a model-read detection table that loads the TypeScript idioms file when it finds tsconfig.json or .ts files (K2). |
|
| F0318 | R11 | K4 | plugins/planning/skills/design/reference/type-discipline/typescript.md:1-132 |
type-discipline/typescript.md is a model-read guidance page of TypeScript idioms (K4), and the design skill's description does not declare TypeScript as its scope. | |
| F0319 | R11 | K7 | plugins/planning/skills/design/SKILL.md:336-342 |
design SKILL.md:349 gives raise NotImplementedError in Python and todo!() in Rust as examples of a not-implemented stub body (K7). |
|
| F0320 | R11 | K7 | plugins/planning/reference/standards-contract.md:54-66, 82 |
standards-contract.md shows the language-neutral index format with an example csharp row and suggests csharp/python/markdown surface ids, which are example content (K7). |
Two readings (other: R6). Reader's note: F0320: R6 is also possible, since the subject is this marketplace's standards-index contract. The ecosystem content is only the example row and suggested ids, so I chose R11. |
| F0321 | R11 | K7 | plugins/planning/skills/interview/context/assumption-sweep.md:91; plugins/planning/skills/interview/templates/checklist.md:75 |
assumption-sweep.md:91 and checklist.md:75 use package.json:14 "bullmq" as an example of a codebase-answered item (K7). |
|
| F0322 | R11 | K7 | plugins/planning/skills/interview/context/loop.md:223 |
loop.md:223 uses "assume Postgres for now" to illustrate a defer-with-assumption answer (K7). |
Kept rows, not touched here (count per rule): none.
Steps
- List every item with its rule: the pull request body repeats the table above with each row's outcome (cut, replaced at a routing site, or kept with its reason).
- Back every R11 call with a search showing whether a script reads the file, for example
git grep -n -F '<file name>' -- plugins scripts .github, quoted in the pull request body. A row whose file a script reads is not cut here: report it on Classify the remaining guidance rows blind and count the cuts per plugin #15730. - Name the cases that read the cut text: in the pull request body, name for each changed skill the existing eval case whose run reads the cut text, or say that none does. The lane names them; it runs none.
- Whole page or part: in the pull request body, say for each changed file whether the cut deletes the whole page or part of it.
- Synced copies:
plugins/planning/reference/standards-contract.mdcarry aGENERATED fromheader. Cut the canonical file and regenerate with the shared-copies sync; the cut reaches every carrier. - Fence ratchet: lower the
skill-stack-fencesceiling in.performance/ratchets.jsonfor each of these files whose fences the cut removes:plugins/planning/skills/design/reference/type-discipline/typescript.md. - References outside the plugin: these files on
mainname a cut file; update or remove each entry the cut makes stale:plugins/planning/skills/design/SKILL.mdinscripts/docs-anchor-baseline.txt,scripts/test_check_next_graph.py;plugins/planning/skills/design/reference/type-discipline/typescript.mdin.performance/ratchets.json,scripts/docs-anchor-baseline.txt;plugins/planning/reference/standards-contract.mdinscripts/affected-tests-live.sh,scripts/check-standards-contract-bump.test.sh,scripts/cross-plugin-source-registry.txt,scripts/shared-copies.txt,scripts/test_check_vocabulary.py. - Open the pull request with
Closesthis issue in its body, then stop: the lane adds no label. A sweep addsdo-not-mergeand the hold line when the pull request opens; the evidence below is a host session's work.
After the pull request opens (host session, not the lane)
The lane opens the pull request and stops there. The pull request stays held with do-not-merge for the eval; a host session runs only the eval and posts its record on the pull request; the merge lane releases the hold when the record matches the head; this issue closes with the pull request.
- Hold line: the hub's sweep (or a host session) adds
do-not-mergeto the pull request and posts, from a listed human's account, a comment with the line<!-- pr-hold reason=eval -->on a line of its own. - Targeted case per changed skill (this replaces Classify the remaining guidance rows blind and count the cuts per plugin #15730's "no more than 400 runs per plugin (the changed skills' cases on the
opusandsonnetaliases, three runs per side, plus control sides on one model)"): one before-and-after case, onsonnetat 3 runs a side;opusruns only to confirm a sonnet loss; a new case gets a 1 to 3 run smoke first (owner decision of 2026-11-16 in the owner-decisions record, superseding the run counts in #15703 comment 6906800940). Select cases with--case, use--runs 3and a--max-cost-usdceiling, and start no batch after a usage-limit error. - Controls: each whole-page deletion carries a sensitivity-control result, its predicted outcome written in the pull request body before the first batch; each partial cut carries a detection-control result. No paired no-loss compare per cut (#15703 comment 6906800940).
- On a LOSS reading: a trace read of each dropped case and an
opusconfirm; only a loss traced to the changed text counts (#16672 comment 6935228111). - Record: the verdict and the control result go into the pull request body. When the run is VALID and shows no loss, the host session posts, from a listed human's account, a comment with the line
<!-- eval-pair verdict=no-loss validity=VALID head=<40-hex head SHA> -->naming the pull request's current head, and keeps "do not merge" anddo-not-mergeout of that comment (docs/contracts/loop-lane/README.md, "Cross-lane PR hold"). A loss or a run that is not VALID leaves the hold in place; say so on the pull request. - Release: pr-merge's scheduled step "Release eval holds whose record matches the head" (
.github/scripts/pr-merge/release-eval-hold.mjs) removesdo-not-mergeonce that record is the newest since the label went on and names the current head, and no other hold stands. A push after the record needs a new record. - AC7 is met here: each whole-page deletion carries a sensitivity-control result and each partial cut a detection-control result, in the pull request body.
Decisions
- D3: each plugin's cut is its own topic and pull request.
- Interview Q32 (D4 of the Brief): bundled defaults that pick a tool, command or library are retired wherever they appear.
- AC1's named exceptions are the kept classes of ADR 0101 (
docs/adr/0101-resolve-ecosystem-specifics-from-the-consumer-repository.md, Decision and the 2026-11-17 amendment). - Bulk-mutation standard: count first, then act; the pull request states its row count.
- The rules this item's rows fall under (rules revision 5):
- R11 (shipped knowledge): everything else that is model-read K2, K3, K4, K5 or K7. Goes through the cutting route: the generic text replaces it only at a routing site where the skill still takes a language-specific step; anywhere else it is deleted with no replacement. An item kept only because a removed item consumes it goes in the same pull request.
Key interfaces
- "The consumer's ecosystem (language, framework, tools): abstract now. Seam: the ecosystem-resolution contract and the consumer's own records."
- Conventions followed: a cut ships with eval evidence (the skills-and-agents review rules).
Done when
- AC1 (this plugin's share):
planningships no model-read tool, library or command choice outside the named exceptions; each listed R11 row is cut. - The pull request body states the row count (6) and lists every row id with its rule and outcome.
- Each R11 row's script-reader search is quoted in the pull request body.
- The pull request body names, for each changed skill, the existing case that reads the cut text, or says none does.
- The pull request body says, for each changed file, whether the cut deletes the whole page or part of it.
- AC10: no new enforcement-placing skill is added here.
Out of scope
- Kept rows of this plugin, and every other plugin's rows.
- Toolchain's bundled defaults (Delete toolchain's bundled ecosystem defaults #15733).
- Widening the portability gate (Annotate surviving specifics and widen the portability gate #15732).
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Priority
Activity
melodic-automation-lanes commentedon Nov 17, 2026
{"v":1,"actor_id":337595936,"title_sha256":"ce0cdd260fc853236c811199fc270d575669e64692da341c21c4c583f0d58e2e","body_sha256":"1f70f9eb983c90aa0a87f61cbef64238a1d1607122c37293c0037589b5e8eea5"}
github-actions commentedon Nov 17, 2026
kyle-sexton commentedon Nov 18, 2026
Delivered by #16810, merged 2026-11-18 (commit e315096). The cut record and the eval result, including the measured loss the owner accepted (decision Q61, option A, quoted on that pull request), are in its body and comments. Closing by hand because that pull request linked this issue with
Refs:.