Repository navigation
Open
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.Needs an unattended run on a host; the host runner takes it, not a person or the issue lane.needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.
Description
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-humanat 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
opusandsonnetaliases, 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.
Metadata
Metadata
Assignees
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.Needs an unattended run on a host; the host runner takes it, not a person or the issue lane.needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.
Type
Fields
Work status
confirmed
Priority
medium
Activity
github-actions commentedon Nov 13, 2026
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: #15709
Understood: this item runs a blind two-reader classification of a stratified sample of inventory rows under rules R1 to R11, rewords any split rule for up to three rounds, states the per-plugin row counts, and files one cut item per plugin in the stated order, each blocking the gate-widening item (#15732 looks like that item).
Nothing is missing. The issue lists #15709 as a dependency and it is still open, so this one waits on it. Parent: #15703. I found no duplicate among the open issues.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 14, 2026
Not admitted to the issue lane yet: blocker #15709 is not closed by a listed human or a merge.
melodic-automation-lanes commentedon Nov 15, 2026
{"v":1,"actor_id":337595936,"title_sha256":"9d79b74de8166e30535bbccff3f3fc28f2e061133b75b36cc237ef795d7c3808","body_sha256":"9828144936142295b079e265a2acb47574f048184c5eeae6c50ed72b8b726179"}
github-actions commentedon Nov 15, 2026
melodic-automation-lanes commentedon Nov 15, 2026
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-runand 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:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/43770041352
To hand it back to the lane, remove
host-runand set Work status to agent-ready again.kyle-sexton commentedon Nov 16, 2026
Classification record for the blind-classification step (done-when item 1). Result: zero split rules after three rounds. The count and the filing have not started; two questions for the owner are at the end.
Method: the inventory's 1106 rows were parsed by script (584 model-read, 424 script-read, 98 both; the totals match the design's). A seeded stratified draw gave 50 sample rows, 5 per kind, and 30 reserve rows disjoint from them. Each round used two fresh agents that saw only the rule table, their rows and the plugins tree at the inventory's commit, never the design text, the counts or the other reader's answers. A rule is split when the two disagree on any row either placed under it (Q27).
What was reworded (R5 and R6 were split only as the other side of a disagreement and were not changed):
Every row that disagreed in an earlier round was placed the same way by both readers of the next round, except one that needed the R1 rewording and agreed in round 3. All five rules involved in a split have a "stays" disposition, so no disagreement moved a row between kept and cut.
Limits of this record:
Not done, waiting on the owner:
The cut items' recipe in this issue's steps ("no more than 400 runs per plugin ... three runs per side") predates the owner's decision of 2026-11-16 on the parent, which drops the per-cut no-loss compare and keeps each cut's control. Cut items will follow that decision. Their number is stated here before any is filed; none is filed without the owner's yes.
kyle-sexton commentedon Nov 16, 2026
Correction to the record above: R3 is not settled, and it goes to the owner.
The round 2 rewording of R3 changed what the rule means, not only how it reads. The original test asks for a capability "inherently bound" to a fixed set, which follows
docs/plugin-philosophy.md("genuinely and inherently locked"). My rewording dropped that word and said a set named in the plugin name or skill description is enough, for every row of that skill. Two readers then agreed, but they agreed on a wider rule.Evidence: the first 100 rows of a full pass under the reworded rules (the count step, started and now stopped) placed 44 under R3 and 2 under R11. The R3 rows include model-read guidance that the filing order in this issue treats as cuts or close to it, for example 13 code-tidying rows (the per-tool dead-code lanes among them) and 14 code-metrics rows (collector pages among them), kept because a description lists the tools.
So:
Adding
needs-human, as this issue's steps say for a rule the rounds do not settle.For the owner, R3: does a skill that lists its supported tools or formats in its description put its model-read guidance for those tools in declared scope?
kyle-sexton commentedon Nov 16, 2026
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.
kyle-sexton commentedon Nov 16, 2026
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).
needs-humanuntil those are answered.kyle-sexton commentedon Nov 16, 2026
Decision recorded (AC1 exception set), with what stays open.
Read against the texts in a fresh context, then each cited line re-read:
docs/adr/0101-resolve-ecosystem-specifics-from-the-consumer-repository.md:49).Not settled by the texts, left for the owner (
needs-humanstays):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.