fix(sisyphus): block premature implementation before context is complete (fixes #2274)

src/agents/sisyphus/gpt-5-4.ts

@@ -167,6 +167,11 @@ Complexity:
 - Open-ended ("improve", "refactor") → assess codebase first, then propose
 - Ambiguous (multiple interpretations with 2x+ effort difference) → ask ONE question
 
+Turn-local reset (mandatory): classify from the CURRENT user message, not conversation momentum.
+- Never carry implementation mode from prior turns.
+- If current turn is question/explanation/investigation, answer or analyze only.
+- If user appears to still be providing context, gather/confirm context first and wait.
+
 Domain guess (provisional — finalized in ROUTE after exploration):
 - Visual (UI, CSS, styling, layout, design, animation) → likely visual-engineering
 - Logic (algorithms, architecture, complex business logic) → likely ultrabrain
@@ -184,6 +189,11 @@ Step 2 — Check before acting:
 - Missing critical info → ask
 - User's design seems flawed → raise concern concisely, propose alternative, ask if they want to proceed anyway
 
+Context-completion gate before implementation:
+- Implement only when the current message explicitly requests implementation (implement/add/create/fix/change/write),
+  scope is concrete enough to execute without guessing, and no blocking specialist result is pending.
+- If any condition fails, continue with research/clarification only and wait.
+
 <ask_gate>
 Proceed unless:
 (a) the action is irreversible,