From 692fba51a83c298b1a88c33461dce6f8a249af67 Mon Sep 17 00:00:00 2001 From: jyviko <2501648+jyviko@users.noreply.github.com> Date: Tue, 20 Oct 2026 23:06:38 -0400 Subject: [PATCH] naming: say how to re-record the corpus names CONTRIBUTING lists the re-record command next to the robustness goldens ones, so a change that renames faces records it in the same pull request. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01QWhMwdqJYQKQq8RCLSL1LT --- CONTRIBUTING.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b2253d0a1..bd829dadc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -161,6 +161,9 @@ the most complete description of the house style. A geometry change that changes the robustness goldens re-records them in the same pull request: `ROBUSTNESS_GOLDENS_BLESS="why it changed" cargo test --profile ci -p solidcraft-engine --lib robustness_goldens::` (see [docs/robustness.md](docs/robustness.md)); CI runs every seed on pull requests that touch geometry. +A change to the persistent names of faces and edges, or to what a stored name finds, re-records the +corpus's names in the same pull request, saying why: +`NAMING_CORPUS_BLESS=1 cargo test --profile ci -p solidcraft-cli --test naming_corpus` (`tests/naming/`). [docs/mutation-testing.md](docs/mutation-testing.md) shows how to find kernel behaviour these black-box suites miss.