| name | validation-gate |
| description | Canonical validation ordering, autofix handling, working-tree checks, and reuse rules. |
| user-invocable | false |
Validation Gate
Load the project profile when selecting repository commands. Use enabled CI only;
if none exists, report that and use required local validation. Run relevant tests
when affected. Root builds, affected examples, affected tests, and relevant OTA
work use profile commands. Upload and monitor require explicit request.
For the narrow autofix-capable pre-commit component, run:
pwsh -NoProfile -ExecutionPolicy Bypass -File tools/quality/run-precommit-full.ps1
For a full repository or integration gate, use the canonical orchestrator:
pwsh -NoProfile -ExecutionPolicy Bypass -File tools/build/run-full-repository-gate.ps1
It discovers the current PlatformIO matrix from the repository; do not replace it
with a copied environment list in governance.
Governance-only changes require a consistency check of routing, shortcuts,
branch/Git/PR rules, tools, Serena, validation, version, session close,
checkpoint, planning, project profile, and reporting rules.
Final-State Ordering
- Record
git status --short before validation so existing user changes are
distinguishable from validation output.
- Run every autofix-capable command before expensive build or test commands.
This includes pre-commit, formatters, clang-format wrappers, line-ending and
EOF fixers, generated refreshers, and a pre-commit wrapper that couples
cppcheck with formatting.
- After each command that can modify files, run
git status --short and
compare it with the recorded baseline.
- A non-zero command or a command that modifies files is
FAILED/AUTOFIXED,
not passed. Report changed files, inspect the focused diff, confirm changes
are in scope, include them in intended scope, and rerun that command until it
exits successfully without further changes.
- Only then run expensive PlatformIO builds/tests. Run
git status --short
afterward. If files changed, stop: the expensive result does not cover the
changed state; restart the autofix-first sequence.
Never infer success from hook names alone: exit status and post-command tree
state are required. Report indirectly covered formatter/cppcheck work as
wrapper-covered, not as independently executed commands. For touched C/C++
source or headers in checkpoint or integration workflows, request cppcheck via
the configured pre-commit path before expensive PlatformIO validation; report a
blocker if it cannot run.
Reuse
Reuse validation across agents or sessions only when all of the following are
documented: identical commit/source state, clean working tree, exact command and
successful result, unchanged relevant scope, and continued sufficiency for the
pending decision. State: Validation reused: <command>, passed for identical commit/source state, clean tree, unchanged relevant scope, and documented result.
Changed relevant scope requires a rerun. Never reuse after branch change without
proven identical tree, merge, rebase, conflict resolution, dependency update,
PlatformIO config change, generated refresh, or any relevant
source/header/example/test/build or metadata modification. Reuse never bypasses
safety, release, package, or hardware requirements. Failed, partial, skipped,
ambiguous, or insufficient validation is never reusable.
For a GitHub Actions-only workflow dependency update, fresh successful Actions
checks on the updated workflow may validate that workflow change. Report local
PlatformIO as skipped, not reused.
For governance or documentation-only work, skip PlatformIO and state:
PlatformIO skipped: governance/docs-only changes.
