Skip to content

Add ecosystem records to cursor-plugins #15723

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. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Understood: add ecosystem records (.claude/ecosystems/) to the cursor-plugins repository by pull request, so /toolchain:check all there shows no skip (unresolved cell. The steps, decisions and done-when are exact. #15704 is not in the open-issues list, so I treat it as not blocking. Sibling per-repository issues (codex-plugins, agent-plugins, and others) cover other repositories, so this is not a duplicate. I found no merged pull request that already fixes it. The work happens in another repository; the unattended run may need a person for that cross-repository step.

    Automated triage. A maintainer reviews it.

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

  5. 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
  6. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    MemberAuthor

    Delivered; closing.

    • Records: merged in chore: add ecosystem records mirroring CI's checks cursor-plugins#154 and fix: keep the local gitleaks scan in the cross-cutting record cursor-plugins#156 (2026-11-14); CI drift (composite pins and line citations) fixed in fix: cite the current check-managed-files pin and automerge lines in the cross-cutting record cursor-plugins#166 (merged 2026-11-16). Six records on the default branch, each valid against the ecosystem-commands schema.
    • Recorded /toolchain:check all output with the records: in docs: add kindle-dedrm to catalog and note MCP servers in description #166's Verification section, range c12a04f..6d486ef: Overall: PASS (3 of 3 ecosystems passed); /toolchain:lint: Overall: PASS (2 of 2 ecosystems passed). Every selected ecosystem resolved its commands from the repository's own records. No cell reads skip (unresolved; that test passes trivially, since toolchain 1.4.x has no code path that prints the cell.
    • Baseline on the same range, records removed (bundled defaults, toolchain 1.4.1): check reads Overall: FAIL (1 of 3 ecosystems failed): bundled shfmt -d reports formatting diffs in four shell files the range does not touch; powershell and markdown pass. Lint reads Overall: PASS (3 of 3 ecosystems passed). Baseline commands: shellcheck -x -S warning <6 files> && shfmt -d <6 files>; Invoke-ScriptAnalyzer -Path . -Recurse; npx markdownlint-cli2 <8 files>; actionlint; typos, gitleaks detect --source . --redact --no-banner --no-git, editorconfig-checker, lychee --offline --no-progress './**/*.md'. With no shell file in the range, the bash file list is every tracked *.sh file (the lint skill's expansion rule under all).
    • Differences, all intended. Listed in docs(knowledge-integration): spec the apply/integrate skill #154 and feat(ai-briefing): wire grok-capture Wave 0 + address publish-review findings #156: the two shell test suites added; CI's shell file list and bash -n per file; the single-file PSScriptAnalyzer call that fails on findings; the SKILL.md frontmatter check in place of markdownlint; no actionlint; the docs-naming, manifest and relative-link checks added; gitleaks dir . --config .gitleaks.toml; every line counts toward the status. Not itemized there, and following the same rule (the record runs what that repository's required-checks workflow runs): shfmt -d and shellcheck's -x -S warning dropped (CI runs plain shellcheck scripts/*.sh .cursor/install.sh), editorconfig-checker dropped (no CI lane), typos --config _typos.toml --hidden and lychee --config lychee.toml as CI's steps pass them.
    • Tool version on the recording machine that differs from a pin: typos 1.52.2 against 1.50.3; no result changed.
  7. removed
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 16, 2026
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