oag-finalize-workflow

Workflow finalization closes an iteration by enforcing review checks and status transitions. It updates the plan file status to 'finalized' and the progress log, then optionally commits code changes to a repository if the review status is 'approved'.

Workflow finalization enforces review checks and status transitions before proceeding. It will not commit code changes to the repository unless the iteration's review status is explicitly marked as 'approved'.

To update your progress tracking log after finishing a development cycle, the finalization process automatically records the closure of the current iteration. This ensures your progress log accurately reflects the completed work as the plan status transitions to 'finalized'.

Yes, you can use auggd to finalize an iteration without committing code to the repository. The codebase commit is an optional step in the finalization workflow, allowing you to close iterations and update progress logs independently of version control actions.

After closing an iteration in your development workflow, you should follow the post-finalize guidance to determine the next stage. This workflow directs you to either start a new iteration, update project documentation, or proceed with overall project closure based on the finalization outcome.