fa107c0461
* fix(#4172): add --merge-async to test:coverage:scripts-floor The "Coverage gate (merged shards)" test.yml job has OOM-crashed (exit 134, SIGABRT) on every push to next since4dfc46b. test:coverage:scripts-floor was the only c8 coverage-merge invocation in package.json still missing --merge-async: c8's default sync merge path (Report._getMergedProcessCov) loads every raw V8 coverage file from the merged 3-shard coverage/tmp directory into memory as one array before merging, instead of folding them in one at a time, and now blows through the job's 8192 MB heap ceiling. This is the same bug class as #4068 (fixed in4d70b4dc4), which added --merge-async to test:coverage:unit and test:coverage:report -- the two other scripts sharing this merge/report code path -- but missed this third sibling, which reads the exact same merged coverage/tmp data in the same job. check-coverage and report both dispatch through c8's shared getCoverageMapFromAllCoverageFiles()/mergeAsync branch, so the fix is identical in shape to #4068's. Extends the existing #4068 regression guard (tests/c8-merge-async-flag.test.cjs) to also assert test:coverage:scripts-floor carries --merge-async, closing the coverage gap #4068 left on this sibling script. Fixes #4172 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * docs(#4172): backfill changeset PR number (pr:0 -> 4173) * fix(#4172): route scripts-floor through `c8 report`, not `check-coverage` The prior commit (1a3d6b75e) added --merge-async to test:coverage:scripts-floor, but the Coverage gate job still OOM-crashed identically on PR #4173's CI run (https://github.com/open-gsd/gsd-core/actions/runs/33587951779/job/100118358975). Root cause of that miss: c8@11.0.0's `check-coverage` CLI subcommand handler (node_modules/c8/lib/commands/check-coverage.js) never forwards argv.mergeAsync into the Report constructor -- only the `report` subcommand's handler (node_modules/c8/lib/commands/report.js) and the default command (which also calls into report.js) do. Verified directly by constructing Report the same way each handler does: the check-coverage path yields report.mergeAsync === undefined even with --merge-async on the command line, while the report path yields true. Fix: route test:coverage:scripts-floor through `c8 report --check-coverage` instead of `c8 check-coverage`. report.js's outputReport() calls the same checkCoverages() threshold-checking helper when --check-coverage is truthy, so behavior (and exit code on threshold failure) is unchanged -- only the code path taken to get there now actually honors --merge-async. Extends the tests/c8-merge-async-flag.test.cjs regression guard with an explicit assertion that scripts-floor invokes `c8 report`, not `check-coverage`, so this can't silently regress back to the broken form. Fixes #4172 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * docs(#4172): correct changeset to describe the actual root cause (check-coverage vs report subcommand gap, not just the missing flag) --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
GSD Core
Git. Ship. Done.
English · Português · 简体中文 · 日本語 · 한국어
A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.
What is GSD Core
GSD Core is a context-engineering and spec-driven development framework that drives AI coding agents (Claude Code, Codex, Antigravity CLI, Kimi CLI, Copilot, Cursor, and more) through a disciplined phase loop. It solves context rot — the quality degradation that accumulates as an AI fills its context window — by running all heavy research, planning, and execution work in fresh-context subagents while keeping your main session lean.
How it works
Each milestone repeats the same five-step loop, one phase at a time:
- Discuss — capture implementation decisions before anything is planned
- Plan — research, decompose, and verify the plan fits a fresh context window
- Execute — run plans in parallel waves; each executor starts with a clean 200k-token context
- Verify — walk through what was built; diagnose and fix before declaring done
- Ship — create the PR, archive the phase, repeat for the next one
Quickstart
npx @opengsd/gsd-core@latest
The installer prompts for your runtime (Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more) and whether to install globally or locally. The installer is required for cross-runtime compatibility — do not copy files from agents/ or commands/ directly.
On another runtime or without Node.js? See Install on your runtime.
Once installed, start a new project or onboard an existing repo:
/gsd-new-project # greenfield project
/gsd-onboard # existing codebase
New here? Follow Your first project for a guided walkthrough from install to first shipped phase, or Onboarding an existing codebase for brownfield setup.
Documentation
What's new in 1.7.0 → docs/whats-new-1.7.0.md
Tutorials — learning by doing:
How-to guides — task-focused recipes:
Reference — authoritative facts:
Explanation — concepts and design decisions:
Full index: docs/README.md. Other languages: 日本語 · 한국어 · Português · 简体中文.
Why it works
Most AI-coding setups fail at scale because context bloat silently degrades output quality, there is no shared memory between sessions, and nothing verifies that code actually works. GSD Core solves all three: heavy work runs in fresh subagents, structured artifacts like STATE.md and CONTEXT.md survive session boundaries, and the verify step walks through what was built and generates fix plans before a phase is declared done. See docs/explanation/context-engineering.md for the full reasoning.
Troubleshooting? See docs/how-to/recover-and-troubleshoot.md.
Community
| Project | Platform |
|---|---|
| gsd-opencode | Original OpenCode port |
| Discord | Community support |
Star History
License
MIT License. See LICENSE for details.
Claude Code is powerful. GSD Core makes it reliable.