[codex] Split 1: baseline dashboard runtime changes#2
Draft
cheesss wants to merge 10 commits into
Draft
Conversation
… 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>
This was referenced May 20, 2026
Closed
133af10 to
d4469c2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First split from the oversized
codex/port-hubs-from-mainPR.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-reportfallback 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.mjsStack
codex/split-report-closure: report closure and evidence contract guardrailscodex/split-mechanism-seed-loop: mechanism seed operating loopcodex/split-bias-news-backfill: bias-aware seed backfill and news pipeline stability