2b9fa009d3
* fix(#373): replace unquoted $GSD_SDK with space-safe gsd_run launcher Workflow bash blocks resolved the runtime as GSD_SDK="node $GSD_TOOLS" and invoked it unquoted ($GSD_SDK query ...). On install paths containing spaces (e.g. /Volumes/Mini Me/...) the unquoted expansion word-split into `node /Volumes/Mini gsd-tools.cjs ...`, failing with "Cannot find module '/Volumes/Mini'" and getting masked by `2>/dev/null || echo "{}"` into a silent empty state. Replace the string variable with a single-line shell launcher that defines a gsd_run function, invokes the runtime with a fully-quoted path and "$@", and preserves the local-cjs / installed-gsd-tools-on-PATH fallback (#3668) plus the loud not-found error and install hint. The launcher uses _GSD_SHIM_NAME indirection so no workflow emits the /gsd-tools substring that the do.md dispatcher-parity scanner would misread, and is single-line to stay within the per-file progressive-disclosure line budgets (#2551). The canonical launcher lives in get-shit-done/workflows/_runtime-launcher.snippet.sh, is propagated once per file by scripts/sync-runtime-launcher.cjs, and is locked by tests/runtime-launcher-parity.test.cjs (fails CI on drift, on a reappearing $GSD_SDK token, or on a /gsd-tools substring). Dependent workflow-assertion tests are updated from $GSD_SDK to gsd_run, and the runtime launcher is registered in CONTEXT.md. Fixes #373 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * ci(#373): add changeset fragment and allow-test-rule for parity guard The runtime-launcher parity test is a structural drift guard that reads workflow markdown to assert the canonical launcher is present and the retired $GSD_SDK / /gsd-tools tokens are absent; annotate it with allow-test-rule per the no-source-grep lint escape hatch. Add the required .changeset fragment for this user-facing fix. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(#373): make parity PATH-fallback assertion cross-platform (Windows) Subtest (E) compared GSD_TOOLS against the Node-side absolute temp path, but the value originates from git-bash which reports the POSIX form, so the prefix comparison failed on windows-latest while the launcher itself worked (the installed stub was invoked). Assert the resolved binary by normalized suffix (/bin/gsd-tools, not .cjs) instead of the absolute prefix; the behavioral stub-invocation assertion is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3.1 KiB
3.1 KiB
--auto mode — fully autonomous discuss-phase
Lazy-loaded. Read this file from
workflows/discuss-phase.mdwhen--autois present in$ARGUMENTS. After the discussion completes, the parent'sauto_advancestep also readsmodes/chain.mdto drive the auto-advance to plan-phase.
Effect across steps
check_existing: if CONTEXT.md exists, auto-select "Update it" — load existing context and continue toanalyze_phase(matches the parent step's documented--autobranch). If no context exists, continue without prompting. For interrupted checkpoints, auto-select "Resume". For existing plans, auto-select "Continue and replan after". Log every decision so the user can audit.cross_reference_todos: fold all todos with relevance score >= 0.4 automatically. Log the selection.present_gray_areas: auto-select ALL gray areas. Log:[--auto] Selected all gray areas: [list area names].discuss_areas: for each discussion question, choose the recommended option (first option, or the one explicitly marked "recommended") without using AskUserQuestion. Skip interactive prompts entirely. Log each auto-selected choice inline so the user can review decisions in the context file:[auto] [Area] — Q: "[question text]" → Selected: "[chosen option]" (recommended default)- After all areas are auto-resolved, skip the "Explore more gray areas"
prompt and proceed directly to
write_context. - After
write_context, auto-advance to plan-phase viamodes/chain.md.
CRITICAL — Auto-mode pass cap
In --auto mode, the discuss step MUST complete in a single pass. After
writing CONTEXT.md once, you are DONE — proceed immediately to
write_context and then auto_advance. Do NOT re-read your own CONTEXT.md to
find "gaps", "undefined types", or "missing decisions" and run additional
passes. This creates a self-feeding loop where each pass generates references
that the next pass treats as gaps, consuming unbounded time and resources.
Check the pass cap from config:
_GSD_SHIM_NAME="gsd-tools.cjs"; GSD_TOOLS="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/get-shit-done/bin/${_GSD_SHIM_NAME}"; if [ -f "$GSD_TOOLS" ]; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif command -v gsd-tools >/dev/null 2>&1; then GSD_TOOLS="$(command -v gsd-tools)"; gsd_run() { "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and gsd-tools is not on PATH. Run: npx -y @opengsd/get-shit-done-redux@latest --claude --local" >&2; exit 1; fi
MAX_PASSES=$(gsd_run query config-get workflow.max_discuss_passes 2>/dev/null || echo "3")
If you have already written and committed CONTEXT.md, the discuss step is complete. Move on.
Combination rules
--auto --text/--auto --batch: text/batch overlays are no-ops in auto mode (no user prompts to render).--auto --analyze: trade-off tables can still be logged for the audit trail; selection still uses the recommended option.--auto --power:--powerwins (power mode generates files for offline answering — incompatible with autonomous selection).