/ship's pre-push test selection now finds the tests of a monorepo app that imports through its own `@/` alias (for example `apps/mobile` mapping `@/*` to `./src/*`). Why: only the root tsconfig was read, so every touched file in such an app failed with `PREGATE_NO_LANE` even with a test beside it. Rebuilt from #4462 by @dtoelke, who found and fixed it; thank you. Nothing to do: a repo whose only tsconfig is at the root (gstack itself) resolves exactly as before. Co-authored-by: stackpt-agent <348614618+stackpt-agent@users.noreply.github.com> Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/specialist-batched#1 reader=testing Review-Finding: p2v/outside-voice#1 reader=outside-voice
CHANGELOG fragments
A PR adds its CHANGELOG entry here as changelog.d/<branch-slug>.md: the entry text only, with no ## [x] heading, and bump: minor or bump: major front matter only when the change warrants more than a patch, and important: security|regression|data-loss|blocker only when it must reach stable within about a day (docs/releases.md#the-daily-check). It never edits VERSION, package.json's version or a released CHANGELOG section. The merge step (gstack-ship-queue land, or train land in a stamped train) assigns the version (under merge: direct, the release PR from gstack-release-stamp open does), folds every fragment into one CHANGELOG section and deletes the files. The entry's first sentence (or bold lead) becomes its line in the GitHub release notes, so write it for someone using gstack: docs/releases.md#release-notes. This README is skipped. See docs/ship-policy.md#changelog-fragments.