← Commit history

Document current-head branch PRs and production validation

John Lauer ·17936dbdb6 ·1mo ago ·parent 19f4733
1 file changed +10
CONTRIBUTING.md+10
@@ -73,3 +73,13 @@ Be kind. We're building this for engineers who need their CAD tools to work with ## License  MIT — see [LICENSE](LICENSE).++## Wiki PRs and concurrent changes++Before editing, read the latest PR reviews and linked issues, record the full current page-repo HEAD, and clone that immutable ref. Recheck HEAD before submission. If it moved, reapply only the intended hunks onto the new head and rerun validation. Never restore older complete files over the current module registry, verb manifest, or dispatch implementation. Overlapping work must build on its merged predecessor or declare its branch dependency.++Prefer `adom-wiki branch create <repo> <branch> --from <hash>`, followed by `repo push <repo> --branch <branch> --files <paths>`, `branch compare`, and `pr create <repo> --from <branch> --body-file <file>`. Branch PRs retain ancestry and a contextual diff. File-set PRs can encode whole-file replacements and silently remove concurrent changes. Read the actual submitted diff, not just the local one.++Review every deletion, module and verb registration, brace and `cfg(test)` boundary. Keep Rust formatting consistent without unrelated whole-file reformatting. Run a production `cargo check --workspace --bins` and the combined workspace tests with required features: tests alone can miss production functions accidentally nested inside test modules. Preserve tests for capabilities merged since the original checkout.++Each PR must state its exact base hash, dependencies, scope, preserved capabilities, test commands/results and native acceptance still needed. IPC deletion visibility, refill Undo steps, final revisions and rendering require native validation; source tests are not evidence of those behaviors. Maintainer merge, release publication and deployed acceptance remain separate. Do not replace a shared runtime to test a PR.