Source: MIZOKI audit 2026-09-06 (pinned fc8b03f9) → work-order backlog 2026-09-08 (docs/audits/AUDIT_WORK_ORDERS_2026-09-08.md); WO-44..49 added 2026-09-08 from the source-verified review v1.1 (docs/reports/MIZOKI_ACQUISITION_ECONOMICS_REVIEW_v1.1_2026-09-06.md, verified on main 635318712). Findings are hypotheses until reproduced on current main (WO-00).

Finding: The 2026-08-18 account-level GitHub App grant was made on mediaintelligence; an org installation is a separate authorization. Cloud/fleet Claude sessions, the Sep 4 review and the create_issues batch all fail on the repo (404 / token refuses). Memory ledger 4b3208ff0 notes the token lacks admin:org. #953 fixed in-repo URLs, but prompt-board files on Drive, scheduled triggers and any connector config that name mediaintelligence/MIZOKICloudRun are still stale. Files: GitHub org settings (install github.com/apps/claude on MIZOKI-3-5, grant the repo); Drive prompt-board folder 1942_8C4Dsj6hmARrBogNsy7lVZP-sKkx; scheduled-task prompts; docs/audits/wo/create_issues.sh (REPO default already correct). Fix: install/authorize the App on the org; start a NEW cloud session afterwards (credentials are scoped at session start); grep the board and triggers for mediaintelligence/MIZOKICloudRun and repoint; then run create_issues.sh --dry-run from a credentialed shell. Acceptance: a fresh cloud session can git ls-remote the org repo; create_issues.sh --dry-run lists all WO-nn; zero stale references on the board. Depends on: none. Blocks: every CC/CX prompt that runs in the cloud, and the issue batch. Owning prompt: owner/operator (WO-40..43 class); CX-1 records the result in the reconciliation table.

Status: CLOSED 2026-09-15 — Claude App on org MIZOKI-3-5 with repository_selection=all (installation 159817622); see OPEN_ITEMS.md row.