Distillation

Date: Sep 10, 2026

• 🔴 [requested-security-review] (12:32) User requested a substantive, non-empty, READ-ONLY adversarial security review of the exact frozen worktree at /home/byk/Code/getsentry/publish against base 7c60ddb7f43040fe8fbfea70efc833f689c04e75, replacing a reviewer that had returned empty output twice.
• 🔴 [enforced-read-only-workflow] (12:32) User directed that repository state must NEVER be edited, formatted, staged, stashed, committed, or otherwise mutated; only read-only checks may be run.
• 🔴 (12:32) User required inspection of every changed tracked file using the combined HEAD diff and every untracked file.
• 🔴 (12:32) User stated the threat model must treat GitHub event payloads, issue fields, labels, comments, dispatch inputs, titles, bodies, paths, workspaces, revisions, and actor identities as attacker-controlled.
• 🔴 (12:32) User required review of approval identity/provenance and requester separation; direct-bot rejection; auto-approval proof ordering and binding; accepted/ci-ready event selection; exact request digest propagation; title/workspace/revision parsing; path and state containment; trusted default-branch controller execution and secret-free manual workflow_dispatch relay; retry-input shell safety; stale ci-ready removal, final revalidation, and mandatory re-add; exact approved revision checkout; immutable actions/Craft references; secret-scope changes; both pre-Craft fences; and dependency-free terminal deauthorization/closure.
• 🔴 (12:32) User stated existing organization-wide SENTRY_INTERNAL_APP_PRIVATE_KEY exposure is accepted as out of scope unless the diff widens that exposure.
• 🔴 (12:32) User required preservation of the invariant that every changed or re-approved request terminates the stale cycle and never reaches ci-ready.
• 🔴 (12:32) User required a pre-inspection fingerprint covering HEAD, unstaged tracked diff, staged diff, and untracked path names plus contents; the same fingerprint must be recomputed at the end and reported as identical or changed.
• 🔴 (12:32) User required findings first, ordered by severity, with every finding marked MUST-FIX, CONCERN, or PASS and supported by current file:line evidence.
• 🔴 (12:32) User required the review to explicitly state whether every changed and untracked file was inspected.
• 🔴 (12:32) User required that if any evidence cannot be obtained, the response must begin with BLOCKED and identify the exact command, tool, and error.
• 🔴 (12:32) User required the review to end with exactly MERGE or DO-NOT-MERGE on its own line.
• 🟡 (12:32) Assistant stated it would first fingerprint the exact repository state, enumerate and inspect every tracked change and untracked file without modifying the worktree, then rerun the same fingerprint and perform read-only validation.