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
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
I read this as a request to add ecosystem records to the github-iac repository, so its
/toolchain:check allruns resolve build, test and lint commands without anINCOMPLETEresult. The work is a pull request in that repository that adds one validated record per ecosystem it uses. The pull request body carries the baseline command list and the two commit SHAs.Nothing is missing. The dependency #15704 doesn't appear among the open issues, so I treated it as not blocking.
The sibling issues (#15712 through #15727) each cover a different repository, so I did not treat them as duplicates. No merged pull request already covers this.
Two things in the done-when need a run with access to github-iac: the recorded
/toolchain:check alloutput, and the merged pull request in that repository. I did not hold the issue for either.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/github-iac/pull/875 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
Status: the records' drift fix is in melodic-software/github-iac#904 (draft, held). With the records,
/toolchain:check allreads PASS (4 of 4 ecosystems);/toolchain:lintreads FAIL on a host without the runner-policy script's runtime, because the check runs anyway and crashes. The owner ruled on 2026-11-16 that a check must not proceed without what it needs, and #15703 forbids installing it, so this needs a toolchain change, filed as #16646. This issue waits on that.kyle-sexton commentedon Nov 17, 2026
Prerequisites declared, and a lint run on a checkout that has both of them reads PASS with the yaml row run and passing.
ba673ccb2550a1a684432976d12f124b9e703683). The yaml record now declares two prerequisites of itscheck-cmdunderrequires(ecosystem-commands contract 1.4.0). The record still installs nothing..claude/ecosystems/<id>.yaml):bash eng/ci-perf/snapshots/snapshot.test.shshellcheck --rcfile=.shellcheckrc <files>dotnet build MelodicSoftware.GithubIac.slnx --configuration Release --nologo -p:RestoreLockedMode=truedotnet test tests/MelodicSoftware.GithubIac.Tests/MelodicSoftware.GithubIac.Tests.csproj --configuration Release --no-build --no-restoredotnet format whitespaceplusdotnet format style --diagnostics IDE0055, both with--verify-no-changesmarkdownlint-cli2 --config .markdownlint-cli2.jsonc <files>npm run test:governance; no build and no lint command.check-cmdthat runsactionlint, twocheck-jsonschema --builtin-schemacalls (Dependabot, workflows),zizmor --persona=regular --offlineand the runner-policy check (node .github/standards/runner-policy/runner-policy.mjs --root .).typos --config _typos.toml .,gitleaks dir . --config .gitleaks.toml --no-banner --redact, editorconfig-checker-config .editorconfig-checker.json,lychee --offline --no-progress --config lychee.toml '**/*.md'and./eng/check-code-group-covers-roots.sh.requiresentries (yamlcheck-cmd) and their probe results on this host:runner-policy runtime (ajv, yaml):npm ls --all --prefix "$REPO_ROOT/.github/standards/runner-policy". It passes only when the installed tree satisfies that directory's exactajv 8.20.0andyaml 2.9.1pins, the ones CI installs withnpm ci --prefix .github/standards/runner-policy --ignore-scripts, and no dependency is missing.UNMET DEPENDENCY ajv@8.20.0,yaml@2.9.1).actionlint (the kjanat/actionlint fork CI installs):actionlint -version | head -n 1 | grep -q "^actionlint\.kjanat\.dev ". Stock rhysd/actionlint prints only its version on that line, so the probe cannot pass on a stock build. It does pass on any kjanat release, andtool-pinwarns when the release drifts from 1.17.0.actionlint.kjanat.dev 1.17.0).ba673cc,all:/toolchain:check all:Overall: PASS (4 of 4 ecosystems passed).dotnet test: 111 passed, 0 skipped;npm run test:governance: 163 passed, 0 skipped./toolchain:lint all:Overall: INCOMPLETE (4 of 5 ecosystems passed; yaml: skip (prerequisite missing: runner-policy runtime (ajv, yaml))).Run on a checkout with both prerequisites present
0a4f9896ffba94a93c95ae117347c6b59a963d1d(github-iacmainafter PR 905 merged), detached HEAD, clean tree. Nothing was installed for this run; the runner-policy runtime was already present in the checkout.requiresprobes (yamlcheck-cmd, run from the repository root, 30-second timeout):runner-policy runtime (ajv, yaml): present, exit 0.npm lslistsajv@8.20.0(with fast-deep-equal 3.1.3, fast-uri 3.1.9, json-schema-traverse 1.0.0, require-from-string 2.0.2) andyaml@2.9.1, with nothing missing.actionlint (the kjanat/actionlint fork CI installs): present, exit 0 (actionlint.kjanat.dev 1.17.0)./toolchain:lint allcells:check-cmdran and exited 0: actionlint had no output, bothcheck-jsonschemacalls printedok -- validation done, zizmor 1.32.0 printedNo findings to report. Good job! (5 ignored, 3 suppressed)over 11 files, and the runner policy printedRunner policy passed.*.shfiles, no output).dotnet format whitespaceanddotnet format style --diagnostics IDE0055, both--verify-no-changes, exit 0).0 issues in 0 files).no leaks found; editorconfig-checker clean; lychee 486 total, 144 OK, 0 errors, 342 excluded; the root-coverage check passed).—(the record'scheck-cmdis null).skip (opt-in unmet). No ruff config, no PSScriptAnalyzer settings or PowerShell files, and no.golangciconfig or Go module. An opt-in skip does not make a run INCOMPLETE.Overall: PASS (5 of 9 ecosystems passed; typescript: no check-cmd; python, powershell, go: skip (opt-in unmet)). Recorded for treeff3dbe1af02909a216560a1b87906aef322500c5. The earlier run's4 of 5counted only the recorded ecosystems that have a lint command; this count also includes typescript and the three bundled defaults, which the skill counts toward the total.ec3.11.1 (pin 4.0.2). actionlint, shellcheck, node, the .NET SDK, gitleaks and lychee match their pins./toolchain:check(lint only in this run; the earlier check run atba673ccstands).kyle-sexton commentedon Nov 17, 2026
Reopening: the yaml record's actionlint probe in github-iac PR 905 passes on any release of the kjanat fork, not only the release the record's tool-pin names, so it does not probe against the pin as the #16646 Brief's criterion 9 asks. A follow-up pull request tightens it to the fork plus the record's own tool-pin version (the shape agent-automations and songwriting use); this closes again on a rerun after that merges. Posted by an agent session.
kyle-sexton commentedon Nov 17, 2026
The tightened actionlint probe merged in https://github.com/melodic-software/github-iac/pull/906, and a lint run at the new main on a checkout with both prerequisites reads PASS.
344e3530ce0f22ea96c0814d06c78810acf79ef6(github-iacmainafter PR 906).v=$(grep -m 1 "^ actionlint: \"" "$REPO_ROOT/.claude/ecosystems/yaml.yaml" | cut -d "\"" -f 2) && [ -n "$v" ] && actionlint -version | head -n 1 | grep -qxF "actionlint.kjanat.dev $v". It requires the whole first line ofactionlint -versionto equalactionlint.kjanat.dev <tool-pin actionlint>, so it rejects stock actionlint, another fork release and an empty pin.runner-policy runtime (ajv, yaml)(npm ls --all --prefix "$REPO_ROOT/.github/standards/runner-policy"): exit 0; ajv@8.20.0 and yaml@2.9.1 installed.actionlint (the kjanat/actionlint fork release tool-pin names): exit 0;actionlint -versionfirst lineactionlint.kjanat.dev 1.17.0, tool-pin1.17.0.—(the consumer record'scheck-cmdis null).skip (opt-in unmet: no ruff config).skip (opt-in unmet: no PSScriptAnalyzer settings or PowerShell files).skip (opt-in unmet: no .golangci config).Overall: PASS (5 of 9 ecosystems passed; typescript: no check-cmd; python, powershell, go: skip (opt-in unmet))ecv3.11.1 (the binary used) vs pin 4.0.2, witheditorconfig-checkerv3.11.3 also on PATH (cross-cutting)./toolchain:check. The earlier check run atba673ccstands, and the record's commands are unchanged since: betweenba673ccand344e353onlyyaml.yaml's actionlintrequiresentry and its notes changed.Posted by an agent session.