docs(fjord-platform PHASE_6_DESIGN): stale gateway host example (account.rasterstate.com → forgejo-site.pages.dev) [cross-repo] #223

New issue

Open

opened 2026-07-21 16:15:13 +00:00 by stephen · 0 comments

stephen commented

2026-07-21 16:15:13 +00:00

Owner

Summary

Cross-repo doc fix — the file lives in rasterstate/fjord-platform. Filed here because fjord-platform's Forgejo issues are redirected to an external tracker (Plane, PLATFORM-*, https://plane.rasterstate.com/fjord/), so a Forgejo issue can't be opened against it directly. Move/mirror into Plane if preferred.

fjord-platform/docs/PHASE_6_DESIGN.md:242 documents the forge-gateway host as https://account.rasterstate.com/api/v1/forge-gateway/<instance-id>/api/v1/..., but that host is not the live platform. Current production is https://forgejo-site.pages.dev (reports {"mode":"live","strategy":"oidc"}); account.rasterstate.com is the Paragon admin surface (returns {"ok":false,"error":"admin_login_required"}, 401, on the API paths). The stale example points readers at the wrong origin.

Fix

Update the example in fjord-platform/docs/PHASE_6_DESIGN.md (line ~242) to the current platform origin (https://forgejo-site.pages.dev, or the canonical APP_ORIGIN / fjord.sh if that is the intended public form), matching fj's DEFAULT_PLATFORM_URL and the live deployment. One-line doc fix; no code change.

Origin

Found during the fj Fjord-account login spike while cross-reading the gateway routes against live prod. The fj client default (forgejo-site.pages.dev) and the live deployment agree; only this design-doc example is drifted.

## Summary **Cross-repo doc fix — the file lives in `rasterstate/fjord-platform`.** Filed here because fjord-platform's Forgejo issues are redirected to an external tracker (Plane, `PLATFORM-*`, https://plane.rasterstate.com/fjord/), so a Forgejo issue can't be opened against it directly. Move/mirror into Plane if preferred. `fjord-platform/docs/PHASE_6_DESIGN.md:242` documents the forge-gateway host as `https://account.rasterstate.com/api/v1/forge-gateway/<instance-id>/api/v1/...`, but that host is **not** the live platform. Current production is `https://forgejo-site.pages.dev` (reports `{"mode":"live","strategy":"oidc"}`); `account.rasterstate.com` is the Paragon admin surface (returns `{"ok":false,"error":"admin_login_required"}`, 401, on the API paths). The stale example points readers at the wrong origin. ## Fix Update the example in `fjord-platform/docs/PHASE_6_DESIGN.md` (line ~242) to the current platform origin (`https://forgejo-site.pages.dev`, or the canonical `APP_ORIGIN` / `fjord.sh` if that is the intended public form), matching `fj`'s `DEFAULT_PLATFORM_URL` and the live deployment. One-line doc fix; no code change. ## Origin Found during the `fj` Fjord-account login spike while cross-reading the gateway routes against live prod. The `fj` client default (`forgejo-site.pages.dev`) and the live deployment agree; only this design-doc example is drifted.

stephen added the

backlog

labels

2026-07-21 16:15:13 +00:00