From 12b19698009311b5880be46b5638b85598436dda Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sat, 14 Nov 2026 04:40:52 -0500 Subject: [PATCH 1/2] chore: add ecosystem records for toolchain commands Add .claude/ecosystems/ records (bash, powershell, markdown, yaml, typescript, cross-cutting) so /toolchain:check and /toolchain:lint resolve this repository's own commands instead of the toolchain plugin's bundled defaults. The records mirror CI's checks in pr-require-checks.yml, cited by file:line; each deviation, each check not run locally and each glob gap is listed in that record's notes. The typescript and yaml records run no command and stop the bundled defaults, because CI runs no lint or build for those files and its schema step is not run locally. Refs: melodic-software/claude-code-plugins#15723 Co-Authored-By: Claude Opus 5.5 --- .claude/ecosystems/bash.yaml | 24 ++++++++++++ .claude/ecosystems/cross-cutting.yaml | 53 +++++++++++++++++++++++++++ .claude/ecosystems/markdown.yaml | 28 ++++++++++++++ .claude/ecosystems/powershell.yaml | 22 +++++++++++ .claude/ecosystems/typescript.yaml | 19 ++++++++++ .claude/ecosystems/yaml.yaml | 17 +++++++++ 6 files changed, 163 insertions(+) create mode 100644 .claude/ecosystems/bash.yaml create mode 100644 .claude/ecosystems/cross-cutting.yaml create mode 100644 .claude/ecosystems/markdown.yaml create mode 100644 .claude/ecosystems/powershell.yaml create mode 100644 .claude/ecosystems/typescript.yaml create mode 100644 .claude/ecosystems/yaml.yaml diff --git a/.claude/ecosystems/bash.yaml b/.claude/ecosystems/bash.yaml new file mode 100644 index 0000000..c77520d --- /dev/null +++ b/.claude/ecosystems/bash.yaml @@ -0,0 +1,24 @@ +# Shell in this repository: scripts/*.sh, .cursor/install.sh and the +# standards-synced .claude/cloud-bootstrap.sh. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# Lint and tests are CI's test-shell job (.github/workflows/pr-require-checks.yml:92-120): +# shellcheck and bash -n over scripts/*.sh and .cursor/install.sh (:105-109), +# then the sync-local and docs-naming regression suites (:113-117). Commands +# run from the repository root. +enabled: true +globs: ["*.sh", "*.bash"] +project-discovery: [] +build-cmd: null +test-cmd: "bash scripts/test-sync-local.sh && bash scripts/test-check-docs-naming.sh" +check-cmd: | + rc=0 + shellcheck scripts/*.sh .cursor/install.sh || rc=1 + for f in scripts/*.sh .cursor/install.sh; do bash -n "$f" || rc=1; done + test "$rc" -eq 0 +fix-cmd: null +code-fix-cmd: null +opt-in: "shellcheck and bash -n always apply to CI's shell file list" +install-hint: "shellcheck with no version pin: CI runs sudo apt-get install -y shellcheck on ubuntu-latest (pr-require-checks.yml:96, :102-103) and verifies no checksum. winget install ShellCheck.ShellCheck | brew install shellcheck. The sync-local suite also needs git and python3 (AGENTS.md:36, :93-96), and pwsh for its PowerShell half." +tool-pin: {} +gates: [] +notes: "No tool-pin: CI installs Ubuntu's shellcheck package, so its version follows the runner image (pr-require-checks.yml:102-103). check-cmd lints CI's file list, not : CI runs shellcheck and bash -n over scripts/*.sh and .cursor/install.sh on every change (:105-109) and leaves out .claude/cloud-bootstrap.sh, a standards-synced file (.github/workflows/pr-check-managed-files-hosted.yml:39), which would lint. No --rcfile: shellcheck reads the root .shellcheckrc by itself, as in CI. AGENTS.md's shell line names only scripts/sync-local.sh and .cursor/install.sh (AGENTS.md:42-43); this record follows CI. CI stops at its first failing step; check-cmd runs shellcheck and bash -n over every listed file and fails when any fails. The two test steps run in order with no continue-on-error (:113-117), so CI stops at the first failure and test-cmd chains them with &&. test-sync-local.sh exits 0 when pwsh is missing: the PowerShell half reports as skipped and the bash half still runs (scripts/test-sync-local.sh:10-12, :99-100, :498-504); read its skipped count. Both suites build their fixtures under TMPDIR (scripts/test-sync-local.sh:38, scripts/test-check-docs-naming.sh:10). scripts/check-docs-naming.sh --check, the last step of the same job (:119-120), runs from cross-cutting.yaml, so a docs/ change triggers it. Glob gaps: no job in this workflow has a path filter (:15-37), so CI runs these steps on every change; these globs select only *.sh and *.bash, so a change to another file the suites read runs no local test, for example scripts/sync-local.ps1, the twin the sync-local suite runs (scripts/test-sync-local.sh:28), or .cursor-plugin/marketplace.json and the plugins/ tree, which its repo-dry-run case syncs from (:198)." diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml new file mode 100644 index 0000000..3468e30 --- /dev/null +++ b/.claude/ecosystems/cross-cutting.yaml @@ -0,0 +1,53 @@ +# 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 docs +# naming check (test-shell job, :119-120), the manifest jq check +# (validate-manifests job, :166-169), the relative-link check (check-links job, +# :220-239), lychee (lychee job, :255-258) and typos (typos job, :272-276). The +# last two are composites 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, in bash. +enabled: true +globs: ["**"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: | + rc=0 + bash scripts/check-docs-naming.sh --check || rc=1 + jq empty .cursor-plugin/marketplace.json || rc=1 + for f in plugins/*/.cursor-plugin/plugin.json; do jq empty "$f" || rc=1; done + ( + status=0 + while IFS= read -r src; do + dir=$(dirname "$src") + while IFS= read -r link; do + case "$link" in http*|mailto:*|'') continue ;; esac + target=${link%%#*} + [ -z "$target" ] && continue + if [ ! -e "$dir/$target" ]; then + echo "::error file=$src::broken relative link -> $link" + status=1 + fi + done < <(sed 's/`[^`]*`//g' "$src" | + grep -oE '\]\([^)#][^)]*\)' | + sed 's/^](//; s/)$//') + done < <(git ls-files '*.md') + exit $status + ) || rc=1 + lychee --offline --no-progress --config lychee.toml '**/*.md' || rc=1 + typos --config _typos.toml --hidden --exclude '.git/' . || rc=1 + test "$rc" -eq 0 +fix-cmd: null +code-fix-cmd: null +opt-in: "lychee.toml and _typos.toml at the repository root for lychee and typos; the docs-naming, jq and relative-link 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 + typos 1.50.3: winget install Crate-CI.Typos | brew install typos-cli; CI verifies the x86_64-unknown-linux-musl release archive by SHA-256 aca6b5d546307092b8d0a8e0a89dd80f9da51f2f7617c5e45c5607c1684ffbf2 + jq: winget install jqlang.jq | brew install jq; CI uses the runner's jq and installs none (pr-require-checks.yml:166-169). The relative-link check needs bash, git, sed and grep. +tool-pin: + lychee: "0.24.2" + typos: "1.50.3" +gates: [] +notes: "Lint-only: owned by /toolchain:lint. Composite lines at ci-workflows@594987a: lychee-offline/action.yml:8, :11, :62 and :74, pins :19 (version) and :24 (checksum); typos/action.yml:9, :12, :98 and :116, pins :46 and :51. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (typos/action.yml:98). CI's typos step also emits annotations from a second json pass (typos/action.yml:105-110); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), 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. Deviations: the relative-link check is CI's script with its comments dropped, inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not : CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks 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 it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); 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 (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. No gitleaks, editorconfig-checker or markdownlint command: .gitleaks.toml, .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :67, :72), 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. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract@594987a v0.39.8) and the result aggregation (:307-326, aggregate-results@ac4d878) in the ci-status job (:281-283); 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, :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..bcb7710 --- /dev/null +++ b/.claude/ecosystems/markdown.yaml @@ -0,0 +1,28 @@ +# Markdown in this repository: READMEs, docs, plugin references and skill +# bodies. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# The check is CI's skill-frontmatter step in the validate-manifests job +# (.github/workflows/pr-require-checks.yml:171-180). CI runs no markdown +# linter; its link checks run from cross-cutting.yaml. Commands run from the +# repository root. +enabled: true +globs: ["*.md"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: | + status=0 + for f in plugins/*/skills/*/SKILL.md; do + if [ "$(head -1 "$f")" != "---" ]; then + echo "::error file=$f::SKILL.md must start with a --- YAML frontmatter block" + status=1 + fi + done + test "$status" -eq 0 +fix-cmd: null +code-fix-cmd: null +opt-in: "always applies to plugins/*/skills/*/SKILL.md; the check needs no config" +install-hint: "None: the command uses only the shell and head." +tool-pin: {} +gates: [] +notes: "check-cmd is CI's step verbatim except its last line, test in place of exit, so the command does not end the shell that runs it. It checks every plugins/*/skills/*/SKILL.md, not , as CI does on every change. The glob expands on disk, so a local run also checks an untracked SKILL.md, which CI's clean checkout does not have. No markdownlint: 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 (: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 lint with it (pr-require-checks.yml:7-13). fix-cmd is null: CI has no markdown fix step. No job in this workflow has a path filter (:15-37), so CI runs this step on every change; the step reads only SKILL.md files, which these globs select." diff --git a/.claude/ecosystems/powershell.yaml b/.claude/ecosystems/powershell.yaml new file mode 100644 index 0000000..19e34f7 --- /dev/null +++ b/.claude/ecosystems/powershell.yaml @@ -0,0 +1,22 @@ +# PowerShell in this repository: scripts/sync-local.ps1, the twin of +# scripts/sync-local.sh. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# Lint is CI's psscriptanalyzer job (.github/workflows/pr-require-checks.yml:122-154): +# Invoke-ScriptAnalyzer on scripts/sync-local.ps1 with no settings file, +# failing on any finding (:149-153). CI runs no PowerShell test of its own; +# the sync-local suite in bash.yaml's test-cmd runs this script. Commands run +# from the repository root. +enabled: true +globs: ["*.ps1", "*.psm1"] +project-discovery: [] +build-cmd: null +test-cmd: null +check-cmd: | + pwsh -NoProfile -Command '$ErrorActionPreference = "Stop"; $findings = Invoke-ScriptAnalyzer -Path ./scripts/sync-local.ps1; if ($findings) { $findings | Format-Table Severity, RuleName, Line, Message -AutoSize -Wrap | Out-String | Write-Host; throw "PSScriptAnalyzer reported $($findings.Count) finding(s)." }; Write-Host "PSScriptAnalyzer: 0 findings."' +fix-cmd: null +code-fix-cmd: null +opt-in: "PSScriptAnalyzer always applies to scripts/sync-local.ps1; CI uses no settings file" +install-hint: "pwsh, then Install-Module PSScriptAnalyzer -Scope CurrentUser -Force, as CI runs it from PSGallery with no version pin (pr-require-checks.yml:132-136); CI verifies no checksum." +tool-pin: {} +gates: [] +notes: "No tool-pin: CI installs the current PSGallery release of PSScriptAnalyzer (pr-require-checks.yml:136). check-cmd is CI's analyzer call (:149-154) with two deviations. It sets $ErrorActionPreference to Stop: without it a missing PSScriptAnalyzer module leaves $findings empty and pwsh exits 0 after printing 0 findings, while CI always has the module from the step before (:132-136). The -SuppressedOnly listing (:144-148) only prints the deliberate suppressions and does not change the result, so it is left out. check-cmd analyzes CI's one path, not , as CI does on every change; the repository holds no other PowerShell file. fix-cmd is null: CI has no format step. Glob gap: no job in this workflow has a path filter (:15-37), so CI runs the sync-local suite on every change; that suite runs this script beside its bash twin (scripts/test-sync-local.sh:4-6, :28) and is bash.yaml's test-cmd, so a change to only scripts/sync-local.ps1 runs no local test." diff --git a/.claude/ecosystems/typescript.yaml b/.claude/ecosystems/typescript.yaml new file mode 100644 index 0000000..3b26c2c --- /dev/null +++ b/.claude/ecosystems/typescript.yaml @@ -0,0 +1,19 @@ +# JavaScript in this repository: two ES modules, scripts/validate-manifests.mjs +# and scripts/validate-environment.mjs; no TypeScript, no tsconfig and no +# package.json. Contract and schema: +# https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands +# CI runs these scripts in the validate-manifests job's schema step +# (.github/workflows/pr-require-checks.yml:187-200), which is not run locally +# (notes). CI lints and builds no JavaScript. So this record runs no command. +enabled: true +globs: ["*.mjs"] +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: "Not run locally: CI's schema step (pr-require-checks.yml:187-200). It runs npm init -y and npm install ajv@8 ajv-formats in the repository root, which write package.json, package-lock.json and node_modules/ there, and curl writes marketplace.schema.json, plugin.schema.json and environment.schema.json there (:190-199), because the scripts read the schemas from the working directory (scripts/validate-manifests.mjs:13-15, scripts/validate-environment.mjs:9-10). .gitignore covers only node_modules/ of those (.gitignore:7), so a local run would leave a package.json, a package-lock.json and three schema files untracked in the tree. CI also fetches the schemas live from cursor/plugins main and cursor.com, and installs ajv@8 and ajv-formats with no exact version, so its result can change with no commit here. No opt-in key: there is no check-cmd for it to govern. Without this file the bundled typescript default (claude-code-plugins plugins/toolchain/reference/ecosystems/typescript.yaml:10, whose globs match *.mjs) would run its tsc, test and Biome commands (:12-14). The record is enabled: true with null commands rather than enabled: false: the repository holds JavaScript source, 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). The same job's jq step (:166-169) runs from cross-cutting.yaml and its skill-frontmatter step (:171-180) from markdown.yaml. Glob gap: no job in this workflow has a path filter (:15-37), so CI runs the schema step on every change; locally no record validates the manifests or .cursor/environment.json against Cursor's schemas, so a change to, for example, .cursor-plugin/marketplace.json, a plugins/*/.cursor-plugin/plugin.json or .cursor/environment.json gets only cross-cutting.yaml's jq syntax check, which does not read .cursor/environment.json." diff --git a/.claude/ecosystems/yaml.yaml b/.claude/ecosystems/yaml.yaml new file mode 100644 index 0000000..fe7039a --- /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 (:91-326). 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. CI's typos lane spell-checks these files too (pr-require-checks.yml:272-276), and that check runs from cross-cutting.yaml." From 2d8a602d0b84de68b4a85a26981e06f3427e3688 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sat, 14 Nov 2026 04:44:28 -0500 Subject: [PATCH 2/2] fix: keep the inline check results out of zsh's read-only status The markdown frontmatter check and the cross-cutting relative-link check copied CI's result variable, status, which zsh holds read-only, so under zsh the assignment failed and the check could pass with a failing file. Name the variable fail in both records and say so in their notes. The powershell record's notes now say GitHub prepends $ErrorActionPreference = 'stop' to a pwsh step, so setting it in check-cmd matches CI; the -SuppressedOnly listing stays the deviation. Refs: melodic-software/claude-code-plugins#15723 Co-Authored-By: Claude Opus 5.5 --- .claude/ecosystems/cross-cutting.yaml | 12 ++++++------ .claude/ecosystems/markdown.yaml | 8 ++++---- .claude/ecosystems/powershell.yaml | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml index 3468e30..469bc3f 100644 --- a/.claude/ecosystems/cross-cutting.yaml +++ b/.claude/ecosystems/cross-cutting.yaml @@ -7,7 +7,7 @@ # :220-239), lychee (lychee job, :255-258) and typos (typos job, :272-276). The # last two are composites 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, in bash. +# from the repository root, in bash or zsh. enabled: true globs: ["**"] project-discovery: [] @@ -19,7 +19,7 @@ check-cmd: | jq empty .cursor-plugin/marketplace.json || rc=1 for f in plugins/*/.cursor-plugin/plugin.json; do jq empty "$f" || rc=1; done ( - status=0 + fail=0 while IFS= read -r src; do dir=$(dirname "$src") while IFS= read -r link; do @@ -28,13 +28,13 @@ check-cmd: | [ -z "$target" ] && continue if [ ! -e "$dir/$target" ]; then echo "::error file=$src::broken relative link -> $link" - status=1 + fail=1 fi done < <(sed 's/`[^`]*`//g' "$src" | grep -oE '\]\([^)#][^)]*\)' | sed 's/^](//; s/)$//') done < <(git ls-files '*.md') - exit $status + exit "$fail" ) || rc=1 lychee --offline --no-progress --config lychee.toml '**/*.md' || rc=1 typos --config _typos.toml --hidden --exclude '.git/' . || rc=1 @@ -45,9 +45,9 @@ opt-in: "lychee.toml and _typos.toml at the repository root for lychee and typos 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 typos 1.50.3: winget install Crate-CI.Typos | brew install typos-cli; CI verifies the x86_64-unknown-linux-musl release archive by SHA-256 aca6b5d546307092b8d0a8e0a89dd80f9da51f2f7617c5e45c5607c1684ffbf2 - jq: winget install jqlang.jq | brew install jq; CI uses the runner's jq and installs none (pr-require-checks.yml:166-169). The relative-link check needs bash, git, sed and grep. + jq: winget install jqlang.jq | brew install jq; CI uses the runner's jq and installs none (pr-require-checks.yml:166-169). The relative-link check needs bash or zsh, git, sed and grep. tool-pin: lychee: "0.24.2" typos: "1.50.3" gates: [] -notes: "Lint-only: owned by /toolchain:lint. Composite lines at ci-workflows@594987a: lychee-offline/action.yml:8, :11, :62 and :74, pins :19 (version) and :24 (checksum); typos/action.yml:9, :12, :98 and :116, pins :46 and :51. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (typos/action.yml:98). CI's typos step also emits annotations from a second json pass (typos/action.yml:105-110); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), 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. Deviations: the relative-link check is CI's script with its comments dropped, inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not : CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks 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 it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); 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 (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. No gitleaks, editorconfig-checker or markdownlint command: .gitleaks.toml, .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :67, :72), 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. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract@594987a v0.39.8) and the result aggregation (:307-326, aggregate-results@ac4d878) in the ci-status job (:281-283); 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, :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)." +notes: "Lint-only: owned by /toolchain:lint. Composite lines at ci-workflows@594987a: lychee-offline/action.yml:8, :11, :62 and :74, pins :19 (version) and :24 (checksum); typos/action.yml:9, :12, :98 and :116, pins :46 and :51. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (typos/action.yml:98). CI's typos step also emits annotations from a second json pass (typos/action.yml:105-110); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), 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. Deviations: the relative-link check is CI's script with its comments dropped, its result variable named fail, not status, which zsh holds read-only, and the whole inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash or zsh, not sh. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not : CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks 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 it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); 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 (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. No gitleaks, editorconfig-checker or markdownlint command: .gitleaks.toml, .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :67, :72), 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. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract@594987a v0.39.8) and the result aggregation (:307-326, aggregate-results@ac4d878) in the ci-status job (:281-283); 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, :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 index bcb7710..686c948 100644 --- a/.claude/ecosystems/markdown.yaml +++ b/.claude/ecosystems/markdown.yaml @@ -11,18 +11,18 @@ project-discovery: [] build-cmd: null test-cmd: null check-cmd: | - status=0 + fail=0 for f in plugins/*/skills/*/SKILL.md; do if [ "$(head -1 "$f")" != "---" ]; then echo "::error file=$f::SKILL.md must start with a --- YAML frontmatter block" - status=1 + fail=1 fi done - test "$status" -eq 0 + test "$fail" -eq 0 fix-cmd: null code-fix-cmd: null opt-in: "always applies to plugins/*/skills/*/SKILL.md; the check needs no config" install-hint: "None: the command uses only the shell and head." tool-pin: {} gates: [] -notes: "check-cmd is CI's step verbatim except its last line, test in place of exit, so the command does not end the shell that runs it. It checks every plugins/*/skills/*/SKILL.md, not , as CI does on every change. The glob expands on disk, so a local run also checks an untracked SKILL.md, which CI's clean checkout does not have. No markdownlint: 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 (: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 lint with it (pr-require-checks.yml:7-13). fix-cmd is null: CI has no markdown fix step. No job in this workflow has a path filter (:15-37), so CI runs this step on every change; the step reads only SKILL.md files, which these globs select." +notes: "check-cmd is CI's step with two changes: its result variable is fail, not status, which zsh holds read-only, and its last line is test in place of exit, so the command does not end the shell that runs it. It checks every plugins/*/skills/*/SKILL.md, not , as CI does on every change. The glob expands on disk, so a local run also checks an untracked SKILL.md, which CI's clean checkout does not have. No markdownlint: 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 (: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 lint with it (pr-require-checks.yml:7-13). fix-cmd is null: CI has no markdown fix step. No job in this workflow has a path filter (:15-37), so CI runs this step on every change; the step reads only SKILL.md files, which these globs select." diff --git a/.claude/ecosystems/powershell.yaml b/.claude/ecosystems/powershell.yaml index 19e34f7..2a7f6f2 100644 --- a/.claude/ecosystems/powershell.yaml +++ b/.claude/ecosystems/powershell.yaml @@ -19,4 +19,4 @@ opt-in: "PSScriptAnalyzer always applies to scripts/sync-local.ps1; CI uses no s install-hint: "pwsh, then Install-Module PSScriptAnalyzer -Scope CurrentUser -Force, as CI runs it from PSGallery with no version pin (pr-require-checks.yml:132-136); CI verifies no checksum." tool-pin: {} gates: [] -notes: "No tool-pin: CI installs the current PSGallery release of PSScriptAnalyzer (pr-require-checks.yml:136). check-cmd is CI's analyzer call (:149-154) with two deviations. It sets $ErrorActionPreference to Stop: without it a missing PSScriptAnalyzer module leaves $findings empty and pwsh exits 0 after printing 0 findings, while CI always has the module from the step before (:132-136). The -SuppressedOnly listing (:144-148) only prints the deliberate suppressions and does not change the result, so it is left out. check-cmd analyzes CI's one path, not , as CI does on every change; the repository holds no other PowerShell file. fix-cmd is null: CI has no format step. Glob gap: no job in this workflow has a path filter (:15-37), so CI runs the sync-local suite on every change; that suite runs this script beside its bash twin (scripts/test-sync-local.sh:4-6, :28) and is bash.yaml's test-cmd, so a change to only scripts/sync-local.ps1 runs no local test." +notes: "No tool-pin: CI installs the current PSGallery release of PSScriptAnalyzer (pr-require-checks.yml:136). check-cmd is CI's analyzer call (:149-154). It sets $ErrorActionPreference to Stop, which GitHub prepends to a shell: pwsh step (docs.github.com workflow syntax, 'Exit codes and error action preference') and a plain pwsh -Command does not: without it a missing PSScriptAnalyzer module leaves $findings empty and pwsh exits 0 after printing 0 findings. Deviation: the -SuppressedOnly listing (:144-148) only prints the deliberate suppressions and does not change the result, so it is left out. check-cmd analyzes CI's one path, not , as CI does on every change; the repository holds no other PowerShell file. fix-cmd is null: CI has no format step. Glob gap: no job in this workflow has a path filter (:15-37), so CI runs the sync-local suite on every change; that suite runs this script beside its bash twin (scripts/test-sync-local.sh:4-6, :28) and is bash.yaml's test-cmd, so a change to only scripts/sync-local.ps1 runs no local test."