diff --git a/.claude/ecosystems/bash.yaml b/.claude/ecosystems/bash.yaml new file mode 100644 index 0000000..fb9b429 --- /dev/null +++ b/.claude/ecosystems/bash.yaml @@ -0,0 +1,18 @@ +# Shell in this repository: .claude/cloud-bootstrap.sh, a standards-synced +# file (.github/workflows/pr-check-managed-files-hosted.yml:39). Contract and +# schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# CI runs no shell lint or test: .github/workflows/pr-require-checks.yml has no +# shellcheck step (:73-153). So this record runs no command. +enabled: true +globs: ["*.sh", "*.bash"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: null +fix-cmd: null +code-fix-cmd: null +install-hint: "None: this record runs no command." +tool-pin: {} +gates: [] +notes: "No command because CI has none for shell. Without this file the bundled bash default (claude-code-plugins plugins/toolchain/reference/ecosystems/bash.yaml:7) would run shellcheck and shfmt on a changed shell file: its opt-in says shellcheck always applies to shell files and shfmt applies when .editorconfig declares shell style (:9), which this repository's .editorconfig does (.editorconfig:46-48). The record is enabled: true with null commands rather than enabled: false: the repository holds a shell script, null commands read as not applicable, and false would also drop the lane for code-metrics, which reads enabled (the ecosystem-commands contract README, Consumers). No opt-in key: there is no check-cmd for it to govern. The script's source of truth is melodic-software/standards; check-managed-files, advisory here, fails a pull request that hand-edits it (pr-check-managed-files-hosted.yml:11-22)." diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml new file mode 100644 index 0000000..a6296e8 --- /dev/null +++ b/.claude/ecosystems/cross-cutting.yaml @@ -0,0 +1,23 @@ +# Repository-wide text checks in this repository. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# Lint-only: /toolchain:lint runs it, /toolchain:check does not. The one check +# is CI's lychee job (.github/workflows/pr-require-checks.yml:93-106), the +# lychee-offline composite pinned at melodic-software/ci-workflows@594987a +# (v0.39.8) with this repository's lychee.toml (:104-106). The command is the +# composite's arguments (lychee-offline/action.yml:62) with its default glob +# (:8), which it passes to lychee unexpanded (:72-74). Commands run from the +# repository root. +enabled: true +globs: ["**"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: "lychee --offline --no-progress --config lychee.toml '**/*.md'" +fix-cmd: null +code-fix-cmd: null +opt-in: "lychee.toml at the repository root" +install-hint: "lychee 0.24.2: winget install lycheeverse.lychee | brew install lychee; CI verifies the x86_64-unknown-linux-gnu release archive by SHA-256 1f4e0ef7f6554a6ed33dd7ac144fb2e1bbed98598e7af973042fc5cd43951c9a" +tool-pin: + lychee: "0.24.2" +gates: [] +notes: "Lint-only: owned by /toolchain:lint. Pins at ci-workflows@594987a: lychee-offline/action.yml:19 (version), :24 (checksum), :40 (asset). CI passes no globs or exclude input (pr-require-checks.yml:105-106), so the defaults '**/*.md' and no --exclude-path apply (action.yml:8, :16). The glob is single-quoted so lychee expands it, as in CI; an unquoted ** in a shell without globstar matches one directory level only. check-cmd checks every markdown file, not : an anchor check spans files, so a changed heading breaks links in files the change does not touch. A local run reads the working tree: lychee.toml sets hidden = true and a glob input does not honor .gitignore, so ignored dot-directories other than the excluded .work/ and .claude/worktrees/ are read too (lychee.toml:11-16, :47-58), which CI's clean checkout does not have. No typos, gitleaks or editorconfig-checker command: _typos.toml, .gitleaks.toml, .editorconfig and .editorconfig-checker.json are standards-synced files (pr-check-managed-files-hosted.yml:41-42, :67, :76), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and these records follow CI, not a local hook. Checks with no local form: the pull-request contract check (pr-require-checks.yml:130-133, check-contract@594987a v0.39.8) and the result aggregation (:134-153, aggregate-results@ac4d878) in the ci-status job (:108); they need the pull request. This ci-status job has no draft refusal. Not run locally: the model review lanes pr-review (.github/workflows/pr-review-hosted.yml:74-85) and pr-review-security (.github/workflows/pr-review-security-hosted.yml:67-78), which review the pull request through ci-workflows reusables called at @main, not pinned; both are advisory and skip drafts (pr-review-hosted.yml:37-38, :78; pr-review-security-hosted.yml:44-46, :71). Not run locally: check-managed-files (pr-check-managed-files-hosted.yml:106-127, check-managed-files@8e1076f v0.71.0), which needs a melodic-software/standards checkout and the pull request; it is advisory and not aggregated into ci-status (:20-22). pr-automerge-dependabot (.github/workflows/pr-automerge-dependabot.yml:22-28) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)." diff --git a/.claude/ecosystems/markdown.yaml b/.claude/ecosystems/markdown.yaml new file mode 100644 index 0000000..1a93c9c --- /dev/null +++ b/.claude/ecosystems/markdown.yaml @@ -0,0 +1,18 @@ +# Markdown in this repository: READMEs, docs, rules and skill bodies. Contract +# and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# CI runs no markdown linter: .github/workflows/pr-require-checks.yml has no +# markdownlint step (:73-153). Its only markdown check is the offline link +# check, which runs from cross-cutting.yaml. So this record runs no command. +enabled: true +globs: ["*.md"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: null +fix-cmd: null +code-fix-cmd: null +install-hint: "None: this record runs no command." +tool-pin: {} +gates: [] +notes: "No command because CI has none for markdown lint. Without this file the bundled markdown default (claude-code-plugins plugins/toolchain/reference/ecosystems/markdown.yaml:7) would run markdownlint-cli2 on changed *.md files, because its opt-in, a markdownlint config, is met by .markdownlint-cli2.jsonc; that file is standards-synced (pr-check-managed-files-hosted.yml:72) and no CI job here reads it. The record is enabled: true with null commands rather than enabled: false: the repository holds markdown, null commands read as not applicable, and false would also drop the lane for code-metrics, which reads enabled (the ecosystem-commands contract README, Consumers). No opt-in key: there is no check-cmd for it to govern. CI's node tests read markdown, for example docs/official-docs.md and AGENTS.md (tests/documentation-contract.test.mjs:33, :49); CI runs those tests on every change, and a change to only a *.md file runs no local test (typescript.yaml notes that glob gap)." diff --git a/.claude/ecosystems/python.yaml b/.claude/ecosystems/python.yaml new file mode 100644 index 0000000..1294273 --- /dev/null +++ b/.claude/ecosystems/python.yaml @@ -0,0 +1,18 @@ +# Python in this repository: four skill scripts under +# plugins/codex-operations/skills/, with no pyproject.toml. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# CI builds and lints no Python: .github/workflows/pr-require-checks.yml has no +# Python step (:73-153). Its node tests run the scripts (typescript.yaml). So +# this record runs no command. +enabled: true +globs: ["*.py"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: null +fix-cmd: null +code-fix-cmd: null +install-hint: "None: this record runs no command." +tool-pin: {} +gates: [] +notes: "No command because CI has none for Python. Without this file the bundled python default (claude-code-plugins plugins/toolchain/reference/ecosystems/python.yaml:13-14) would run uv run pytest -x -q and uv run ruff check . --no-fix && uv run ruff format . --check && uv run pyright.The scripts are tested through node: tests/codex-changelog.test.mjs and tests/codex-operations.test.mjs spawn them (tests/codex-changelog.test.mjs:22-26, tests/codex-operations.test.mjs:21-30), and that suite is typescript.yaml's test-cmd, kept there so one change does not run it twice. A change to only a *.py file therefore runs no test locally, while CI runs the node tests on every full event (pr-require-checks.yml:76, :88-89). The record is enabled: true with null commands rather than enabled: false: null commands read as not applicable and stop the bundled Python default, while false would also drop the Python lane for code-metrics, which reads enabled (the ecosystem-commands contract README, Consumers). No opt-in key: there is no check-cmd for it to govern." diff --git a/.claude/ecosystems/typescript.yaml b/.claude/ecosystems/typescript.yaml new file mode 100644 index 0000000..5e5db3b --- /dev/null +++ b/.claude/ecosystems/typescript.yaml @@ -0,0 +1,20 @@ +# JavaScript in this repository: ES modules (*.mjs), no TypeScript and no +# tsconfig. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# The test is CI's validate-marketplace job: npm test, then npm run validate +# (.github/workflows/pr-require-checks.yml:74-91; the scripts are +# package.json:11-12). CI lints no JavaScript and builds none. Commands run +# from the repository root. +enabled: true +globs: ["*.mjs", "package.json"] +project-discovery: [] +build-cmd: null +test-cmd: "npm test && npm run validate" +check-cmd: null +fix-cmd: null +code-fix-cmd: null +install-hint: "node 24 (.node-version, which CI's setup-node reads: pr-require-checks.yml:84-87). package.json declares no dependencies, so there is nothing to install. The Python-backed tests need python, python3 or py -3 on PATH." +tool-pin: + node: "24" +gates: [] +notes: "Pin: .node-version:1 names the major only. .node-version is a standards-synced file (pr-check-managed-files-hosted.yml:73), so a sync can change it and leave this pin behind. The two CI steps run in order with no continue-on-error, so CI stops at the first failure (pr-require-checks.yml:88-91); test-cmd chains them with && for the same reason. node --test exits 0 when a test is skipped; read its skipped count. The tests that run the bundled Python scripts skip when no Python launcher answers --version (tests/helpers.mjs:109-125; tests/codex-changelog.test.mjs:22-23, tests/codex-operations.test.mjs:21-22), and the symlink and POSIX-shim tests skip on Windows (plugins/plugin-ops/skills/verify-plugin/scripts/validate-marketplace.test.mjs:661; tests/codex-changelog.test.mjs:229). A local run reads the working tree: npm run validate lists directories with readdir, not git (validate-marketplace.mjs:109-111), so an untracked file under a plugin can raise a finding CI's clean checkout does not. These tests also exercise the *.py scripts; python.yaml runs no command of its own. Glob gaps: CI's validate-marketplace job has no path filter (pr-require-checks.yml:76), so CI runs these tests on every change; these globs select only *.mjs and package.json, so a change to any other file runs no local test, for example a SKILL.md, a plugin.json, .agents/plugins/marketplace.json, a *.py script, a test fixture, .node-version, a plugin's agents/openai.yaml (tests/helpers.mjs:39), or docs/*.md, AGENTS.md and README.md (tests/documentation-contract.test.mjs:33, :49, :103)." diff --git a/.claude/ecosystems/yaml.yaml b/.claude/ecosystems/yaml.yaml new file mode 100644 index 0000000..a9d5657 --- /dev/null +++ b/.claude/ecosystems/yaml.yaml @@ -0,0 +1,17 @@ +# GitHub Actions workflows and Dependabot config in this repository. Contract +# and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# CI lints no workflow: .github/workflows/pr-require-checks.yml has no +# actionlint, schema or zizmor step (:73-153). So this record runs no command. +enabled: true +globs: [".github/**/*.yml", ".github/**/*.yaml"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: null +fix-cmd: null +code-fix-cmd: null +install-hint: "None: this record runs no command." +tool-pin: {} +gates: [] +notes: "No command because CI has none for workflow lint. Without this file the bundled yaml default (claude-code-plugins plugins/toolchain/reference/ecosystems/yaml.yaml:8-9) would run actionlint, because its opt-in, GitHub Actions workflows present, is met. The record is enabled: true with null commands rather than enabled: false: the repository holds workflows, null commands read as not applicable, and false would also drop the lane for code-metrics, which reads enabled (the ecosystem-commands contract README, Consumers). No opt-in key: there is no check-cmd for it to govern. The workflows' CI-only checks are listed in cross-cutting.yaml's notes. The plugins' agents/openai.yaml sidecars are outside these globs; CI's node tests read them (tests/helpers.mjs:39) on every change, and a change to only a sidecar runs no local test (typescript.yaml notes that glob gap)."