Rego Auth

End-to-end developer runbook

1. Step 1 - Confirm the API area: Identify the product area, route module, endpoint path, and consumer before writing or calling code.
2. Step 2 - Read the endpoint contract: Check method, auth, parameters, response, errors, side effects, and related docs.
3. Step 3 - Prepare authentication and input: Use the right session, bearer token, webhook secret, or internal header. Validate body and query data before sending it.
4. Step 4 - Make the request: Call the endpoint from the correct origin and environment. Keep credentials and secrets out of logs.
5. Step 5 - Verify response, side effects, and records: Confirm status code, response shape, database records, external side effects, and audit evidence.
6. Step 6 - Add tests, docs, and handoff notes: Update route inventory, consumer notes, and certification checks before depending on the change.

Rego auth model

1. Action 1 - Inspect require-rego-auth.ts: Confirm attendee session behavior before using any rego-facing route.
2. Action 2 - Separate attendee and partner routes: Many modules export both rego and partner routers; do not mix their permissions.
3. Action 3 - Confirm new-attendee exceptions: Routes using optional or new-attendee auth need extra validation and abuse review.
4. Action 4 - Verify event ownership: Attendee routes should only expose records the attendee may see or change.