Skip to content

Delete every path no live deployment reaches - #190

Merged
sdcarlson merged 4 commits into
mainfrom
wp/omni/delete-undeployed-paths
Nov 2, 2026
Merged

sdcarlson merged 4 commits into
mainfrom
wp/omni/delete-undeployed-paths

Conversation

@sdcarlson

Copy link
Copy Markdown
Collaborator

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 view and wrangler 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 8a21350 if you want it back.

What changed. Four commits, each revertable:

  1. Server: LLM route and adapters, inference ledger, Postgres and migrations, OIDC auth, broker server and data plant, OAuth flow, realtime speech, Jev/Kev calls, CI's Postgres job.
  2. Client: each gate with one possible outcome becomes that outcome. Also gone: LLM client, persona engine and prompts, Mind engine, crystallize, run lineage, Think result modal, markdown answers, house keys, sign-in flow, meaning search, remote speech, semantic speech compiler, MCP and async transports, manifest provenance, and the forge:spec, eval:registry-jev, metrics:line and db:migrate tooling.
  3. Dependencies: jose, pg, react-markdown, remark-gfm, @anthropic-ai/sdk, @types/pg, direct zod.
  4. Docs: README, DEPLOYMENT, AGENTS, APEX_PLAN §7, DESIGN.

What did not change.

  • Human-only files are untouched: wrangler.jsonc, .env.example, deploy-preview.yml, .mcp.json. They now hold stale entries (see below).
  • Because deploy-preview.yml asserts 503 on five paths, those stay as one-line stubs.
  • Kept because they build or guard the live artifact: verify:curated and the nightly quality line, catalog:build, scan:bundle, tests of live code.
  • stale in the capability store stays because it is in the account backup format (MasterMind account-saves-v1).

Visible differences on the live host, once deployed.

  • GET /api/inference-runs/:id/lineage and POST /api/speech/realtime-session go from 503 to 404. /api/oauth stays 404.
  • GET /api/inference-runs keeps its 503 with a different message.
  • The LLM pill loses its re-check button, and the amber "checking" state and Think spinner flash are gone.
  • Assistant text from an imported local backup renders as plain text, without provenance chips or Crystallize. Its fields still import.

Tests run (clean build):

  • typecheck passes. lint has 0 errors and 4 warnings.
  • npm test: 856 passed, 93 files.
  • build, wrangler dry run, and scan:bundle with canaries (14 secrets, 32 files) pass.
  • test:e2e on next start: 7 of 7.

Measurements. Against the real Worker under wrangler dev:

  • The deploy gate's five paths, /, /api/public and /api/polymarket return the same status as live.
  • Golden path and world watch pass.
  • Both account-portal specs fail on that localhost port, and fail the same way on unmodified main, so that is not from this PR.

Known failures. None in CI's scope. An earlier 5-worker e2e run against wrangler dev also 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_PREVIEW is 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.

  • Turn on Workers Logs and write server events as allowlisted JSON lines #188 (draft, telemetry) will conflict badly. It edits files deleted here, and only its proxy, Polymarket and logging parts still apply.
  • server_broker remains 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: drop brokerOrigins, executeBroker and the stubs' last client together.
  • Stale entries in human-only files: .env.example lists deleted variables, and deploy-preview.yml could drop its five checks along with the stubs.

Next permissible package. The server_broker removal, 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

sdcarlson and others added 4 commits November 2, 2026 02:58
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>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-02T11:02:51.096311Z 2d8b603 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@sdcarlson
sdcarlson merged commit 3078e65 into main Nov 2, 2026
4 checks passed
@sdcarlson
sdcarlson deleted the wp/omni/delete-undeployed-paths branch November 2, 2026 11:20
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