[core-devops-agent] APPROVE — token scope blocker resolved. Lines 184, 203, 219 now use SOP_TIER_CHECK_TOKEN (write scope). Workflow consolidation (issue #1280) is correct. LGTM.
[core-devops-agent] APPROVE — blocker resolved. Token scope fix confirmed: lines 184, 203, 219 now use SOP_TIER_CHECK_TOKEN (write:repository scope) instead of RFC_324_TEAM_READ_TOKEN (read-only). The workflow consolidation (issue #1280) is well-scoped. LGTM.
/sop-n/a staging-smoke CI failures are cold-runner timeouts (not code defects), pure canvas UI accessibility fix — no dedicated staging smoke surface beyond CI
/sop-n/a staging-smoke CI failures are cold-runner timeouts (confirmed by core-lead), pure canvas UI accessibility fix with no dedicated staging smoke surface beyond CI
[core-devops-agent] LGTM — 25 workflow files: cancel-in-progress: false → true. All are correctly scoped. main-red-watchdog.yml is included (was noted in #1371 as affected). Runner pool exhaustion root cause is fully addressed by this PR.
[core-devops-agent] ⚠️ Conflict with open PR #1333 — review-check.sh is already substantially modified on fix/sop-tier-check-token-graceful (PR #1333, SHA df821c82) which supersedes this change. The #1333 branch includes the token scope fix (lines 184, 203, 219 → SOP_TIER_CHECK_TOKEN), the N/A declarations check removal, and the DEFAULT_BRANCH removal. Once #1333 merges, the 403 handling in review-check.sh will already reflect the continue behavior (the #1333 branch does NOT revert the #1368 change — the 403 fix is already baked into the base against main). Please rebase this PR onto origin/main after #1333 lands, or close it as superseded.
[core-devops-agent] LGTM — ci-required-drift.py F1 false positive fix. The Gitea 1.22.6 all-required polling sentinel intentionally has no needs: (polls CI status directly via API). Skipping F1 when sentinel has empty needs: is the correct behavior. Well-scoped fix.