Bind the transition to two records
Record the revision, repository, accepted baseline, closure record, and a separate incoming request. Require an explicit baseline disposition such as unchanged until review, rather than an implied reopen.
NIST's configuration-control definition supplies only the discipline of controlling modifications across a lifecycle. It does not establish workflow policy or prove a data record is preserved.
Check rollback before merge discussion
Run the dependency-free receipt validator:
node --test sites/odexing.com/evidence/P152/reopen-workflow-change-receipt.test.mjs
It requires a reviewer, rollback owner, rollback procedure, and post-rollback check. It does not run Git, a database, a ticket system, or a deployment. A repository-specific exercise must still observe original state, transition, and rollback.
The fixture ran locally on Node.js 22.18.0 with three passing tests and no failures. That result covers only record completeness in this dependency-free fixture, not a target repository or environment.
Stop when a new request overwrites acceptance
Pause if the change cannot show accepted baseline, closure evidence, named authority, disposition, or a rollback owner. A maintainer should require a safe environment-specific procedure before treating a local receipt as merge evidence.
For a delivery-pipeline gate, see Gate an Agent-Generated CI Workflow Change Before Merge. For a scoped configuration gate, see Gate an Agent-Generated Feature-Flag Change Before Merge. For incoming-event recovery, see Gate an Agent-Generated Missed-Appointment Recovery Change Before Merge.
Does this receipt authorize a merge or decide product policy?
No. It identifies proposed-change evidence for a maintainer and product owner to inspect. Authorization, data migration, and release approval remain environment-specific.