v1.91.267.0 docs(captain): observable questions are not the person's to answer (GSTA-124 follow-up) (#3503)

* docs(captain): observable questions are not the person's to answer

Captain-side reading of the rule shipped in plan-tune/SKILL.md.tmpl and
docs/proactive.md (#3493, pstack item 4): a question a command, render or
measurement can settle is settled by the thread; a Captain that receives one
sends it back with the check that answers it. gstack holds the how; the Drive
copy of captain.md syncs from main.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* chore: changelog entry for the captain.md observable-questions bullet

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pre-landing review fixes

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* chore: changelog says the Drive copy needs a recopy, not a sync

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [1.91.267.0] - 2026-10-27
+
+**The Captain guide says which questions never need to reach a person.** Follow-up to #3493 (pstack absorb item 4, GSTA-124).
+
+### Changed
+- **`capy/skill/gstack/captain.md` section 1**: a new bullet after "Always a fresh ask": a question a command, render or measurement can settle is settled by the thread, which runs the thing and reports the result; only a product or preference call goes up, with the observation already made; a Captain that receives an observable question sends it back with the check that answers it. The Drive copy of `captain.md` needs the owner's recopy (or a Capy re-sync) to pick this up.
+
 ## [1.91.266.0] - 2026-10-27
 
 ### Added

VERSION

@@ -1 +1 @@
-1.91.266.0
+1.91.267.0

agents-digest/gstack-AGENTS.md

@@ -1,4 +1,4 @@
-# gstack digest v1.91.266.0 — regenerate/re-copy after upgrading gstack
+# gstack digest v1.91.267.0 — regenerate/re-copy after upgrading gstack
 
 Behavioral rules from gstack (https://github.com/garrytan/gstack), compressed
 for agent hosts without a full skill install. The full skills add workflows,

capy/skill/gstack/captain.md

@@ -26,6 +26,12 @@ and the Captain's drive) is the `/captain` skill and `docs/captain.md` in the gs
   - a change to a threshold, budget, trial count or test kind;
   - closing someone's contribution without landing it;
   - anything destructive or irreversible.
+- **Observable questions are not the person's to answer.** A question a command, a render or a measurement
+  can settle locally, read-only and for free ("is the new path faster", "does the test endpoint take this
+  payload", "does the test still fail") is settled by the thread: it runs the thing and reports the result.
+  A call that changes state, reaches a live system or spends money is still an ask. Only a product or preference call
+  goes up, with the observation already made. A Captain that receives an observable question sends it
+  back with the check that answers it instead of relaying it.
 - **What a gstack workflow does in Capy.** Launched with `GSTACK_SESSION_KIND=unattended`, a workflow takes
   each recommended option, writes everything else as a pending gate item, and stops. Your job is to carry
   those pending items to the Captain or person in the shape below, then feed the answer back.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "gstack",
-  "version": "1.91.266",
+  "version": "1.91.267",
   "description": "Garry's Stack — Claude Code skills + fast headless browser. One repo, one install, entire AI engineering workflow.",
   "license": "MIT",
   "type": "module",