project-config-review

Config change approval workflows present proposed mutations as grouped summaries and diffs, then loop on user comments until explicit approval is granted before writing to PROJECT_CONFIG.md.

A config governance review intercepts every init, update, add, or remove mutation, produces a change summary diff, and enforces a guarded write to the project config file only after explicit user approval.

Yes, config review workflows generate a preview diff for all init, update, add, or remove mutations, grouping proposed changes by owned section to provide a clear change summary before any write occurs.

Initiate a review session by presenting proposed config changes to the user, then loop on their comments until they grant explicit approval, which triggers the guarded write to PROJECT_CONFIG.md.

Yes, the governance workflow can be invoked on every init, update, add, or remove mutation, ensuring all project config changes are reviewed with summaries and diffs before being written.

Without explicit approval, the config review workflow continues looping on comments and no write is executed to PROJECT_CONFIG.md, ensuring proposed mutations are never applied unguarded.