Skip to content

Cut the model-read ecosystem specifics from user-interface, starting with its framework pages, their concerns index and tests #16753

Description

@kyle-sexton

Parent

Refs #15703
Source: #15730 (blind classification under rules revision 5, #15730 comment 6950077480), cut item 4 of 47 in its filing order.

Depends on

Blocks #15732 (the portability gate widens only after every cut lands).

Outcome

user-interface ships no model-read tool, library or command choice outside ADR 0101's named exceptions: the 12 rows below are cut (R11 10, R4 2).

#15730's filing order names this cut ahead of the rest: "user-interface's framework pages with their concerns index and its tests".

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): 12 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
D25 R4 K3 plugins/user-interface/reference/defaults.yaml:227-231 components.primitives_default: base-ui (defaults.yaml) picks the primitives library a React project builds on when it has none; R3 does not hold, because React appears in the design skill's description only as a trigger example under "in any stack".
F0495 R4 K5 plugins/user-interface/reference/component-libraries.md:52-79 component-libraries.md "Accessible primitives for React" maps the components.primitives_default setting (bundled base-ui in defaults.yaml) to the library the consumer installs, so the table serves a bundled default that picks a library. Two readings (other: R11, R3). Reader's note: React rows (F0495, F0498-F0502): the design skill's description contains the trigger "'build the checkout page in React'" under "in any stack". I read a trigger example as not naming a target, so these rows are not R3. If it does name one, F0498 (React-only) becomes R3, and so may F0495's React table. F0499-F0502 mix in Next.js and Tailwind content, so they would stay R11. Reader's note: F0495: the row is K5 URLs, so R11 is one other reading, and R3 is another if the React trigger in the design description counts as naming a target. R4 was chosen because the table is how the bundled primitives_default: base-ui picks a library.
F0496 R11 K4 plugins/user-interface/reference/types/web/typography/tailwind.md:1-112 types/web/typography/tailwind.md is a model-read Tailwind guidance page; no user-interface skill description names Tailwind, so R3 does not hold.
F0497 R11 K4 plugins/user-interface/reference/types/web/color/tailwind.md:1-58 types/web/color/tailwind.md is a model-read Tailwind @theme/oklch guidance page; Tailwind is not a target any user-interface skill description names.
F0498 R11 K4 plugins/user-interface/reference/types/web/component-api/implementation.md:1-250 types/web/component-api/implementation.md is model-read React implementation guidance (createContext, JSX); React appears only as an example in the design description, not as a named scope. Two readings (other: R3). Reader's note: React rows (F0495, F0498-F0502): the design skill's description contains the trigger "'build the checkout page in React'" under "in any stack". I read a trigger example as not naming a target, so these rows are not R3. If it does name one, F0498 (React-only) becomes R3, and so may F0495's React table. F0499-F0502 mix in Next.js and Tailwind content, so they would stay R11.
F0499 R11 K4 plugins/user-interface/reference/types/web/performance.md:17-18,38-101,231-297,338-397 types/web/performance.md still carries model-read Next.js/React guidance (next/image, next/dynamic, TanStack Virtual) that no earlier rule holds. Two readings (other: R3). Reader's note: React rows (F0495, F0498-F0502): the design skill's description contains the trigger "'build the checkout page in React'" under "in any stack". I read a trigger example as not naming a target, so these rows are not R3. If it does name one, F0498 (React-only) becomes R3, and so may F0495's React table. F0499-F0502 mix in Next.js and Tailwind content, so they would stay R11.
F0500 R11 K4 plugins/user-interface/reference/types/web/states.md:9-10,110-204 types/web/states.md still carries model-read Next.js/React/React Query guidance (not-found/error conventions, useOptimistic, onMutate rollback). Two readings (other: R3). Reader's note: React rows (F0495, F0498-F0502): the design skill's description contains the trigger "'build the checkout page in React'" under "in any stack". I read a trigger example as not naming a target, so these rows are not R3. If it does name one, F0498 (React-only) becomes R3, and so may F0495's React table. F0499-F0502 mix in Next.js and Tailwind content, so they would stay R11.
F0501 R11 K4 plugins/user-interface/reference/types/web/theming.md:78-125,256-276,328-349 types/web/theming.md still carries model-read Next.js viewport themeColor and next-themes ThemeProvider guidance. Two readings (other: R3). Reader's note: React rows (F0495, F0498-F0502): the design skill's description contains the trigger "'build the checkout page in React'" under "in any stack". I read a trigger example as not naming a target, so these rows are not R3. If it does name one, F0498 (React-only) becomes R3, and so may F0495's React table. F0499-F0502 mix in Next.js and Tailwind content, so they would stay R11.
F0502 R11 K4 plugins/user-interface/reference/types/web/accessibility.md:15,86,189-197,253 types/web/accessibility.md still carries model-read React guidance (the inert prop and its React 19.0.0 pointer, lines 186-197) and Tailwind outline-none and order-* in its hunt lists, and no earlier rule holds that content. Two readings (other: R3). Reader's note: React rows (F0495, F0498-F0502): the design skill's description contains the trigger "'build the checkout page in React'" under "in any stack". I read a trigger example as not naming a target, so these rows are not R3. If it does name one, F0498 (React-only) becomes R3, and so may F0495's React table. F0499-F0502 mix in Next.js and Tailwind content, so they would stay R11.
F0503 R11 K4 plugins/user-interface/reference/types/touch-web.md:200-207,292 types/touch-web.md:200 gives model-read Tailwind pointer-fine: guidance, and :292 hunts the Next.js viewport export.
F0504 R11 K7 plugins/user-interface/reference/animation/{catalog,behaviors,performance,gestures}.md animation/catalog, behaviors and performance use Motion AnimatePresence/MotionConfig and Tailwind transition-all as K7 examples of neutral motion rules.
F0505 R11 K4 plugins/user-interface/skills/audit/reference/launch-scope.md:72-74,88,150,192,375,458-464 audit/reference/launch-scope.md is a model-read hunt list naming Next.js, next-themes, Leva, ReactQueryDevtools and similar framework devtools, which is quality guidance, not a security floor.

