From ae22d9b0c88207986c47933b27f35c6c40d9b6fe Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Mon, 27 Jul 2026 21:51:40 +0100 Subject: [PATCH] fix(validate-action): exclude non-pedigree files from K9 checks MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit coordination.k9 and session/custom-checks.k9 are the estate-standard session-management coordination bindings (plain YAML, ~40 repos) — an unrelated file family that happens to share the .k9 extension. self-validating/methodology-guard.k9.ncl is a K9 *validator definition* (rules about agent methodology constraints), not a pedigree target. None of the three were ever meant to satisfy the K9!/pedigree schema this action checks for, so every one of them fails the K9!/pedigree checks by design, not by defect. That was producing 6 of the 8 "Validate K9 contracts" errors currently blocking PRs in bitfuckit, contractiles, recon-silly-ation and stateful-artefacts (and latently affecting every other repo carrying the same estate-standard files). Add the three path fragments to the action's default paths-ignore so this is fixed once, here, instead of via a local override repeated in every wrapper repo. Co-Authored-By: Claude Opus 5 --- validate-action/action.yml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/validate-action/action.yml b/validate-action/action.yml index 655bf0a..e2144fa 100644 --- a/validate-action/action.yml +++ b/validate-action/action.yml @@ -43,6 +43,20 @@ inputs: absolute-zero/) follows the convention that a tracked subdirectory named after an upstream hyperpolymath repo is a vendored copy whose K9 files belong to the upstream's CI, not the host's. + + The `coordination.k9` / `session/custom-checks.k9` / self-validating + `methodology-guard.k9.ncl` entries below carve out a second, unrelated + class of false positive: files that share the `.k9`/`.k9.ncl` + extension by estate convention but are NOT K9 pedigree contracts and + were never meant to satisfy the K9!/pedigree schema this action + checks. `coordination.k9` and `session/custom-checks.k9` are the + estate-standard session-management coordination bindings (plain YAML, + ~40 repos) — see session/README.md in any repo that has them. + `methodology-guard.k9.ncl` is a K9 *validator definition* (rules + about agent methodology constraints), not a target pedigree file — + see its own header comment. Both families fail every K9!/pedigree + check by design, not by defect; ignoring them here is the one-time + fix instead of 40+ repos each carrying a local paths-ignore override. required: false default: | vendor/ @@ -53,6 +67,9 @@ inputs: test/fixtures/ tests/fixtures/ absolute-zero/ + coordination.k9 + session/custom-checks.k9 + self-validating/methodology-guard.k9.ncl outputs: files-scanned: