@oddessentials/repo-standards 5.0.0 → 5.2.0

package/README.md

@@ -68,7 +68,7 @@ The master spec includes a `meta` block that defines system-wide expectations:
 
 ## Structure of `config/standards.json`
 
-- `version` — schema version (currently `4`)
+- `version` — schema version (currently `5`)
 - `meta` — global rules and migration policy
 - `ciSystems` — supported CI platforms
   _(currently `github-actions`, `azure-devops`)_
@@ -104,6 +104,12 @@ The `version` field indicates schema compatibility:
 - `2` — Adds `bazelHints`, `meta.executorHints.bazel` for Bazel support, `anyOfFiles`, `pinningNotes`, enforcement/severity levels, ratio-based coverage thresholds, Rust/Go stacks. Enforces strict validation with `additionalProperties: false`.
 - `3` — Expands release, build determinism, and provenance/CI automation requirements; adds unified release workflow and template automation guidance.
 - `4` — Stable API contract with `getStandards()`, `getSchema()`, `STANDARDS_VERSION` exports; Node 22 LTS alignment.
+- `5` — Adds automated version-guard guidance for repositories using semantic-release; schema aligned to package major version 5.
+
+To keep `config/standards.json` in sync with semantic-release major bumps, use
+`scripts/sync-standards-version.cjs` during the semantic-release prepare step
+and commit the updated files. This updates the schema version and README
+references in one place.
 
 Consumers should ignore unknown fields for forward compatibility.
 

package/dist/config/standards.csharp-dotnet.azure-devops.json

@@ -206,6 +206,57 @@
           "verification": "Check that versioning is driven by a SemVer-aware tool (for example, GitVersion) and verify that running the release/versioning step locally or in CI produces the expected version metadata, updates project files, and generates changelog entries from commit history."
         }
       },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Run the version guard in PR validation jobs before merge.",
+            "stage": "quality"
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "stack": {
+          "exampleConfigFiles": [
+            "scripts/check-version-unchanged.sh",
+            ".github/workflows/ci.yml",
+            "azure-pipelines.yml"
+          ],
+          "exampleTools": [
+            "GitVersion",
+            "git"
+          ],
+          "notes": "When GitVersion or similar tooling computes versions, block manual edits to Directory.Build.props or *.csproj version fields via the version guard. Allow changes only in release automation.",
+          "optionalFiles": [
+            "Directory.Build.props",
+            "*.csproj",
+            "VERSION"
+          ],
+          "verification": "Run the guard and confirm it fails when <Version> or <VersionPrefix> changes in props/csproj files."
+        }
+      },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts.",
+            "stage": "quality"
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "stack": {
+          "exampleConfigFiles": [
+            ".editorconfig"
+          ],
+          "exampleTools": [
+            "dotnet format",
+            "GitVersion"
+          ],
+          "notes": "Use .editorconfig to exclude auto-generated files from formatting. GitVersion may generate or modify files that shouldn't be reformatted. Add glob patterns for generated code directories (e.g., **/obj/**, **/bin/**).",
+          "verification": "Run 'dotnet format --verify-no-changes' and confirm generated files are excluded."
+        }
+      },
       {
         "ciHints": {
           "azure-devops": {
@@ -1199,5 +1250,5 @@
   },
   "stack": "csharp-dotnet",
   "stackLabel": "C# / .NET",
-  "version": 4
+  "version": 5
 }

package/dist/config/standards.csharp-dotnet.github-actions.json

@@ -206,6 +206,57 @@
           "verification": "Check that versioning is driven by a SemVer-aware tool (for example, GitVersion) and verify that running the release/versioning step locally or in CI produces the expected version metadata, updates project files, and generates changelog entries from commit history."
         }
       },
