fix(env): NEXT_PUBLIC_API_URL -> live origin (api.0pt.app is dead) #23

2026-08-26T23:08:20Z

admin commented

2026-08-26 23:08:20 +00:00

Part of the OS coherence sweep (dead hostnames must not be presented as reachable defaults).

Change: .env.example NEXT_PUBLIC_API_URL https://api.0pt.app -> https://0pt.app, with a NOTE comment explaining why.

Why: api.0pt.app has no deployment behind it — it falls through to the wildcard-Vercel catch-all and returns DEPLOYMENT_NOT_FOUND. The app serves its own /api routes on the site origin (app/api/*), so the honest example value is the live origin. No code reads NEXT_PUBLIC_API_URL (grep-verified; docs/08-infrastructure.md already records "no read found"), so this is docs-of-record hygiene only — zero runtime impact.

Other api.0pt.app references found, deliberately NOT touched (contract/infra decisions outside this sweep):

contracts/openapi.yaml:17 (server URL)
infra/Caddyfile:3 and docs/08-infrastructure.md:133 (Caddy vhost)
siax.repo.json:24 (fqdn)
docs/architecture/ARCHITECTURE.md, docs/compliance/INVENTORY.md, docs/compliance/SLUTRAPPORT.md — these already flag the hostname as unverified/ej verifierat.

Do not merge without review.

Part of the OS coherence sweep (dead hostnames must not be presented as reachable defaults). **Change**: `.env.example` `NEXT_PUBLIC_API_URL` `https://api.0pt.app` -> `https://0pt.app`, with a NOTE comment explaining why. **Why**: `api.0pt.app` has no deployment behind it — it falls through to the wildcard-Vercel catch-all and returns `DEPLOYMENT_NOT_FOUND`. The app serves its own `/api` routes on the site origin (`app/api/*`), so the honest example value is the live origin. No code reads `NEXT_PUBLIC_API_URL` (grep-verified; `docs/08-infrastructure.md` already records "no read found"), so this is docs-of-record hygiene only — zero runtime impact. **Other `api.0pt.app` references found, deliberately NOT touched** (contract/infra decisions outside this sweep): - `contracts/openapi.yaml:17` (server URL) - `infra/Caddyfile:3` and `docs/08-infrastructure.md:133` (Caddy vhost) - `siax.repo.json:24` (fqdn) - `docs/architecture/ARCHITECTURE.md`, `docs/compliance/INVENTORY.md`, `docs/compliance/SLUTRAPPORT.md` — these already flag the hostname as unverified/ej verifierat. Do not merge without review.

admin added 1 commit 2026-08-26 23:08:20 +00:00

fix(env): point NEXT_PUBLIC_API_URL at the live origin, not dead api.0pt.app

CI (SIAX Cloud) / security (push) Successful in 20s

Details

CI (SIAX Cloud) / quality (push) Successful in 48s

Details

Security Scan (SIAX Cloud) / security (push) Successful in 29s

Details

CI (SIAX Cloud) / security (pull_request) Successful in 30s

Details

CI (SIAX Cloud) / quality (pull_request) Successful in 59s

Details

Security Scan (SIAX Cloud) / security (pull_request) Successful in 28s

Details

f596a771dc

api.0pt.app has no deployment behind it: it falls through to the
wildcard-Vercel catch-all and returns DEPLOYMENT_NOT_FOUND (404), like
every other dead *.0pt.app hostname. The only live hostname is 0pt.app
itself, and the app serves its own /api routes on that same origin
(app/api/*), so the honest example value is https://0pt.app.

No code reads NEXT_PUBLIC_API_URL today (grep-verified; docs/08 already
records 'no read found'), so this only stops the example file from
teaching operators a dead URL. Same coherence sweep context: only
id.cloud.siax.io and id-customers.siax.io are live IdPs — dead hostnames
must not be presented as reachable defaults anywhere.

Other api.0pt.app references (infra/Caddyfile, contracts/openapi.yaml,
siax.repo.json, docs/*) are deliberately left untouched: the docs
already flag them as unverified, and Caddyfile/openapi/repo-manifest
changes are contract/infra decisions outside this sweep's scope.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

admin merged commit into main

2026-08-27 04:36:39 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: admin/0pt#23