forge-orkes 0.64.2 → 0.64.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-orkes",
-  "version": "0.64.2",
+  "version": "0.64.3",
   "description": "Set up the Forge meta-prompting framework for Claude Code in your project",
   "bin": {
     "create-forge": "./bin/create-forge.js"

package/template/.claude/hooks/forge-slice-runner.sh

@@ -111,6 +111,28 @@ PHASES="$(awk '
 report_field() {  # report_field <file> <key> — a TOP-LEVEL `key:` (col 0)
   grep -E "^$2:" "$1" 2>/dev/null | head -1 | sed -E "s/^$2:[[:space:]]*//; s/[[:space:]]*(#.*)?$//; s/^\"//; s/\"$//"
 }
+report_field_flat() {  # report_field_flat <file> <key> — report_field + YAML block scalars
+  # A long interrupt question is naturally written as a block scalar (`key: |` /
+  # `key: >`), and report_field's single-line read returns the literal indicator —
+  # so the §8 ping carried "|" as the whole question (seen live: m-40 phase
+  # 73-approval-prompt-digest, 2026-07-22). When the value is a block-scalar
+  # indicator, collect the block's more-indented lines and FLATTEN to one line
+  # (newlines → spaces) so the ping payload stays a single TSV field. Blank lines
+  # inside the block are kept-as-separators; the first non-blank column-0 line
+  # (the next top-level key) ends the block. Plain scalars pass through unchanged.
+  _ff="$(report_field "$1" "$2")"
+  case "$_ff" in
+    '|'*|'>'*)
+      awk -v k="$2" '
+        hit && /^[^[:space:]]/ { exit }
+        hit { sub(/^[[:space:]]+/, ""); sub(/[[:space:]]+$/, "");
+              if (length($0)) printf "%s%s", (n++ ? " " : ""), $0; next }
+        !hit && index($0, k ":") == 1 { hit = 1 }
+      ' "$1"
+      ;;
+    *) printf '%s' "$_ff" ;;
+  esac
+}
 report_nested() {  # report_nested <file> <key> — an INDENTED `key:` (checks.*/usage.*)
   # The report nests checks.failed and usage.model under their parent block;
   # report_field's `^key:` anchor can't see them. Each nested key we read
@@ -501,7 +523,7 @@ for phase in $PHASES; do
         continue
       fi
       # Retry exhausted → HALT the slice early, failure evidence attached.
-      _ev="$(report_field "$report" evidence)"
+      _ev="$(report_field_flat "$report" evidence)"
       slice_notify halt slice \
         "slice HALTED at phase $phase ($idx/$total) after 1 retry — verdict=$verdict checks.failed=$cfailed; evidence: $report${_ev:+ ; $_ev}"
       printf '[runner] phase %s: HALTED after retry — failure evidence at %s\n' "$phase" "$report" >&2
@@ -582,7 +604,7 @@ for phase in $PHASES; do
       # The park happens BEFORE the next phase launches, so an irreversible action
       # (declared in the report, deferred by the phase) is caught pre-execution.
       interrupt="$(report_field "$report" interrupt)"
-      ipayload="$(report_field "$report" interrupt_payload)"
+      ipayload="$(report_field_flat "$report" interrupt_payload)"
 
       # A design fork must arrive as something to LOOK AT — the payload is a
       # sketch/mockup PATH that exists, never prose describing a visual (§8).

package/template/.forge/templates/slice-runner/phase-report.yml

@@ -31,9 +31,13 @@ interrupt: none
 
 interrupt_payload: ""
 # interrupt_payload — REQUIRED (may be empty string when interrupt==none).
-# For ambiguity/irreversible/budget: the question text to put in the ping.
+# For ambiguity/irreversible/budget: the question text to put in the ping. A long
+# question may be a YAML block scalar (`interrupt_payload: |` + indented lines) —
+# the runner flattens it to ONE line (newlines → spaces) for the ping, so write
+# it to read well as a single line too.
 # For a `fork` (design decision): a PATH to a sketch/mockup the operator LOOKS AT —
 # never prose describing a visual (brief §8: a fork arrives as something to see).
+# A fork payload must stay a single-line path, never a block scalar.
 
 checks:
   passed: 0