The deployment's sign-in map makes three origins hold a session for the issuer
hanzo.id. These pin what D3 relies on from nextSignout:
- a navigating sign-out starting on any of the three visits each once, in at
most three hops, ends the captured cookie's sessions and returns to the
registered address;
- a request on a host that is none of them (api.hanzo.ai, which a Host-rewriting
route produces) ends its own sessions and starts no walk, never a loop;
- an unregistered post_logout_redirect_uri carried through the walk is still
refused at the last hop;
- IAM_SIGNOUT_APPS is honoured by a walk that starts on hanzo.ai.
No runtime change.