wogiflow 2.4.0 → 2.4.2

package/.claude/commands/wogi-pre-compact.md

@@ -4,9 +4,9 @@ effort: medium
 ---
 Save workflow state (task progress, checkpoints, session context) before context compaction.
 
-**Why "pre-compact"**: This skill saves state but cannot trigger `/compact` programmatically — `/compact` is a Claude Code native command that only the user or Claude Code's auto-compaction can invoke. Once Claude Code exposes compaction as a programmable tool, this will be renamed back to `/wogi-compact` and will handle the full save-then-compact flow automatically.
+**CRITICAL — NEVER ASK THE USER TO COMPACT**: After saving state, output the session summary and then run `/compact` yourself immediately. Do NOT say "Now run /compact" or ask the user to do anything. Compaction must be seamless and invisible to the user. The PostCompact hook restores critical state automatically.
 
-**After running this**: Run `/compact` to actually compact the context. The PostCompact hook will restore critical state automatically.
+**NEVER INVOKE THIS PROACTIVELY**: This skill should only run when the user explicitly asks to compact or save context. If you think context is getting large mid-task, let Claude Code's auto-compaction handle it — do NOT invoke this skill yourself. The user said "implement" not "compact".
 
 ## Recursive Context Compaction
 
@@ -206,4 +206,6 @@ node node_modules/wogiflow/scripts/flow-context-compact compact --prune
 node node_modules/wogiflow/scripts/flow-context-compact context "authentication task"
 ```
 
-After providing the summary, proceed directly: run `/compact` immediately. Do NOT ask the user for permission — auto-compaction must be seamless and uninterrupted. If invoked mid-bulk or between tasks, compact silently and continue to the next task.
+After providing the summary, run `/compact` immediately — no confirmation, no "Now run /compact", no waiting. The user must NEVER be asked to compact manually. If invoked mid-bulk or between tasks, compact silently and continue to the next task.
+
+**Anti-pattern (BANNED)**: Outputting "Now run /compact to compact the context" or any variant that asks the user to take action. This has frustrated the user multiple times. YOU run /compact, not the user.

package/package.json

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

package/scripts/hooks/core/commit-log-gate.js

@@ -15,8 +15,10 @@
  * v1.0: Initial implementation — pre-commit blocking gate
  */
 
+const fs = require('node:fs');
+const path = require('node:path');
 const { execFileSync } = require('node:child_process');
-const { getConfig, getReadyData } = require('../../flow-utils');
+const { getConfig, getReadyData, PATHS } = require('../../flow-utils');
 
 /**
  * Check if a Bash command contains a git commit
@@ -120,25 +122,34 @@ function checkCommitLogGate(command, config) {
     return { allowed: true, blocked: false };
   }
 
-  // Check if request-log.md is in staged changes
-  const hasLogEntry = stagedFiles.some(f => f.endsWith('request-log.md'));
+  // Check if request-log.md contains an entry for the active task.
+  // We check file content instead of git staging because .workflow/ may be
+  // in .gitignore (intentional user choice to keep state files out of git).
+  // Checking staged files would silently fail when the directory is gitignored.
+  const task = readyData.inProgress[0];
+  const taskId = (typeof task === 'string' ? task : task.id) || 'unknown';
+
+  const logPath = path.join(PATHS.state, 'request-log.md');
+  let hasLogEntry = false;
+  try {
+    const logContent = fs.readFileSync(logPath, 'utf-8');
+    hasLogEntry = logContent.includes(taskId);
+  } catch (_err) {
+    // File doesn't exist or can't be read — no log entry
+  }
+
   if (hasLogEntry) {
     return { allowed: true, blocked: false };
   }
 
-  // Block: active task + code changes but no log entry
-  const task = readyData.inProgress[0];
-  const taskId = (typeof task === 'string' ? task : task.id) || 'unknown';
-
   return {
     allowed: false,
     blocked: true,
     reason: 'commit_without_log_entry',
     message: [
-      `BLOCKED: Active task ${taskId} but request-log.md is not staged.`,
+      `BLOCKED: Active task ${taskId} but no request-log entry found.`,
       'Add a request-log entry before committing.',
-      'Append a ### R-[N] entry to .workflow/state/request-log.md following the existing format,',
-      'then stage it: git add .workflow/state/request-log.md'
+      `Append a ### R-[N] entry referencing ${taskId} to .workflow/state/request-log.md following the existing format.`
     ].join(' ')
   };
 }

package/scripts/hooks/core/task-gate.js

@@ -296,6 +296,33 @@ function checkTaskGate(options = {}, config) {
     };
   }
 
+  // getActiveTask() returned null — check if a task EXISTS in inProgress
+  // but was rejected for missing routing proof (routedAt + receipt).
+  // This gives the AI an actionable error instead of the misleading "no active task".
+  try {
+    const readyData = getReadyData();
+    if (readyData.inProgress && readyData.inProgress.length > 0) {
+      const task = readyData.inProgress[0];
+      const taskId = typeof task === 'string' ? task : task.id;
+      if (taskId) {
+        trackBypassAttempt({
+          filePath,
+          operation,
+          reason: 'task_missing_routing_proof',
+          taskId
+        });
+        return {
+          allowed: false,
+          blocked: true,
+          message: `Task ${taskId} is in inProgress but has no routing proof (missing routedAt and no routing receipt file).\n\nThis usually means the task was inserted into ready.json manually instead of through /wogi-start.\n\nTo fix:\n1. Use /wogi-start ${taskId} to properly route this task\n2. Or remove it from inProgress and start fresh: /wogi-ready`,
+          reason: 'task_missing_routing_proof'
+        };
+      }
+    }
+  } catch (_err) {
+    // Fall through to normal "no active task" path
+  }
+
   // No active task - should we block?
   const shouldBlock = config.enforcement?.taskGating?.blockWithoutTask !== false;