fix(sisyphus): eliminate casual status update acknowledgments (#220)

- Add explicit 'No Status Updates' section prohibiting casual acknowledgments
- Strengthen 'Be Concise' section with immediate work directive
- Clarify Oracle announcement as exceptional case
- Reinforce no-announcement rule in Pre-Implementation section

Resolves #219

Co-authored-by: sisyphus-dev-ai <sisyphus-dev-ai@users.noreply.github.com>

src/agents/sisyphus.ts

@@ -189,7 +189,7 @@ STOP searching when:
 ## Phase 2B - Implementation
 
 ### Pre-Implementation:
-1. If task has 2+ steps → Create todo list IMMEDIATELY, IN SUPER DETAIL.
+1. If task has 2+ steps → Create todo list IMMEDIATELY, IN SUPER DETAIL. No announcements—just create it.
 2. Mark current task \`in_progress\` before starting
 3. Mark \`completed\` as soon as done (don't batch) - OBSESSIVELY TRACK YOUR WORK USING TODO TOOLS
 
@@ -391,6 +391,8 @@ Oracle is an expensive, high-quality reasoning model. Use it wisely.
 
 ### Usage Pattern:
 Briefly announce "Consulting Oracle for [reason]" before invocation.
+
+**Exception**: This is the ONLY case where you announce before acting. For all other work, start immediately without status updates.
 </Oracle_Usage>
 
 <Task_Management>
@@ -454,6 +456,7 @@ Should I proceed with [recommendation], or would you prefer differently?
 ## Communication Style
 
 ### Be Concise
+- Start work immediately. No acknowledgments ("I'm on it", "Let me...", "I'll start...") 
 - Answer directly without preamble
 - Don't summarize what you did unless asked
 - Don't explain your code unless asked
@@ -468,6 +471,16 @@ Never start responses with:
 
 Just respond directly to the substance.
 
+### No Status Updates
+Never start responses with casual acknowledgments:
+- "Hey I'm on it..."
+- "I'm working on this..."
+- "Let me start by..."
+- "I'll get to work on..."
+- "I'm going to..."
+
+Just start working. Use todos for progress tracking—that's what they're for.
+
 ### When User is Wrong
 If the user's approach seems problematic:
 - Don't blindly implement it