+      {
+        "ciHints": {
+          "github-actions": {
+            "job": "ci",
+            "notes": "Run the version guard in PR workflows against the base ref."
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "stack": {
+          "exampleConfigFiles": [
+            "scripts/check-version-unchanged.sh",
+            ".github/workflows/ci.yml",
+            "azure-pipelines.yml"
+          ],
+          "exampleTools": [
+            "GitVersion",
+            "git"
+          ],
+          "notes": "When GitVersion or similar tooling computes versions, block manual edits to Directory.Build.props or *.csproj version fields via the version guard. Allow changes only in release automation.",
+          "optionalFiles": [
+            "Directory.Build.props",
+            "*.csproj",
+            "VERSION"
+          ],
+          "verification": "Run the guard and confirm it fails when <Version> or <VersionPrefix> changes in props/csproj files."
+        }
+      },
+      {
+        "ciHints": {
+          "github-actions": {
+            "job": "ci",
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts."
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "stack": {
+          "exampleConfigFiles": [
+            ".editorconfig"
+          ],
+          "exampleTools": [
+            "dotnet format",
+            "GitVersion"
+          ],
+          "notes": "Use .editorconfig to exclude auto-generated files from formatting. GitVersion may generate or modify files that shouldn't be reformatted. Add glob patterns for generated code directories (e.g., **/obj/**, **/bin/**).",
+          "verification": "Run 'dotnet format --verify-no-changes' and confirm generated files are excluded."
+        }
+      },
       {
         "ciHints": {
           "github-actions": {
@@ -1199,5 +1250,5 @@
   },
   "stack": "csharp-dotnet",
   "stackLabel": "C# / .NET",
-  "version": 4
+  "version": 5
 }

package/dist/config/standards.csharp-dotnet.json

@@ -229,6 +229,65 @@
           "verification": "Check that versioning is driven by a SemVer-aware tool (for example, GitVersion) and verify that running the release/versioning step locally or in CI produces the expected version metadata, updates project files, and generates changelog entries from commit history."
         }
       },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Run the version guard in PR validation jobs before merge.",
+            "stage": "quality"
+          },
+          "github-actions": {
+            "job": "ci",
+            "notes": "Run the version guard in PR workflows against the base ref."
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "stack": {
+          "exampleConfigFiles": [
+            "scripts/check-version-unchanged.sh",
+            ".github/workflows/ci.yml",
+            "azure-pipelines.yml"
+          ],
+          "exampleTools": [
+            "GitVersion",
+            "git"
+          ],
+          "notes": "When GitVersion or similar tooling computes versions, block manual edits to Directory.Build.props or *.csproj version fields via the version guard. Allow changes only in release automation.",
+          "optionalFiles": [
+            "Directory.Build.props",
+            "*.csproj",
+            "VERSION"
+          ],
+          "verification": "Run the guard and confirm it fails when <Version> or <VersionPrefix> changes in props/csproj files."
+        }
+      },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts.",
+            "stage": "quality"
+          },
+          "github-actions": {
+            "job": "ci",
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts."
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "stack": {
+          "exampleConfigFiles": [
+            ".editorconfig"
+          ],
+          "exampleTools": [
+            "dotnet format",
+            "GitVersion"
+          ],
+          "notes": "Use .editorconfig to exclude auto-generated files from formatting. GitVersion may generate or modify files that shouldn't be reformatted. Add glob patterns for generated code directories (e.g., **/obj/**, **/bin/**).",
+          "verification": "Run 'dotnet format --verify-no-changes' and confirm generated files are excluded."
+        }
+      },
       {
         "ciHints": {
           "azure-devops": {
@@ -1343,5 +1402,5 @@
   },
   "stack": "csharp-dotnet",
   "stackLabel": "C# / .NET",
-  "version": 4
+  "version": 5
 }

package/dist/config/standards.go.azure-devops.json

@@ -202,6 +202,55 @@
           "verification": "Check that git tags follow vMAJOR.MINOR.PATCH format and goreleaser or similar tooling generates releases and changelogs."
         }
       },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Run the version guard in PR validation jobs before merge.",
