From 3148984e6678e2096133c5761e07d496ebbab836 Mon Sep 17 00:00:00 2001 From: garrytan Date: Sun, 1 Nov 2026 04:43:52 +0000 Subject: [PATCH] docs: capy-install names how --project resolves (GST-743) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/capy-install.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/capy-install.md b/docs/capy-install.md index 22a3481b0..1c1a1f0b3 100644 --- a/docs/capy-install.md +++ b/docs/capy-install.md @@ -241,7 +241,12 @@ keeps the lease. `bin/gstack-lease list` shows `alive|dead|stale`, and clone too, through `GSTACK_CAPY_CLONED`). 2. Preflight: `git`, `curl`, `node`, `jq`, then Bun. The project's pins (`--project `, default the git toplevel of the current directory) are - read with the doctor's own parser (`bin/gstack-runtime-pins.ts`: engines, + read (a `--project` inside a repository resolves to that repository's git + toplevel, so `--project /` means ``; outside a repository + it resolves to the directory's real path, and a value that is not a + directory, such as a repo slug, exits 2 with a usage error before anything + runs; the pins, the doctor and the install verdict all use the resolved + directory) with the doctor's own parser (`bin/gstack-runtime-pins.ts`: engines, packageManager, `.tool-versions`, `.bun-version` and CI `bun-version:` lanes for this platform). CI exact pins for this platform are alternatives: a repository may test several Bun versions (gstack's own CI pins 1.4.2 and