Skip to content

Write this repository's ecosystem records and capture the command-list baseline #15704

Description

@kyle-sexton

Parent

Refs #15703
Source: PLAN Phase 1, topic ecosystem-specifics

Depends on

  • none: on the frontier now

Outcome

This repository resolves its build, test and lint commands from its own ecosystem records, and a recorded baseline of the commands /toolchain:check and /toolchain:lint run on one fixed diff exists for later items to compare against.

Demo: re-run /toolchain:check all and /toolchain:lint on the fixed diff after the records land; the command list matches the baseline in the pull request body line for line, apart from the listed intended differences.

Steps the plan fixes:

  • Pick one merged commit range that touches at least one file of each ecosystem this repository has; record both SHAs in the pull request body.
  • Run check and lint on it with the bundled defaults in place. Take the baseline from the Bash commands the run executed, not its reply text, and put the list per ecosystem in the pull request body.
  • Write one ecosystem record per covered ecosystem with the commands this repository's own rules require. Where a bundled default differs from a repository rule (Python lint runs through the pinned ruff wrapper), follow the rule and list the difference as intended.
  • Three other shipped readers pick these records up: code-metrics lane resolution, the dead-code classifier and the autonomy prerequisite probe. Capture each one's output before and after; list any change as intended or fix the record (a cross-cutting record must not become a code-metrics lane).
  • Run budget: 6 runs, no eval batch; launch nothing after the first usage-limit error.

Decisions

  • D2: this repository's records land by pull request; nobody types /toolchain:setup apply. The record is a schema-validated YAML file the consumer commits, and this repository is the consumer.
  • D26: the records follow this repository's own rules where a bundled default differs, each difference listed as intended.
  • Alternative rejected: deleting toolchain's bundled files before these records exist.

Key interfaces

  • The record's format is the existing ecosystem-commands schema; that contract is not widened.
  • Dependency direction: skills depend on contracts and reach each other only by /plugin:skill; no skill reads another plugin's artifact.

Done when

  • AC11 (first half): .claude/ecosystems/ holds at least one record per ecosystem in the baseline, and each validates against the ecosystem-commands schema.
  • A diff of the before and after command lists prints only the lines the pull request body lists as intended.
  • The code-metrics lane list, the dead-code classification and the autonomy probe output are unchanged or listed as intended.
  • The pull request body holds the two SHAs and the baseline list, and names this repository's dogfooding step.
  • AC7: no skill text is cut here, so no control result is owed.
  • AC10: no enforcement-placing skill is added here.

Out of scope

  • Deleting or editing toolchain's bundled ecosystem files.
  • Records for any other repository.

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. 1 remaining item

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

    @melodic-automation-lanes
    Contributor

    No work-resolve-issue run started in the 1 hour since agent-ready was last added. 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.

  5. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Medium
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: none

    I read this as a bounded task. It has two parts. First, add schema-validated ecosystem records under .claude/ecosystems/, one per ecosystem this repository has. Second, record a baseline of the commands /toolchain:check and /toolchain:lint run on one fixed merged commit range. The baseline and both SHAs go in the pull request body, along with a before/after comparison that includes the code-metrics, dead-code and autonomy-probe outputs. The outcome, the decisions and the done-when list are all exact, so I found nothing to ask the reporter. I found no duplicate among the open issues and no merged pull request that already does this. #15703 is the parent, and #15733 (delete the bundled defaults) is the follow-up the issue says must come after this one.

    Automated triage. A maintainer reviews it.

  6. removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 13, 2026
  7. added
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 13, 2026
  8. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: its body or a criterion names .claude/ecosystems/, which the issue lane cannot push (patch-protected-path); a builder session takes it. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  9. removed
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 13, 2026
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

    No labels
    No labels

    Type

    Fields

    Work status

    confirmed

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions