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
melodic-automation-lanes commentedon Nov 13, 2026
No work-resolve-issue run started in the 1 hour since
agent-readywas last added. work-unblock removed and addedagent-readyback 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.github-actions commentedon Nov 13, 2026
The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).
github-actions commentedon Nov 13, 2026
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: this tracks a pull request in the songwriting repository that adds ecosystem records under
.claude/ecosystems/. Each record is validated against the ecosystem-commands schema, and/toolchain:check allthere should then show noskip (unresolvedcell. The steps and done-when list are exact, so nothing is missing. The dependency #15704 is not in the open list, so I treated it as not blocking. The sibling "Add ecosystem records to ..." issues cover other repositories, so none is a duplicate. I found no merged pull request that already does this.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).kyle-sexton commentedon Nov 14, 2026
Reopened by the GitHub Support session. https://github.com/melodic-software/songwriting/pull/58 merged this repository's records, and its body closed this issue with a Closes line I wrote in error. Met: the merged pull request, records on the default branch, each record valid against the schema. Still owed from the done-when and steps: a recorded /toolchain:check all output that contains no 'skip (unresolved', and the baseline steps (one merged commit range with both SHAs, the command list of a run with the bundled defaults, and a re-run with the records).
kyle-sexton commentedon Nov 16, 2026
Delivered; closing.
b15e857). Six records on the default branch:bash,cross-cutting,markdown,python(every command null),typescript(disabled) andyaml. Each is valid against the ecosystem-commands schema:check-jsonschemaprintedok -- validation done, re-run 2026-11-16 on the default branch at8e4b7ba.e1acf55e197b65e629c17c70415389d747a3ea47..8e4b7baf5e9135d1d93d6ee0e75dcbcff15e7686on songwriting's default-branch first-parent line, from https://github.com/melodic-software/songwriting/pull/10 through https://github.com/melodic-software/songwriting/pull/66, with PR 58 included. Toolchain 1.4.3.package.jsonandpackage-lock.json./toolchain:check all:Overall: PASS (2 of 2 ecosystems that ran a command passed: bash, markdown; powershell: skip (opt-in unmet); python, dotnet, go: no command)/toolchain:lint:Overall: PASS (4 of 4 ecosystems that ran a command passed: bash, markdown, yaml, cross-cutting; python: no command)go.mod.skip (unresolved. That test cannot fail: toolchain 1.4.3 has no code path that prints the cell. Its skip classes aretool missing,dependencies missing,unsupportedandopt-in unmet.Overall: FAIL (1 of 7 ecosystems failed; python: Test FAIL (uv run pytest -x -q: failed to spawn pytest; the repository declares no Python project or dependencies))Overall: FAIL (1 of 6 ecosystems failed; cross-cutting: lychee 114 errors in 26 inputs, all under node_modules/)node_modules/. The worktree setup'snpm ciinstalled it, and it is gitignored. The repository's own Markdown is clean.uv run pytest -x -qshellcheck -x -S warning <2 files> && shfmt -d <2 files>npx markdownlint-cli2 <54 files>actionlinttyposgitleaks detect --source . --redact --no-banner --no-gitlychee --offline --no-progress './**/*.md'uv run pytestno longer runs.npx.<files>.--rcfile=.shellcheckrcand without-x -S warning, andshfmt -dis gone, because CI has no shfmt lane.--config .markdownlint-cli2.jsonc.typos --config _typos.toml ..gitleaks dir . --config .gitleaks.toml --no-banner --redact.mainshowed no change since035f744topr-run-checks.ymlor to any lane composite the records cite, and every tool pin matches. The one cited path that changed is the check-contract action, which has no local form..github/**, the same pattern as CI's actionlint filter (pr-require-checks.yml:70-71). They now select.github/standards/dependabot-policy/policy.json, added in https://github.com/melodic-software/songwriting/pull/65.git ls-files ':(glob).github/**'lists 8 files with it; the old globs listed 7.v0.74.0, after https://github.com/melodic-software/songwriting/pull/63.package.json, after https://github.com/melodic-software/songwriting/pull/62.Overall: PASS (2 of 2 ecosystems that ran a command passed: bash, markdown; powershell: skip (opt-in unmet); python, dotnet, go: no command)Overall: PASS (4 of 4 ecosystems that ran a command passed: bash, markdown, yaml, cross-cutting; python: no command)kyle-sexton commentedon Nov 16, 2026
Reopened by the GitHub Work session, which closed it earlier today. The lint PASS recorded above came from the wrong tool: the yaml record runs
actionlintand pins the kjanat fork 1.17.0 that CI uses, but the host that ran it has the standard build 1.7.12. It passed only because these workflows use no syntax the fork alone accepts. The owner ruled on 2026-11-16 that a check must not proceed without the tool it needs, and #15703 forbids installing it, so that cell should read not run, not PASS. Every other recorded result stands. This waits on the toolchain change in #16646, like #15713 and #15717.kyle-sexton commentedon Nov 17, 2026
Prerequisite declared; record run on a host with the CI build.
requires(ecosystem-commands contract 1.4.0), in https://github.com/melodic-software/songwriting/pull/68.shellcheck --rcfile=.shellcheckrc <files>markdownlint-cli2 --config .markdownlint-cli2.jsonc <files>actionlinttypos --config _typos.toml ., thengitleaks dir . --config .gitleaks.toml --no-banner --redactenabled: false.go.mod.requiresentries:check-cmd:actionlint (the kjanat build tool-pin names). The probe readstool-pin.actionlintfrom the record and passes only when the first line ofactionlint -versionis exactlyactionlint.kjanat.dev <version>. Stock rhysd/actionlint prints the bare version there (command.go:164-165), so it cannot pass.actionlint.kjanat.dev 1.17.0, pin 1.17.0). The same filter rejected1.7.12,actionlint.kjanat.dev 1.16.0and an empty pin.check-jsonschemaagainst the contract schema:ok -- validation done./toolchain:check all:Overall: PASS (2 of 2 ecosystems that ran a command passed: bash, markdown; powershell: skip (opt-in unmet); python, dotnet, go: no command)/toolchain:lint all:Overall: PASS (4 of 4 ecosystems that ran a command passed: bash, markdown, yaml, cross-cutting; python: no command)/toolchain:linton the branch diff (only the record changed, which no ecosystem glob claims, so only cross-cutting runs):Overall: PASS (1 of 1 ecosystems passed: cross-cutting)skip (prerequisite missing. No FAIL and no INCOMPLETE. The yaml lint ran on the build CI pins, so this run meets the close condition. The issue closes once the pull request merges.1.16.0, exits 1 against the real binary. That cell would readskip (prerequisite missing: actionlint (the kjanat build tool-pin names)), with OverallINCOMPLETEand no FAIL.