Skip to content

Add ecosystem records to songwriting #15721

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

    The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).

  5. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    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 all there should then show no skip (unresolved cell. 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.

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

  8. removed
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 14, 2026
  9. kyle-sexton commented on Nov 14, 2026

    @kyle-sexton
    MemberAuthor

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

  10. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

    Delivered; closing.

    • Records: merged in https://github.com/melodic-software/songwriting/pull/58 (squash b15e857). Six records on the default branch: bash, cross-cutting, markdown, python (every command null), typescript (disabled) and yaml. Each is valid against the ecosystem-commands schema: check-jsonschema printed ok -- validation done, re-run 2026-11-16 on the default branch at 8e4b7ba.
    • Range: e1acf55e197b65e629c17c70415389d747a3ea47..8e4b7baf5e9135d1d93d6ee0e75dcbcff15e7686 on 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.
      • It changes 86 files: 2 shell scripts, 3 Python scripts, 54 Markdown files, 7 workflow and Actions config files, package.json and package-lock.json.
      • Both skills were given this changed-file list. The baseline runs got 80 files, because the six record files were absent from that tree.
    • Recorded output with the records:
      • /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)
      • Every command that ran came from the repository's own records.
      • PowerShell, .NET and Go have no record and fall back to bundled defaults, which ran nothing: the repository has no PowerShell file, no project and no go.mod.
      • No cell reads skip (unresolved. That test cannot fail: toolchain 1.4.3 has no code path that prints the cell. Its skip classes are tool missing, dependencies missing, unsupported and opt-in unmet.
    • Baseline on the same range, records removed (bundled defaults):
      • Check: 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))
      • Lint: Overall: FAIL (1 of 6 ecosystems failed; cross-cutting: lychee 114 errors in 26 inputs, all under node_modules/)
      • Both lychee failures are in node_modules/. The worktree setup's npm ci installed it, and it is gitignored. The repository's own Markdown is clean.
      • The two pairs of Overall lines count differently. The baseline lines count every ecosystem row shown, including .NET and Go with no project. The lines with the records count only ecosystems that ran a command.
      • Baseline commands:
        • uv run pytest -x -q
        • shellcheck -x -S warning <2 files> && shfmt -d <2 files>
        • npx markdownlint-cli2 <54 files>
        • actionlint
        • typos
        • gitleaks detect --source . --redact --no-banner --no-git
        • editorconfig-checker
        • lychee --offline --no-progress './**/*.md'
      • Python lint and TypeScript were skipped because their opt-in conditions were not met.
    • Differences between the two command lists, all intended.
      • Listed in PR 58:
        • Python's commands are null, so the bundled uv run pytest no longer runs.
        • TypeScript is disabled.
        • markdownlint runs from PATH, not through npx.
        • shellcheck and markdownlint take <files>.
        • No editorconfig-checker run, because CI turns that lane off.
        • No lychee run, because its ruleset lives in ci-workflows.
      • Not itemized in PR 58, but each follows the rule that the record runs what the required-checks workflow runs:
        • shellcheck runs with --rcfile=.shellcheckrc and without -x -S warning, and shfmt -d is gone, because CI has no shfmt lane.
        • markdownlint runs with --config .markdownlint-cli2.jsonc.
        • typos runs as typos --config _typos.toml ..
        • gitleaks runs as gitleaks dir . --config .gitleaks.toml --no-banner --redact.
      • Both baseline FAILs come from lanes the records drop for those reasons.
    • CI drift since the records merged:
  11. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

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

  12. kyle-sexton commented on Nov 17, 2026

    @kyle-sexton
    MemberAuthor

    Prerequisite declared; record run on a host with the CI build.

    • Change: the songwriting yaml record declares the actionlint fork build under requires (ecosystem-commands contract 1.4.0), in https://github.com/melodic-software/songwriting/pull/68.
    • Toolchain: toolchain 1.6.0, skill files followed from the installed plugin directory; the session had an older version loaded.
    • Commands per ecosystem, from songwriting's own records:
      • bash: shellcheck --rcfile=.shellcheckrc <files>
      • markdown: markdownlint-cli2 --config .markdownlint-cli2.jsonc <files>
      • yaml (lint only): actionlint
      • cross-cutting (lint only): typos --config _typos.toml ., then gitleaks dir . --config .gitleaks.toml --no-banner --redact
      • python: every command null. typescript: enabled: false.
      • powershell, dotnet and go have no record. They fall back to bundled defaults, which ran nothing: there are no PowerShell files, no project and no go.mod.
    • requires entries:
      • yaml check-cmd: actionlint (the kjanat build tool-pin names). The probe reads tool-pin.actionlint from the record and passes only when the first line of actionlint -version is exactly actionlint.kjanat.dev <version>. Stock rhysd/actionlint prints the bare version there (command.go:164-165), so it cannot pass.
      • Probe result on this host: exit 0 (present; actionlint.kjanat.dev 1.17.0, pin 1.17.0). The same filter rejected 1.7.12, actionlint.kjanat.dev 1.16.0 and an empty pin.
    • Schema: check-jsonschema against the contract schema: ok -- validation done.
    • Recorded output:
      • /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:lint on 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)
      • No cell reads 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.
    • Not-run path: the same probe, pointed at a copy of the record pinned to 1.16.0, exits 1 against the real binary. That cell would read skip (prerequisite missing: actionlint (the kjanat build tool-pin names)), with Overall INCOMPLETE and no FAIL.
    • Limit: the probe trusts what the binary reports about itself. CI's SHA-256 check covers the release tarball and has no local equivalent.
    • Tool-pin drift warning: typos 1.52.2 ran against pin 1.50.3. actionlint matched its pin.
    • Merged: pull request 68 merged 2026-11-17 as the head this run recorded. Posted by an agent session.
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