From aa183ad9b9f6f6271d8b5afd53514e0323c06ceb Mon Sep 17 00:00:00 2001
From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com>
Date: Wed, 19 Aug 2026 00:10:48 +0200
Subject: [PATCH 1/2] docs(guide): name the project flag as load-bearing for
 build checks

The deploy-check recipe warned about --region but treated --project as
incidental. It is not: a gcloud default pointing at another project
returns that project's builds, and when its triggers share the names and
region, the wrong list is indistinguishable from the right one. Adds the
context check that settles it.
---
 agentic/docs/project-guide.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/agentic/docs/project-guide.md b/agentic/docs/project-guide.md
index 114a0cb699..4d740a668f 100644
--- a/agentic/docs/project-guide.md
+++ b/agentic/docs/project-guide.md
@@ -898,7 +898,7 @@ Roughly five minutes from merge to live, per build.
 #### Checking whether something actually deployed
 
 The triggers are **regional, in `europe-west4`**, and regional builds do not
-appear in the global build list. Always pass `--region`:
+appear in the global build list. Always pass both `--region` and `--project`:
 
 ```bash
 gcloud builds list --region=europe-west4 --project=anyplot --limit=10 \
@@ -911,6 +911,17 @@ since — which reads as "nothing has deployed for months" and is simply the
 wrong list. That mistake has been made and had to be corrected by the repo
 owner.
 
+Omitting `--project` fails more quietly. A gcloud install whose default project
+is another one of the owner's projects returns *that* project's builds, and
+because those triggers carry the same names in the same region, the output looks
+entirely credible — a plausible list of `deploy-api` and `deploy-app` runs that
+simply stop a few days ago. There is no error to notice. Confirm the context
+before drawing a conclusion from it:
+
+```bash
+gcloud config get-value project    # must print: anyplot
+```
+
 `.github/workflows/notify-deployment.yml` only **records** a GitHub deployment;
 it does not deploy anything. A green run there says nothing about whether the
 code is live.

From dc4bd8f042d1cc0356e43fe9062e607b9932ed0c Mon Sep 17 00:00:00 2001
From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com>
Date: Wed, 19 Aug 2026 00:16:24 +0200
Subject: [PATCH 2/2] docs(changelog): note the deploy-check project flag fix

---
 CHANGELOG.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index c02a7469fe..6425e6ec64 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,6 +16,18 @@ aggregate instead: an italic *Catalog* line at the end of the version section an
 
 ## [Unreleased]
 
+### Fixed
+
+- **Deploy checks could report another project's builds** — the runbook's recipe for
+  "did this actually deploy?" flagged `--region` as the easy thing to forget and treated
+  `--project` as incidental. It is not. A gcloud install whose default project is a
+  different one returns *that* project's builds, and when its triggers happen to carry
+  the same names in the same region, the wrong answer is indistinguishable from the
+  right one — no error, just a credible list of `deploy-api` runs that stop a few days
+  ago. It produced a false "nothing has deployed since the 16th" on a day with a dozen
+  deploys. `agentic/docs/project-guide.md` now names both flags and the context check
+  that settles it.
+
 ## [3.1.0] — 2026-08-19 — Legible to machines
 
 anyplot 3.1 makes the catalogue readable by machines. An assistant asked about a plot can now find