From dcde44345fae07339244cd4915e7ec80fe49a566 Mon Sep 17 00:00:00 2001 From: garrytan Date: Wed, 28 Oct 2026 22:38:12 +0000 Subject: [PATCH] docs(capy-install): an ok install keeps the other current verdicts (#3561) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/capy-install.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/capy-install.md b/docs/capy-install.md index 1bed678f9..f98f87d6e 100644 --- a/docs/capy-install.md +++ b/docs/capy-install.md @@ -274,7 +274,16 @@ keeps the lease. `bin/gstack-lease list` shows `alive|dead|stale`, and honoured, the resolved Bun (`bun_path`, `bun_version`, `bun_rule`, and `bun_install` when this run downloaded it), the resolved Node when the project pins one (`node_path`, `node_version`, `node_rule`), the trailer, the remote - minimum, the launch PATH and the time. Admission refuses a workflow whose + minimum, the launch PATH and the time. An ok run (install or `--check`) at + the same checkout, project, HEAD and Bun as an earlier ok verdict keeps what + that verdict certified, so one machine stays admitted for /ship and its + `--for document-release` docs step (#3561): `required` becomes the union, + pins count as planning-only only when both runs skipped them, and the + verdict's `for` lists every workflow, comma-separated (`for=ship,document-release`; + the installer prints `the install verdict at keeps for= and adds + (for=)`, and the trailer still names this run's workflow). A + failing run, a new HEAD or another Bun replaces the verdict, and so does any + workflow install over a review-voice verdict. Admission refuses a workflow whose running Bun is not the one the verdict recorded ([BUN_RESOLUTION_DRIFT](troubleshooting.md#bun-resolution-drift)), and so do the pregate's lanes and guards, which also refuse an invalid verdict