project creatortrack social branches ship gated on rebase 20260715T214425
name: CreatorTrack social branches: build-complete, ship blocked on main-drift rebase description: Two CT feature branches (social-data-layer-and-scripts, social-meta-ingest) are fully built/reviewed/verified but unshipped; main drifted 67 commits; rebase risk assessed as low. type: project
As of 2026-07-15, two long-lived CreatorTrack feature branches finished their full build+review+verification cycle and are sitting ready in dev slots, not yet shipped:
feat/social-data-layer-and-scripts(41 commits): Social rebuilt as a real data layer (497 transcripts scraped, per-video structure extraction, voice-profile + retrieval generation, Scripts app UI + chat tool). Blind-judge eval preferred profiled scripts 17/17.feat/social-meta-ingest(5 tasks, M1-M5): Instagram/Facebook/TikTok ingestion, 2,646 videos across 4 platforms, cross-post matching (650-pair review queue still open).
While these branches were in flight, main moved 67 commits ahead (a separate "public-platform" workstream hardening workspace-scoping on core create operations: createTask/createNode/createBlock, plus new scheduling/booking + workspace-slug-registry migrations). A dry-run rebase simulation (git merge-tree, no mutation) found: phase 2 rebases onto phase 1 with zero conflicts; phase 2 has no impact from main's drift; phase 1 to main has 6 conflict files (1 mechanical, 4 needs-care, 1 human-judgment doc merge) but no semantic breakage, since the branches' create-calls already pass workspace ids that satisfy main's new hardening.
Why: Justin flagged the drift himself mid-session ("my public platform work is happening in parallel") after a session restart interrupted the final-pass review agents; this materially changed the ship story from "just get a go-ahead" to "rebase carefully, then get a go-ahead."
How to apply: Before shipping either branch, rebase phase 1 onto current main (resolve the 6 known conflict files), re-run verification, and get Justin's explicit approval. Recommended to wait until the public-platform workstream reaches a settling point rather than rebasing onto a still-moving main. Ship-time checklist: provision SOCIAL_SYNC_CRON_SECRET, enable daily-sync timer, restore transcripts+structures into prod from the durable export (JSONL + SQL dump + Google Doc backups exist), re-run backfills, Justin reconnects YouTube on ws 85 for impressions/CTR. See [[reference_creatortrack_client]] and [[project_creatortrack_social_scripts_productization]] for prior state.
[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.72, mode staged]