admin/0pt
5
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

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

Merged
admin merged 1 commits from fix/os-coherence-sweep into main 2026-08-27 04:36:39 +00:00
Conversation 0 Commits 1 Files Changed 1
+4 -1
1 Commits
Author SHA1 Message Date
adminandClaude Fable 5 f596a771dc 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 
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>
 2026-08-27 01:08:03 +02:00