Verify Easy Mode AI runs on the shared

Found by the finish phase of epic 13411. The epic's Done-means "A coder task in that project runs on the shared node using the sponsored AI credit" was never run. ## Observation - The "Jaah Easy Mode runners" GitHub App does not exist: `GET /orgs/jaah-ai/installations` (with `me/users/roman@gmind.tech/github_admin`) on 2026-11-04 lists only `jaah-app`. Without it, an Easy Mode runner gets the readable 409 "No Easy Mode runner app is configured" and cannot push (Task 13446, `apps/api/app/easy_mode_runner_tokens.py`). GitHub only creates an App after a signed-in person confirms the manifest form in a browser; a token cannot do it. - AC-20 (view-only console) was never run because no session has run on the shared node. - AC-7 (re-placement) was deferred: dev's Shared pool host had no room ("No shared machine has room."). ## What to do (verification; fix only a defect you find) 1. Ask the operator ONCE (AskUserQuestion, header `Human act`) to click Settings › Integrations › GitHub › Easy Mode runner app › Create the GitHub App on the dev console, install it on `jaah-ai` (all repos), save a "GitHub App key" credential, pick it in `easy_mode_runner_app_credential_id`, and share it with this task. Also ask (same round) whether to add room to dev's Shared pool for AC-7. 2. Live scope check: a minted token for test repo A pushes to A and is refused on B (cite both git outputs, never the token). 3. AC-14: in dev org `t13444-easy`, project 57907 (or a new Easy Mode project), start a coder task; observe its session on the org's shared node (`t13444-easy-shared-1` or its replacement), a pushed branch/PR via the one-repo token, and a `spend` ledger entry drawn from the sponsored credit. Debit to the floor (operator) → next task held with the balance reason and the tenant sees how to top up. 4. AC-20: as a client member, open that session's console → view-only with a read-only indication; as operator → two-way. 5. AC-7: operator disables the shared node; within one placement pass a new shared node exists and the project is reassigned (before/after). Out of scope: Lambda/app publishing (separate follow-up), any change to token minting design, the wizard, the App panel. Done means: - Scope check, AC-14, AC-20 and AC-7 each cited with dev evidence (screenshots / API output) in the report. - Any defect found fixed via a PR merged through the lane with Jaah Deploy green; otherwise settle no_pr with the evidence. - If the human act is refused or AC-7 has no pool room, settle with that oracle named as blocked.