project creatortrack social meta ingest build complete 20260715T214444

Two CreatorTrack feature branches finished full build+review cycles as of 2026-07-15:

• feat/social-data-layer-and-scripts (41 commits): Social data layer rebuild, 497 transcripts scraped, per-video structure extraction, voice profile + retrieval generation, Scripts app UI + chat tool. Blind-judge eval preferred profiled scripts 17/17 (+4.9 similarity).
• feat/social-meta-ingest (M1-M5): Instagram/Facebook/TikTok ingestion, 2,646 videos across 4 platforms, cross-post matching (650-pair review queue still open).

While building, main moved 67 commits (a separate "public-platform" workstream hardening workspace-scoping on core create operations). Verified via git merge-tree dry-run: phase 2 rebases onto phase 1 with zero conflicts; phase 2 has no impact from the main drift (writes bypass the hardened endpoints); phase 1 -> main has 6 conflict files (1 mechanical, 4 needs-care, 1 genuine human-judgment add/add on docs/APP-PLAYBOOK.md). Our send-to-Task/Page code already satisfies main's new workspace contract, so no code changes needed for the drift itself.

Why: Justin explicitly did not want to rebase/ship onto an actively-moving main; recommendation was to wait until the public-platform work settles.

How to apply: Before touching either branch again, check whether main has moved further and re-verify the rebase plan. Ship sequence: rebase phase 1 onto main (resolve 6 conflicts) -> review -> Justin approves -> /ship phase 1 -> provision SOCIAL_SYNC_CRON_SECRET + enable daily-sync timer + restore transcripts/structures to prod + backfill -> Justin reconnects YouTube on ws 85 -> rebase+ship phase 2. Branches are protected from the CT dev-slot reaper; data is triple-backed-up (JSONL + SQL dump + Google Doc).

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.75, mode staged]