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: Low
Uncertainty: Known
Flags: none
Blocked by: none
Decision comment (#15718 (comment)):
This decision settles the open questions, so none are asked again.
What I understood: add ecosystem records by pull request in melodic-software/provisioning so
/toolchain:check allshows no unresolved cell. Siblings under #15703 follow the same pattern (#15719, #15717). Steps that need a host run are routed separately and don't hold this triage.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 13, 2026
Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Nov 13, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: confirmed; its comment says why.melodic-automation-lanes commentedon Nov 13, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Add .claude/ecosystems/ records via a pull request in one named owner repository so /toolchain:check all there shows no skip (unresolved) cell.
Related work
Open questions
RECOMMENDED: Target repository: melodic-software/provisioning, if a repository by that name has a Claude lane workflow and no records; otherwise retitle the item with the correct name. Basis: Sibling candidates #15713, #15714, #15717, #15719 to #15722, #15725 and #15727 each end their title with a repository name, which suggests provisioning is the target here.
RECOMMENDED: Confirm #15704 is closed as completed and the records and baseline landed on the default branch; if #15927 was closed without merging, wait for the replacement before starting. Basis: 15927
RECOMMENDED: Leave it to a builder or host session with write access to the target repository, and keep the unattended lane to verification only. Basis: judgment
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Nov 14, 2026
Decision recorded. Target repository: melodic-software/provisioning
Agent choice, not an owner answer (GitHub Support session).
The triage question was which repository this item covers. The title already names it: "Add ecosystem records to provisioning" is
melodic-software/provisioning, in the same title form as the 14 sibling items under #15703 (for example #15719 "standards", #15717 "github-iac"), which intake triaged without this question.melodic-software/provisioningadds the.claude/ecosystems/records/toolchain:check allin that repository shows noskip (unresolved: ...)cellkyle-sexton commentedon Nov 16, 2026
Delivered; closing.
enabled: falsebecause that CI has no Python lane), each valid against the ecosystem-commands schema. Each command and pin follows that repository's CI; the differences from the bundled defaults, and the places a record differs from CI on purpose, are listed in the pull request's Fix section./toolchain:check alloutput: in tooling: gh CLI --json/--jq body fetch + bash redirect silently mojibake-corrupts UTF-8 em-dashes on write-back (durable tracker content at risk) #1037's Verification section, on commit range04c7bc0..ce356d6. With the records it readsOverall: PASS (4 of 4 ecosystems passed)and holds noskip (unresolvedcell.