Project creatortrack deploy no migrate

forge_creatortrack_deploy.sh builds and restarts creatortrack-prod but does not apply pending migrations against the prod DB (lifeos, tracked in core.schema_migrations). Discovered 2026-07-08 when the Link In Bio feature deployed successfully but errored in prod (relation "links.pages" does not exist) because its migration only ran against dev clones. A second session's google_contacts_links_table migration had the same problem, deployed at 15:03 with no migration applied, silently breaking Google Contacts sync until caught as a side effect of this fix.

Why: Any future CreatorTrack deploy that includes schema changes will ship broken in prod until someone remembers to manually run the migration. This already happened twice in one day across two different sessions.

How to apply: Before or immediately after any CreatorTrack prod deploy that touches db/migrations, check core.schema_migrations on lifeos for pending entries and apply them. Consider this an open recommendation: add a migrate step to forge_creatortrack_deploy.sh (apply pending migrations after successful build, before restart) so this can't recur. Flag to Justin if a deploy involves new tables/columns.

[auto-memory session 60edb075-6de4-453e-81bb-a0c9ec2a9418, confidence 0.85, mode direct]