Skip to content

Add ecosystem records to dotfiles #15714

Closed
Closed

Description

@kyle-sexton

Parent

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

Depends on

Outcome

The repository named in this item's title resolves its build, test and lint commands from its own ecosystem records, so its runs do not report INCOMPLETE once unattended runs stop using the marketplace's bundled defaults.

Demo: on that repository's default branch, .claude/ecosystems/ holds its records, and a /toolchain:check all run there shows no skip (unresolved: ...) cell.

The target repository belongs to the owner (melodic-software). It is one of 15 that have a Claude lane workflow and no ecosystem records, counted on 2026-11-12. The pull request is opened in that repository; this item tracks it.

Steps, the same as for this repository's own records (#15704):

  • Pick one merged commit range in the target repository that touches at least one file of each ecosystem it has; record both SHAs in the pull request body.
  • Run /toolchain:check all and /toolchain:lint there with the bundled defaults in place. Take the baseline command list from the Bash commands the run executed and put it in the pull request body.
  • Write one ecosystem record per covered ecosystem, following that repository's own rules where a bundled default differs, each difference listed as intended. Validate each record against the ecosystem-commands schema.
  • Re-run on the same diff; the command list matches the baseline apart from the listed intended differences.
  • Shell, markdown, YAML and PowerShell have no build file to infer a command from, so each of those the repository uses needs a record.
  • Run budget: 6 runs; launch nothing after a usage-limit error.
  • Check the diff for secrets and machine-specific data before the first push.

Decisions

  • Owner, 2026-11-12: "I don't want anything to be 'we cannot accept incomplete.' We'll need to run that setup in each repository. We'll need to make sure that everything is set up and in place."
  • D7: records land in the owner's other lane repositories before unattended runs change.
  • D2: records land by pull request; nobody types /toolchain:setup apply. If the target repository turns out to need the user-typed setup, stop and give the owner the one command.
  • Owner, 2026-11-12 (scope): every owner repository with a Claude lane workflow and no records is covered, 15 in all.

Key interfaces

  • The record's format is the existing ecosystem-commands schema.

Done when

  • AC5 (precondition): the target repository has a merged pull request adding its records, and .claude/ecosystems/ on its default branch is non-empty.
  • Each record validates against the ecosystem-commands schema.
  • A recorded /toolchain:check all output for that repository contains no skip (unresolved.
  • The merged pull request's URL is posted on this item.

Out of scope

  • Any change to the target repository other than its ecosystem records.
  • Any repository the owner does not own.

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. 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.

  4. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Small
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    I understood this as a bounded task. It adds ecosystem records under .claude/ecosystems/ in the dotfiles repository, through a pull request opened there. Each record must validate against the ecosystem-commands schema. A /toolchain:check all run there must then show no skip (unresolved cell.

    The issue is exact enough to triage as it stands. The parent item #15703 and the dependency #15704 are named. #15704 is not in the open-issues list, so I treated it as not blocking. I found no duplicate: the sibling items (#15712–#15727) each cover a different repository, and none covers dotfiles. I found no merged pull request that already does this.

    Automated triage. A maintainer reviews it.

  5. 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
  6. 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).

  7. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

    Record for the done-when items. Merged: https://github.com/melodic-software/dotfiles/pull/1616 (squash 03abc6f7, reviewed head 442572ad, both review lanes and Codex 0 findings).

    • AC5: .claude/ecosystems/ on dotfiles main holds eight records: bash, chezmoi, cross-cutting, markdown, powershell, python, typescript (disabled), yaml (read back from the default branch after the merge).

    • Schema: each record validated against docs/contracts/ecosystem-commands/ecosystem.schema.json with check-jsonschema (ok -- validation done for all eight).

    • Recorded /toolchain:check all output: in the pull request's Verification section. No cell reads skip (unresolved. As the parent's note says, that string cannot appear on toolchain 1.4.x, so the evidence that can fail is this: every selected ecosystem's commands were resolved from the repository's own records, and the last run's line reads

      Overall: FAIL (1 of 5 ecosystems failed, 1 gate failed; bash: Test FAIL (tools/shell-init-cache/test.sh); gate plugin-manifest FAIL (core@melodic-software not published))

      Neither failure comes from a record:

      • tools/shell-init-cache/test.sh assertions 46 and 47 fail on the machine the run used and passed in CI on the same head (run 43802856009). Cause not established.
      • The plugin-manifest gate fails on dotfiles main itself: .chezmoidata/claude.json still lists core@melodic-software, which the marketplace stopped publishing in feat(plugin-profiles)!: switch plugin sets by profile and remove the core bundle #16483. The records run the gate as CI does; the stale entry is a separate defect in dotfiles, reported to the hub session.
    • Baseline and intended differences: both SHAs of the commit range, the baseline command list and each ecosystem's intended differences are in the pull request body. 5 of the 6 budgeted runs were used; lint read PASS (7 of 7 ecosystems passed) before and after.

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

    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