Kept rows, not touched here (count per rule): R3 5, R9 1.

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.
  • R4 rows: the bundled default goes; the choice is resolved from the consumer through the ecosystem-resolution contract (docs/contracts/ecosystem-resolution/). A shipped default that picks a library goes with this cut.
  • Fence ratchet: lower the skill-stack-fences ceiling in .performance/ratchets.json for each of these files whose fences the cut removes: plugins/user-interface/skills/audit/reference/launch-scope.md.
  • References outside the plugin: these files on main name a cut file; update or remove each entry the cut makes stale: plugins/user-interface/reference/defaults.yaml in .github/actions/resolve-config/action.yml, .github/actions/resolve-config/models.test.mjs, .github/actions/resolve-config/resolve-config.mjs, .github/actions/resolve-config/resolve.mjs, .github/scripts/pr-merge/merge-holds.test.mjs; plugins/user-interface/skills/audit/reference/launch-scope.md in .performance/ratchets.json, scripts/docs-anchor-baseline.txt.
  • Open the pull request with Closes this issue in its body, then stop: the lane adds no label. A sweep adds do-not-merge and 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-merge to 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 opus and sonnet aliases, three runs per side, plus control sides on one model)"): one before-and-after case, on sonnet at 3 runs a side; opus runs 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 3 and a --max-cost-usd ceiling, 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 opus confirm; 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" and do-not-merge out 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) removes do-not-merge once 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.
    • R4 (consumer default): the value picks a tool or library for the consumer. Goes: no bundled default survives (ADR 0101 decision 2, "Ship no bundled default"); the choice is resolved from the consumer.

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): user-interface ships no model-read tool, library or command choice outside the named exceptions; each listed R11 and R4 row is cut.
  • The pull request body states the row count (12) 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

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 17, 2026
  2. added theissue type on Nov 17, 2026
  3. updated Priority medium and Work status ready on Nov 17, 2026
  4. melodic-automation-lanes commented on Nov 17, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"9da384b107f293a7b905d8032c356fafd9d1518807e81113cdb72a7b779be577","body_sha256":"b485d136bc9854baa41124789baee7697299fd0b6b5199c6f47fa416bf14abfc"}

  5. github-actions commented on Nov 17, 2026

    @github-actions
    Contributor
    No description provided.
  6. added
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 17, 2026
  7. melodic-automation-lanes commented on Nov 17, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue lane stopped on this issue (host-only): the run reports the work needs a host run the lane cannot make.
    It added host-run and set Work status to confirmed: an agent run on a host builds it, and it waits on no decision from a person.

    In the run's words:

    host-only: this cut needs claude plugin eval runs that this lane cannot make. The issue says to write and freeze the content-dependent eval cases, then reproduce them on the before version, before any edit. It also needs one before-and-after targeted case on sonnet (3 runs a side) for each changed skill, a sensitivity-control result for each whole-page deletion (tailwind.md x2, component-api/implementation.md) and a detection-control result for each partial cut, all in the PR body (AC7 and the targeted-case done-when item). ADR 0101 decision 5 and plugin-eval's Detection control section say a cut ships only with that evidence. Bash in this lane runs only the named wrappers, and none of them runs plugin eval. The PR-label eval workflow (pr-run-plugin-evals.yml) compares the plugin loaded against not loaded, so it cannot produce a two-version compare or a control. Nothing was edited, because the issue says to freeze and reproduce the cases first.

    What the run says it did not do:

    • Freezing the content-dependent eval cases and reproducing them on the before version. This needs claude plugin eval on a host.
    • Cutting the 12 rows (D25, F0495-F0505) and updating the references outside the plugin (.github/actions/resolve-config/*, .github/scripts/pr-merge/merge-holds.test.mjs, .performance/ratchets.json, scripts/docs-anchor-baseline.txt). Not started, because the issue requires the cases to be frozen first.
    • Targeted-case verdicts for each changed skill, and the sensitivity and detection control results (AC7). These need host eval runs.
    • Script-reader searches for each R11 row. Not run, because the cut did not start.

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/44108822188

    To hand it back to the lane, remove host-run and set Work status to agent-ready again.

  8. removed
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 17, 2026
  9. melodic-automation-lanes commented on Nov 17, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue run that agent-ready started 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 added agent-ready back 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.

  10. github-actions commented on Nov 17, 2026

    @github-actions
    Contributor
    No description provided.
  11. github-actions commented on Nov 17, 2026

    @github-actions
    Contributor
    No description provided.
  12. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 44162742064, the work-resolve-issue run that agent-ready started, before it finished; that run ended at 2026-11-17T20:44:04Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits the same limits.stranded-backoff-hours kill-switch hours after each refused run before re-firing it, never longer.

  13. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor
    No description provided.
  14. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 44228517737, the work-resolve-issue run that agent-ready started, before it finished; that run ended at 2026-11-18T03:43:51Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits the same limits.stranded-backoff-hours kill-switch hours after each refused run before re-firing it, never longer.

  15. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor
    No description provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.

    Type

    Fields

    Work status

    needs-triage

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions