Turns one scoped release request into a reviewed branch artifact, preview deployment, browser-verified result, pull request, production promotion, and Slack proof using the accounts the team already owns.
Safe outputs only. Credentials, links, paths, and source identifiers were removed before publication.
Tools: GitHub issue context
Issue boundary ready The sample issue maps to two reviewed implementation paths and one safe release branch; no file content was read during scoping.
Tools: Selected repository files, GitHub Actions checks
Bounded patch plan Change one reviewed path, preview the generated branch, verify branch checks and the visible empty state, then prepare PR, promotion, Slack, and issue-proof actions.
Tools: Create release branch, Commit reviewed patch, Create Vercel preview
Preview ready The sample branch patch and preview are ready. Provider writes are simulated and clearly labeled.
Tools: Release branch checks
Branch checks passed The exact generated branch has current successful sample check evidence.
Tools: Browser Operator QA
Preview verified Visible sample evidence satisfies the requested behavior and remains inside vercel.app.
Tools: Open release pull request, Promote verified deployment, Post release proof, Update source issue
Release proof complete Selected files, branch checks, preview, browser QA, PR, promotion, notification, and source-issue sample evidence are present.
Prepare, verify, approve, and ship one bounded release with recoverable proof at every external action.