devflow-kit 1.2.0 → 1.3.1

package/scripts/hooks/session-start-memory

@@ -0,0 +1,151 @@
+#!/bin/bash
+
+# SessionStart Hook
+# Injects working memory AND ambient skill content as additionalContext.
+# Memory: restores .memory/WORKING-MEMORY.md + patterns + git state + compact recovery.
+# Ambient: injects ambient-router SKILL.md so Claude has it in context (no Read call needed).
+# Either section can fire independently — ambient works even without memory files.
+
+set -e
+
+# jq is required to parse hook input JSON — silently no-op if missing
+if ! command -v jq &>/dev/null; then exit 0; fi
+
+INPUT=$(cat)
+
+CWD=$(echo "$INPUT" | jq -r '.cwd // ""' 2>/dev/null)
+if [ -z "$CWD" ]; then
+  exit 0
+fi
+
+CONTEXT=""
+
+# --- Section 1: Working Memory ---
+
+MEMORY_FILE="$CWD/.memory/WORKING-MEMORY.md"
+
+if [ -f "$MEMORY_FILE" ]; then
+  MEMORY_CONTENT=$(cat "$MEMORY_FILE")
+
+  # Read accumulated patterns if they exist
+  PATTERNS_FILE="$CWD/.memory/PROJECT-PATTERNS.md"
+  PATTERNS_CONTENT=""
+  if [ -f "$PATTERNS_FILE" ]; then
+    PATTERNS_CONTENT=$(cat "$PATTERNS_FILE")
+  fi
+
+  # Compute staleness warning
+  if stat --version &>/dev/null 2>&1; then
+    FILE_MTIME=$(stat -c %Y "$MEMORY_FILE")
+  else
+    FILE_MTIME=$(stat -f %m "$MEMORY_FILE")
+  fi
+  NOW=$(date +%s)
+  AGE=$(( NOW - FILE_MTIME ))
+
+  # Check for pre-compact memory snapshot (compaction recovery)
+  BACKUP_FILE="$CWD/.memory/backup.json"
+  COMPACT_NOTE=""
+  if [ -f "$BACKUP_FILE" ]; then
+    BACKUP_MEMORY=$(jq -r '.memory_snapshot // ""' "$BACKUP_FILE" 2>/dev/null)
+    if [ -n "$BACKUP_MEMORY" ]; then
+      BACKUP_TS=$(jq -r '.timestamp // ""' "$BACKUP_FILE" 2>/dev/null)
+      BACKUP_EPOCH=0
+      if [ -n "$BACKUP_TS" ]; then
+        BACKUP_EPOCH=$(date -j -f "%Y-%m-%dT%H:%M:%SZ" "$BACKUP_TS" +%s 2>/dev/null \
+          || date -d "$BACKUP_TS" +%s 2>/dev/null \
+          || echo "0")
+      fi
+      if [ "$BACKUP_EPOCH" -gt "$FILE_MTIME" ]; then
+        COMPACT_NOTE="
+--- PRE-COMPACT SNAPSHOT ($BACKUP_TS) ---
+Context was compacted. This snapshot may contain decisions or progress not yet in working memory.
+
+$BACKUP_MEMORY
+"
+      fi
+    fi
+  fi
+
+  STALE_WARNING=""
+  if [ "$AGE" -gt 3600 ]; then
+    HOURS=$(( AGE / 3600 ))
+    STALE_WARNING="⚠ This working memory is ${HOURS}h old. Verify before relying on it.
+
+"
+  fi
+
+  # Capture fresh git state
+  GIT_BRANCH=""
+  GIT_STATUS=""
+  GIT_LOG=""
+
+  if cd "$CWD" 2>/dev/null && git rev-parse --git-dir >/dev/null 2>&1; then
+    GIT_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
+    GIT_STATUS=$(git status --porcelain 2>/dev/null | head -20)
+    GIT_LOG=$(git log --oneline -5 2>/dev/null || echo "")
+  fi
+
+  # Build memory context
+  CONTEXT="${STALE_WARNING}--- WORKING MEMORY (from previous session) ---
+
+${MEMORY_CONTENT}"
+
+  # Insert accumulated patterns between working memory and git state
+  if [ -n "$PATTERNS_CONTENT" ]; then
+    CONTEXT="${CONTEXT}
+
+--- PROJECT PATTERNS (accumulated) ---
+
+${PATTERNS_CONTENT}"
+  fi
+
+  CONTEXT="${CONTEXT}
+
+--- CURRENT GIT STATE ---
+Branch: ${GIT_BRANCH}
+Recent commits:
+${GIT_LOG}"
+
+  if [ -n "$GIT_STATUS" ]; then
+    CONTEXT="${CONTEXT}
+Uncommitted changes:
+${GIT_STATUS}"
+  fi
+
+  if [ -n "$COMPACT_NOTE" ]; then
+    CONTEXT="${CONTEXT}
+${COMPACT_NOTE}"
+  fi
+fi
+
+# --- Section 2: Ambient Skill Injection ---
+
+# Inject ambient-router SKILL.md directly into context so Claude doesn't need a Read call.
+# Only injects when ambient mode is enabled (UserPromptSubmit hook present in settings).
+AMBIENT_SKILL_PATH="$HOME/.claude/skills/ambient-router/SKILL.md"
+[ ! -f "$AMBIENT_SKILL_PATH" ] && AMBIENT_SKILL_PATH="$CWD/.claude/skills/ambient-router/SKILL.md"
+
+SETTINGS_FILE="$HOME/.claude/settings.json"
+if [ -f "$AMBIENT_SKILL_PATH" ] && [ -f "$SETTINGS_FILE" ] && grep -q "ambient-prompt" "$SETTINGS_FILE" 2>/dev/null; then
+  AMBIENT_SKILL_CONTENT=$(cat "$AMBIENT_SKILL_PATH")
+  CONTEXT="${CONTEXT}
+
+--- AMBIENT ROUTER (auto-loaded) ---
+${AMBIENT_SKILL_CONTENT}"
+fi
+
+# --- Output ---
+
+# Only output if we have something to inject
+if [ -z "$CONTEXT" ]; then
+  exit 0
+fi
+
+# Output as additionalContext JSON envelope (Claude sees it as system context, not user-visible)
+jq -n --arg ctx "$CONTEXT" '{
+  "hookSpecificOutput": {
+    "hookEventName": "SessionStart",
+    "additionalContext": $ctx
+  }
+}'

