b89e8b511e
V2 lives entirely under v2/ and is built around three asks the team raised about V1: per-video assets sometimes drifted onto the wrong trend, hashtag scrapes returned junk that wasn't filterable per-client, and there was no multi-user model behind Microsoft SSO. Highlights: - Stable TikTok numeric-id key for every per-video asset; URL form drift is logged loudly to drift_log.jsonl and never silently nulls assets. Stage 5 manifest hard-gates Stage 6 if any selected video is missing any required asset; --drop-failing auto-backfills from the next-best recipe candidates. - Per-brief engagement floor (min_likes / min_plays / min_stl_pct), applied at Apify scrape time and re-validated locally; spend_log.json records raw_returned vs kept_after_floor per scrape. - Users + teams + memberships with owner/admin/editor/viewer roles; SSO upserts a user keyed on Azure oid, auto-creates a personal team, and a super-admin is bootstrapped via BOOTSTRAP_SUPER_ADMIN_EMAIL on first sign-in. Phase A integration test: 16/16 pass. - 10-stage TS pipeline (brief → seed → scrape1 → select → scrape2 → validate → analyse → insights → trends → qa → build) wired through one CLI; each stage idempotent + resumable from disk via .state sentinels. §4.5 rubrics shipped under prompts/ and loaded into Claude calls. - React 18 + Vite + TS + Tailwind operator SPA: brief intake form, team management, super-admin user list, help/FAQ ported from V1. - Separate Docker Compose project (name: social-reporting-v2, port 3457, Postgres 5437) with deploy/setup-v2.sh, deploy-v2.sh, rollback-to-v1.sh scripts that take over V1's /social-reports URL and let us roll back. Verification: 62 unit tests pass (auth/session, ids extractor with full URL fixture, engagement floor, recipes, manifest, linking-fix, MoM compare). Live smoke run on a Dove brief: 1400 raw → 253 kept (82% culled) → 21 fully-bundled videos → 25 editorial trends across 8 brief-driven categories, with drift=0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
26 lines
1 KiB
TypeScript
26 lines
1 KiB
TypeScript
import { envStr, IS_PRODUCTION } from './env.js';
|
|
|
|
const EXPECTED = 'social-reporting-v2';
|
|
|
|
/**
|
|
* V2 ships as a separate Docker Compose project that MUST share neither containers nor
|
|
* volumes with V1. Compose derives the project name from the parent directory by default,
|
|
* which on the shared optical-dev server collapses everything under `deploy/` onto one
|
|
* project name and lets apps silently evict each other's data. Per CLAUDE.md, every
|
|
* compose file must pin a unique `name:` field. This boot guard catches the case where
|
|
* the env var didn't make it through.
|
|
*
|
|
* In dev we warn; in prod we refuse to start.
|
|
*/
|
|
export function assertComposeNameOrExit(): void {
|
|
const actual = envStr('COMPOSE_PROJECT_NAME');
|
|
if (actual === EXPECTED) return;
|
|
|
|
const msg = `[compose-name-guard] COMPOSE_PROJECT_NAME='${actual || '(unset)'}' — expected '${EXPECTED}'. ` +
|
|
`If you're running outside Docker this is fine; otherwise check docker-compose.v2.yml.`;
|
|
if (IS_PRODUCTION) {
|
|
console.error(msg);
|
|
process.exit(1);
|
|
}
|
|
console.warn(msg);
|
|
}
|