feat: refactor landing page around SignalFlow content operating system

[Ankit6149]

Scope

Implements the landing-page direction in #135 without changing Studio/domain/provider/publishing behavior.

What changed

• rewrote the hero around the actual content-operations problem rather than one source → 12 destinations;
• clearly separates available today from product direction / in development;
• keeps Open Studio as the primary current CTA;
• explains the canonical Signal → Opportunity → Story → Produce → Judge → Publish/Remember lifecycle;
• adds a truthful current-foundation section for manual source intake, real configured AI routes, edit-safe review/recovery, and export;
• introduces product-direction visuals for media decisioning without presenting them as live capability;
• explains approval, private/local processing direction, and multi-client architecture at a high level;
• replaces the disconnected landing visual rhythm with one scoped, responsive CSS-module system;
• adds deliberate mobile/tablet reflow, focus states, containment, and reduced-motion handling.

Repository health repaired while verifying

The canonical documentation reset had left four frontend regression guards coupled to retired headings/copy. Those tests were updated to protect the same implementation invariants against the new canonical docs instead of weakening or deleting the guards.

The production audit also exposed a transitive nanoid high-severity advisory. The lockfile was safely refreshed from 3.3.16 to 3.3.18 through npm's non-forced audit fix path. Next remains pinned at 16.2.11; no forced framework upgrade was taken.

Truth boundary

No automatic signals, opportunities, media generation/editing, Private Hybrid, mobile, desktop agent, durable scheduling, or narrative memory capability is presented as currently shipped.

Current-product wording remains limited to the capabilities documented in docs/CAPABILITY_MATRIX.md.

Final changed files

• frontend/components/LandingPage.js
• frontend/components/LandingPage.module.css
• frontend/package-lock.json
• frontend/tests/landingPageRevamp.test.mjs
• four existing product/document regression guards aligned with the canonical documentation reset

Temporary CI diagnostics/repair workflows were removed; .github/workflows/ci.yml is back to the repository's original standard pipeline and has no net PR diff.

Verification

Final normal CI is green:

• MCP tests ✅
• Python tests ✅
• frontend npm test ✅
• npm audit --omit=dev --audit-level=high ✅
• npm run build ✅

Rendered production/deployment inspection remains a deployment-level check after merge; implementation and repository gates are complete.

[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:33pm