fix: remove the vestigial vercel.json ingestion service (live duplicate)

[tornidomaroc-web]

Security fix. Removes experimentalServices.ingestion from vercel.json, which was serving a live duplicate of the ingestion service. Also logs the incident as register #45 (OPEN). Two files: vercel.json (−4) + docs/PROGRESS.md (+8/−3).

The finding

GET https://tryknowflow.com/_/ingestion/health returns 200 {"ok":true,"embed_provider":"voyage",...}. The experimentalServices.ingestion block (entrypoint: services/ingestion, routePrefix: /_/ingestion) was active, serving a second copy of the FastAPI ingestion service on Vercel — alongside the real one on Railway (INGESTION_SERVICE_URL = knowflow-production.up.railway.app).

Correction to an earlier misread: this is not stale April code. Vercel rebuilds services/ingestion from the deployed commit, so the duplicate runs the same current main.py as Railway. The danger is the duplicate existing, not a code delta.

Why it matters

• (a) Token-shared. INGESTION_TOKEN is a Vercel project env var the Next route already needs, so the same token that authorizes Next→Railway also opens this copy's /convert and /embed (_check_auth is a single-token equality). VOYAGE_API_KEY is set on Vercel (confirmed), so a token-holder can burn Voyage embedding credits and run arbitrary documents through MarkItDown here — bypassing every Next-route guard (auth, per-KB doc limit, enforceLimit('upload'), rate limits), none of which live in the Python service. /convert here is Vercel-edge-capped at 4.5 MB inbound (unlike Railway), which bounds but does not remove the abuse.
• (b) /health is unauthenticated — discloses embedding provider/model/dimension and is a liveness oracle.
• (c) INGESTION_TOKEN has been reachable on an unintended public endpoint and must be rotated.

The fix

Removes only the ingestion sub-key, keeping frontend exactly as-is:

{
  "experimentalServices": {
    "frontend": {
      "routePrefix": "/",
      "framework": "nextjs"
    }
  }
}

Minimal by design — the frontend declaration is untouched, so its deploy behavior does not change.

MANDATORY preview verification before merge

On the preview deployment, confirm all:

1. Frontend still serves — the site loads and an authenticated page renders.
2. A real upload completes end-to-end via Railway (Next → Railway /convert → document reaches ready).
3. <preview>/_/ingestion/health → 404 (was 200).

Do not merge until all three pass. No blind edit to live deploy config.

Post-merge sequencing — ROTATE LAST (deliberate)

1. Merge the config fix.
2. Confirm production https://tryknowflow.com/_/ingestion/health → 404. If it does not 404, delete the service in the Vercel dashboard — config removal may be necessary-but-insufficient if Vercel persists an already-built service.
3. THEN rotate INGESTION_TOKEN on Railway first, then Vercel, as near-simultaneously as possible (a mismatch window 401s uploads until both match — an availability blip, not a security gap).

Rotate-last is intentional: rotating before teardown just re-exposes the fresh token on the still-live duplicate (shared env), so it would not help.

Scope

• Distinct incident from B5b (upload content hardening) — not B5b progress. PROGRESS.md §1 B5b row and PIVOT_PLAN.md:270 are deliberately untouched (verified: B5b row byte-identical, PIVOT_PLAN unchanged).
• docs/PROGRESS.md: new register docs: advance the three stale header lines to reality (main @ 63d498c, PR #44) #45 row + one §7 changelog block (append-only, per PR docs: migrate the changelog out of the line-8 header field into PROGRESS §7 #66) + the three header fields refreshed (the docs: migrate the changelog out of the line-8 header field into PROGRESS §7 #66 policy requires it each step; Active branch had pointed at a deleted branch, Main tip was one merge stale). Registers docs: record live-DB reconciliation + "migration ≠ applied" lesson #17 and docs: mark register #31 RESOLVED (per-language quizzes, live-proven) #44 byte-identical; all 17 landed §7 entries byte-identical.

Checks

• npm run typecheck → exit 0.
• db-types: no SQL migration touched → regenerated types byte-identical.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
knowflow	Ready	Preview, Comment	Jul 23, 2026 12:36am