jade-core-atomic-commit

To create an atomic Git commit for migration rules, stage only the files touched by the current verified rule and execute a single conventional commit. This prevents rule batches from mixing and keeps migration history auditable.

Preventing unrelated changes in migration commits requires strict safety validation. The process refuses to commit when unrelated files are dirty or staged, protecting the workspace from accidental cross-rule file modifications.

Conventional commit formatting for migration pipelines stages verified file edits and creates a single commit per rule. It advances sequentially through committed checkpoints, ensuring each migration step is isolated and traceable.

Logging Git commit hashes to JSON requires writing the commit hash, message, timestamp, and file list to artifacts/09-rule-commit-log.json. This allows the orchestrator to confirm migration progress and verify rule completion.

Atomic commits fail when other files are staged because strict file-list validation rejects dirty or unrelated working-tree changes. This safety check ensures only verified rule-specific edits are committed, preventing cross-rule contamination.

Strict file-list validation is needed when batching file edits in rule-based migration pipelines. It ensures that only verified files for the current rule are staged, allowing you to advance sequentially without breaking sequential batching.