Repository navigation
Description
Part 1 of 5 of #16755. Refs #15703. Blocks #15732 through #16755.
Problem
testing:write and its context pages illustrate neutral naming, placement and isolation rules with .NET/xUnit, JS and C# examples, and give .NET-only framework traps, in a skill whose description names no language.
Rows (5: all R11)
| Row | Rule | Kind | Cited at (as of 5b66a7f) | Fact |
|---|---|---|---|---|
| F0421 | R11 | K7 | plugins/testing/skills/write/SKILL.md:94 |
.NET/xUnit naming forms |
| F0422 | R11 | K4 | plugins/testing/skills/write/SKILL.md:119 |
.NET framework-traps gotcha (MTP options, global.json, nesting) |
| F0423 | R11 | K7 | plugins/testing/skills/write/context/write.md:50,56-59,95,137-157 |
Aspire/docker-compose/tilt row, .NET/xUnit naming, JS hollow-out, C# database-read examples |
| F0425 | R11 | K7 | plugins/testing/skills/write/context/organize.md:13,53-54 |
{Project}.Tests "in .NET" and {ClassUnderTest}Tests |
| F0426 | R11 | K4 | plugins/testing/skills/write/context/organize.md:47-49 |
"Nested test projects (.NET)" guidance |
Files
- Cut:
plugins/testing/skills/write/SKILL.md,plugins/testing/skills/write/context/write.md,plugins/testing/skills/write/context/organize.md. - Outside references at d46efa9:
.performance/ratchets.json:197(write.md skill-stack-fences ceiling 1).
Rules this part follows (from #16755, rules revision 5)
- R11 (shipped knowledge): model-read K2, K3, K4, K5 or K7 text. 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.
- R4 (consumer default): the value picks a tool or library for the consumer. It goes: no bundled default survives (ADR 0101 decision 2, "Ship no bundled default"); the choice is resolved from the consumer through
docs/contracts/ecosystem-resolution/. - R8 (measured fact): cut it like the other rows and mark it in the pull request body as pending its targeted case; the host session's eval (below) decides whether it comes back, annotated
portability-ok: measured <case-id>. - 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). Bundled defaults that pick a tool, command or library are retired wherever they appear (Interview Q32, D4 of the Brief). - Line numbers below were read at
5b66a7faand may have moved; find each row by its cited text.
After the pull request opens (host session, not the lane)
The lane opens the pull request with Closes this issue and stops; it adds no label. The pull request stays held for the eval:
- Hold line: a sweep or host session adds
do-not-mergeand posts, from a listed human's account, a comment with<!-- pr-hold reason=eval -->on a line of its own. - Targeted case per changed skill: one before-and-after case on
sonnetat 3 runs a side,--case,--runs 3, a--max-cost-usdceiling;opusonly to confirm a sonnet loss; a new case gets a 1 to 3 run smoke first; start no batch after a usage-limit error (owner decision of 2026-11-16). - Controls: the owner's Q53 decision of 2026-11-17 (owner-decisions.md L202) reads: "each cut pull request is gated on a no-loss compare alone, with no wrong-text side". It supersedes Cut the model-read ecosystem specifics from testing #16755's Controls line and its AC7 sentence ("each partial cut carries a detection-control result"). A whole-page deletion still states its predicted outcome in the pull request body before the first batch, and the record says the case cannot detect wrong text.
- On a LOSS reading: a trace read of each dropped case and an
opusconfirm; only a loss traced to the changed text counts. - R8 rows: the row's targeted case with and without it; on a
case dropor a mean fall of 0.15 or more without it, restore the row annotatedportability-ok: measured <case-id>; a deterministic grader states before the run in how many of n runs it must fail. - Record: on a VALID no-loss run, post from a listed human's account
<!-- eval-pair verdict=no-loss validity=VALID head=<40-hex head SHA> -->naming the current head, with no "do not merge" text (docs/contracts/loop-lane/README.md, "Cross-lane PR hold"). pr-merge's "Release eval holds whose record matches the head" step (.github/scripts/pr-merge/release-eval-hold.mjs) then removesdo-not-merge; a later push needs a new record.
Out of scope
Rows outside this part's table, the parent's kept rows, every other plugin, toolchain's bundled defaults (#15733), and widening the portability gate (#15732).
Done when
- Every row in this part's table is cut or replaced at a routing site; a row whose cited text is already gone on
mainis listed as GONE. - The pull request body states this part's row count (5) and lists every row id with its rule and outcome.
- Each R11 row's script-reader search is quoted in the pull request body; a row whose file a script reads is not cut, and is listed in the pull request body under a
Script readersheading. - The pull request body names, for the write skill, the existing eval 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.
- The
skill-stack-fencesceiling forplugins/testing/skills/write/context/write.mdin.performance/ratchets.jsonis lowered if the cut removes its fence. - AC10: no new enforcement-placing skill is added.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Work status
needs-triage
Priority
medium
Activity
github-actions commentedon Nov 21, 2026
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: three testing:write skill files (SKILL.md, context/write.md, context/organize.md) and one ratchet ceiling in .performance/ratchets.json; read by the model when the write skill runs.
Reversible: yes; revert the pull request. Rows marked R8 can be restored with a portability-ok annotation if the eval shows a loss.
Open questions: none
Understood: cut or replace the five R11 rows (F0421, F0422, F0423, F0425, F0426) of .NET/JS/C#-specific text from the testing write skill and its context pages. The scope, rules and done-when are exact, and the eval gate runs after the pull request opens. This is part 1 of 5 of #16755. Related open issues cover other parts of the same cut, such as "Cut the model-read ecosystem specifics from testing: diagnose and plan"; they are siblings, not duplicates.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"305baab3a285ae5253e1145dedb7011e88e7785f77b168247d1a8f8dcce81fb8","body_sha256":"53189e22e6fe8a9aebd497f7b13abd5e2f100a30095bc7dbb4790aa720105970"}
github-actions commentedon Nov 21, 2026
github-actions commentedon Nov 21, 2026