Merge pull request #416 from githubnext/codex/evergreen-structural-blockers

Prioritize structural Evergreen blockers

Author: mrjf

.github/workflows/evergreen.lock.yml

@@ -589,6 +589,12 @@ that command, rerun the same command, and repeat until it passes, only
 non-mechanical blockers remain, or a stop rule applies. Prefer one coherent
 gate-clearing commit over several tiny symptom commits.
 
+Prioritize structural blockers before warning churn. If the failing command is
+dominated by a large complexity, architecture, or control-flow blocker that will
+keep the gate red, address that blocker directly when it is scoped and safe; if
+it requires a broader refactor or policy decision, report that instead of
+spending the run on smaller diagnostics that cannot make the gate pass.
+
 ## Stop States
 
 End each run with exactly one of these states:

.github/workflows/evergreen.md

@@ -133,7 +133,8 @@ readiness controller and the agentic orchestrator must both respect this file.
   failures, `bun run lint` is the source of truth; do not guess from truncated
   GitHub summaries. For lint and typecheck gates, iterate locally until the
   current command passes, only non-mechanical blockers remain, or a stop rule
-  applies.
+  applies. Prioritize structural blockers, such as large complexity or
+  control-flow issues, before warning churn that cannot make the gate pass.
 - Generated file policy: recompile committed lockfiles/snapshots when their
   sources change. After editing any `.github/workflows/*.md` workflow, recompile
   and commit the generated `.lock.yml`.

.github/workflows/shared/evergreen/repo-policy.md

@@ -18,5 +18,6 @@ Prefer targeted commands over broad commands. Apply or propose the smallest
 safe patch that clears the current failing gate, not just the first diagnostic.
 For lint and typecheck failures, fix all current mechanical diagnostics from the
 same command when they are local and low-risk, then rerun the command before
-pushing. Route policy conflicts to the appropriate review or human decision
-instead of guessing.
+pushing. Prioritize structural blockers, such as large complexity or control
+flow issues, before warning churn that cannot make the gate pass. Route policy
+conflicts to the appropriate review or human decision instead of guessing.