diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml index de91940..e5765ce 100644 --- a/.claude/ecosystems/cross-cutting.yaml +++ b/.claude/ecosystems/cross-cutting.yaml @@ -4,8 +4,10 @@ # 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. +# melodic-software/ci-workflows@594987a (v0.39.8). The final line, gitleaks, is +# the local secret scan, which no CI job here runs; notes give its source. +# Every check runs and any failure fails the command. Commands run from the +# repository root. enabled: true globs: ["**"] project-discovery: [] @@ -16,14 +18,17 @@ check-cmd: | jq empty .claude/settings.json || rc=1 jq empty .cursor/environment.json || rc=1 lychee --offline --no-progress --config lychee.toml '**/*.md' || rc=1 + gitleaks dir . --config .gitleaks.toml --no-banner --redact || 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" +opt-in: "lychee.toml and .gitleaks.toml at the repository root for lychee and gitleaks; 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 + gitleaks 8.30.1: winget install Gitleaks.Gitleaks | brew install gitleaks; no CI job here installs it; the gitleaks composite at ci-workflows@594987a verifies the linux_x64 release archive by SHA-256 551f6fc83ea457d62a0d98237cbad105af8d557003051f41f3e7ca7b3f2470eb 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" + gitleaks: "8.30.1" 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)." +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/. 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 would run without this file (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 typos or editorconfig-checker command: without this file the bundled default (cross-cutting.yaml:11, :14) would run both, because their configs, _typos.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, :76), and no CI job here runs those tools. lefthook.yml:1-6 pulls git hooks from claude-code-plugins; apart from gitleaks 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-29) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)."