+            "stage": "quality"
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "stack": {
+          "exampleConfigFiles": [
+            "scripts/check-version-unchanged.sh",
+            ".github/workflows/ci.yml",
+            "azure-pipelines.yml"
+          ],
+          "exampleTools": [
+            "goreleaser",
+            "git"
+          ],
+          "notes": "Go versioning is tag-driven; only enable the guard if you keep a VERSION file or embed version constants in code. The guard should ensure those fields are not edited manually in PRs.",
+          "optionalFiles": [
+            "VERSION"
+          ],
+          "verification": "Run the guard and confirm it fails when VERSION or version constants change outside release automation."
+        }
+      },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts.",
+            "stage": "quality"
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "stack": {
+          "exampleConfigFiles": [
+            ".golangci.yml"
+          ],
+          "exampleTools": [
+            "gofmt",
+            "goreleaser"
+          ],
+          "notes": "Go formatting (gofmt) only affects .go files, so CHANGELOG.md is automatically excluded. If using code generators, exclude generated directories in .golangci.yml skip-dirs.",
+          "verification": "Run 'gofmt -d .' and confirm generated code directories are excluded."
+        }
+      },
       {
         "ciHints": {
           "azure-devops": {
@@ -1184,5 +1233,5 @@
   },
   "stack": "go",
   "stackLabel": "Go",
-  "version": 4
+  "version": 5
 }

package/dist/config/standards.go.github-actions.json

@@ -202,6 +202,55 @@
           "verification": "Check that git tags follow vMAJOR.MINOR.PATCH format and goreleaser or similar tooling generates releases and changelogs."
         }
       },
+      {
+        "ciHints": {
+          "github-actions": {
+            "job": "ci",
+            "notes": "Run the version guard in PR workflows against the base ref."
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "stack": {
+          "exampleConfigFiles": [
+            "scripts/check-version-unchanged.sh",
+            ".github/workflows/ci.yml",
+            "azure-pipelines.yml"
+          ],
+          "exampleTools": [
+            "goreleaser",
+            "git"
+          ],
+          "notes": "Go versioning is tag-driven; only enable the guard if you keep a VERSION file or embed version constants in code. The guard should ensure those fields are not edited manually in PRs.",
+          "optionalFiles": [
+            "VERSION"
+          ],
+          "verification": "Run the guard and confirm it fails when VERSION or version constants change outside release automation."
+        }
+      },
+      {
+        "ciHints": {
+          "github-actions": {
+            "job": "ci",
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts."
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "stack": {
+          "exampleConfigFiles": [
+            ".golangci.yml"
+          ],
+          "exampleTools": [
+            "gofmt",
+            "goreleaser"
+          ],
+          "notes": "Go formatting (gofmt) only affects .go files, so CHANGELOG.md is automatically excluded. If using code generators, exclude generated directories in .golangci.yml skip-dirs.",
+          "verification": "Run 'gofmt -d .' and confirm generated code directories are excluded."
+        }
+      },
       {
         "ciHints": {
           "github-actions": {
@@ -1184,5 +1233,5 @@
   },
   "stack": "go",
   "stackLabel": "Go",
-  "version": 4
+  "version": 5
 }

package/dist/config/standards.go.json

@@ -225,6 +225,63 @@
           "verification": "Check that git tags follow vMAJOR.MINOR.PATCH format and goreleaser or similar tooling generates releases and changelogs."
         }
       },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Run the version guard in PR validation jobs before merge.",
+            "stage": "quality"
+          },
+          "github-actions": {
+            "job": "ci",
+            "notes": "Run the version guard in PR workflows against the base ref."
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "stack": {
+          "exampleConfigFiles": [
+            "scripts/check-version-unchanged.sh",
+            ".github/workflows/ci.yml",
+            "azure-pipelines.yml"
+          ],
+          "exampleTools": [
+            "goreleaser",
+            "git"
+          ],
+          "notes": "Go versioning is tag-driven; only enable the guard if you keep a VERSION file or embed version constants in code. The guard should ensure those fields are not edited manually in PRs.",
+          "optionalFiles": [
+            "VERSION"
+          ],
+          "verification": "Run the guard and confirm it fails when VERSION or version constants change outside release automation."
+        }
+      },
+      {
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts.",
+            "stage": "quality"
+          },
+          "github-actions": {
+            "job": "ci",
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts."
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "stack": {
+          "exampleConfigFiles": [
+            ".golangci.yml"
+          ],
+          "exampleTools": [
+            "gofmt",
+            "goreleaser"
+          ],
+          "notes": "Go formatting (gofmt) only affects .go files, so CHANGELOG.md is automatically excluded. If using code generators, exclude generated directories in .golangci.yml skip-dirs.",
+          "verification": "Run 'gofmt -d .' and confirm generated code directories are excluded."
+        }
+      },
       {
         "ciHints": {
           "azure-devops": {
@@ -1328,5 +1385,5 @@
   },
   "stack": "go",
   "stackLabel": "Go",
-  "version": 4
+  "version": 5
 }

package/dist/config/standards.json

@@ -881,6 +881,215 @@
           }
         }
       },