package/scripts/hooks/{stop-update-memory.sh → stop-update-memory}

@@ -5,10 +5,10 @@
 # The session ends immediately — no visible edit in the TUI.
 # On failure: does nothing (stale memory is better than fake data).
 
-set -euo pipefail
+set -e
 
 # Break feedback loop: background updater's headless session triggers stop hook on exit.
-# DEVFLOW_BG_UPDATER is set by background-memory-update.sh before invoking claude.
+# DEVFLOW_BG_UPDATER is set by background-memory-update before invoking claude.
 if [ "${DEVFLOW_BG_UPDATER:-}" = "1" ]; then exit 0; fi
 
 # jq is required to parse hook input JSON — silently no-op if missing
@@ -24,7 +24,7 @@ fi
 
 # Auto-create .memory/ and ensure .gitignore entries (idempotent after first run)
 SCRIPT_DIR_EARLY="$(cd "$(dirname "$0")" && pwd)"
-source "$SCRIPT_DIR_EARLY/ensure-memory-gitignore.sh" "$CWD" || exit 0
+source "$SCRIPT_DIR_EARLY/ensure-memory-gitignore" "$CWD" || exit 0
 
 # Logging (shared log file with background updater; [stop-hook] prefix distinguishes)
 MEMORY_FILE="$CWD/.memory/WORKING-MEMORY.md"
@@ -65,7 +65,7 @@ fi
 
 # Resolve the background updater script (same directory as this hook)
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-UPDATER="$SCRIPT_DIR/background-memory-update.sh"
+UPDATER="$SCRIPT_DIR/background-memory-update"
 if [ ! -x "$UPDATER" ]; then
   log "Skipped: updater not found/not executable at $UPDATER"
   exit 0

