Records how an installation runs the Dashboard and the API on sibling
hostnames (dash./api.) beside the default same-origin topology, from one
image: the API origin reaches the Dashboard at run time in a meta element,
the display host stays on the API's origin (device cookies and the offline
code cache depend on it), the API trusts its own origin as Better Auth
already does, cookies stay host-only, CORS stays narrow and becomes part of
the module UI contract, the reference proxy gains per-hostname routing, and
the deploy smoke test proves both topologies, the split one in a real
browser.
Amends ADR 0034 and extends ADR 0044.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Rebased onto main after #52 (b642d8f) and force-pushed. The branch is now its two commits (a56a853, 55accd0); the earlier "merge main into branch" commit is gone.
CI is green on 55accd0: verify, infrastructure-smoke, migration-smoke, image-build, deploy-smoke.
Rebased onto `main` after #52 (`b642d8f`) and force-pushed. The branch is now its two commits (`a56a853`, `55accd0`); the earlier "merge main into branch" commit is gone.
CI is green on `55accd0`: verify, infrastructure-smoke, migration-smoke, image-build, deploy-smoke.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
dc0a3c38acto55accd0e65Rebased onto
mainafter #52 (b642d8f) and force-pushed. The branch is now its two commits (a56a853,55accd0); the earlier "merge main into branch" commit is gone.CI is green on
55accd0: verify, infrastructure-smoke, migration-smoke, image-build, deploy-smoke.