code-conductor: Command for Claude Code

Phase entry - Resume Read

Before doing anything else, restore any stored context for the current commit by running scripts/resume-read.mjs. It resolves the current git hash, prefers a valid DB snapshot (conductor-db get-snapshot), falls back to the .claude/memory/session-snapshot.json handoff file, and prints a RESUME_HIT block on a hit / nothing on a miss. Capture its stdout and its exit code with the canonical per-platform form (each first probes for node and treats its absence as a clean miss, never an error):

• Unix / Git Bash:

  if command -v node >/dev/null 2>&1; then
    resume_out="$(node scripts/resume-read.mjs 2>>.conductor/last-write.log)"; resume_rc=$?
  else resume_rc=3; resume_out=""; fi
  

• PowerShell:

  if (Get-Command node -ErrorAction SilentlyContinue) {
    $__eap = $ErrorActionPreference; $ErrorActionPreference = 'Continue'
    if (Test-Path variable:PSNativeCommandUseErrorActionPreference) {
      $__nap = $PSNativeCommandUseErrorActionPreference; $PSNativeCommandUseErrorActionPreference = $false
    }
    try {
      $resume_out = node scripts/resume-read.mjs 2>> .conductor/last-write.log; $resume_rc = $LASTEXITCODE
    } catch { $resume_rc = 3; $resume_out = "" }
    finally {
      $ErrorActionPreference = $__eap
      if (Test-Path variable:__nap) { $PSNativeCommandUseErrorActionPreference = $__nap }
    }
  } else { $resume_rc = 3; $resume_out = "" }
  

Branch on resume_rc - only 0 and 4 are meaningful; every other code proceeds fresh:

• 0 → parse the captured block and adopt it as this phase's starting context, then echo one banner to the user: > Resumed from stored snapshot @ <commit> (phase: <phase>), appending (checkpoint prose available) when the block reports prose: available. Parsing (the command owns normalization): split on \n; strip a trailing \r from every line; drop leading/trailing wholly-blank lines; require lines[0].trim() === 'RESUME_HIT' (anything else = miss); key: value lines split on the first ': ' (both sides trimmed); the pending: block is every subsequent ^\s*-\s+ line up to the first blank line or EOF, each item trimmed. Unknown keys are ignored. In PowerShell, node … binds string[] for multi-line output - normalize with $lines = @($resume_out); a $null/empty capture with resume_rc = 3 is a miss.
• 4 → operational halt. Do not run this phase's normal work. Emit exactly: SNAP_INVALID: corrupt handoff at .claude/memory/session-snapshot.json - inspect or remove it, then re-run. and enter standby awaiting user action. The corrupt file is left on disk (the script did not delete it).
• 3 or any other code → proceed fresh (clean miss, bypass, degrade, absent node, or any unexpected runtime code). Ignore the capture.

resume-read.mjs writes its own trace lines to .conductor/last-write.log via appendFileSync; the 2>> redirect above only sinks the incidental exit-4 halt reason away from the UI - it is not the trace channel.

Before starting any task, Read .claude/memory/project.md with limit: 60 and stop at its <!-- end current state --> line: that ## Current State digest is the bounded summary. For detail, Grep project.md with -n for the heading its Active spec: or Last checkpoint: line names, then Read that entry with offset and limit: 60. If the file has no ## Current State section, Read it with limit: 40 instead, then Grep ^## (Spec|Checkpoint) with -n and Read the last match of each with offset and limit: 60. Never read the whole file: its history is append-only and grows with the project.