Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/ecosystems/cross-cutting.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -32,4 +32,4 @@ tool-pin:
lychee: "0.24.2"
gitleaks: "8.30.1"
gates: []
notes: "Lint-only: owned by /toolchain:lint. The lychee command, version and checksum are those of ci-workflows' lychee-offline/action.yml at the commit pr-require-checks.yml:119 pins (its `globs`, `config`, `exclude`, `version` and `sha256` input defaults); Dependabot moves that pin to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. 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 (the action's `globs` and `exclude` defaults); 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 <files>: 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 <files>. 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 at the commit it pins) and the result aggregation (:151-170, aggregate-results at the same commit) 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)."
notes: "Lint-only: owned by /toolchain:lint. The lychee command, version and checksum are those of ci-workflows' lychee-offline/action.yml at the commit pr-require-checks.yml:119 pins (its `globs`, `config`, `exclude`, `version` and `sha256` input defaults); Dependabot moves that pin to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. 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 (the action's `globs` and `exclude` defaults); 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 <files>: 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 <files>. 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 at the commit it pins) and the result aggregation (:151-170, aggregate-results at the same commit) 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@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)."
Loading