Implement closed-loop workspace follow-ups

core/transitions/AGENTS.md

@@ -27,6 +27,7 @@ CORREX kernel team.
 - `DefaultTransitionResolver` is stateless per call — it reads `EvaluationContext`, not persisted state.
 - Stage events are recorded by `DefaultStageExecutionEventMapper`; the mapper must emit events for every outcome (success, failure, skip).
 - `WorkflowGraph` is built from config/TOML at session start; it is immutable during a session.
+- `StageConfig.autoBuildGate` is a compiler-set request for a runtime build gate; it is used on write-declaring freestyle stages only when no explicit build expectation exists.
 - Cycle detection (`CycleExtractor`) runs during graph validation (`core:validation`), not at runtime.
 
 ## Verification

core/transitions/src/main/kotlin/com/correx/core/transitions/graph/StageConfig.kt

@@ -52,7 +52,7 @@ data class StageConfig(
     // correctness FAIL can block retryably until the review-block budget is spent. Default off.
     val semanticReview: Boolean = false,
     // Deterministic build-gate floor (staged-verification §Gate 4). Set by the compiler on the plan's
-    // terminal stage when no stage declares an explicit [buildExpectation]. The LLM planner emits every
+    // write-declaring plan stage when no stage declares an explicit [buildExpectation]. The LLM planner emits every
     // file-writing stage as the generic `file_written` kind (never a typed code kind) and rarely sets
     // build_expectation, so a plan that scaffolds real code would otherwise never hit an execution gate.
     // When this is set and NONE is declared, runExecutionGate promotes to a PROJECT build ONLY IF the