wogiflow 2.3.1 → 2.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -67,9 +67,11 @@ When invoked with a **quoted request** instead of a task ID, assess intent and r
67
67
 
68
68
  ### Request Categories
69
69
 
70
- **Conversational follow-ups** ("yes", "go ahead", "option 2", "no", "skip that"):
70
+ **Conversational follow-ups** ("yes", "go ahead", "continue", "option 2", "no", "skip that"):
71
71
  Look back at conversation for the pending question/proposal. Execute the implied action (affirmative) or acknowledge and ask what to do instead (negative).
72
72
 
73
+ **"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.
74
+
73
75
  **Failed local `/wogi-*` command** (error output containing a `/wogi-*` command name):
74
76
  When a local `/wogi-*` CLI command fails (error in output, "Unknown skill", command not found), the AI MUST:
75
77
  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?"
499
501
 
500
502
  **Quality gate keeps failing**: Report, attempt fix, after 3 failures suggest `/wogi-debug-hypothesis`.
501
503
 
502
- **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 suggestexecute).
504
+ **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.
503
505
 
504
506
  ## Progress Tracking (MANDATORY for L1+ tasks)
505
507
 
@@ -307,7 +307,11 @@ Before closing any task, ensure all required gates pass (per `config.json → qu
307
307
 
308
308
  ## Context Management
309
309
 
310
- 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.
310
+ 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.
311
+
312
+ **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.
313
+
314
+ **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.
311
315
 
312
316
  **What survives compaction automatically** (via PostCompact hook + state files):
313
317
  - Active task ID, title, type, and acceptance criteria
@@ -317,9 +321,13 @@ Context compaction happens automatically — WogiFlow persists all critical stat
317
321
  - Last request-log entry number
318
322
  - Routing enforcement (re-armed automatically)
319
323
 
320
- **`/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.
324
+ **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.
325
+
326
+ **The ONLY times to invoke `/wogi-pre-compact`**:
327
+ - User explicitly says "compact", "save context", or "running low on context"
328
+ - `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
321
329
 
322
- **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.
330
+ **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.
323
331
 
324
332
  ## Compact Instructions
325
333
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "wogiflow",
3
- "version": "2.3.1",
3
+ "version": "2.3.2",
4
4
  "description": "AI-powered development workflow management system with multi-model support",
5
5
  "main": "lib/index.js",
6
6
  "bin": {