+      {
+        "appliesTo": {
+          "stacks": [
+            "typescript-js",
+            "csharp-dotnet",
+            "python",
+            "rust",
+            "go"
+          ]
+        },
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Run the version guard in PR validation jobs before merge.",
+            "stage": "quality"
+          },
+          "github-actions": {
+            "job": "ci",
+            "notes": "Run the version guard in PR workflows against the base ref."
+          }
+        },
+        "description": "If semantic-release or automated versioning is enabled, block manual edits to canonical version fields in pull requests. Enforce a CI guard (and optional pre-push hook) that fails when version lines change outside the release workflow.",
+        "enforcement": "required",
+        "executionStage": "ci-pr",
+        "id": "version-guard",
+        "label": "Version Guard (Automated Releases)",
+        "severity": "error",
+        "stackHints": {
+          "csharp-dotnet": {
+            "exampleConfigFiles": [
+              "scripts/check-version-unchanged.sh",
+              ".github/workflows/ci.yml",
+              "azure-pipelines.yml"
+            ],
+            "exampleTools": [
+              "GitVersion",
+              "git"
+            ],
+            "notes": "When GitVersion or similar tooling computes versions, block manual edits to Directory.Build.props or *.csproj version fields via the version guard. Allow changes only in release automation.",
+            "optionalFiles": [
+              "Directory.Build.props",
+              "*.csproj",
+              "VERSION"
+            ],
+            "verification": "Run the guard and confirm it fails when <Version> or <VersionPrefix> changes in props/csproj files."
+          },
+          "go": {
+            "exampleConfigFiles": [
+              "scripts/check-version-unchanged.sh",
+              ".github/workflows/ci.yml",
+              "azure-pipelines.yml"
+            ],
+            "exampleTools": [
+              "goreleaser",
+              "git"
+            ],
+            "notes": "Go versioning is tag-driven; only enable the guard if you keep a VERSION file or embed version constants in code. The guard should ensure those fields are not edited manually in PRs.",
+            "optionalFiles": [
+              "VERSION"
+            ],
+            "verification": "Run the guard and confirm it fails when VERSION or version constants change outside release automation."
+          },
+          "python": {
+            "exampleConfigFiles": [
+              "scripts/check-version-unchanged.sh",
+              ".github/workflows/ci.yml",
+              "azure-pipelines.yml"
+            ],
+            "exampleTools": [
+              "semantic-release",
+              "git"
+            ],
+            "notes": "Block manual edits to version fields in pyproject.toml or setup.cfg when automated release tooling computes versions from commit history.",
+            "optionalFiles": [
+              "setup.cfg",
+              "setup.py",
+              "VERSION"
+            ],
+            "requiredFiles": [
+              "pyproject.toml"
+            ],
+            "verification": "Run the guard and confirm it fails when version lines change in pyproject.toml or setup.cfg."
+          },
+          "rust": {
+            "exampleConfigFiles": [
+              "scripts/check-version-unchanged.sh",
+              ".github/workflows/ci.yml",
+              "azure-pipelines.yml"
+            ],
+            "exampleTools": [
+              "cargo-release",
+              "semantic-release",
+              "git"
+            ],
+            "notes": "When using cargo-release or semantic-release-cargo, guard against manual edits to Cargo.toml version fields in PRs.",
+            "requiredFiles": [
+              "Cargo.toml"
+            ],
+            "verification": "Run the guard and confirm it fails when Cargo.toml version changes."
+          },
+          "typescript-js": {
+            "exampleConfigFiles": [
+              "scripts/check-version-unchanged.sh",
+              ".github/workflows/ci.yml",
+              "azure-pipelines.yml"
+            ],
+            "exampleTools": [
+              "semantic-release",
+              "git"
+            ],
+            "notes": "Add a CI step that runs scripts/check-version-unchanged.sh against the PR base ref. This blocks manual edits to package.json version when semantic-release owns versioning. Optionally wire the same script into a pre-push hook for fast feedback.",
+            "optionalFiles": [
+              "VERSION"
+            ],
+            "requiredFiles": [
+              "package.json"
+            ],
+            "verification": "Run the guard with the PR base ref (for example, origin/main) and confirm it fails when package.json version changes."
+          }
+        }
+      },
+      {
+        "appliesTo": {
+          "stacks": [
+            "typescript-js",
+            "csharp-dotnet",
+            "python",
+            "rust",
+            "go"
+          ]
+        },
+        "ciHints": {
+          "azure-devops": {
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts.",
+            "stage": "quality"
+          },
+          "github-actions": {
+            "job": "ci",
+            "notes": "Ensure format:check step uses ignore file that excludes release artifacts."
+          }
+        },
+        "description": "Exclude auto-generated release artifacts (CHANGELOG.md, package-lock.json, etc.) from code formatters to prevent CI failures. Release automation tools generate files that may not conform to your formatter's style, causing format checks to fail on subsequent CI runs.",
+        "enforcement": "required",
+        "executionStage": "pre-commit",
+        "id": "release-artifact-exclusion",
+        "label": "Release Artifact Formatter Exclusion",
+        "severity": "error",
+        "stackHints": {
+          "csharp-dotnet": {
+            "exampleConfigFiles": [
+              ".editorconfig"
+            ],
+            "exampleTools": [
+              "dotnet format",
+              "GitVersion"
+            ],
+            "notes": "Use .editorconfig to exclude auto-generated files from formatting. GitVersion may generate or modify files that shouldn't be reformatted. Add glob patterns for generated code directories (e.g., **/obj/**, **/bin/**).",
+            "verification": "Run 'dotnet format --verify-no-changes' and confirm generated files are excluded."
+          },
+          "go": {
+            "exampleConfigFiles": [
+              ".golangci.yml"
+            ],
+            "exampleTools": [
+              "gofmt",
+              "goreleaser"
+            ],
+            "notes": "Go formatting (gofmt) only affects .go files, so CHANGELOG.md is automatically excluded. If using code generators, exclude generated directories in .golangci.yml skip-dirs.",
+            "verification": "Run 'gofmt -d .' and confirm generated code directories are excluded."
+          },
+          "python": {
+            "exampleConfigFiles": [
+              "pyproject.toml"
+            ],
+            "exampleTools": [
+              "black",
+              "ruff",
+              "bumpversion"
+            ],
+            "notes": "In pyproject.toml [tool.black] or [tool.ruff], add extend-exclude patterns for auto-generated files like CHANGELOG.md. Some versioning tools generate or modify files that should not be reformatted.",
+            "verification": "Run 'black --check .' or 'ruff format --check' and confirm generated files are excluded."
+          },
+          "rust": {
+            "exampleConfigFiles": [
+              "rustfmt.toml"
+            ],
+            "exampleTools": [
+              "rustfmt",
+              "cargo-release"
+            ],
+            "notes": "Rust rarely has auto-generated source files, but if using tools that generate Rust code, exclude those directories in rustfmt.toml. CHANGELOG.md isn't checked by rustfmt (it only checks .rs files).",
+            "verification": "Run 'cargo fmt --check' and confirm it passes after releases."
+          },
+          "typescript-js": {
+            "exampleConfigFiles": [
+              ".prettierignore",
+              ".releaserc.json"
+            ],
+            "exampleTools": [
+              "prettier",
+              "semantic-release"
+            ],
+            "notes": "Add CHANGELOG.md and package-lock.json to .prettierignore. These files are auto-generated by semantic-release and npm respectively. Without this exclusion, format:check fails after releases because the generated format differs from Prettier's expected style. Document each exclusion with a comment explaining it's auto-generated.",
+            "requiredFiles": [
+              ".prettierignore"
+            ],
+            "verification": "Run 'npm run format:check' and confirm CHANGELOG.md is not checked. Review .prettierignore and confirm auto-generated files are listed with explanatory comments."
+          }
+        }
+      },
       {
         "appliesTo": {
           "stacks": [
@@ -4497,5 +4706,5 @@
       "languageFamily": "js"
     }
   },
-  "version": 4
+  "version": 5
 }