Repository navigation
Delete every path no live deployment reaches - #190
Merged
Merged
Conversation
The one live app is the Worker at omni.syberlabs.io: demo mode on, no secrets, no database. So the LLM route, inference ledger and Postgres, hosted auth, capability broker server, data plant, OAuth flow, realtime speech and Jev/Kev calls could not run. The five paths the deploy gate checks stay as one-line 503 stubs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… orphaned Gates with one possible outcome on the live Worker become that outcome. Visitors see the same messages. Deleted: the client LLM stack, persona prompts and engine, crystallize, run lineage, markdown answers, house keys, OAuth sign-in, meaning search, remote speech, the semantic speech compiler, MCP and async transports, manifest provenance, and the tooling and tests only those paths used. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jose, pg, react-markdown, remark-gfm, @anthropic-ai/sdk, @types/pg and the direct zod pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Objective. Delete every path no live deployed app can reach (owner's rule). The one live app is the Worker at omni.syberlabs.io: demo mode on, no secrets, no database (checked with
wrangler versions viewandwrangler secret list; no other Flyspace Worker is on the account). Treating those as constants leaves about 22k fewer lines (172 files, +786/−22,661).This removes AI answers from the codebase, not only from the preview. The full app has no deployment, so by this rule its model path is dead. Everything is at
8a21350if you want it back.What changed. Four commits, each revertable:
forge:spec,eval:registry-jev,metrics:lineanddb:migratetooling.jose,pg,react-markdown,remark-gfm,@anthropic-ai/sdk,@types/pg, directzod.What did not change.
wrangler.jsonc,.env.example,deploy-preview.yml,.mcp.json. They now hold stale entries (see below).deploy-preview.ymlasserts 503 on five paths, those stay as one-line stubs.verify:curatedand the nightly quality line,catalog:build,scan:bundle, tests of live code.stalein the capability store stays because it is in the account backup format (MasterMindaccount-saves-v1).Visible differences on the live host, once deployed.
GET /api/inference-runs/:id/lineageandPOST /api/speech/realtime-sessiongo from 503 to 404./api/oauthstays 404.GET /api/inference-runskeeps its 503 with a different message.Tests run (clean build):
typecheckpasses.linthas 0 errors and 4 warnings.npm test: 856 passed, 93 files.build, wrangler dry run, andscan:bundlewith canaries (14 secrets, 32 files) pass.test:e2eonnext start: 7 of 7.Measurements. Against the real Worker under
wrangler dev:/,/api/publicand/api/polymarketreturn the same status as live.main, so that is not from this PR.Known failures. None in CI's scope. An earlier 5-worker e2e run against
wrangler devalso failed golden path and world watch; both passed at 2 workers, which I read as load, not proven.Claim ceiling. Tested locally. Not deployed:
DEPLOY_PREVIEWis off, and live is still the 2026-10-12 version, so merging changes nothing on the host until someone deploys.Architectural decisions introduced. Liveness is now defined by the deployed Worker. AGENTS.md carries the rule and APEX_PLAN §7 records the cut.
Evidence that could falsify it. A deployment this account's Cloudflare listing does not show, such as a private full-app instance, would make its paths live. The docs say none exists; I could not check beyond this account.
Needs the owner, not in this PR.
server_brokerremains on the browser side. Curated FRED still routes through the 503 stub, so a visitor's typed key is POSTed to our Worker before the error. Not new, but worth removing: dropbrokerOrigins,executeBrokerand the stubs' last client together..env.examplelists deleted variables, anddeploy-preview.ymlcould drop its five checks along with the stubs.Next permissible package. The
server_brokerremoval, then deploying.GitHits was unavailable this session (the server failed to connect). This PR only removes dependencies and changes no dependency API, so no grounding was needed or claimed.
🤖 Generated with Claude Code