Repository navigation
Description
Parent
Refs #15703
Source: #15730 (blind classification under rules revision 5, #15730 comment 6950077480), cut item 43 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.
Blocks #15732 (the portability gate widens only after every cut lands).
Outcome
playwright ships no model-read tool, library or command choice outside ADR 0101's named exceptions: the 1 rows below are cut (R11 1).
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): 1 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 |
|---|---|---|---|---|---|
| F0330 | R11 | K4 | plugins/playwright/skills/playwright/reference/e2e-orchestrator-recipe.md:1-96 |
e2e-orchestrator-recipe.md is model-read how-to for .NET Aspire, docker compose and tilt, which no plugin or skill description names, so tool branding does not cover it. |
Kept rows, not touched here (count per rule): R3 2, R6 1. 1 more rows were answered GONE (cited content no longer on main) and need nothing.
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.
- 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):
playwrightships 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 (1) 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
github-actions commentedon Nov 17, 2026
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the playwright plugin's e2e-orchestrator-recipe.md reference page, read by the model when the playwright skill runs; plus the pull request body evidence.
Reversible: yes; revert the page deletion or edit.
Open questions: none
I read this as a bounded cut of one row (F0330, R11): remove the model-read e2e orchestrator recipe page from
playwright, or replace it with generic text at a routing site. The pull request must carry the script-reader search, the sensitivity-control result, the targeted-case verdict and the row count of 1. The issue states its outcome and done-when exactly, and I found no open duplicate. The sibling per-plugin cut issues cover other plugins.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 17, 2026
{"v":1,"actor_id":337595936,"title_sha256":"a034dca8c0f794f3ad255db2a849d0a14f7ceb08ef52a06c3374620fdb0f9560","body_sha256":"ada813989c869c337e4a527865d7c87268865dc21f41a3c333b1a0e09553fdbd"}
1 remaining item
github-actions commentedon Nov 18, 2026
melodic-automation-lanes commentedon Nov 18, 2026
The work-resolve-issue run that
agent-readystarted failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.melodic-automation-lanes commentedon Nov 19, 2026
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44447638270, the work-resolve-issue run that
agent-readystarted, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-19T03:43:18Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or thekill-switchwait.github-actions commentedon Nov 19, 2026