juno-code 1.0.42 → 1.0.43

package/dist/templates/scripts/kanban.sh

@@ -9,6 +9,12 @@
 #
 # Usage: ./.juno_task/scripts/kanban.sh [juno-kanban arguments]
 # Example: ./.juno_task/scripts/kanban.sh list --limit 5
+# Example: ./.juno_task/scripts/kanban.sh list -f json --raw  # (flag order normalized)
+# Example: ./.juno_task/scripts/kanban.sh -f json --raw list  # (also works)
+#
+# Note: Global flags (-f/--format, -p/--pretty, --raw, -v/--verbose, -c/--config)
+#       can be placed anywhere in the command line. This wrapper normalizes them
+#       to appear before the command for juno-kanban compatibility.
 #
 # Environment Variables:
 #   JUNO_DEBUG=true    - Show [DEBUG] diagnostic messages
@@ -170,6 +176,67 @@ PROJECT_ROOT="$( cd "$SCRIPT_DIR/../.." && pwd )"
 # Change to project root
 cd "$PROJECT_ROOT"
 
+# Arrays to store normalized arguments (declared at script level for proper handling)
+declare -a NORMALIZED_GLOBAL_FLAGS=()
+declare -a NORMALIZED_COMMAND_ARGS=()
+
+# Normalize argument order for juno-kanban
+# juno-kanban requires global flags BEFORE the command, but users often
+# write them after (e.g., "list -f json --raw" instead of "-f json --raw list")
+# This function reorders arguments so global flags come first.
+# Results are stored in NORMALIZED_GLOBAL_FLAGS and NORMALIZED_COMMAND_ARGS arrays.
+normalize_arguments() {
+    # Reset arrays
+    NORMALIZED_GLOBAL_FLAGS=()
+    NORMALIZED_COMMAND_ARGS=()
+    local found_command=false
+
+    # Known subcommands
+    local commands="create search get show update archive mark list merge"
+
+    while [[ $# -gt 0 ]]; do
+        case $1 in
+            # Global flags that take a value
+            -f|--format|-c|--config)
+                if [[ -n "${2:-}" ]]; then
+                    NORMALIZED_GLOBAL_FLAGS+=("$1" "$2")
+                    shift 2
+                else
+                    NORMALIZED_GLOBAL_FLAGS+=("$1")
+                    shift
+                fi
+                ;;
+            # Global flags that don't take a value
+            -p|--pretty|--raw|-v|--verbose|-h|--help|--version)
+                NORMALIZED_GLOBAL_FLAGS+=("$1")
+                shift
+                ;;
+            # Check if this is a known command
+            *)
+                # Check if this argument is a known command
+                local is_command=false
+                for cmd in $commands; do
+                    if [[ "$1" == "$cmd" ]]; then
+                        is_command=true
+                        found_command=true
+                        break
+                    fi
+                done
+
+                # If we found a command, everything from here goes to command_args
+                if $is_command || $found_command; then
+                    NORMALIZED_COMMAND_ARGS+=("$1")
+                    found_command=true
+                else
+                    # Before finding a command, treat as command arg
+                    NORMALIZED_COMMAND_ARGS+=("$1")
+                fi
+                shift
+                ;;
+        esac
+    done
+}
+
 # Main kanban logic
 main() {
     log_info "=== juno-kanban Wrapper ==="
@@ -182,11 +249,26 @@ main() {
 
     log_success "Python environment ready!"
 
-    # Execute juno-kanban with all passed arguments from project root
+    # Normalize argument order (global flags before command)
+    # This allows users to write "list -f json --raw" which gets reordered to "-f json --raw list"
+    normalize_arguments "$@"
+
+    if [ "${JUNO_DEBUG:-false}" = "true" ]; then
+        echo "[DEBUG] Original args: $*" >&2
+        echo "[DEBUG] Normalized global flags: ${NORMALIZED_GLOBAL_FLAGS[*]:-<none>}" >&2
+        echo "[DEBUG] Normalized command args: ${NORMALIZED_COMMAND_ARGS[*]:-<none>}" >&2
+    fi
+
+    # Execute juno-kanban with normalized arguments from project root
     # Close stdin (redirect from /dev/null) to prevent hanging when called from tools
     # that don't provide stdin (similar to Issue #42 hook fix)
-    log_info "Executing juno-kanban: $*"
-    juno-kanban "$@" < /dev/null
+    # Build the command properly preserving argument quoting
+    log_info "Executing juno-kanban with normalized arguments"
+
+    # Execute with proper array expansion to preserve quoting
+    # Use ${arr[@]+"${arr[@]}"} pattern to handle empty arrays with set -u
+    juno-kanban ${NORMALIZED_GLOBAL_FLAGS[@]+"${NORMALIZED_GLOBAL_FLAGS[@]}"} \
+                ${NORMALIZED_COMMAND_ARGS[@]+"${NORMALIZED_COMMAND_ARGS[@]}"} < /dev/null
 }
 
 # Run main function with all arguments

package/dist/templates/scripts/run_until_completion.sh

@@ -360,7 +360,9 @@ PROJECT_ROOT="$( cd "$SCRIPT_DIR/../.." && pwd )"
 cd "$PROJECT_ROOT"
 
 # Function to get a snapshot of kanban state for comparison
-# Returns a sorted string of "task_id:status" pairs
+# Uses the summary statistics (total_tasks + status_counts) as a reliable indicator
+# of kanban state changes. This approach is more robust than parsing multi-line JSON
+# which can contain control characters that break jq parsing.
 get_kanban_state_snapshot() {
     local snapshot=""
 
@@ -370,24 +372,44 @@ get_kanban_state_snapshot() {
         return
     fi
 
-    # Get all non-done/archive tasks as JSON
+    # Use --raw format for cleaner JSON output
+    # The --raw flag outputs: line 1 = tasks array, line 2 = summary object
     local kanban_output
-    if kanban_output=$("$KANBAN_SCRIPT" list --status backlog todo in_progress 2>/dev/null); then
-        # Extract just the JSON array part (skip the SUMMARY section)
-        local json_part
-        json_part=$(echo "$kanban_output" | grep -E '^\[' | head -1)
-
-        if [[ -z "$json_part" ]]; then
-            # Try to find JSON array in the output
-            json_part=$(echo "$kanban_output" | sed -n '/^\[/,/^\]/p' | head -1)
-        fi
+    if kanban_output=$("$KANBAN_SCRIPT" -f json --raw list --status backlog todo in_progress 2>/dev/null); then
+        if command -v jq &> /dev/null; then
+            # Extract the summary line (last line of --raw output)
+            local summary_line
+            summary_line=$(echo "$kanban_output" | tail -1)
+
+            # Extract status counts from summary - this is a reliable state indicator
+            # Format: "backlog:N|done:N|in_progress:N|todo:N|archive:N|total:N"
+            local summary_snapshot=""
+            if [[ -n "$summary_line" ]] && echo "$summary_line" | grep -q '"summary"'; then
+                summary_snapshot=$(echo "$summary_line" | jq -r '
+                    .summary |
+                    "backlog:\(.status_counts.backlog // 0)|" +
+                    "todo:\(.status_counts.todo // 0)|" +
+                    "in_progress:\(.status_counts.in_progress // 0)|" +
+                    "done:\(.status_counts.done // 0)|" +
+                    "archive:\(.status_counts.archive // 0)|" +
+                    "total:\(.total_tasks // 0)"
+                ' 2>/dev/null)
+            fi
 
-        # If we have JSON output, extract task IDs and statuses
-        if [[ -n "$json_part" ]] && command -v jq &> /dev/null; then
-            # Create a deterministic snapshot: sorted "id:status" pairs
-            snapshot=$(echo "$kanban_output" | jq -r 'if type == "array" then .[] | "\(.id):\(.status)" else empty end' 2>/dev/null | sort | tr '\n' '|')
+            # Also try to extract task IDs using grep (more robust than jq for multi-line JSON)
+            # This catches cases where tasks are added/removed but counts stay the same
+            local task_ids=""
+            task_ids=$(echo "$kanban_output" | grep -o '"id": *"[^"]*"' | sed 's/"id": *"\([^"]*\)"/\1/' | sort | tr '\n' ',')
+
+            # Combine summary stats and task IDs for comprehensive state tracking
+            if [[ -n "$summary_snapshot" ]]; then
+                snapshot="${summary_snapshot}|ids:${task_ids}"
+            elif [[ -n "$task_ids" ]]; then
+                # Fallback to just task IDs if summary parsing failed
+                snapshot="ids:${task_ids}"
+            fi
         else
-            # Fallback: use the raw output as state (less precise but still detects changes)
+            # Fallback without jq: use grep to extract id and status fields
             snapshot=$(echo "$kanban_output" | grep -E '"id"|"status"' | tr -d ' \n')
         fi
     fi
@@ -560,6 +582,11 @@ main() {
                 log_warning "No kanban changes detected. Stale iteration count: $STALE_COUNTER/$STALE_THRESHOLD"
 
                 if [ "$STALE_COUNTER" -ge "$STALE_THRESHOLD" ]; then
+                    # Execute ON_STALE hook before exiting
+                    log_status ""
+                    log_status "Executing ON_STALE hook due to stale iteration detection"
+                    execute_hook_commands "ON_STALE"
+
                     log_error ""
                     log_error "=========================================="
                     log_error "STALE ITERATION LIMIT REACHED"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "juno-code",
-  "version": "1.0.42",
+  "version": "1.0.43",
   "description": "Ralph Wiggum meet Kanban! Ralph style execution for [Claude Code, Codex, Gemini, Cursor]. One task per iteration, automatic progress tracking, and git commits. Set it and let it run.",
   "keywords": [
     "Ralph",