Skip to content

Classify the remaining guidance rows blind and count the cuts per plugin #15730

Closed

Description

@kyle-sexton

Parent

Refs #15703
Source: PLAN Phase 14 (first work item), topic ecosystem-specifics

Depends on

Outcome

The classification rules for model-read ecosystem specifics are shown to decide the same way for two independent readers, the rows to cut are counted per plugin, and one cut item per plugin is filed in the planned order.

Demo: the classification record on this item shows zero split rules (or the owner's ruling on each), and the per-plugin cut items exist under the container with their row counts.

Steps:

  • Blind classification: two fresh agents each classify a stratified sample of about 50 inventory rows (at least 5 per kind) under the design's classification rules R1 to R11, without seeing the other's answers.
  • A rule is split when they disagree on any sampled row that either placed under it. Reword a split rule and re-classify the disagreeing rows plus ten fresh rows, at most three rounds. A rule still split after three rounds goes to the owner; label this item needs-human at that point.
  • Count the rows to cut per plugin and state the number on this item.
  • File one cut item per plugin under the container, in this order: the discovery explore fallback table; the review ecosystem-specialist agent's generic defaults; mutation-testing's per-tool tables; user-interface's framework pages with their concerns index and its tests; planning's TypeScript idioms page with the type-discipline contract's sentence; then every other plugin with rows under rule R11, the plugin with the most rows first. A shipped default that picks a library goes with its plugin's cut.
  • Each cut item says: list every item with its rule; back every R5 or R11 call with a search showing whether a script reads the file; freeze content-dependent cases first; carry the sensitivity-control result for each whole-page deletion and the detection-control result for each partial cut; run 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).
  • Each cut item blocks the gate-widening item; add those edges when filing.

Decisions

  • Q27: a classification rule is split when the two blind classifiers disagree on any sampled row that either placed under it; at most three rounds of rewording, then the owner decides.
  • Q28: the remaining cuts go in the design's named order, then by plugin with the most rows to cut first.
  • 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.
  • Bulk-mutation standard: count first, then act; each pull request states its row count.

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

  • The classification record shows zero split rules, or names the owner's ruling on each.
  • The per-plugin row counts are stated on this item.
  • One cut item per plugin exists under the container, each blocking the gate-widening item, and their number is stated before filing.
  • AC1 and AC7 are carried into each cut item's Done when (no generic skill ships a model-read tool, library or command choice outside the named exceptions; each whole-page deletion carries a sensitivity-control result and each partial cut a detection-control result).
  • AC10: no new enforcement-placing skill is added here.

