clerk-backend-apilisted

## Options context User Prompt: $ARGUMENTS ## CRITICAL: Mandatory checks before EVERY write request Before ANY POST / PATCH / PUT / DELETE, you MUST do ALL of the following in your response: 1. **Check CLERK_SECRET_KEY** — verify it is set: ```bash echo $CLERK_SECRET_KEY | head -c 10 ``` If empty, stop and ask the user. Do not proceed without a valid key. 2. **Check CLERK_BAPI_SCOPES** — run: ```bash echo $CLERK_BAPI_SCOPES ``` Inspect the output. If scopes are missing or do not include the required write permission, tell the user: *"This is a write operation and your current scopes may not allow it. Rerun with --admin to bypass?"* Do NOT attempt the request and fail — ask first. 3. **For DELETE requests:** warn explicitly that the action is **IRREVERSIBLE** and list exactly what data will be permanently destroyed (user record, all sessions, all memberships, all associated data). Require explicit confirmation before proceeding. This warning is MANDATORY — never skip it. 4. **For metadata operations:** always explain which metadata type is being used and why (see Metadata types section below). --- ## FAST PATH: Common operations (use directly, no spec fetching needed) For the operations below, skip spec fetching and execute immediately using these exact templates. Substitute `$CLERK_SECRET_KEY`, `$USER_ID`, `$ORG_ID`, `$EMAIL` as needed from the user's context. ### Create organization + invite member (two-step) ```bash # Step 1 — Create orga