Distillation

🟡 (11:47) [requested-review] User requested a READ-ONLY, substantive adversarial security review of the exact current worktree at /home/byk/Code/getsentry/publish against base commit 7c60ddb7f43040fe8fbfea70efc833f689c04e75 (origin/main). 🔴 (11:47) [enforced-read-only-workflow] User prohibited editing, formatting, staging, stashing, committing, or otherwise mutating any file or repository state during the security review. 🟡 (11:47) User requested inspection of every changed tracked file, combining staged and unstaged changes, and every untracked file. 🔴 (11:47) User directed the review to use git diff HEAD plus direct reads of untracked files, rather than relying only on git diff. 🔴 (11:47) User stated GitHub event payloads and issue content must be treated as attacker-controlled. 🟡 (11:47) User requested review of: approval authorization/provenance; request snapshot binding; accepted/ci-ready event binding; canonical title/workspace/revision parsing; poller trusted-code execution and manual recovery; CI transitions/races; exact-revision checkout; path/state containment; secret exposure; action/container pinning; final pre-Craft fence; and terminal cleanup/reconciliation. 🔴 (11:47) User stated the accepted scope decision that SENTRY_INTERNAL_APP_PRIVATE_KEY is an existing organization-level secret available broadly; the change must not be blocked solely because that secret cannot be migrated in this worktree, but any NEW widening introduced by the diff must be reported. 🔴 (11:47) User stated the authorization invariant that direct bot labels never fall through to collaborator permission. 🔴 (11:47) User stated the approval invariant that the requester cannot self-approve. 🔴 (11:47) User stated renamed, body-changed, dry-run-changed, re-approved, or revision-changed releases never reach ci-ready in the stale cycle. 🔴 (11:47) User stated the poller removes stale ci-ready, revalidates, and always re-adds ci-ready. 🔴 (11:47) User stated workflow_dispatch manual recovery executes only trusted default-branch controller code. 🟡 (11:47) User authorized read-only tests/checks if useful. 🟡 (11:47) User requested an initial and final fingerprint covering HEAD, tracked diff, staged diff, and untracked file paths plus contents, followed by verification that the fingerprint remained unchanged. 🔴 (11:47) User required findings to appear first, ordered by severity, with current file:line evidence and one of the classifications MUST-FIX, CONCERN, or PASS. 🟡 (11:47) User requested an explicit statement that every changed file was inspected. 🔴 (11:47) User required that, if blocked, the response begin with BLOCKED and name the exact tool/error. 🔴 (11:47) User required the final security-review response to end with exactly MERGE or DO-NOT-MERGE. 🔴 (11:47) User directed: “Never return empty output.”