Distillation

Date: Sep 10, 2026

• 🔴 (01:15) User-provided GitHub Actions documentation states pull_request_target runs in the context of the base repository’s default branch rather than the PR merge commit; it can label or comment on fork PRs without executing unsafe head code, and should be avoided when building or running PR code.
• 🔴 (01:15) User-provided GitHub Actions documentation states push workflows use the pushed ref’s tip commit, can run workflows not yet merged into the default branch, and revert associated SHA/refs to the default branch when a branch is deleted.
• 🔴 (01:15) User-provided GitHub Actions documentation states scheduled workflows run only on the default branch, use its latest commit, default to UTC, optionally accept an IANA timezone, and have a minimum interval of once every 5 minutes.
• 🔴 (01:15) User-provided GitHub Actions documentation states the workflow_dispatch UI button requires the workflow file on the default branch; after the workflow runs at least once, it can be dispatched against any branch or tag through the GitHub API or GitHub CLI.
• 🔴 (01:15) User-provided GitHub Actions documentation states workflow_run supports completed, requested, and in_progress; requires the workflow file on the default branch; cannot chain more than 3 levels; and can access secrets and write tokens even when the preceding workflow was unprivileged.
• 🔴 (01:15) User-provided GitHub Actions documentation states a workflow_run triggers regardless of the preceding workflow’s conclusion; jobs can branch on github.event.workflow_run.conclusion == 'success' or github.event.workflow_run.conclusion == 'failure'.
• 🔴 (01:16) User-provided repository environment configuration for production has deployment_branch_policy.custom_branch_policies=true, deployment_branch_policy.protected_branches=false, can_admins_bypass=false, and a single custom deployment branch policy: branch main.
• 🔴 (01:16) User-provided commit identifiers, in order, were: 1. d23441a48e516b6c34aea4fa41551a30e30af803, 2. 11d5960a326750d5838078e36cf38b85af677262, 3. bcd2ba49218906704ab6c1aa796996da409d3eb1, 4. 249970729cb0ef3589644e2896645e5dc5ba9c38, 5. 0057852bfaa89a56745cba8c7296529d2fc39830.
• 🔴 (01:18) User-provided tool result states actionlint is not installed.
• 🔴 (01:19) User-provided GitHub REST API documentation states API versions are date-named; breaking changes receive new versions, while additive non-breaking changes are available across all supported versions.
• 🔴 (01:19) User-provided GitHub REST API documentation states clients should select a version with the X-GitHub-Api-Version header; requests without it default to 2022-11-28, and unsupported versions return 410 Gone.
• 🔴 (01:19) User-provided GitHub REST API documentation lists supported versions as 2026-03-10 with no scheduled end of support and 2022-11-28 with support ending March 10, 2028.
• 🔴 (01:19) User-provided GitHub REST API documentation states a prior API version remains supported for at least 24 months after a newer version is released; approaching retirement is communicated with Deprecation and Sunset response headers.
• 🔴 (01:19) User-provided GitHub REST API documentation states GitHub may exceptionally make out-of-cadence changes for critical security, data-exposure, availability, or reliability issues, and may deprecate very-low-usage services outside the normal process with communication to affected integrators.
• 🔴 (01:21) User stated the corrected-tree review had returned an empty response.
• 🔴 [requested-review] (01:21) User requested an immediate non-empty corrected-tree review report listing findings first as MUST-FIX, CONCERN, or PASS, with exact current file:line evidence, command results, and tree-integrity evidence.
• 🔴 [enforced-output-format] (01:21) User required a completed review to end exactly MERGE or DO-NOT-MERGE; if incomplete, the report must begin BLOCKED, state the exact tool/error, and end exactly DO-NOT-MERGE.
• 🔴 [enforced-workflow] (01:21) User directed that files must never be edited and responses must never be empty.