package/shared/skills/ambient-router/SKILL.md

@@ -36,7 +36,7 @@ Determine what the user is trying to do from their prompt.
 | **EXPLORE** | "what is", "where is", "find", "show me", "explain", "how does" | "where is the config?", "explain this function" |
 | **CHAT** | greetings, meta-questions, confirmations, short responses | "thanks", "yes", "what can you do?" |
 
-**Ambiguous prompts:** Default to the lowest-overhead classification. "Update the README" → BUILD/STANDARD. Git operations like "commit this" → QUICK.
+**Ambiguous prompts:** Default to the lowest-overhead classification. "Update the README" → BUILD/GUIDED. Git operations like "commit this" → QUICK.
 
 ## Step 2: Classify Depth
 
@@ -45,10 +45,10 @@ Determine how much enforcement the prompt warrants.
 | Depth | Criteria | Action |
 |-------|----------|--------|
 | **QUICK** | CHAT intent. EXPLORE with no analytical depth ("where is X?"). Git/devops operations (commit, push, merge, branch, pr, deploy, reinstall). Single-word continuations. | Respond normally. Zero overhead. Do not state classification. |
-| **STANDARD** | BUILD/DEBUG/REVIEW/PLAN intent (any word count). EXPLORE with analytical depth ("analyze our X", "discuss how Y works"). | Read and apply 2-3 relevant skills from the selection matrix below. State classification briefly. |
-| **ESCALATE** | Multi-file architectural change, system-wide scope, > 5 files. Detailed implementation plan (100+ words with plan structure). | Respond at best effort + recommend: "This looks like it would benefit from `/implement` for full lifecycle management." |
+| **GUIDED** | BUILD/DEBUG/REVIEW/PLAN intent (any word count). EXPLORE with analytical depth ("analyze our X", "discuss how Y works"). | Read and apply 2-3 relevant skills from the selection matrix below. State classification briefly. |
+| **ELEVATE** | Multi-file architectural change, system-wide scope, > 5 files. Detailed implementation plan (100+ words with plan structure). | Respond at best effort + recommend: "This looks like it would benefit from `/implement` for full lifecycle management." |
 
-## Step 3: Select Skills (STANDARD depth only)
+## Step 3: Select Skills (GUIDED depth only)
 
 Based on classified intent, read the following skills to inform your response.
 
@@ -65,19 +65,26 @@ See `references/skill-catalog.md` for the full skill-to-intent mapping with file
 
 ## Step 4: Apply
 
+<IMPORTANT>
+When classification is GUIDED or ELEVATE, skill application is NON-NEGOTIABLE.
+Do not rationalize skipping skills. Do not respond without loading them first.
+If test-driven-development is selected, you MUST write the failing test before ANY production code.
+</IMPORTANT>
+
 - **QUICK:** Respond directly. No preamble, no classification statement.
-- **STANDARD:** State classification briefly: `Ambient: BUILD/STANDARD. Loading: test-driven-development, implementation-patterns.` Then read the selected skills and apply their patterns to your response. For BUILD intent, enforce RED-GREEN-REFACTOR from test-driven-development.
-- **ESCALATE:** Respond with your best effort, then append: `> This task spans multiple files/systems. Consider \`/implement\` for full lifecycle (exploration → planning → implementation → review).`
+- **GUIDED:** State classification briefly: `Ambient: BUILD/GUIDED. Loading: test-driven-development, implementation-patterns.` Then read the selected skills and apply their patterns. No exceptions.
+- **ELEVATE:** Respond with your best effort, then append: `> This task spans multiple files/systems. Consider \`/implement\` for full lifecycle.`
 
 ---
 
 ## Transparency Rules
 
 1. **QUICK → silent.** No classification output.
