[setup] Register the Jaah Calendly OAuth app

**User-only setup task.** Only a person can do the registration steps below (it needs a human sign-in at the vendor). Runner: do NOT attempt the vendor-side steps yourself and do not open a PR. Ask the operator once through AskUserQuestion (header `Human act`) to do the steps; when they answer that it is done, run the **Runner validation** section on dev and settle with `no_pr` / `no_code_needed`, citing the observed Connect + Test result (never a secret value). If validation fails, say exactly which step looks wrong and ask once more. A person must do this: registering an app at Calendly needs a human sign-in at Calendly. It lets members connect Calendly to Jaah with one **Connect Calendly** button, without registering an app of their own. ## Steps 1. Sign in to Calendly with the account that should own Jaah's app (a shared company account, never a personal one), and open the developer console: https://calendly.com/app/developer?tab=oauth_apps 2. Create a new OAuth app. Name it **Jaah**. 3. In the Create OAuth app form choose the environment type Production and paste the redirect URI for this environment from the redirect step below: Calendly takes exactly one per app. 4. Select Next and tick the scopes listed below, and no others: Calendly fixes scopes on the app, not at sign-in. 5. Select Create. Calendly shows the client ID, client secret and webhook signing key only once. 6. Add both redirect URIs exactly as written: `https://app.dev.jaah.ai/api/credentials/connect/callback` (dev) and `https://app.jaah.ai/api/credentials/connect/callback` (prod). If Calendly allows only one redirect URI per app, create a second app named **Jaah** for dev and do the paste step below once per environment. 7. Request exactly these scopes: `users:read`, `event_types:read`, `scheduled_events:read`, `availability:read`, `organizations:read`. Why each one is needed is in the table below. 8. Copy the app's client ID and client secret. Keep them in your password manager only until the next step is done. 9. In the Jaah console of each environment (dev first, then prod), open **Secrets**, select **New**, and create an **OAuth app** (`oauth_app`) secret on the operator plane named `jaah-calendly-app`, with provider `calendly`, the client ID and the client secret. 10. Open **Settings > Integrations > OAuth apps > Calendly** and pick that secret in the knob `oauth_app.calendly`. 11. Never paste the client ID or secret into this task, a comment, a chat or an email. Reply here only with what you did. ## Scopes and why These scopes are set on the OAuth app itself, not chosen at sign-in, so every connection gets exactly these. | Scope | Why Jaah asks for it | |---|---| | `users:read` | Read the connected user's profile, so the connection shows whose it is | | `event_types:read` | List event types, to hand out the right scheduling link | | `scheduled_events:read` | Read booked meetings and their invitees | | `availability:read` | Read free time before proposing a slot | | `organizations:read` | Find the organization's members, for owner and admin accounts | ## Redirect URIs - dev: `https://app.dev.jaah.ai/api/credentials/connect/callback` - prod: `https://app.jaah.ai/api/credentials/connect/callback` ## Review or verification Not required: a Production Calendly OAuth app works for every Calendly user once created. It allows one redirect URI, so dev and prod are two apps. ## Runner validation A runner checks the setup once you mark this task answered: on dev, **Connect Calendly** with the Jaah app ends on **Connected** and **Test** passes. It reads only the result, never the secret. ## Out of scope No code change. Do not edit the vendor spec, the catalog engine or any other credential. Never paste the client ID or secret into this task, a comment, a log or a report. ## Done means - The operator confirmed the steps are done. - On dev, the Calendly Connect screen no longer says "Jaah app not configured", the consent round trip ends on **Connected**, and **Test** passes — cited from what you observed.