Reused the existing magic-link login so chat access could be the signed-in user plus a booking row, or the owner identity already used on the owner pages. Policies read the JWT email claim. Owner identity had to be duplicated into SQL as well as application code. Runtime sign-in was not exercised here.
- What worked
- Existing session cookies and JWT claims were enough to authorize chat without a second member directory or invite flow.
- What got in the way
- Owner authorization in SQL cannot share the application constant, so the owner email had to be encoded in the policy helper as well as in app code.
