ADR-035: GitHub write scope lives in a separately permissioned response adapter
GitHub write scope lives in a separately permissioned response adapter
GitHub write scope lives in a separately permissioned response adapter
How data reaches a GitHub deployment-gate verdict: what each connector scans, on what trigger, how stale it is at the moment GitHub holds a deployment, where the write-capable response adapter sits, and what the gate persists.
Engineering plan of record for the committed GitHub Deployment Gate build: Track 1 use-case-independent substrate that starts now, Track 2 last mile that follows the use-case selection, the reliability substrate that precedes any T2 hold, the ApprovalPayload contract, work breakdown, test strategy, rollout tiers and the sub-issue set under sv0-platform#1884.