wogiflow 2.3.1 → 2.3.3

package/.claude/commands/wogi-onboard.md

@@ -842,9 +842,11 @@ Display:
 This replaces the bootstrap CLAUDE.md (created by postinstall) with the complete version rendered from Handlebars templates using the project's actual config values.
 
 ```bash
-npx flow bridge sync
+npx flow bridge sync --force
 ```
 
+**IMPORTANT**: The `--force` flag is required to overwrite the bootstrap CLAUDE.md from postinstall. Without it, bridge sync may skip the file if it doesn't recognize the marker.
+
 This runs the bridge which:
 1. Reads `.workflow/config.json` (just created in Phase 6)
 2. Renders `.workflow/templates/claude-md.hbs` with config values

package/.claude/commands/wogi-start.md

@@ -67,9 +67,11 @@ When invoked with a **quoted request** instead of a task ID, assess intent and r
 
 ### Request Categories
 
-**Conversational follow-ups** ("yes", "go ahead", "option 2", "no", "skip that"):
+**Conversational follow-ups** ("yes", "go ahead", "continue", "option 2", "no", "skip that"):
 Look back at conversation for the pending question/proposal. Execute the implied action (affirmative) or acknowledge and ask what to do instead (negative).
 
+**"Continue" after task completion**: When the user says "continue" after a task finishes and there are more tasks in `ready.json` → **start the next task immediately**. Do NOT invoke `/wogi-pre-compact`, do NOT output a compaction summary, do NOT ask about context. Just start the next task. Compaction is the system's job — it happens automatically when needed.
+
 **Failed local `/wogi-*` command** (error output containing a `/wogi-*` command name):
 When a local `/wogi-*` CLI command fails (error in output, "Unknown skill", command not found), the AI MUST:
 1. **Stop current work** — user actions always take priority over in-progress AI work
@@ -499,7 +501,7 @@ Reflection: "Have I introduced any bugs or regressions?"
 
 **Quality gate keeps failing**: Report, attempt fix, after 3 failures suggest `/wogi-debug-hypothesis`.
 
-**Context too large**: When `config.autoCompact.betweenTasks` is true (default), compact AUTOMATICALLY between tasks — do NOT ask the user. Just do it. Mid-task: commit progress, invoke `/wogi-pre-compact` directly (don't suggest — execute).
+**Context too large**: When `config.autoCompact.betweenTasks` is true (default), compact AUTOMATICALLY between tasks — do NOT ask the user, do NOT show a summary, do NOT invoke `/wogi-pre-compact`. Just compact silently and continue with the next task. The PostCompact hook restores all state automatically. Mid-task: commit progress, compact silently, resume from checkpoint. The user should never see compaction happen — it's invisible infrastructure.
 
 ## Progress Tracking (MANDATORY for L1+ tasks)
 

package/.workflow/templates/claude-md.hbs

@@ -307,7 +307,11 @@ Before closing any task, ensure all required gates pass (per `config.json → qu
 
 ## Context Management
 
-Context compaction happens automatically — WogiFlow persists all critical state to disk continuously, and the PostCompact hook restores it after compaction. You do NOT need to manually run `/wogi-pre-compact` before compaction.
+Context compaction happens **automatically and silently**. The user must NEVER be bothered with compaction. WogiFlow persists all critical state to disk continuously, and the PostCompact hook restores it after compaction.
+
+**NEVER invoke `/wogi-pre-compact` proactively.** Only run it when the user explicitly asks to compact or save context. When the user says "continue", "go ahead", or "keep going" — that means **start the next task**, not compact. Compaction is the SYSTEM's job, not yours.
+
+**Anti-pattern you MUST avoid**: User says "continue" → you decide context is getting large → you invoke `/wogi-pre-compact` → you output a long summary → you ask the user to `/compact`. This is WRONG. The user said "continue" — start the next task immediately.
 
 **What survives compaction automatically** (via PostCompact hook + state files):
 - Active task ID, title, type, and acceptance criteria
@@ -317,9 +321,13 @@ Context compaction happens automatically — WogiFlow persists all critical stat
 - Last request-log entry number
 - Routing enforcement (re-armed automatically)
 
-**`/wogi-pre-compact` is optional** — use it only when you want a detailed summary for a very long session. It is NOT required for state safety.
+**When auto-compaction triggers mid-session**: The system handles it. The PostCompact hook reloads state. You resume working on the next task from `ready.json`. No user interaction needed.
+
+**The ONLY times to invoke `/wogi-pre-compact`**:
+- User explicitly says "compact", "save context", or "running low on context"
+- `config.autoCompact.betweenTasks` is true AND you're between tasks AND context is above threshold — but even then, just compact silently and continue, don't ask
 
-**For L1+ tasks**: The pre-task context estimator (Step 0.25) checks if the task fits in remaining context. If it doesn't → compact BEFORE starting to avoid mid-task compaction.
+**For L1+ tasks**: The pre-task context estimator (Step 0.25) checks if the task fits in remaining context. If it doesn't → compact silently and continue, do NOT ask the user.
 
 ## Compact Instructions
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wogiflow",
-  "version": "2.3.1",
+  "version": "2.3.3",
   "description": "AI-powered development workflow management system with multi-model support",
   "main": "lib/index.js",
   "bin": {

package/scripts/postinstall.js

@@ -651,7 +651,8 @@ function generateBootstrapClaudeMd() {
     return;
   }
 
-  const bootstrapContent = `# Project Instructions
+  const bootstrapContent = `<!-- Generated by CLI Bridge -->
+# Project Instructions
 
 You are an AI development assistant using the WogiFlow methodology v1.0.