Reference creatortrack migrate tool wrong default dir

The generic forge_workspace_migrate.py / migrate-check tool defaults to the forge spine's migrations directory, not CreatorTrack's db/migrations. Any migration-drift check run against CreatorTrack without explicitly setting WORKSPACE_MIGRATIONS_DIR=db/migrations will silently check the wrong migration set and report 'schema up to date' even when CreatorTrack migrations are actually pending against prod lifeos.

Why: Discovered 2026-07-11 when a newly-hardened deploy guard in forge_creatortrack_deploy.sh reported no pending migrations right after two new CreatorTrack migrations were merged to main — the guard was pointed at the wrong dir by default. Fixed by defining CT_MIGRATIONS_DIR=db/migrations explicitly in the script and confirming prod DB name is lifeos.

How to apply: Any script or command that calls the generic migrate tool against a CreatorTrack repo path must explicitly set WORKSPACE_MIGRATIONS_DIR=db/migrations (e.g. cd creatortrack && WORKSPACE_MIGRATIONS_DIR=db/migrations python3 ~/forge/scripts/forge_workspace_migrate.py). Never trust a bare 'up to date' result from this tool against CreatorTrack without confirming the env var was set. Related: [[project_creatortrack_deploy_no_migrate]].

[auto-memory session edb31021-e228-4857-8a08-60791e27c955, confidence 0.85, mode direct]