A fresh install now lands on a concrete first move, not a dead end.
- First-run project scaffold that classifies the repo into one of a fixed set of buckets using local git and file markers
- Returning-session loop tip once past the first run
- Setup first-move nudge
- office-hours handoff to launch the next review via the Skill tool
- The top-level gstack skill is now a pure router
- Browse-content test assertions repointed from the root skill to browse/SKILL.md
- Parity carve-guard size caps bumped approximately 1–2KB per skill to account for the shared first-run-guidance preamble section
gstack reads your repo, hands you the right first skill, and the bare gstack front door routes instead of dumping browse docs.
gstack's first-run experience used to leak: a new user could install, type gstack, and land in a wall of browser-QA documentation regardless of what they wanted. This release makes the front door route, and adds a project-aware first-run scaffold.
On the first skill run, gstack detects your repo state and shows one short, specific suggestion.
On a returning session it nudges the full plan → review → ship loop once.
office-hours now offers to launch the next review for you instead of listing options you have to retype.
The top-level gstack skill is now a pure router: the duplicated browse docs it used to carry live only in /browse.
Added: First-run project scaffold that classifies the repo into one of a fixed set of buckets using local git + file markers only.
Added: Returning-session loop tip once past the first run.
Added: Setup first-move nudge.
Added: office-hours handoff to launch the next review via the Skill tool.
Changed: The top-level gstack skill is now a pure router.
Activation telemetry event types are accepted by the telemetry ingest path.
Browse-content test assertions repointed from the root skill to browse/SKILL.md.
Parity / carve-guard size caps bumped ~1–2KB per skill to account for the shared first-run-guidance preamble section.