governance · diff

git:20261119.92f0209 to git:20261121.7cfcf94

6 added, 12 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
- applyTo: "README.md,docs/**,AGENTS.md,CLAUDE.md,.github/**,.claude/skills/**,scripts/**,docker/**"
+ applyTo: "README.md,docs/**,AGENTS.md,CLAUDE.md,.github/**,.agents/**,.claude/skills,scripts/**,docker/**"
---
# Governance Instructions
- - Keep commands, file paths, workflow names, config keys, release paths, and directory references aligned with the executable repository state.
- - `AGENTS.md` is the canonical AI collaboration document; if its meaning changes, sync `CLAUDE.md`, `.github/copilot-instructions.md`, `.github/instructions/*.instructions.md`, and repository skills as needed.
- - Root `SKILL.md` and `docs/openclaw-skill-integration.md` describe product or external integration behavior, not repository governance.
- - Explain which pipeline, release path, deployment path, review automation, or governance asset is affected and what the rollback path is.
- - Before creating/updating PRs, PR review, or issue analysis, refresh the latest code baseline with `git fetch --all --prune`; only run `git pull --ff-only` when the worktree is clean and the current branch can fast-forward. If not, keep local state intact and record the fetched remote baseline or branch gap before proceeding.
- - Keep `README.md` limited to homepage-level content such as positioning, high-level capabilities, quick start, main entrypoints, and sponsorship/cooperation; put detailed behavior, configuration, troubleshooting, field contracts, and edge cases in `docs/*.md`.
- - Avoid widening permissions, secret exposure, or destructive automation without a clearly documented need.
- - Preserve the repository's opt-in auto-tag behavior (`#patch`, `#minor`, `#major`) unless the change explicitly updates release policy.
- - Use merged PR titles and labels for release notes. Follow AGENTS.md §9 to archive a published version in `docs/CHANGELOG.md`.
- - When creating, reviewing, or suggesting PRs, prefer PR titles in `<type>: <change summary>` form and omit tool/agent source prefixes such as `[codex]`, `codex`, `autocode`, or `copilot`; treat this as non-blocking guidance, not a review hard blocker.
- - If only one language version of a document is updated, explain why the counterpart was not synchronized.
+ - `AGENTS.md` is the canonical AI collaboration source; sync `CLAUDE.md`, `.github/copilot-instructions.md`, `.github/instructions/*.instructions.md`, `.agents/skills/**`, and `scripts/check_ai_assets.py` when governance contracts change, then run `python scripts/check_ai_assets.py`.
+ - Keep commands, file paths, workflow names, config keys, and release paths aligned with executable repository state.
+ - Root `SKILL.md` and `docs/openclaw-skill-integration.md` describe product/external integrations, not repository governance.
+ - Avoid widening CI/workflow permissions, secret exposure, or destructive automation without a clearly documented need; preserve opt-in auto-tag (`#patch`, `#minor`, `#major`).
+ - If only one language version of a bilingual doc is updated, state why the counterpart was not synchronized.