Prepare public replay corpus release

[Taz33m]

Summary

• expands the public real-curated corpus to six verified replay cases across four event types
• adds Corpus mode filtering/sorting, per-case corpus quality summaries, and case-factory workflow status
• adds public release plumbing with Vercel config and GitHub Actions verification

Verification

• npm run verify:release
• git diff --cached --check before commit
• public hygiene and corpus quality gates pass

Notes

• Public workbench remains research/education only, not investment advice
• Deployment still requires an explicit production publish step

---

Summary by cubic

Prepares the public replay corpus for release with six verified real-curated cases across four event types, a new Corpus mode with per-case quality, and a polished public presentation. Raises corpus gates, adds a deterministic curation CLI, hardens source discovery, and wires verification for a safe public build.

• New Features

  • Added two real-curated cases: SAVE (regulatory/antitrust shock) and MMM (litigation settlement), each with held-out validation and bundle manifests.
  • Introduced Corpus mode with filter/sort (event type, ticker, source depth, validation depth, abnormal move) and per-case quality and bundle status UI.
  • Surfaced case-level corpus quality in demo payloads/types; raised public gates to 6 cases, 6 tickers, 4 event types, and full top-rank validation; updated smoke/static tests and demo aggregates (e.g., 10 blocked future sources).
  • Added real-case-workflow CLI for deterministic, offline-friendly curation with tests; expanded source_discovery to reject private DNS/credentialed URLs, cap fetch size/redirects, and support gzip/deflate, with new tests.
  • Polished public presentation: revamped README with a 45s demo and visuals, improved web UI styling, and added assets; added GitHub Actions verify workflow and vercel.json.

• Migration

  • Run npm run verify:release locally; CI runs npm run verify.
  • Vercel builds use vercel.json (npm ci, npm run web:build, output to apps/web/dist); production publish remains a manual step.
  • Public workbench is for research/education only.

^{Written for commit 8b87fbc. Summary will update on new commits.}

[cubic-dev-ai]

2 issues found across 32 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/verify.yml">

<violation number="1" location=".github/workflows/verify.yml:14">
P2: Pin GitHub Actions to full commit SHAs instead of version tags to reduce CI supply-chain risk.</violation>
</file>

<file name="apps/web/src/App.tsx">

<violation number="1" location="apps/web/src/App.tsx:1098">
P2: Event-type coverage uses only `corpus_quality.metrics`, so fallback corpus data is ignored and the coverage map can incorrectly show all required event types as missing.</violation>
</file>

_{Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.}

[cubic-dev-ai]

P2: Pin GitHub Actions to full commit SHAs instead of version tags to reduce CI supply-chain risk.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/verify.yml, line 14:

<comment>Pin GitHub Actions to full commit SHAs instead of version tags to reduce CI supply-chain risk.</comment>

<file context>
@@ -0,0 +1,31 @@
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
</file context>

[cubic-dev-ai]

P2: Event-type coverage uses only corpus_quality.metrics, so fallback corpus data is ignored and the coverage map can incorrectly show all required event types as missing.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/web/src/App.tsx, line 1098:

<comment>Event-type coverage uses only `corpus_quality.metrics`, so fallback corpus data is ignored and the coverage map can incorrectly show all required event types as missing.</comment>

<file context>
@@ -1061,6 +1078,260 @@ function ModeTabs({ activeMode, onChange }: { activeMode: Mode; onChange: (mode:
+  const validationRate = corpusQuality?.metrics.top_ranked_validated_rate
+    ?? validationCases?.aggregate?.top_ranked_validated_rate
+    ?? null;
+  const coveredEventTypes = new Set(corpusQuality?.metrics.event_types ?? []);
+  const nextAction = corpusQuality?.next_action ?? 'Generate demo assets after adding verified real-curated bundles.';
+
</file context>