Repository navigation
Closed
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.
Description
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 alland/toolchain:lintthere 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 alloutput for that repository contains noskip (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.
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.
Type
Fields
Work status
confirmed
Priority
medium
Activity
github-actions commentedon Nov 13, 2026
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this item tracks a pull request in the agent-plugins repository. The PR adds
.claude/ecosystems/records, one per ecosystem, validated against the ecosystem-commands schema. Once they are merged,/toolchain:check allthere should show noskip (unresolved ...)cell. The outcome, steps and done-when are exact, and the owner's decisions are recorded in the body, so nothing is missing. The dependency #15704 does not appear among the open issues. This is one of a set of sibling per-repository items (for example #15727 and #15726), not a duplicate. No merged pull request already covers it.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 13, 2026
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).chore: add ecosystem records mirroring CI's checks (#137)
fix: keep the local gitleaks scan in the cross-cutting record (#139)
fix: cite the current check-managed-files pin and automerge lines in …
kyle-sexton commentedon Nov 16, 2026
Delivered; closing.
/toolchain:check alloutput with the records: in chore: sync standards components #147's Verification section, range455a89f..8437305:Overall: PASS (1 of 1 ecosystems passed);/toolchain:lint:Overall: PASS (1 of 1 ecosystems passed). Every selected ecosystem resolved its commands from the repository's own records. No cell readsskip (unresolved; that test passes trivially, since toolchain 1.4.x has no code path that prints the cell.Overall: PASS (2 of 2 ecosystems passed), lintOverall: PASS (3 of 3 ecosystems passed). Baseline commands:shellcheck -x -S warning <2 files> && shfmt -d <2 files>;npx markdownlint-cli2 REVIEW.md;actionlint;typos,gitleaks detect --source . --redact --no-banner --no-git, editorconfig-checker,lychee --offline --no-progress './**/*.md'.bash -non each of CI's two scripts and every command counting toward the status; markdownlint and actionlint not run;jq emptyon the two JSON files CI checks; typos and editorconfig-checker not run (no CI lane);gitleaks dir . --config .gitleaks.toml. Not itemized there, and following the same rule (the record runs what that repository's required-checks workflow runs):shfmt -dand shellcheck's-x -S warningdropped (CI runs plainshellcheck .claude/cloud-bootstrap.sh .cursor/install.sh), andlychee --config lychee.tomlas CI's step passes it. With markdown and yaml set to no command, the overall counts drop from 2 and 3 ecosystems to 1 and 1.