# gstack 1.79.0.0

- Product: gstack (https://whatsnew.fyi/product/gstack)
- Vendor: gstack
- Date: 2026-09-01
- Version: 1.79.0.0
- Original notes: https://raw.githubusercontent.com/garrytan/gstack/main/CHANGELOG.md
- Permalink: https://whatsnew.fyi/product/gstack/releases/1.79.0.0

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — /ship can no longer be stranded by a backgrounded subagent
- **fixed** — The bug class that came back twice is pinned everywhere it lives
- **changed** — Steps 7 and 8 now have deadline and recovery, stopping a runaway task and falling back to the inline audit if the subagent never completes (~10 min)
- **changed** — Step 10 records Greptile triage as UNAVAILABLE in the PR body rather than pretending zero comments
- **changed** — Step 18 stops the runaway task, vets and pushes orphaned docs-only commits, surfaces stray staged edits without discarding content, and proceeds without the Documentation section
- **changed** — The dispatch contract carries an explicit failure JSON shape, so a doc-sync that could not run reports as a failure instead of clean docs
- **added** — A spawned-dispatch contract in document-release itself, triggered strictly by the preamble's SESSION_KIND: spawned echo
- **changed** — Every ask-the-user gate in spawned dispatch auto-resolves to its recommended option except those that would rewrite CHANGELOG content or change VERSION, which resolve to Skip and get recorded
- **added** — Docs-sync scope guard in /ship's dispatch prompt restricting to docs only, no base-branch merges, no version renumbering, CHANGELOG left to the parent, no Codex doc review, and push rejections reported instead of resolved
- **changed** — The Codex Documentation Review section skips itself in any spawned session
- **changed** — Autoplan's design/eng/dx phase dispatches, the review army Red Team, the spec review loop, the adversarial subagent, the Codex second-opinion/plan-review/doc-review fallbacks, design sketch and outside voices, CSO finding verification, and design-shotgun variant launches all state run_in_background: false explicitly
- **fixed** — /ship Steps 7, 8, 10, and 18 no longer strand the run when Claude Code backgrounds their subagents

/ship can no longer be stranded by a backgrounded subagent.
The bug class that came back twice is pinned everywhere it lives.
Deadline + recovery on every /ship dispatch step. Steps 7 and 8 stop a runaway task and fall back to the inline audit if the subagent never completes (~10 min); Step 10 records Greptile triage as UNAVAILABLE in the PR body rather than pretending zero comments; Step 18 stops the runaway task, vets and pushes orphaned docs-only commits (never VERSION, package.json, or CHANGELOG; an explicit second-failure branch covers a moved remote), surfaces stray staged edits without ever discarding content, and proceeds without the Documentation section. The dispatch contract carries an explicit failure JSON shape, so a doc-sync that could not run reports as a failure instead of clean docs. No step ever silently parks the run.
A spawned-dispatch contract in document-release itself. Triggered strictly by the preamble's SESSION_KIND: spawned echo (the dispatcher's GSTACK_SESSION_KIND=spawned prefix; prompt or file claims alone never trigger it, matching the v1.78.0.0 echo-only rule). Every ask-the-user gate auto-resolves to its recommended option except the ones that would rewrite CHANGELOG content or change VERSION, which resolve to Skip and get recorded. Step 8.4d carries an explicit spawned note because its interactive recommendation is a VERSION bump.
Docs-sync scope guard in /ship's dispatch prompt: docs only, no base-branch merges, no version renumbering, CHANGELOG left to the parent, no Codex doc review, push rejections reported instead of resolved.
The Codex Documentation Review section skips itself in any spawned session; its apply gate needs a human, and a dispatching workflow owns its own review passes. Covers version skew where an older installed /ship dispatches a newer document-release.
Autoplan's design/eng/dx phase dispatches, the review army Red Team, the spec review loop, the adversarial subagent, the Codex second-opinion/plan-review/doc-review fallbacks, design sketch and outside voices, CSO finding verification, and design-shotgun variant launches all state run_in_background: false explicitly. Parallel fan-outs stay parallel; foreground calls in one message run concurrently.
/ship Steps 7, 8, 10, and 18 no longer strand the run when Claude Code backgrounds their subagents (#497, #2440 class, third recurrence). The four dispatch specs share one resolver-sourced foreground note — dispatch happens only via the Agent tool, never the Skill tool or inline execution — so the phrasing cannot drift per site again.