fix: align landing metadata with content operating system

[Ankit6149]

Scope

Completes the landing-page refactor from #187 by aligning public discovery metadata with the content-operating-system positioning already live in the page body.

What changed

• replaces the retired One Brief, Every Channel browser/OpenGraph/Twitter positioning;
• updates JSON-LD and the static schema to describe SignalFlow as an approval-first content operating system in progress;
• keeps structured featureList limited to currently implemented foundation capabilities;
• explicitly labels signal detection, opportunity ranking, media production, scheduling, and narrative memory as broader product direction rather than shipped features;
• updates the generated OpenGraph image copy and alt text;
• updates the PWA manifest description;
• adds landing regression coverage so old campaign-generator metadata cannot silently return.

Truth boundary

The current Studio is described as manual source context → real model route → editable/recoverable drafts → export/confirmed connector paths. Automatic signals, opportunity ranking, media production, scheduling, and narrative memory remain future direction.

Verification

Full CI required before merge: frontend tests, production dependency audit, Next build, MCP tests, and Python tests.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
signal-flow-studio	Ready	Preview	Aug 16, 2026 6:39pm