odd-studio 3.7.4 → 3.7.5

package/hooks/odd-studio.sh

@@ -136,6 +136,12 @@ build-gate)
   [ "$TOOL_NAME" = "Agent" ] || exit 0
   [ "$CURRENT_PHASE" = "build" ] || exit 0
 
+  # Quick-fix bypass: orchestrator can dispatch agents for small fixes without full swarm init.
+  # Marker has 1h TTL and must be explicitly created via `touch .odd/.odd-quick-fix`.
+  if marker_valid ".odd/.odd-quick-fix" 3600; then
+    exit 0
+  fi
+
   # Allow brief-generation and sync agents through
   AGENT_PROMPT=$(echo "$INPUT" | jq -r '.tool_input.prompt // empty' | head -c 300)
   if echo "$AGENT_PROMPT" | grep -qiE '(session.brief|session-brief|generate.*brief|odd-sync|fix.*hook|update.*hook)'; then
@@ -179,6 +185,13 @@ swarm-write)
     exit 0
   fi
 
+  # Quick-fix bypass: orchestrator can edit source directly for small fixes.
+  # Marker has 1h TTL and must be explicitly created via `touch .odd/.odd-quick-fix`.
+  # Use for single-file typo/type fixes where full swarm ceremony is overkill.
+  if marker_valid ".odd/.odd-quick-fix" 3600; then
+    exit 0
+  fi
+
   # Gate 2: Agent write token must be fresh (120s TTL)
   # Only Task agents create this token — the orchestrator must NOT.
   if ! marker_valid ".odd/.odd-flow-agent-token" 120; then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "odd-studio",
-  "version": "3.7.4",
+  "version": "3.7.5",
   "description": "Outcome-Driven Development for AI coding agents — a planning and build harness for domain experts building serious software with AI. Works with Claude Code, OpenCode, and Codex.",
   "keywords": [
     "claude-code",

package/skill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "odd"
-version: "3.7.4"
+version: "3.7.5"
 description: "Outcome-Driven Development planning and build coach. Use /odd to start or resume an ODD project — building personas, writing outcomes, mapping contracts, creating a Master Implementation Plan, and directing a odd-flow-powered build. Designed for domain experts who are not developers. Works with Claude Code, OpenCode, and Codex."
 metadata:
   priority: 10
@@ -106,7 +106,7 @@ Display this when no existing state is found:
 
 ---
 
-Welcome to ODD Studio v3.7.4.
+Welcome to ODD Studio v3.7.5.
 
 You are about to plan and build something real — using a methodology called Outcome-Driven Development. Before we write a single line of code, we are going to get precise about three things:
 
@@ -130,7 +130,7 @@ Display this when existing state is found. Replace the bracketed values with act
 
 ---
 
-Welcome back to ODD Studio v3.7.4.
+Welcome back to ODD Studio v3.7.5.
 
 **Project:** [project.name]
 **Current Phase:** [state.currentPhase]
@@ -400,7 +400,7 @@ Execute the following steps in order:
 
 **1. Commit the verified state** via git with message: `feat: verified [outcome name] — [phase]`
 
-> **Note:** Automated Checkpoint/vibeguard scanning was removed in v3.7.4. The scanner flagged dep-lockfile CVEs as code vulnerabilities and made every commit impossible. Security scanning is reintroduced only with a scanner that can distinguish code findings from lockfile findings. In the meantime, domain experts remain responsible for flagging anything suspicious during the verification walkthrough.
+> **Note:** Automated Checkpoint/vibeguard scanning was removed in v3.7.5. The scanner flagged dep-lockfile CVEs as code vulnerabilities and made every commit impossible. Security scanning is reintroduced only with a scanner that can distinguish code findings from lockfile findings. In the meantime, domain experts remain responsible for flagging anything suspicious during the verification walkthrough.
 
 Call `mcp__odd-flow__memory_store` key `odd-outcome-[name]` with status `verified`, namespace `odd-project`.