v1.42.1 Features
132. Package Legitimacy Gate
Purpose: Stop hallucinated, suspicious, or slopsquatting package names before they reach a shell install command.
Behavior:
- Phase research writes a
## Package Legitimacy Audittable for recommended packages. - Packages verified only through search are treated as
[ASSUMED], not trusted. [SLOP]packages are removed from recommendations.- Plans that need
[ASSUMED]or suspicious packages add a human verification checkpoint. - Executor install failures stop for human verification instead of auto-trying similarly named packages.
Requirements:
- REQ-PKG-GATE-01: Research MUST record package registry, age, download/source signals, slopcheck verdict, and disposition.
- REQ-PKG-GATE-02: Planner MUST gate unverified or suspicious package installs before execution.
- REQ-PKG-GATE-03: Executor MUST NOT auto-substitute package names after failed package-manager installs.
Reference: v1.42.1 Release Notes
133. Skill Surface Budgeting
Purpose: Let users reduce installed skill and agent surface area when context budget matters.
Install profiles:
| Profile | Purpose |
|---|---|
core | Minimal main-loop surface |
standard | Core plus common phase-management commands |
full | Complete surface; default |
Runtime control: /gsd:surface lists profile state and enables, disables, or resets skill clusters without reinstalling.
Requirements:
- REQ-SURFACE-01: Installer MUST resolve
--profile=<name>and persist the active profile in.gsd-profile. - REQ-SURFACE-02:
--minimaland--core-onlyMUST remain aliases for--profile=core. - REQ-SURFACE-03: Runtime surface state MUST persist outside the install profile marker.
Reference: ADR-0011
134. Installer Migrations
Purpose: Make runtime config cleanup explicit, auditable, and rollback-aware during installs and updates.
Capabilities:
- First-time baseline migration records managed files.
- Legacy stale-file cleanup uses ownership evidence before deleting or rewriting.
- User-owned artifacts are preserved.
- Ambiguous GSD-looking files block with a clear report instead of being silently overwritten.
- Migration plans support dry-run reporting and rollback protection.
Requirements:
- REQ-INSTALL-MIGRATION-01: Migration records MUST include metadata, install scope, and ownership evidence.
- REQ-INSTALL-MIGRATION-02: Destructive actions MUST fail closed when ownership is ambiguous.
- REQ-INSTALL-MIGRATION-03: Install failures MUST restore the pre-install state when rollback data exists.
Reference: Installer Migrations
135. Custom Ship PR Body Sections
Command: /gsd-ship
Config key: ship.pr_body_sections
Purpose: Add project-specific PRD-style sections to generated PR bodies without editing GSD workflow files.
Behavior: Configured sections append after the required Summary, Changes, Requirements Addressed, Verification, and Key Decisions sections. They can copy from artifact headings, render templates, or fall back to static text.
Requirements:
- REQ-SHIP-SECTIONS-01: Custom sections MUST NOT replace, remove, or reorder required PR sections.
- REQ-SHIP-SECTIONS-02: Unknown template tokens MUST be rejected by config validation.
- REQ-SHIP-SECTIONS-03: Disabled sections MUST stay in config without appearing in PR output.
Reference: Custom PR Body Sections
136. Review Default Reviewers
Command: /gsd-review
Config key: review.default_reviewers
Purpose: Let teams choose the default reviewer subset for no-flag /gsd-review runs.
Precedence:
explicit reviewer flags -> --all -> review.default_reviewers -> all detected reviewersRequirements:
- REQ-REVIEW-DEFAULTS-01: Missing
review.default_reviewersMUST preserve the previous all-detected behavior. - REQ-REVIEW-DEFAULTS-02: Empty arrays MUST be rejected; remove the key to restore all-detected behavior.
- REQ-REVIEW-DEFAULTS-03: Known but unavailable reviewers MUST be skipped with diagnostics rather than hard-failing the run.
Reference: Configuration Reference
137. Fallow Structural Review Pre-Pass
Command: /gsd-code-review
Config keys: code_quality.fallow.*
Purpose: Add an optional structural analysis pass before the agent review.
Behavior: When enabled, GSD resolves a fallow binary, runs a bounded audit, writes FALLOW.json, and embeds structural findings in REVIEW.md.
Requirements:
- REQ-FALLOW-01: Fallow MUST be opt-in and disabled by default.
- REQ-FALLOW-02: Missing or failing fallow runs MUST produce clear diagnostics.
- REQ-FALLOW-03: Findings larger than the embed budget MUST be skipped with a warning, preserving the raw JSON artifact.
Reference: Configuration Reference
138. End-of-Phase Human Verification Mode
Config key: workflow.human_verify_mode
Purpose: Reduce mid-flight human checkpoint interruptions while preserving human verification requirements.