Skip to content

[codex] Split 1: baseline dashboard runtime changes#2

Draft
cheesss wants to merge 10 commits into
mainfrom
codex/split-runtime-dashboard-baseline
Draft

[codex] Split 1: baseline dashboard runtime changes#2
cheesss wants to merge 10 commits into
mainfrom
codex/split-runtime-dashboard-baseline

Conversation

@cheesss

@cheesss cheesss commented May 20, 2026

Copy link
Copy Markdown
Owner

Summary

First split from the oversized codex/port-hubs-from-main PR.

This PR keeps the baseline dashboard/runtime port together while excluding the large generated/cache/backup churn from the original PR. It also keeps the legacy /api/reports/nonexistent-report fallback expectation aligned for this baseline slice.

Why split

The original PR had 938 changed files and multi-million-line generated/cache deletions. This is the first stack layer so later report, seed, and backfill changes can be reviewed against a narrower base.

Validation

  • node --import tsx --test tests/event-dashboard-emerging-tech.test.mjs

Stack

  1. This PR: baseline dashboard/runtime
  2. codex/split-report-closure: report closure and evidence contract guardrails
  3. codex/split-mechanism-seed-loop: mechanism seed operating loop
  4. codex/split-bias-news-backfill: bias-aware seed backfill and news pipeline stability

cheesss and others added 9 commits April 14, 2026 13:15
… reaction platform

Remove World Monitor / operator shell / signal workspace framing.
Rewrite README to focus on the actual pipeline: news collection → canonical
event clustering → abnormal returns → matched controls → meta-model → evidence grading.
Update landing page content (EN/KO/JA) with concrete stats (40+ sources,
53k events, 116k graded outcomes) and three-layer architecture explanation.
Update package.json and VitePress descriptions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@cheesss cheesss force-pushed the codex/split-runtime-dashboard-baseline branch from 133af10 to d4469c2 Compare May 20, 2026 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant