diff --git a/.claude/ecosystems/bash.yaml b/.claude/ecosystems/bash.yaml new file mode 100644 index 0000000..84c212b --- /dev/null +++ b/.claude/ecosystems/bash.yaml @@ -0,0 +1,24 @@ +# Shell in this repository: .claude/cloud-bootstrap.sh (standards-synced) and +# .cursor/install.sh. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# Lint is the check-scripts-and-manifests job of +# .github/workflows/pr-require-checks.yml (:84-106): shellcheck (:96-97) and +# bash -n (:98-102) over both scripts. Commands run from the repository root. +enabled: true +globs: ["*.sh", "*.bash"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: | + rc=0 + shellcheck .claude/cloud-bootstrap.sh .cursor/install.sh || rc=1 + bash -n .claude/cloud-bootstrap.sh || rc=1 + bash -n .cursor/install.sh || rc=1 + test "$rc" -eq 0 +fix-cmd: null +code-fix-cmd: null +opt-in: "shellcheck and bash -n always apply to CI's two shell files" +install-hint: "shellcheck with no version pin: CI uses the shellcheck preinstalled on the ubuntu-24.04 runner image and installs none (pr-require-checks.yml:87, :94-95), so no checksum is verified. winget install ShellCheck.ShellCheck | brew install shellcheck. bash -n needs bash." +tool-pin: {} +gates: [] +notes: "No tool-pin: CI installs no shellcheck and uses the runner image's, so its version follows the ubuntu-24.04 image (pr-require-checks.yml:87, :94-95). check-cmd passes shellcheck the same two files and no flags, as CI does (:96-97); this repository tracks no .shellcheckrc. check-cmd lints CI's file list, not : no job in this workflow has a path filter (:12-37), so CI runs both steps on every change; the steps read only the two scripts, which these globs select. The file list copies CI's (:97, :100); when CI's list changes, change it here. Deviations: CI's bash -n step is a for loop in a run step with no shell key, which runs under bash -e and stops at the first file that fails (:98-102), and the job stops at its first failing step; check-cmd unrolls the loop, runs shellcheck and both bash -n calls, and fails when any fails. No shfmt: the bundled bash default (claude-code-plugins plugins/toolchain/reference/ecosystems/bash.yaml:7-8) runs shfmt -d and shfmt -w when .editorconfig declares shell style (:9), which this repository's .editorconfig does (.editorconfig:44-48); CI runs no shfmt, so check-cmd and fix-cmd replace those commands and fix-cmd is null. No test-cmd: CI runs no shell tests." diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml new file mode 100644 index 0000000..de91940 --- /dev/null +++ b/.claude/ecosystems/cross-cutting.yaml @@ -0,0 +1,29 @@ +# Repository-wide 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. Each line is a +# step of .github/workflows/pr-require-checks.yml, in its job order: the +# manifest jq check (check-scripts-and-manifests job, :103-106) and lychee +# (lychee job, :118-121), a composite pinned at +# melodic-software/ci-workflows@594987a (v0.39.8). Every check runs and any +# failure fails the command. Commands run from the repository root. +enabled: true +globs: ["**"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: | + rc=0 + jq empty .claude/settings.json || rc=1 + jq empty .cursor/environment.json || rc=1 + lychee --offline --no-progress --config lychee.toml '**/*.md' || rc=1 + test "$rc" -eq 0 +fix-cmd: null +code-fix-cmd: null +opt-in: "lychee.toml at the repository root for lychee; the jq checks always apply" +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 + jq: winget install jqlang.jq | brew install jq; CI uses the jq preinstalled on the ubuntu-24.04 runner image and installs none (pr-require-checks.yml:94-95). +tool-pin: + lychee: "0.24.2" +gates: [] +notes: "Lint-only: owned by /toolchain:lint. Composite lines at ci-workflows@594987a: lychee-offline/action.yml:8, :11, :16, :62 and :74, pins :19 (version) and :24 (checksum), asset :40. The lychee step passes only the input config: lychee.toml (pr-require-checks.yml:118-121), so the defaults '**/*.md' and no --exclude-path apply (lychee-offline/action.yml:8, :16); the glob is single-quoted so lychee expands it, as in CI. jq has no tool-pin: CI uses the runner image's jq (pr-require-checks.yml:94-95). Deviations: CI's jq step runs two jq calls in a run step with no shell key, under bash -e, so it stops at the first failure (:103-106), and the job stops at its first failing step; check-cmd keeps the two separate calls, because one jq call over several files reads them as one stream, so two truncated files could pass together, and runs every check, failing when any fails. No check reads : jq reads its two named manifests and lychee all markdown, as CI does on every change, since no job in this workflow has a path filter (:12-37). The jq file list copies CI's (:105-106); when CI's list changes, change it here. Links span files, so a renamed file or heading breaks links in files the change does not touch. A local run reads the working tree, where lychee can raise findings CI's clean checkout does not: lychee.toml sets hidden = true and a glob input does not honor .gitignore (lychee.toml:11-16), so an untracked *.md is checked unless it sits under a path lychee.toml excludes (:47-58), for example .work/ or .claude/worktrees/. No typos, gitleaks or editorconfig-checker command: without this file the bundled cross-cutting default (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:10-16) would run all three, because their configs, _typos.toml, .gitleaks.toml and .editorconfig-checker.json, meet its opt-in (:18); those are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:6-10; .github/workflows/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; these records follow CI, not a local hook. Checks with no local form: the pull-request contract check (pr-require-checks.yml:145-150, check-contract@594987a v0.39.8) and the result aggregation (:151-170, aggregate-results@ac4d878) in the ci-status job (:123-170); 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, :76-78; pr-review-security-hosted.yml:44-46, :69-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:21-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..4846012 --- /dev/null +++ b/.claude/ecosystems/markdown.yaml @@ -0,0 +1,18 @@ +# Markdown in this repository: README.md, AGENTS.md, CLAUDE.md and the +# standards-synced REVIEW.md. 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 (:84-170). Its offline link check 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-8) would run markdownlint-cli2 on changed *.md files, because its opt-in, a markdownlint config (:9), is met by .markdownlint-cli2.jsonc; that file is standards-synced (.github/workflows/pr-check-managed-files-hosted.yml:72) and CI deliberately does not re-lint with it (pr-require-checks.yml:6-10). 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 lychee job checks the links and anchors in these files (pr-require-checks.yml:108-121), and that check runs from cross-cutting.yaml." diff --git a/.claude/ecosystems/yaml.yaml b/.claude/ecosystems/yaml.yaml new file mode 100644 index 0000000..50f3692 --- /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 (:84-170). 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-11) would run actionlint, because its opt-in, GitHub Actions workflows present (:13), 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' checks with no local form are listed in cross-cutting.yaml's notes. These globs, the bundled default's, do not select lefthook.yml or docs/conventions/source-control/commit-convention.yml; CI lints neither, so no command is lost."