apply-arbiter-patch

To safely apply git patches, this tool reads the consensus-arbiter patch manifest, presents a diff-style summary of affected files, and requests explicit operator confirmation before executing git apply. This ensures you review pending changes before they are committed to your environment.

A patch manifest lists pending changes from the consensus-arbiter. Automated patch management processes this manifest by summarizing the diffs, applying the patches deterministically one-by-one via git apply, and writing an audit record to arbiter-decisions.md for governance traceability.

You can automate git apply for development or testing phases by using the --yes flag, which bypasses the interactive diff preview and explicit operator confirmation, allowing patches to apply automatically while still recording the session in the applied patches log.

Automated patch management supports automatic rollback when a git apply failure occurs during the patch session. It applies patches one-by-one, ensuring that any failed application triggers an immediate rollback to maintain repository integrity.

To audit applied arbiter patches, the tool writes an operational audit trail to arbiter-decisions.md with an applied status and timestamp. It also updates the applied patches log, ensuring full governance and traceability for all applied patch sessions.

You can optionally run tests automatically after applying a git patch. Once the patch session completes the git apply operation, the workflow can trigger subsequent test execution to validate the applied changes within your development or testing environment.