migrate

To keep workflow files in sync with system design changes, this migration automatically applies pending updates before running any workflow skill. It ensures changes are idempotent, auditable, and safe to re-run without manual intervention, preventing configuration drift.

To run the bash migration script manually and validate files, execute the migrate.sh script directly. This triggers the migration process outside the automated workflow, allowing you to re-validate that all files are correctly aligned with the current design.

Workflow migration changes are logged for auditing in the docs/workflow/.cache/migrations.log file. You can review these applied changes and verify file synchronization status by checking the log or using git diff on the repository.

To force re-running idempotent migrations that appear stuck, delete the migrations tracking file located in the workflow cache. Removing this file resets the tracking state, allowing the system to safely re-apply all migrations from the beginning.

Yes, the workflow migration runs automatically at the start of every workflow skill. This prevents file drift by ensuring your workflow files are always validated and updated to match the current system design before any processing begins.