-2. **STANDARD → brief statement.** One line: intent, depth, skills loaded.
-3. **ESCALATE → recommendation.** Best-effort response + workflow nudge.
+2. **GUIDED → brief statement + full skill enforcement.** One line: intent, depth, skills loaded. Then follow every skill requirement without shortcuts.
+3. **ELEVATE → recommendation.** Best-effort response + workflow nudge.
 4. **Never lie about classification.** If uncertain, say so.
 5. **Never over-classify.** When in doubt, go one tier lower.
+6. **Never under-apply.** Rationalization is the enemy of quality. If a skill requires a step, do the step.
 
 ## Edge Cases
 

package/shared/skills/ambient-router/references/skill-catalog.md

@@ -4,7 +4,7 @@ Full mapping of DevFlow skills to ambient intents and file-type triggers. The am
 
 ## Skills Available for Ambient Loading
 
-These skills may be loaded during STANDARD-depth ambient routing.
+These skills may be loaded during GUIDED-depth ambient routing.
 
 ### BUILD Intent
 
@@ -65,4 +65,4 @@ These skills are loaded only by explicit DevFlow commands (primarily `/code-revi
 - **Maximum 3 skills** per ambient response (primary + up to 2 secondary)
 - **Primary skills** are always loaded for the classified intent
 - **Secondary skills** are loaded only when file patterns match conversation context
-- If more than 3 skills seem relevant, this is an ESCALATE signal
+- If more than 3 skills seem relevant, this is an ELEVATE signal

package/shared/skills/architecture-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: architecture-patterns
-description: Architecture analysis patterns for code review. Detects SOLID violations, tight coupling, layering issues, and dependency direction problems. Loaded by Reviewer agent when focus=architecture.
+description: This skill should be used when reviewing code for SOLID violations, tight coupling, or layering issues.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/complexity-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: complexity-patterns
-description: Complexity analysis patterns for code review. Detects high cyclomatic complexity, deep nesting, long functions, and readability issues that hinder maintainability. Loaded by Reviewer agent when focus=complexity.
+description: This skill should be used when reviewing code for high cyclomatic complexity, deep nesting, or long functions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/consistency-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: consistency-patterns
-description: Consistency analysis patterns for code review. Detects naming convention violations, pattern deviations, unnecessary simplification, and feature truncation in diffs. Loaded by Reviewer agent when focus=consistency.
+description: This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/database-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-patterns
-description: Database analysis patterns for code review. Detects missing indexes, slow queries, unsafe migrations, schema design issues, and connection pool misuse. Loaded by Reviewer agent when focus=database.
+description: This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/dependencies-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dependencies-patterns
-description: Dependency analysis patterns for code review. Detects known CVEs, outdated packages, license incompatibilities, and unnecessary transitive dependencies. Loaded by Reviewer agent when focus=dependencies.
+description: This skill should be used when reviewing dependency changes, lock files, or package additions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/documentation-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-patterns
-description: Documentation analysis patterns for code review. Detects doc drift from code changes, missing documentation for public APIs, stale comments, and misleading README sections. Loaded by Reviewer agent when focus=documentation.
+description: This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/performance-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance-patterns
-description: Performance analysis patterns for code review. Detects N+1 queries, memory leaks, unbounded allocations, I/O bottlenecks, and missing caching opportunities. Loaded by Reviewer agent when focus=performance.
+description: This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/regression-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: regression-patterns
-description: Regression analysis patterns for code review. Detects lost functionality, removed exports, changed signatures, and behavioral changes that break existing consumers. Loaded by Reviewer agent when focus=regression.
+description: This skill should be used when reviewing changes that may remove exports, change signatures, or alter behavior.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/review-methodology/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review-methodology
-description: Standard review methodology providing the 6-step process and 3-category issue classification (must-fix, should-fix, nit) used by all DevFlow review agents. Ensures consistent, fair, and actionable code reviews across all focus areas. Loaded by the unified Reviewer agent.
+description: This skill should be used when performing a code review to apply the standard 6-step review process.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Bash
 ---

package/shared/skills/security-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security-patterns
-description: Security vulnerability analysis patterns for code review. Detects injection flaws, authentication bypasses, insecure cryptography, hardcoded secrets, and missing input sanitization. Loaded by Reviewer agent when focus=security.
+description: This skill should be used when reviewing code for injection flaws, auth bypasses, or hardcoded secrets.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/self-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: self-review
-description: Self-review framework evaluating implementation quality against 9 pillars (correctness, completeness, security, performance, maintainability, testing, documentation, error handling, simplicity). Fixes P0/P1 issues immediately rather than reporting them. Used by the Scrutinizer agent as a quality gate.
+description: This skill should be used when evaluating implementation quality before submission, checking correctness, security, and simplicity.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Edit, Write, Bash
 ---

package/shared/skills/test-driven-development/SKILL.md

@@ -1,9 +1,6 @@
 ---
 name: test-driven-development
-description: >-
-  Enforce RED-GREEN-REFACTOR cycle during implementation. Write failing tests before
-  production code. Distinct from test-patterns (which reviews test quality) — this
-  skill enforces the TDD workflow during code generation.
+description: This skill should be used when implementing new features, fixing bugs, or writing new code. Enforces RED-GREEN-REFACTOR.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:
@@ -94,7 +91,7 @@ See `references/rationalization-prevention.md` for extended examples with code.
 
 ## Process Enforcement
 
-When implementing any feature under ambient BUILD/STANDARD:
+When implementing any feature under ambient BUILD/GUIDED:
 
 1. **Identify the first behavior** — What is the simplest thing this feature must do?
 2. **Write the test** — Describe that behavior as a failing test
@@ -133,7 +130,7 @@ When skipping TDD, never rationalize. State clearly: "Skipping TDD because: [spe
 
 ## Integration with Ambient Mode
 
-- **BUILD/STANDARD** → TDD enforced. Every new function/method gets test-first treatment.
+- **BUILD/GUIDED** → TDD enforced. Every new function/method gets test-first treatment.
 - **BUILD/QUICK** → TDD skipped (trivial single-file edit).
-- **BUILD/ESCALATE** → TDD mentioned in nudge toward `/implement`.
-- **DEBUG/STANDARD** → TDD applies to the fix: write a test that reproduces the bug first, then fix.
+- **BUILD/ELEVATE** → TDD mentioned in nudge toward `/implement`.
+- **DEBUG/GUIDED** → TDD applies to the fix: write a test that reproduces the bug first, then fix.

package/src/templates/settings.json

@@ -9,7 +9,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "${DEVFLOW_DIR}/scripts/hooks/stop-update-memory.sh",
+            "command": "${DEVFLOW_DIR}/scripts/hooks/run-hook stop-update-memory",
             "timeout": 10
           }
         ]
@@ -20,7 +20,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "${DEVFLOW_DIR}/scripts/hooks/session-start-memory.sh",
+            "command": "${DEVFLOW_DIR}/scripts/hooks/run-hook session-start-memory",
             "timeout": 10
           }
         ]
@@ -31,7 +31,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "${DEVFLOW_DIR}/scripts/hooks/pre-compact-memory.sh",
+            "command": "${DEVFLOW_DIR}/scripts/hooks/run-hook pre-compact-memory",
             "timeout": 10
           }
         ]

package/scripts/hooks/session-start-memory.sh

@@ -1,126 +0,0 @@
-#!/bin/bash
-
-# Working Memory: SessionStart Hook
-# Reads .memory/WORKING-MEMORY.md and injects it as additionalContext for the new session.
-# Also captures fresh git state so Claude knows what's changed since the memory was written.
-# Adds staleness warning if memory is >1 hour old.
-
-set -euo pipefail
-
-# jq is required to parse hook input JSON — silently no-op if missing
-if ! command -v jq &>/dev/null; then exit 0; fi
-
-INPUT=$(cat)
-
-CWD=$(echo "$INPUT" | jq -r '.cwd // ""' 2>/dev/null)
-if [ -z "$CWD" ]; then
-  exit 0
-fi
-
-MEMORY_FILE="$CWD/.memory/WORKING-MEMORY.md"
-
-# No memory file = nothing to restore (fresh project or first session)
-if [ ! -f "$MEMORY_FILE" ]; then
-  exit 0
-fi
-
-MEMORY_CONTENT=$(cat "$MEMORY_FILE")
-
-# Read accumulated patterns if they exist
-PATTERNS_FILE="$CWD/.memory/PROJECT-PATTERNS.md"
-PATTERNS_CONTENT=""
-if [ -f "$PATTERNS_FILE" ]; then
-  PATTERNS_CONTENT=$(cat "$PATTERNS_FILE")
-fi
-
-# Compute staleness warning
-if stat --version &>/dev/null 2>&1; then
-  FILE_MTIME=$(stat -c %Y "$MEMORY_FILE")
-else
-  FILE_MTIME=$(stat -f %m "$MEMORY_FILE")
-fi
-NOW=$(date +%s)
-AGE=$(( NOW - FILE_MTIME ))
-
-# Check for pre-compact memory snapshot (compaction recovery)
-BACKUP_FILE="$CWD/.memory/backup.json"
-COMPACT_NOTE=""
-if [ -f "$BACKUP_FILE" ]; then
-  BACKUP_MEMORY=$(jq -r '.memory_snapshot // ""' "$BACKUP_FILE" 2>/dev/null)
-  if [ -n "$BACKUP_MEMORY" ]; then
-    BACKUP_TS=$(jq -r '.timestamp // ""' "$BACKUP_FILE" 2>/dev/null)
-    BACKUP_EPOCH=0
-    if [ -n "$BACKUP_TS" ]; then
-      BACKUP_EPOCH=$(date -j -f "%Y-%m-%dT%H:%M:%SZ" "$BACKUP_TS" +%s 2>/dev/null \
-        || date -d "$BACKUP_TS" +%s 2>/dev/null \
-        || echo "0")
-    fi
-    if [ "$BACKUP_EPOCH" -gt "$FILE_MTIME" ]; then
-      COMPACT_NOTE="
---- PRE-COMPACT SNAPSHOT ($BACKUP_TS) ---
-Context was compacted. This snapshot may contain decisions or progress not yet in working memory.
-
-$BACKUP_MEMORY
-"
-    fi
-  fi
-fi
-
-STALE_WARNING=""
-if [ "$AGE" -gt 3600 ]; then
-  HOURS=$(( AGE / 3600 ))
-  STALE_WARNING="⚠ This working memory is ${HOURS}h old. Verify before relying on it.
-
-"
-fi
-
-# Capture fresh git state
-GIT_BRANCH=""
-GIT_STATUS=""
-GIT_LOG=""
-
-if cd "$CWD" 2>/dev/null && git rev-parse --git-dir >/dev/null 2>&1; then
-  GIT_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
-  GIT_STATUS=$(git status --porcelain 2>/dev/null | head -20)
-  GIT_LOG=$(git log --oneline -5 2>/dev/null || echo "")
-fi
-
-# Build context string
-CONTEXT="${STALE_WARNING}--- WORKING MEMORY (from previous session) ---
-
-${MEMORY_CONTENT}"
-
-# Insert accumulated patterns between working memory and git state
-if [ -n "$PATTERNS_CONTENT" ]; then
-  CONTEXT="${CONTEXT}
-
---- PROJECT PATTERNS (accumulated) ---
-
-${PATTERNS_CONTENT}"
-fi
-
-CONTEXT="${CONTEXT}
-
---- CURRENT GIT STATE ---
-Branch: ${GIT_BRANCH}
-Recent commits:
-${GIT_LOG}"
-
-if [ -n "$GIT_STATUS" ]; then
-  CONTEXT="${CONTEXT}
-Uncommitted changes:
-${GIT_STATUS}"
-fi
-
-if [ -n "$COMPACT_NOTE" ]; then
-  CONTEXT="${CONTEXT}
-${COMPACT_NOTE}"
-fi
-
-# Output as additionalContext JSON envelope (Claude sees it as system context, not user-visible)
-jq -n --arg ctx "$CONTEXT" '{
-  "hookSpecificOutput": {
-    "hookEventName": "SessionStart",
-    "additionalContext": $ctx
-  }
-}'