Out of scope

  • Cutting any guidance (the per-plugin items do that).
  • Widening the portability gate.

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 12, 2026
  2. added theissue type on Nov 12, 2026
  3. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Large
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none
    Blast radius: tracker records only (a classification record, per-plugin row counts, new cut items under #15703); no guidance is cut here.
    Reversible: yes; the counts and filed items can be edited or closed.
    Open questions: none
    Decision recorded by the latest owner comment:

    Decision recorded. The owner answered both round-4 questions on 2026-11-17, typed in a session: "go w/ recommendations" to each, with the options restated in full.

    • R3: content written for one target or language that the skill's description names is declared scope, judged per row: a row that serves only such a named target stays under R3.
    • R6: "a value one of its scripts emits" covers only a value a script writes into output the model reads. An id a script merely validates against, or names in a deprecation notice, is not covered; ladder rung ids and coverage claims fall under R7.
      [quote truncated; the full decision is at the link]
      Classify the remaining guidance rows blind and count the cuts per plugin #15730 (comment)

    That decision settles the round-4 open questions. The remaining steps (full pass over the refreshed rows, per-plugin counts, filing cut items) are host work already routed via host-run. No other open issue or merged PR duplicates this request.

    Automated triage. A maintainer reviews it.

  4. melodic-automation-lanes commented on Nov 14, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  5. melodic-automation-lanes commented on Nov 15, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"9d79b74de8166e30535bbccff3f3fc28f2e061133b75b36cc237ef795d7c3808","body_sha256":"9828144936142295b079e265a2acb47574f048184c5eeae6c50ed72b8b726179"}

  6. github-actions commented on Nov 15, 2026

    @github-actions
    Contributor
    No description provided.
  7. added
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 15, 2026
  8. melodic-automation-lanes commented on Nov 15, 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: every done-when item of #15730 is tracker work this lane cannot do, and the inputs are not in the checkout. It asks for (a) two blind classifications of about 50 inventory rows under the design's rules R1 to R11, but neither the design nor the inventory is in the repository (no file names R1 to R11 for ecosystem specifics, and git history has nothing for #15703); (b) the per-plugin row counts stated on the issue; (c) one cut item per plugin filed under container #15703, each blocking the gate-widening item; and (d) a needs-human label if a rule stays split after three rounds. This lane only writes a patch and has no tracker write, and the issue's Out of scope bars cutting guidance, so there is nothing to commit. Run it from an attended or tracker-capable session with the #15703 design and inventory to hand.

    What the run says it did not do:

    • Blind classification by two fresh agents of about 50 inventory rows under R1 to R11: the design and inventory are not in the checkout
    • Per-plugin row counts stated on #15730: needs the classification, and this lane cannot comment on the issue
    • Filing one cut item per plugin under #15703, each blocking the gate-widening item: this lane has no tracker write
    • Tidy, review, verify: skipped because no file changed

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

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

  9. 2 remaining items

  10. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Nov 16, 2026
  11. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

    Addendum to the record: R6 and R7 agree only on a shared non-literal reading. Both round 1 readers reported, independently, that the rule order read literally lets R6 (mechanism record) match every model-read contract id first, so R7 (contract value) would never apply. Each then placed those rows under R7 anyway, with R6 as runner-up, which is why the comparison shows no split there. A reader who follows first-match exactly would place them under R6. The dispositions differ (R6 keeps one copy; R7 renames ids that name a tool for a mechanism class), so this is not a label-only question. R6 and R7 were not reworded in rounds 2 and 3. Those rounds' fresh rows held one model-read contract id (reserve row V13, round 3), and both readers placed it under R3, an earlier rule, so the R6 against R7 order was not tested again.

    For the owner, with the R3 question above: state in R6 that an ecosystem-specific id other skills or config write or match is judged by R7, not R6 (recommended; it is the reading both readers chose), or keep first-match as written and drop R7's model-read case.

  12. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded.

    Owner, 2026-11-16, asked whether a skill that lists the tools or formats it supports in its description thereby puts its model-read guidance for those tools in declared scope (rule R3), with the recommendation "no": "go w/ recommendations" (said in the hub session, relayed to this one).

    • R3 as decided: a description that lists supported tools or formats does not make that skill's model-read guidance declared scope. Declared scope needs a capability that cannot exist without the set (a tool-branded plugin, an artifact for one platform, a reader that is the product). Guidance for tools a general capability supports is judged by the later rules.
    • What this undoes: the round 2 rewording of R3. The 100 rows classified under it are not used. R3 needs a wording that states the decision, and one more blind round on rows that test it, before the full pass restarts.
    • Still with the owner: which exception set AC1 means (ADR 0101's four classes, or the design's R6, R8 and R10 as well), what the per-plugin count covers, and the R6 against R7 order in the addendum above. This issue keeps needs-human until those are answered.
  13. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded (AC1 exception set), with what stays open.

    Read against the texts in a fresh context, then each cited line re-read:

    • "Named exceptions" in AC1 means the four kept classes of ADR 0101 ("The named exceptions are the last four classes", docs/adr/0101-resolve-ecosystem-specifics-from-the-consumer-repository.md:49).
    • Both texts limit the cut to a choice. AC1: "no generic skill ships a model-read tool, library or command choice". ADR 0101:43 defines the cut class as "text a model reads to choose what to run, recommend or build".
    • R10 (illustration) stays, outside AC1. Its own test is that it "does not sit in a step that selects a tool", so it is not a choice.
    • R6 (mechanism record), first two clauses, stays, outside AC1. A file, key, rule id, script or behavior of this marketplace, and the upstream source of a kept script, are not a choice made for the consumer.
    • These rows fit none of the five classes, while ADR 0101:38-39 says each named tool "is one of these". That is the ADR revisit trigger at line 96 ("A class of shipped content that fits none of the five classes above"): the ADR is incomplete here, it does not order these rows cut. My earlier comment that such a row "is a review finding under the ADR as merged" was too wide and is withdrawn for R10 and these two R6 clauses.

    Not settled by the texts, left for the owner (needs-human stays):

    • R6, third clause ("how to install, run or read the output of a tool a kept adapter or kept default drives"): this is text about what to run, and a kept default has no class in the ADR ("Ship no bundled default", line 35).
    • R8 (measured fact): a measurement "that contradicts a reasonable default" exists to change what the model runs. One row in the current output carries it.

    For each: either the ADR gains a kept class for it, or the rule changes from stays to goes. The full pass does not restart until that, the count scope and the R6 against R7 order are answered.

  14. kyle-sexton commented on Nov 17, 2026

    @kyle-sexton
    MemberAuthor

    Classification record: round 4 (rules revision 4), 2026-11-17

    Posted by an agent session. Nothing is filed and nothing is counted yet: round 4 split, so the
    full pass, the per-plugin table and the cut-item count wait on the owner's answers below.
    needs-human stays on this item.

    What changed since the last record

    • Rules revision 4, under the owner's decision of 2026-11-16 (relayed by an agent session:
      "ADR 0101 gains kept classes for R6's third clause and R8; the count covers R11 plus failing R4
      and R8; R6 defers ecosystem ids to R7"), the owner's R3 ruling (a description that lists tools
      does not make declared scope), and the "No ecosystem-specific examples" rule merged in PR 16634 /
      16649:
      • R3: "the capability cannot exist without" a fixed set the plugin name or skill description
        names; a description listing the formats a general capability supports does not qualify.
      • R4: goes (ADR 0101 decision 2, "Ship no bundled default"); no overridable default survives.
      • R6: includes values our scripts emit; an ecosystem id no script emits goes to R7; "kept
        default" dropped.
      • R8: survival judged on the row's targeted case, not the plugin's full suite.
      • R9: a link to one ecosystem's tool docs, or a stack-specific example, is not a cited source.
      • R10 retired; R11 takes every model-read K7 row no earlier rule holds.
      • Each reworded rule was checked against the basis the design states for it before any row was
        classified.
    • ADR 0101 amendment for the two kept classes: docs(adr): keep kept-adapter operation and measured fact in ADR 0101 #16720 (ready, not merged).
    • Input refreshed against main at 5b66a7f (by script): 528 model-read rows outside K9/K10
      plus 25 script- or both-read K3 rows (an R4 check, since a script-read value can still pick a
      library) = 553. 17 rows are gone because every cited file is gone on main (15 + 2: architecture
      1, biome-format 3, debugging 1, harness-ops 1, ruff-format 5, testing 3 (the property pages),
      typos-format 3). 536 rows remain (513 + 23). Readers also answer GONE when a cited passage was
      rewritten away in a file that still exists. The design's R8 example row (finding-classes.md:51)
      no longer holds its pairing on main, so round 4 used two other R8 candidates.

    Round 4

    Two fresh readers, given only the rules and the rows, classified 36 rows: the round-1 R3
    disagreements, rows the widened revision-3 R3 caught, eight model-read K6 rows (two whose values a
    script of ours may emit), five K7 rows, a tool-doc link row, two R8 candidates, three R4 rows and
    seven fresh controls. Compared by script.

    Result Rows
    Agree 31 of 36
    Agreed answers R1 2, R3 3, R4 2, R5 4, R6 8, R7 4, R8 1, R11 7
    Split rules R3, R6, R7, R11
    Row Reader A Reader B Moves the cut count
    F0316 pixel-art MZ example scripts (K7) R3 R11 yes
    F0024 architecture map-flow body (K4) R3 R6 no (both keep)
    F0139 corrections ladder rung ids (K6) R7 R6 no (both keep)
    F0357 review's synced ladder copy (K6) R7 R6 no (both keep)
    F0454 toolchain manifest coverage claim (K6) R7 R6 no (both keep)

    The readings, quoted:

    • F0316. A: "The pixel-art examples are RPG Maker MZ engine-layout artifacts, and the plugin and
      skill descriptions name RPG Maker MZ as an output target." B: "R3 fails because every pixel-art
      description lists MZ beside other targets (Godot, PICO-8, plain strips, 9-slice, blob-47), which
      is a general capability listing the targets it supports."
    • F0024. A: "The map-flow description scopes the skill to 'one C# entry point', and its shipped
      adapter reads only tracked *.cs files and refuses any other language." B: "C# is the one
      language a general entry-point tracing capability supports, which R3 excludes."
    • F0139. A: "the alias is a tool-named rung id that consumers write, which R7's ladder-rung clause
      covers." B: "The cited rung ids are this marketplace's ladder ids, and its scripts emit them:
      rules-ledger.mjs:50 prints CHECKING_RUNGS ..., rules-ledger.mjs:143 and
      rule-inventory.sh:214 print semgrep-rule in their old-id notices."
    • F0357. A: "keeps the tool-named semgrep-rule rung id as an alias; these are model-read K6 ids
      that skills match, and no script emits them." B: "its rung ids are values rules-ledger.mjs
      prints ... and names in its old-id message."
    • F0454. A: "a model-read coverage claim listing ecosystems; R7 says a coverage claim changes with
      the mechanism it describes." B: "The manifest description states a behavior of this marketplace
      ... and no other skill or config writes or matches that text, so the R6 hand-off to R7 does not
      apply."

    Per this item's rule, a split after the owner's decisions goes to the owner rather than to another
    rewording round.

    Owner question 1: R3 for one named target or one-language reader

    When a skill's description names a platform or language and the row's content serves only it, but
    the capability could serve others (pixel-art lists MZ beside Godot and PICO-8; map-flow traces
    C# only), is the row declared scope under R3?

    • A (recommended): yes, per row. R3 holds when the description names the platform or format
      and the row's content is an artifact for, or a reader of, only that named one; a description
      that lists several formats one general reader handles is not declared scope. Basis: the design
      states that R3 extends the philosophy's inherently-locked test to output targets and fixed reader
      formats, which revision 4 keeps in its examples ("a game engine layout", "a skill whose product is
      reading those formats and whose shipped reader parses only them").
    • B: no. Only a capability bound as a whole (a tool-branded plugin, a skill whose only product
      is that platform's artifact) is declared scope; per-target content of a multi-target skill is
      judged by the later rules. Closer to "genuinely and inherently locked"
      (docs/plugin-philosophy.md:458); F0316 becomes a cut (R11).

    Owner question 2: what "a value one of its scripts emits" covers in R6

    Do ladder rung ids that a script holds in a list or names in a deprecation notice, and a manifest's
    coverage claim, go to R6 or R7? Both keep the row; R7's disposition renames a tool-named rung id
    and opens an ecosystem-id list, R6's keeps the text once.

    • A (recommended): R7. "Emits" means a value a script writes into output the model then reads
      (a report field such as cov_source), not an id a script validates against or names in a notice.
      Basis: R7's disposition names both cases outright ("a ladder rung ... is renamed"; "a coverage
      claim changes with the mechanism it describes"), and the design limits R7 to mechanism-class tool
      ids and ecosystem ids as data.
    • B: R6. Any id a script of ours prints is a mechanism record; R7 keeps only ids no script
      prints.

    Answering both unblocks: the full pass over the 536 refreshed rows, the per-plugin table, the
    cut-item count, and removal of needs-human.

    Correction to this item's text

    Overlap noted for the review cut item

    An unpushed branch for #16646 (no PR yet) edits plugins/review/agents/ecosystem-specialist.md:
    it adds a prerequisite paragraph right after the stack-default fallback lines (dotnet test,
    pytest, ruff check and the rest) that the review cut item covers, and a new report example
    naming one ecosystem's tools (a YAML lint skip naming ajv and npm ci), which revision 4 would
    place under R11. The review cut item should be drafted against that branch's text once it merges.

    Cut items that would be filed: not yet counted (blocked by the two questions above). None is filed.

  15. kyle-sexton commented on Nov 17, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded. The owner answered both round-4 questions on 2026-11-17, typed in a session: "go w/ recommendations" to each, with the options restated in full.

    • R3: content written for one target or language that the skill's description names is declared scope, judged per row: a row that serves only such a named target stays under R3.
    • R6: "a value one of its scripts emits" covers only a value a script writes into output the model reads. An id a script merely validates against, or names in a deprecation notice, is not covered; ladder rung ids and coverage claims fall under R7.

    Rules revision 5 is revision 4 with R3, R6 and R7 worded to these two answers; every other rule is unchanged. Round 4's five split rows under revision 5:

    Row Rule Why
    F0316 pixel-art MZ example scripts R3 each script is an artifact for RPG Maker MZ only, a target the skill descriptions name
    F0024 architecture map-flow body R3 the description names one C# entry point and the shipped reader parses only *.cs
    F0139 corrections ladder rung ids R7 ladder rung ids
    F0357 review's synced ladder copy R7 ladder rung ids
    F0454 toolchain manifest coverage claim R7 a coverage claim

    Both readers' answers on each row are now reconcilable: the readers split on what the two questions asked, and no row stays open. Only F0316 changes the cut count (it stays). Next: the full pass over the 536 refreshed rows under revision 5, then the per-plugin table and the cut-item count. Nothing is filed.

  16. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Nov 17, 2026
  17. kyle-sexton commented on Nov 17, 2026

    @kyle-sexton
    MemberAuthor

    Per-plugin cut count (done-when 2 and 3)

    Posted by an agent session. Full pass under rules revision 5 over the 536 refreshed rows (input at 5b66a7fa), one reader per chunk, tallied by script (first answer per row). 536 of 536 answered, no conflicts.

    Plugin Rows R11 R4 R8 (cut unless its case fails) Gone Kept Cut item Note
    toolchain 38 24 9 0 0 5 no #15733 owns it
    testing 37 24 2 0 2 9 yes
    code-tidying 55 21 3 1 1 29 yes
    tdd 24 22 1 0 0 1 yes
    mutation-testing 27 19 2 1 0 5 yes
    docs-hygiene 17 14 2 0 0 1 yes
    implementation 14 14 0 0 0 0 yes
    user-interface 18 10 2 0 0 6 yes
    source-control 16 7 0 0 0 9 yes
    harness-config 9 5 0 1 1 2 yes
    instruction-placement 11 4 0 2 0 5 yes
    planning 6 6 0 0 0 0 yes
    review 15 5 1 0 1 8 yes
    knowledge 7 5 0 0 0 2 yes
    performance 8 3 1 1 0 3 yes
    verification 7 5 0 0 0 2 yes
    work-items 5 5 0 0 0 0 yes
    app-control 5 4 0 0 0 1 yes
    code-metrics 30 4 0 0 0 26 yes
    debugging 8 4 0 0 1 3 yes
    harness-memory 4 4 0 0 0 0 yes
    improvement 4 4 0 0 0 0 yes
    ai-slop 3 3 0 0 0 0 yes
    developer-experience 3 3 0 0 0 0 yes
    discovery 5 3 0 0 0 2 yes
    education 3 3 0 0 0 0 yes
    mcp-tools 10 3 0 0 0 7 yes
    prototype 4 2 1 0 0 1 yes
    session-flow 4 3 0 0 0 1 yes
    architecture 24 2 0 0 1 21 yes
    codebase-health 2 2 0 0 0 0 yes
    corrections 7 2 0 0 4 1 yes
    disk-hygiene 2 1 0 1 0 0 yes
    github 3 2 0 0 0 1 yes
    playbooks 5 2 0 0 0 3 yes
    adhd 1 1 0 0 0 0 yes
    ai-briefing 1 1 0 0 0 0 yes
    bugs 1 1 0 0 0 0 yes
    coupling 2 1 0 0 0 1 yes
    dometrain 1 1 0 0 0 0 yes
    evals 2 1 0 0 0 1 yes
    event-storming 1 1 0 0 0 0 yes
    machine-health 3 1 0 0 0 2 yes
    playwright 5 1 0 0 1 3 yes
    skill-quality 3 1 0 0 0 2 yes
    songwriting 2 1 0 0 0 1 yes
    visualization 4 1 0 0 0 3 yes
    wizard 2 1 0 0 0 1 yes
    Shared generated copies 1 0 0 0 0 1 no not a plugin on main
    actionlint 4 0 0 0 0 4 no
    animation 1 0 0 0 0 1 no
    attribution 1 0 0 0 0 1 no
    autonomy 2 0 0 0 0 2 no
    bash-format 3 0 0 0 0 3 no
    context7 5 0 0 0 0 5 no
    docs-naming 1 0 0 0 0 1 no
    eol-normalizer 2 0 0 0 0 2 no
    explainer-video 3 0 0 0 0 3 no
    firecrawl 3 0 0 0 0 3 no
    gaming 3 0 0 0 0 3 no
    go-format 3 0 0 0 0 3 no
    guardrails 2 0 0 0 0 2 no
    harness-ops 4 0 0 0 0 4 no
    kindle-dedrm 2 0 0 0 0 2 no
    markdown-format 3 0 0 0 0 3 no
    naming 1 0 0 0 0 1 no
    overengineering 2 0 0 0 0 2 no
    pixel-art 4 0 0 0 0 4 no
    playgrounds 1 0 0 0 0 1 no
    plugin-quality 1 0 0 0 0 1 no
    powershell-format 3 0 0 0 0 3 no
    repo-fleet-hygiene 2 0 0 0 0 2 no
    repo-hygiene 3 0 0 0 0 3 no
    retro-audio 2 0 0 0 0 2 no
    sql-server 5 0 0 0 0 5 no
    user-experience 1 0 0 0 0 1 no

    Per-rule totals over all rows: {'R1': 2, 'R2': 31, 'R3': 75, 'R4': 24, 'R5': 12, 'R6': 87, 'R7': 23, 'R8': 7, 'R9': 6, 'R11': 257, 'GONE': 12}.

    Rows to cut (R11 + R4 + R8): 288 in total (R11 257, R4 24, R8 7). Toolchain's 33 are excluded because #15733 owns that cut, leaving 255 rows across 47 plugins. R8 rows are cut unless their targeted case fails without them.

    47 cut items will be filed under #15703, each blocking #15732, in this order: 1. discovery, 2. review, 3. mutation-testing, 4. user-interface, 5. planning, 6. testing, 7. code-tidying, 8. tdd, 9. docs-hygiene, 10. implementation, 11. source-control, 12. harness-config, 13. instruction-placement, 14. knowledge, 15. performance, 16. verification, 17. work-items, 18. app-control, 19. code-metrics, 20. debugging, 21. harness-memory, 22. improvement, 23. ai-slop, 24. developer-experience, 25. education, 26. mcp-tools, 27. prototype, 28. session-flow, 29. architecture, 30. codebase-health, 31. corrections, 32. disk-hygiene, 33. github, 34. playbooks, 35. adhd, 36. ai-briefing, 37. bugs, 38. coupling, 39. dometrain, 40. evals, 41. event-storming, 42. machine-health, 43. playwright, 44. skill-quality, 45. songwriting, 46. visualization, 47. wizard.

    The issue's named cuts come first (discovery explore fallback table; review ecosystem-specialist; mutation-testing per-tool tables; user-interface framework pages; planning TypeScript idioms page), then the rest by rows to cut, most first.

    The eval recipe in this issue's Steps ("no more than 400 runs per plugin ... opus and sonnet aliases, three runs per side") is superseded for every cut item: one targeted before-and-after case per changed skill on sonnet at 3 runs a side, opus only to confirm a sonnet loss, no paired compare, each whole-page cut keeping its own sensitivity control (#15703 comment 6906800940; #16672 comment 6935228111). Each cut item states it.

    Cut rows with two readings

    A reader's note named another rule for these cut rows; each cut item marks the row and quotes the note. In 36 of 44 the other rule is one that keeps rows (some notes name it only for part of the cited range).

    • review F0361 (R11; other reading R2); the other reading names a rule that keeps rows
    • mutation-testing F0276 (R11; other reading R6); the other reading names a rule that keeps rows
    • mutation-testing F0281 (R8; other reading R11)
    • mutation-testing F0289 (R4; other reading R11)
    • mutation-testing F0301 (R11; other reading R6); the other reading names a rule that keeps rows
    • user-interface F0495 (R4; other reading R11, R3); the other reading names a rule that keeps rows
    • user-interface F0498 (R11; other reading R3); the other reading names a rule that keeps rows
    • user-interface F0499 (R11; other reading R3); the other reading names a rule that keeps rows
    • user-interface F0500 (R11; other reading R3); the other reading names a rule that keeps rows
    • user-interface F0501 (R11; other reading R3); the other reading names a rule that keeps rows
    • user-interface F0502 (R11; other reading R3); the other reading names a rule that keeps rows
    • planning F0320 (R11; other reading R6); the other reading names a rule that keeps rows
    • testing F0432 (R11; other reading R9); the other reading names a rule that keeps rows
    • testing F0434 (R11; other reading R9); the other reading names a rule that keeps rows
    • testing F0445 (R11; other reading R4, R6); the other reading names a rule that keeps rows
    • testing F0448 (R11; other reading R4)
    • testing F0453 (R4; other reading R6, R7); the other reading names a rule that keeps rows
    • code-tidying F0097 (R11; other reading R6); the other reading names a rule that keeps rows
    • code-tidying F0101 (R11; other reading GONE); the other reading names a rule that keeps rows
    • tdd F0397 (R4; other reading R11)
    • tdd F0412 (R11; other reading R9); the other reading names a rule that keeps rows
    • tdd F0414 (R11; other reading R9); the other reading names a rule that keeps rows
    • docs-hygiene F0172 (R11; other reading R9); the other reading names a rule that keeps rows
    • docs-hygiene F0174 (R11; other reading R6); the other reading names a rule that keeps rows
    • docs-hygiene F0180 (R11; other reading R3); the other reading names a rule that keeps rows
    • source-control F0377 (R11; other reading R6); the other reading names a rule that keeps rows
    • harness-config F0211 (R8; other reading R11)
    • instruction-placement F0242 (R11; other reading R2); the other reading names a rule that keeps rows
    • knowledge F0258 (R11; other reading R6); the other reading names a rule that keeps rows
    • performance F0305 (R4; other reading R11)
    • performance F0307 (R8; other reading R4)
    • performance F0311 (R11; other reading R9); the other reading names a rule that keeps rows
    • work-items F0525 (R11; other reading R7); the other reading names a rule that keeps rows
    • app-control F0012 (R11; other reading R4)
    • code-metrics F0055 (R11; other reading R6, R7); the other reading names a rule that keeps rows
    • code-metrics F0078 (R11; other reading R10, R2, R3, R5, R6, R9); the other reading names a rule that keeps rows
    • code-metrics F0079 (R11; other reading R10, R2, R3, R5, R6, R9); the other reading names a rule that keeps rows
    • debugging F0149 (R11; other reading GONE); the other reading names a rule that keeps rows
    • debugging F0155 (R11; other reading R6); the other reading names a rule that keeps rows
    • ai-slop F0010 (R11; other reading R6); the other reading names a rule that keeps rows
    • mcp-tools F0272 (R11; other reading R9); the other reading names a rule that keeps rows
    • session-flow F0369 (R11; other reading R6); the other reading names a rule that keeps rows
    • disk-hygiene F0165 (R8; other reading R2); the other reading names a rule that keeps rows
    • dometrain F0183 (R11; other reading R1, R3); the other reading names a rule that keeps rows

    Approval

    The owner approved filing on 2026-11-17, asked "File the 47 cut items for #15730?", option A "file all 47, in the tally's order"; answer verbatim: "go w/ recommendations".

  18. kyle-sexton commented on Nov 17, 2026

    @kyle-sexton
    MemberAuthor

    The done-when is met; closing. Posted by an agent session.

    Stated gaps:

    • 44 cut rows carry a second reading from a reader's note (listed in the count comment and quoted on each row). The flag is a text match on any other rule a note names, so some are incidental. None changes which plugins get an item; a lane that finds a row is kept under its other reading reports it on its cut item.
    • The design's rule table was brought to revision 5 in knowledge-corpus#73; two of its counts now point at this tally instead of being recomputed.
  19. 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
  20. kyle-sexton commented on Nov 19, 2026

    @kyle-sexton
    MemberAuthor

    Report from cut item #16764 (pull request #17470), under its rule "A row whose file a script reads is not cut here: report it on #15730."

    Row F0212, file plugins/harness-config/skills/audit/reference/required-permissions.md: a script reads this file. plugins/harness-config/skills/audit/scripts/audit-engine.sh uses it as its baseline, taking only table rows whose first cell is a backticked Tool(...) pattern under the sensitive-file-deny, destructive-bash-deny and ask-rules headings.

    Pull request #17470 still changed three prose passages in that file (the python -c / node -e examples, "a Python or Node script", and the Bash(npm run *) wildcard example). No table row changed, so the script's input is the same before and after. The cut was kept on that basis; the pull request's eval has no case for this file.

    Posted by an agent session.

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

    confirmed

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions