[ancongui]

Connect a native product project and GitHub repository to a private GitHub ProjectsV2 board through the current user's separately consented OAuth account. Studio verifies the current viewer and repository, supports private personal creation with explicit confirmation or discovery of an existing personal/organization board, and configures one existing single-select field.

The dedicated setup page shows seven effective forge run statuses and their GitHub destinations. Every new choice is explicit. Completed runs still await product review and use the Paused mapping; Studio preserves the unchanged eight-key API contract without offering an inactive Succeeded control. Saving requires consent for the selected field. Unknown creation, configuration and delivery outcomes retain their original request identities and readback paths without automatic replay.

Delivery uses recorded issue/pull request evidence, committed native effect intents and exact provider readback. Current actor, project/repository access and OAuth authority are rechecked before effects. Human field changes are held for review. Schema 34 adds board configuration and custody, and permits legitimate OAuth grants without an expiry. Typed HTTP, CLI, SDK and MCP interfaces share those contracts. This implementation does not write custom remote branch fields or milestones.

The Studio source now also keeps protected SCM consent actions visible, provides an explicit registered-person search and selection, and chooses bounded or native outer scrolling from the measured space available. The three protected dialogs preserve active input identity, caret and IME composition while changing fit mode. The shared field-structure option is opt-in; other callers retain their existing structure.

Current validation covers 40 distinct affected browser cases across disclosed test cuts: 27 passed in the focused 40-case cohort and the remaining 13 passed after correcting test-only modal-width and footer assumptions. The production source stayed unchanged between those runs. Thirteen shared primitive/Wizard tests, Studio lint/format/typecheck/production build and seven capture-registry tests passed. The earlier 109-case run remains recorded as 101 passes and eight failures; it is not presented as current-source full coverage.

The retained 654-image walkthrough and its earlier documentation validation belong to the preceding source cut. Production and capture-producer changes require a fresh combined capture after source composition and review; those historical image hashes have not been re-pinned. This PR must not merge on the earlier capture evidence. The protected-consent producer now covers standard bounded and short-window flow journeys with physical action, keyboard, fit and no-write guards.

Controlled native PostgreSQL evidence covers 27 distinct Projects cases across earlier documented source cuts. The reviewed Source/handoff backend postimages passed 28 host/native-registrar cases with six effect counters at zero; that is separate from a current full-composition PostgreSQL qualification. No live GitHub consent, board effects, deployment or whole-product/CRM acceptance is claimed.