diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml index ef3b2ec..8cf439c 100644 --- a/.claude/ecosystems/cross-cutting.yaml +++ b/.claude/ecosystems/cross-cutting.yaml @@ -55,4 +55,4 @@ tool-pin: typos: "1.50.3" gitleaks: "8.30.1" gates: [] -notes: "Lint-only: owned by /toolchain:lint. The lychee and typos commands, versions and checksums are those of ci-workflows' lychee-offline and typos composites at the commits pr-require-checks.yml:256 and :273 pin (lychee-offline's `globs`, `config`, `exclude`, `version` and `sha256` input defaults; typos' `paths`, `config`, `hidden`, `version` and `sha256` input defaults); Dependabot moves those pins to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (the action's `hidden` input). CI's typos step also emits annotations from a second json pass (the action's `annotations` input, default true); 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 (the action's `globs` and `exclude` defaults); 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. Deviation from CI: gitleaks. No CI job in this repository runs gitleaks; the line keeps the local secret scan that the bundled cross-cutting default ran before this file existed (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:12, opt-in :18, met by the tracked .gitleaks.toml), so these records do not switch a secret scan off. Its command, version and checksum are those of the gitleaks composite at ci-workflows@594987a (v0.39.8), which this repository does not call: gitleaks/scan.sh:113, :136 and :142 with the defaults at gitleaks/action.yml:9, :15 and :30, pins :50 (version) and :55 (checksum). gitleaks scans every file on disk under the repository root, tracked, untracked or git-ignored (a scratch file under .work/ included), and not git history; it does not read . No editorconfig-checker or markdownlint command: .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, :72), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and apart from gitleaks 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 at the commit it pins) and the result aggregation (:307-326, aggregate-results at the same commit) 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-29) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)." +notes: "Lint-only: owned by /toolchain:lint. The lychee and typos commands, versions and checksums are those of ci-workflows' lychee-offline and typos composites at the commits pr-require-checks.yml:256 and :273 pin (lychee-offline's `globs`, `config`, `exclude`, `version` and `sha256` input defaults; typos' `paths`, `config`, `hidden`, `version` and `sha256` input defaults); Dependabot moves those pins to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (the action's `hidden` input). CI's typos step also emits annotations from a second json pass (the action's `annotations` input, default true); 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 (the action's `globs` and `exclude` defaults); 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. Deviation from CI: gitleaks. No CI job in this repository runs gitleaks; the line keeps the local secret scan that the bundled cross-cutting default ran before this file existed (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:12, opt-in :18, met by the tracked .gitleaks.toml), so these records do not switch a secret scan off. Its command, version and checksum are those of the gitleaks composite at ci-workflows@594987a (v0.39.8), which this repository does not call: gitleaks/scan.sh:113, :136 and :142 with the defaults at gitleaks/action.yml:9, :15 and :30, pins :50 (version) and :55 (checksum). gitleaks scans every file on disk under the repository root, tracked, untracked or git-ignored (a scratch file under .work/ included), and not git history; it does not read . No editorconfig-checker or markdownlint command: .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, :72), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and apart from gitleaks 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 at the commit it pins) and the result aggregation (:307-326, aggregate-results at the same commit) 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@944d346 v0.74.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-30) checks nothing; it arms auto-merge on a Dependabot pull request (:3-8)."