[setup] Register the Jaah WordPress.com OAuth app

**User-only setup task.** Only a person can do the registration steps below (a human sign-in at the vendor). Runner: do NOT attempt the vendor-side steps and do not open a PR. Ask the operator once through AskUserQuestion (header `Human act`) to do the steps; when they say it is done, run **Runner validation** on dev and settle `no_pr` / `no_code_needed`, citing the observed Connect + Test result (never a secret value). If validation fails, name the step that looks wrong and ask once more. A person must do this: registering an app at WordPress.com needs a human sign-in. It lets members connect WordPress.com to Jaah with one **Connect WordPress.com** button. ## Steps 1. Sign in to WordPress.com with the account that should own Jaah's app (a shared company account, never a personal one), and open: https://developer.wordpress.com/apps/new/ 2. Create a new OAuth app. Name it **Jaah**. 3. In the Create an Application form, enter a Description such as: Jaah agents draft and publish content on the sites you connect. 4. Under Website URL enter the public homepage of the company that runs this Jaah (its https address). 5. Put the redirect URI in the Redirect URLs field: `https://app.jaah.ai/api/credentials/connect/callback` (prod). If the field takes only one URL, create a second app named **Jaah** with `https://app.dev.jaah.ai/api/credentials/connect/callback` (dev) and do the paste steps once per environment. 6. Leave Javascript Origins empty, set Type to Web, answer the anti-spam question and select Create. 7. The Client ID and Client Secret are on the application's page (developer.wordpress.com/apps) under OAuth Information. Keep them in your password manager only until the next step is done. 8. 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-wordpress_com-app`, with provider `wordpress_com`, the client ID and the client secret. 9. Open **Settings > Integrations > OAuth apps > WordPress.com** and pick that secret in the knob `oauth_app.wordpress_com`. 10. 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 Jaah names no scopes on the sign-in request: WordPress.com grants the access set on Jaah's app itself, and lists it on its approval screen. ## Review or verification WordPress.com applications need no review; they work for any WordPress.com account once created. ## Runner validation On dev, **Connect WordPress.com** with the Jaah app ends on **Connected** and **Test** passes. Read 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 a client ID or secret anywhere. ## Done means - The operator confirmed the steps are done. - On dev, the vendor's Connect screen no longer says "Jaah app not configured", consent ends on **Connected**, and **Test** passes — cited from what you observed.