build: the forge lane is the lane that runs

8a415e9 moved the REGISTRY_USER/REGISTRY_PASSWORD fetch out of the
`bucket:`/`site:` gate in .github/workflows/build.yml and left
.hanzo/workflows/build.yml untouched. Those two files are one artifact spelled
twice — github.com reads only `.github/workflows`, git.hanzo.ai reads only
`.hanzo/workflows` — and this repo's own `build-yml-is-one-file` gate exists to
refuse exactly this. It would have caught it: the gate passes at a830325 and
fails at 8a415e9.

The consequence is the inverse of the fix's intent. The copy that got the fix is
read by the forge nobody builds on; the copy the runners actually execute still
asks KMS for the registry credential only when a repo declares a bucket or a
site. So a repo declaring only `images:` — the common shape — still arrives at
`docker login registry.hanzo.ai` with two empty strings, and deleting the
REGISTRY_USER/REGISTRY_PASSWORD org secrets on the strength of 8a415e9 would
have broken every image build in three orgs rather than none.

They were byte-identical at a830325 (md5 1c027d00), and the only difference the
gate tolerates is a self-naming path that neither copy actually spells
differently, so the mirror is a literal copy.

No condition changes: under `mode: buildx` all 24 steps have effective
conditions identical to f098b39, which is what the v1 tag points at today.

.github/actions/sitedeploy/action.yml

@@ -0,0 +1,60 @@
+name: sitedeploy
+description: Publish a built static export to the Hanzo PaaS Sites plane.
+# For every repo whose deploy is "a static export goes live" — hanzo.ai, hanzo.app,
+# hips, computer and the ones after them. Those were each about to carry their own
+# copy of enqueue → upload → complete, which is how one contract becomes N
+# transcriptions that drift (see the imgver action next door for the same story
+# told about image tags).
+#
+#   - uses: hanzoai/ci/.github/actions/sitedeploy@v1
+#     with:  { slug: hanzo-ai, dir: out }
+#     env:   { HANZO_DEPLOY_TOKEN: '${{ secrets.HANZO_DEPLOY_TOKEN }}' }
+#
+# A SITE IS NOT AN APP. This publishes files and stops: no image, no CR, no
+# replicas, no registry. Building a container so a Go binary can serve /public is
+# the shape the Sites plane exists to retire.
+#
+# ONE credential. The 202 hands back a prefix-scoped, 30-minute presigned POST
+# grant, so CI never holds a bucket key — do NOT add SITES_S3_* here; that is the
+# standing shared-bucket credential the grant replaced.
+inputs:
+  slug:
+    description: The project slug on the Sites plane (POST /v1/projects/<slug>/deploy)
+    required: true
+  dir:
+    description: The built export directory
+    required: true
+  api:
+    description: Cloud API base
+    required: false
+    default: https://api.hanzo.ai
+  jobs:
+    description: Parallel uploads
+    required: false
+    default: '24'
+runs:
+  using: composite
+  steps:
+    - name: Fetch sitedeploy
+      shell: bash
+      # The action ref is the script ref: an action pinned to @v1 runs v1's
+      # sitedeploy. Both forges, because this repo is served from each.
+      run: |
+        set -euo pipefail
+        ref="${GITHUB_ACTION_REF:-v1}"
+        for url in https://git.hanzo.ai/hanzoai/ci https://github.com/hanzoai/ci; do
+          git clone -q --depth 1 --branch "$ref" "$url" "$RUNNER_TEMP/sitedeploy-ci" 2>/dev/null && break
+        done
+        [ -x "$RUNNER_TEMP/sitedeploy-ci/bin/sitedeploy" ] \
+          || { echo "::error::could not fetch hanzoai/ci@$ref (bin/sitedeploy)"; exit 1; }
+
+    - name: Deploy
+      shell: bash
+      env:
+        HANZO_API: ${{ inputs.api }}
+        SITEDEPLOY_JOBS: ${{ inputs.jobs }}
+        SITEDEPLOY_COMMIT: ${{ github.sha }}
+        SITEDEPLOY_BRANCH: ${{ github.ref_name }}
+      run: |
+        set -euo pipefail
+        bash "$RUNNER_TEMP/sitedeploy-ci/bin/sitedeploy" '${{ inputs.slug }}' '${{ inputs.dir }}'

Dockerfile

@@ -6,12 +6,20 @@
 # it. So the image is still the binary and a CA bundle — nothing served from
 # disk, nothing to go stale against the code, and no JS toolchain on the path
 # that ships the board you read when the builds are broken.
-FROM golang:1.24-alpine AS builder
+FROM golang:1.26.5-alpine AS builder
 WORKDIR /build
 # Resolve through the module proxy: proxy.golang.org and sum.golang.org agree
 # and neither can change under us, which a direct fetch against a moved tag
 # cannot promise.
 ENV GOPROXY=https://proxy.golang.org,direct
+# The base image above is pinned to exactly the Go go.mod asks for, so nothing
+# is downloaded here — the pin is what makes this build hermetic. GOTOOLCHAIN
+# is set to auto anyway, because the golang images default it to `local` and
+# that turns the NEXT go.mod bump from "fetches the toolchain it needs" into
+# "dies mid-build with go.mod requires go >= X". The pin is the fast path; this
+# is the one that keeps a version bump from being a build break. bin/gover
+# gates the same rule for every repo this pipeline builds.
+ENV GOTOOLCHAIN=auto
 COPY go.mod ./
 RUN --mount=type=cache,id=ci-gomod,target=/go/pkg/mod go mod download
 COPY . .

LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Hanzo AI, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -171,10 +171,13 @@ Builds are `CGO_ENABLED=0 -trimpath`: the host that installs this runs it on
 whatever base image the host is, and the digest must be a function of the
 source, not of the checkout path.
 
-## Runners — our cloud or your own
+## Runners — our fleet or your own
 
-By default the build runs on the **Hanzo cloud** arc pool (we run it; metered as
-build minutes). To run on **your own** self-hosted arc runners, pass their labels:
+By default the build runs on the **Hanzo `git-runner` fleet** on git.hanzo.ai
+(we run it; metered as build minutes) — the only pool that serves the default
+`hanzo-build-linux-amd64` label. There is no arc pool: arc (arcd) was retired
+2026-08-01 and never served any label in this default. To run on **your own**
+self-hosted runners, pass their labels:
 
 ```yaml
     uses: hanzoai/ci/.github/workflows/build.yml@v1
@@ -185,7 +188,7 @@ build minutes). To run on **your own** self-hosted arc runners, pass their label
 
 ## Delegate to platform (skip runner buildx)
 
-By default the build runs buildx **on** the arc runner. To instead hand the build
+By default the build runs buildx **on** the runner. To instead hand the build
 to **platform.hanzo.ai** — which builds in-cluster with BuildKit and rolls the
 service itself — pass `mode: delegate`:
 
@@ -197,7 +200,7 @@ service itself — pass `mode: delegate`:
 ```
 
 The GitHub job then just POSTs each image in `hanzo.yml` to platform's direct
-build webhook (`/v1/arcd/enqueue`) and exits in **seconds** — no runner buildx,
+build webhook (`/v1/runner`) and exits in **seconds** — no runner buildx,
 no KMS, no runner-side deploy. Platform creates the build job, launches an
 in-cluster BuildKit Job on its own pool, pushes to the registry, and patches the
 operator `Service` CR to roll it. It's the same build path as the platform
@@ -205,10 +208,10 @@ GitHub-App webhook — one build path, two front doors.
 
 Requires one extra secret, `PLATFORM_BUILD_CALLBACK_TOKEN` (org- or repo-level,
 picked up via `secrets: inherit`). Override the endpoint with the
-`PLATFORM_ENQUEUE_URL` repo/org variable (default `https://platform.hanzo.ai/v1/arcd/enqueue`).
+`PLATFORM_ENQUEUE_URL` repo/org variable (default `https://platform.hanzo.ai/v1/runner`).
 
 `mode: buildx` (the default) is unchanged — existing repos keep running buildx on
-arc, so delegation is strictly opt-in.
+the fleet runner, so delegation is strictly opt-in.
 
 ## Credentials
 
@@ -220,6 +223,6 @@ run time. No long-lived registry or cluster credentials live in GitHub.
 ## Platform-native
 
 `hanzo.yml` is also read by platform.hanzo.ai: a repo on the platform webhook
-needs **only** `hanzo.yml` — the platform builds it on arc and rolls it out, no
+needs **only** `hanzo.yml` — the platform builds it in-cluster and rolls it out, no
 workflow file at all. This reusable is the GitHub-Actions path for repos that
 trigger through GitHub instead of the platform.

bin/conflictmarkers

@@ -0,0 +1,112 @@
+#!/usr/bin/env bash
+# conflictmarkers — refuse a repo that has committed an unresolved merge.
+# One implementation, every caller.
+#
+#   conflictmarkers [dir]
+#
+# WHAT THIS CATCHES
+#
+# `git merge` writes its disagreement INTO the file and stops. Resolving means
+# editing those lines out; nothing forces you to. `git add` on a file that still
+# contains them is accepted without complaint, and from that moment the markers
+# are ordinary committed content — `git status` is clean, `git diff` is empty,
+# and the conflict is now a permanent feature of the branch.
+#
+# It survives because of WHERE it lands. The file is usually generated or
+# vendored — large, rarely opened, excluded from review by its own size. Nobody
+# reads line 23,807 of a .d.ts. hanzoai/base carried exactly this on main:
+#
+#   plugins/jsvm/internal/types/generated/types.d.ts:23807   <<<<<<< HEAD
+#   plugins/jsvm/internal/types/generated/types.d.ts:23850   >>>>>>> upstream/master
+#
+# from an upstream merge nobody finished, sitting in the shipped package.
+#
+# The compilers are no help, which is the whole problem. In TypeScript the
+# markers are a syntax error — but a .d.ts nothing imports is never parsed, so
+# there is no error to see. In Go they are a parse error only in a file the
+# build reaches. In YAML, JSON, Markdown, SQL, HTML and every config format we
+# ship, they are silently VALID content: a marker in a values file is a key
+# nobody notices, and a marker in a Markdown doc renders as text.
+#
+# So the defect class is "both sides of a merge shipped, and nothing in the
+# pipeline had an opinion". That is the same shape as its two siblings in this
+# step — a declaration and reality disagreeing, with no reader positioned to
+# notice — which is why it belongs here rather than in any one repo's gate.
+#
+# WHAT IT LOOKS FOR, AND WHY NOT MORE
+#
+# Only the two LABELLED markers git actually writes:
+#
+#   ^<<<<<<< <label>     the start marker, seven '<' then a space
+#   ^=======              the divider, seven bare equals
+#   ^>>>>>>> <label>     the end marker, seven '>' then a space
+#
+# ALL THREE, IN THAT ORDER, EACH ON ITS OWN LINE. Not any one of them — the
+# whole shape. That is not belt-and-braces, it is the difference between a gate
+# and a nuisance, and it was measured the expensive way: matching the start
+# marker ALONE failed hanzoai/app, whose builder tests carry
+#
+#   <<<<<<< START_TITLE index.html >>>>>>> END_TITLE
+#
+# as literal fixture data. That line opens with seven '<' and a space and is
+# not a merge conflict — both markers sit on ONE line, which is a thing git
+# never writes. A start marker that also carries an end marker is therefore
+# excluded outright, and a file must show the divider and a separate end line
+# before this refuses it.
+#
+# The divider is only ever matched as part of that conjunction, never alone:
+# seven bare equals signs at column 1 is also how reStructuredText and Setext
+# Markdown underline a heading, and failing every doc in the estate is how a
+# gate gets switched off.
+#
+# Exactly seven, anchored at column 1: `<<<<<<<<` (eight — a heredoc, a C++
+# stream) does not match, and neither does an indented mention inside a comment
+# explaining conflict markers, which is what lets this file describe them
+# without flagging itself.
+#
+# Tracked files only, via `git grep`, so a stray marker in an untracked scratch
+# file or in node_modules cannot fail a build. `-I` skips binaries.
+set -euo pipefail
+
+cd "${1:-.}"
+
+git rev-parse --is-inside-work-tree >/dev/null 2>&1 || {
+  echo "conflictmarkers: not a git work tree ($(pwd)) — skipping"; exit 0; }
+
+# Built from variables rather than written literally, so this script is not its
+# own first finding when it scans the repo that carries it.
+L=$(printf '<%.0s' $(seq 7))
+E=$(printf '=%.0s' $(seq 7))
+R=$(printf '>%.0s' $(seq 7))
+
+# Candidate files: those carrying a start marker that is NOT also an end marker
+# on the same line. `-l` for names only; the line numbers come later, per file.
+cands=$(git grep -I -l -E "^${L} " -- . || true)
+
+bad=""
+for f in $cands; do
+  grep -qE "^${L} " -- "$f" 2>/dev/null || continue
+  # The same-line form (app's fixture) is not a conflict. Require at least one
+  # start line that does not also carry an end marker.
+  grep -E "^${L} " -- "$f" 2>/dev/null | grep -qv -- "$R" || continue
+  # And require the rest of the shape: a bare divider and a separate end line.
+  grep -qE "^${E}$" -- "$f" 2>/dev/null || continue
+  grep -E "^${R} " -- "$f" 2>/dev/null | grep -qv -- "$L" || continue
+  bad="$bad $f"
+done
+
+if [ -n "$bad" ]; then
+  echo "::error::committed merge-conflict markers — an unresolved merge is in the tree"
+  for f in $bad; do
+    grep -nE "^(${L} |${E}$|${R} )" -- "$f" | while IFS= read -r line; do
+      echo "  $f:$line"
+    done
+    echo "::error file=${f}::committed conflict marker"
+  done
+  echo
+  echo "Resolve the merge and commit the result. If the file is GENERATED, do not"
+  echo "hand-edit it — re-run its generator and commit that."
+  exit 1
+fi
+
+echo "OK: no committed conflict markers ($(git ls-files | wc -l) tracked files)"

bin/gover

@@ -0,0 +1,147 @@
+#!/usr/bin/env bash
+# gover — refuse a Dockerfile whose Go builder image is older than the module
+# it compiles. One implementation, every caller.
+#
+#   gover <dockerfile> [context-dir]     # e.g. gover Dockerfile .
+#
+# WHAT THIS CATCHES, AND WHY IT IS A GATE AND NOT A CONVENTION
+#
+# The official `golang` images set GOTOOLCHAIN=local. That is deliberate on
+# their part — the image promises the Go it ships and refuses to silently
+# fetch another. The consequence is that a go.mod requiring a NEWER Go than
+# the base image does not degrade, it dies:
+#
+#   go: go.mod requires go >= 1.26.5 (running go 1.26.4; GOTOOLCHAIN=local)
+#
+# hanzoai/visor v1.108.16 is the shipped instance. The failure is invisible
+# until the image build runs, because every local `go build` succeeds: a
+# developer box runs GOTOOLCHAIN=auto and simply downloads what the module
+# asks for. So the mismatch is introduced by editing go.mod — a file that has
+# nothing to do with Docker — and is discovered by a red release build.
+#
+# It is also not one repo's problem. A sweep of every Dockerfile across the
+# orgs found 58 FROM lines in 23 repos already below their own go.mod, and
+# only 7 of 223 Go builder stages set GOTOOLCHAIN=auto. Fixing those 58 fixes
+# today; this gate is what makes the 59th impossible, which is the part worth
+# having.
+#
+# WHAT IT DELIBERATELY DOES NOT DO
+#
+# It does not require the newest Go, and it does not care that an image is
+# behind `latest`. A newer toolchain compiling an older `go` directive is
+# always valid, so pinning ahead of go.mod is fine and stays silent. The only
+# thing refused is an image BELOW the module's floor, because that is the only
+# arrangement that cannot build.
+#
+# A floating tag (`golang:1.26-alpine`, no patch) resolves to the newest patch
+# of that minor when the image is pulled. Against a patch-pinned go.mod that
+# is correct today and fragile tomorrow — a stale registry mirror serves an
+# older patch and the build dies with the message above. That earns a warning,
+# never a failure: it builds, and a gate that fails what builds trains people
+# to skip gates.
+#
+# EXIT: 0 clean (warnings still print), 1 when a stage cannot build.
+set -uo pipefail
+
+df=${1:?usage: gover <dockerfile> [context-dir]}
+ctx=${2:-.}
+[ -f "$df" ] || { echo "gover: no such Dockerfile: $df" >&2; exit 1; }
+
+# --- the module floor -------------------------------------------------------
+# Nearest go.mod walking up from the Dockerfile, then the build context, then
+# the repo root. Multi-module repos are the reason this walks rather than
+# assuming the root: hanzoai/s3 builds s3-rdma-sidecar/ and telemetry/server/
+# from their own go.mod files, each with a different floor.
+#
+# WHICH go.mod, precisely: the BUILD CONTEXT decides, not where the file sits.
+# A Dockerfile under test/kafka/ built with `context: ../..` compiles the ROOT
+# module, and judging it by test/kafka/go.mod reads the wrong floor — in
+# hanzoai/s3 that difference is 1.25.0 vs 1.26.5, i.e. the difference between
+# "fine" and "cannot build". So when a Dockerfile copies the context's own
+# go.mod (`COPY go.mod ...`, the overwhelmingly common shape), that is the
+# module being compiled and the context's go.mod wins.
+#
+# Otherwise fall back to the nearest go.mod above the Dockerfile, which is the
+# right answer for a subdirectory that is its own module and is built with its
+# own directory as the context — hanzoai/s3's s3-rdma-sidecar/ and
+# telemetry/server/ are both that shape.
+govers=""; gosrc=""
+if grep -qiE '^[[:space:]]*COPY([[:space:]]+--[^[:space:]]+)*[[:space:]]+([^[:space:]]+[[:space:]]+)*go\.mod([[:space:]]|$)' "$df" 2>/dev/null \
+   && [ -f "$ctx/go.mod" ]; then
+  gosrc="$ctx/go.mod"
+fi
+if [ -z "$gosrc" ]; then
+  d=$(dirname "$df")
+  while :; do
+    if [ -f "$d/go.mod" ]; then gosrc="$d/go.mod"; break; fi
+    [ "$d" = "." ] || [ "$d" = "/" ] || [ -z "$d" ] && break
+    d=$(dirname "$d")
+  done
+fi
+[ -z "$gosrc" ] && [ -f "$ctx/go.mod" ] && gosrc="$ctx/go.mod"
+[ -z "$gosrc" ] && [ -f "go.mod" ] && gosrc="go.mod"
+# No module in play — nothing to compare against, and a non-Go image is not
+# this gate's business.
+[ -z "$gosrc" ] && exit 0
+govers=$(grep -m1 -E '^go[[:space:]]+[0-9]' "$gosrc" 2>/dev/null | awk '{print $2}')
+[ -z "$govers" ] && exit 0
+
+# --- ARG defaults -----------------------------------------------------------
+# `FROM golang:${GO_VERSION}-bookworm` is only as good as its default, and the
+# default is the value CI builds with unless hanzo.yml passes `args:`. Read
+# them so the parameterised Dockerfiles are checked too, not skipped.
+declare -A args=()
+while IFS= read -r line; do
+  if [[ $line =~ ^[[:space:]]*[Aa][Rr][Gg][[:space:]]+([A-Za-z_][A-Za-z0-9_]*)=(.*)$ ]]; then
+    v="${BASH_REMATCH[2]}"
+    v="${v%%#*}"                       # strip trailing comment
+    v="${v//\"/}"; v="${v//\'/}"       # strip quotes
+    v="${v#"${v%%[![:space:]]*}"}"; v="${v%"${v##*[![:space:]]}"}"
+    args[${BASH_REMATCH[1]}]="$v"
+  fi
+done < "$df"
+
+# semver -> comparable integer; missing patch becomes -1 so a floating tag is
+# distinguishable from an explicit .0 rather than silently equal to it.
+num() { # num <major> <minor> <patch|-1>
+  printf '%d' $(( $1 * 1000000 + $2 * 1000 + ($3 < 0 ? 999 : $3) ))
+}
+parse() { # parse <version-ish> -> "major minor patch"; empty when unparseable
+  local v=$1
+  [[ $v =~ ^([0-9]+)\.([0-9]+)\.([0-9]+) ]] && { echo "${BASH_REMATCH[1]} ${BASH_REMATCH[2]} ${BASH_REMATCH[3]}"; return; }
+  [[ $v =~ ^([0-9]+)\.([0-9]+) ]] && { echo "${BASH_REMATCH[1]} ${BASH_REMATCH[2]} -1"; return; }
+  echo ""
+}
+
+read -r mM mm mp <<<"$(parse "$govers")"
+[ -z "${mM:-}" ] && exit 0   # go.mod says something we cannot read; not our call
+
+rc=0; n=0
+while IFS= read -r line; do
+  # FROM [--flag ...] [registry/]golang:<tag> [AS stage]
+  [[ $line =~ ^[[:space:]]*[Ff][Rr][Oo][Mm][[:space:]]+(--[^[:space:]]+[[:space:]]+)*([^[:space:]]*golang:[^[:space:]]+) ]] || continue
+  ref="${BASH_REMATCH[2]}"
+  tag="${ref##*golang:}"
+  # resolve ${VAR} / $VAR against the ARG defaults
+  while [[ $tag =~ \$\{?([A-Za-z_][A-Za-z0-9_]*)\}? ]]; do
+    name="${BASH_REMATCH[1]}"; sub="${args[$name]:-}"
+    [ -z "$sub" ] && { tag=""; break; }
+    tag="${tag//\$\{$name\}/$sub}"; tag="${tag//\$$name/$sub}"
+  done
+  [ -z "$tag" ] && continue
+  n=$((n+1))
+  read -r iM im ip <<<"$(parse "$tag")"
+  # `golang:alpine`, `golang:1-alpine`, `ARG GO_VERSION=INVALID` — no version to
+  # compare. Say so once; do not guess and do not fail.
+  [ -z "${iM:-}" ] && { echo "gover: $df: '$ref' names no Go version — cannot check it against $gosrc ($govers)"; continue; }
+  if [ "$(num "$iM" "$im" "$ip")" -lt "$(num "$mM" "$mm" "$mp")" ]; then
+    echo "::error file=$df::Go builder image is older than the module it builds: '$ref' provides Go $iM.$im${ip:+.$ip} but $gosrc requires go $govers. The golang images set GOTOOLCHAIN=local, so this build fails with 'go.mod requires go >= $govers'. Fix: pin the base to golang:$govers-<variant>, and add 'ENV GOTOOLCHAIN=auto' to the builder stage so a future go.mod bump downloads the toolchain instead of failing."
+    rc=1
+  elif [ "$ip" -lt 0 ] && [ "$mp" -ge 0 ]; then
+    echo "::warning file=$df::'$ref' floats to the newest patch of $iM.$im, while $gosrc pins go $govers. It builds today and fails the moment a registry mirror serves an older patch. Pin golang:$govers-<variant> to make it hermetic."
+  fi
+done < "$df"
+
+[ "$n" = 0 ] && exit 0
+[ "$rc" = 0 ] && echo "gover: OK — $df ($n Go stage$([ "$n" = 1 ] || echo s)) satisfies $gosrc (go $govers)"
+exit $rc

bin/gover_test.sh

@@ -0,0 +1,128 @@
+#!/usr/bin/env bash
+# Tests for bin/gover. Offline and deterministic: every case is a Dockerfile and
+# a go.mod written into a temp dir, so this needs no registry and no network.
+# Run: bash bin/gover_test.sh
+set -uo pipefail
+cd "$(dirname "$0")/.."
+GOVER="$PWD/bin/gover"
+tmp=$(mktemp -d); trap 'rm -rf "$tmp"' EXIT
+fail=0
+
+# t <name> <want-rc> <go.mod-directive> <dockerfile-body...>
+t() {
+  local name=$1 want=$2 gomod=$3; shift 3
+  local d="$tmp/$RANDOM$RANDOM"; mkdir -p "$d"
+  printf 'module x\n\ngo %s\n' "$gomod" > "$d/go.mod"
+  printf '%s\n' "$@" > "$d/Dockerfile"
+  out=$(cd "$d" && bash "$GOVER" Dockerfile . 2>&1); rc=$?
+  if [ "$rc" = "$want" ]; then printf 'ok    %-56s rc=%s\n' "$name" "$rc"
+  else printf 'FAIL  %-56s rc=%s (want %s)\n      %s\n' "$name" "$rc" "$want" "$out"; fail=1; fi
+}
+# grep-based assertion for the message body, not just the code
+tmsg() {
+  local name=$1 pat=$2 gomod=$3; shift 3
+  local d="$tmp/$RANDOM$RANDOM"; mkdir -p "$d"
+  printf 'module x\n\ngo %s\n' "$gomod" > "$d/go.mod"
+  printf '%s\n' "$@" > "$d/Dockerfile"
+  out=$(cd "$d" && bash "$GOVER" Dockerfile . 2>&1)
+  if printf '%s' "$out" | grep -q "$pat"; then printf 'ok    %-56s\n' "$name"
+  else printf 'FAIL  %-56s\n      got: %s\n' "$name" "$out"; fail=1; fi
+}
+
+# --- the refusal: image below the module floor ------------------------------
+# This is the visor v1.108.16 shape exactly.
+t "patch below floor is refused"          1 1.26.5 'FROM golang:1.26.4-alpine'
+t "minor below floor is refused"          1 1.26.5 'FROM golang:1.25-alpine'
+t "ancient relic is refused"              1 1.26.4 'FROM golang:1.10.1'
+t "second stage is checked too"           1 1.26.5 'FROM node:22 AS web' 'FROM golang:1.26.1-bookworm AS api'
+
+# --- the allowances ---------------------------------------------------------
+t "exact match builds"                    0 1.26.5 'FROM golang:1.26.5-alpine'
+t "newer image than floor is fine"        0 1.26.4 'FROM golang:1.26.5-alpine'
+t "much newer image is fine"              0 1.25.0 'FROM golang:1.26.5-bookworm'
+t "alpine suffix is not a Go patch"       0 1.26   'FROM golang:1.26-alpine3.24'
+t "registry prefix is stripped"           0 1.26.5 'FROM docker.io/library/golang:1.26.5-alpine'
+t "--platform flag is skipped"            0 1.26.5 'FROM --platform=$BUILDPLATFORM golang:1.26.5-alpine AS b'
+t "non-Go image is not our business"      0 1.26.5 'FROM alpine:3.21'
+
+# --- floating tags warn, never fail -----------------------------------------
+# They build. A gate that fails what builds trains people to skip gates.
+t "floating tag does not fail"            0 1.26.5 'FROM golang:1.26-alpine'
+tmsg "floating tag warns" '::warning'       1.26.5 'FROM golang:1.26-alpine'
+t "floating minor below floor IS refused" 1 1.26.5 'FROM golang:1.25-alpine'
+
+# --- ARG resolution ---------------------------------------------------------
+# A parameterised FROM is only as good as its default; check it, don't skip it.
+t "ARG default below floor is refused"    1 1.26.5 'ARG GO_VERSION=1.26.4' 'FROM golang:${GO_VERSION}-bookworm'
+t "ARG default at floor builds"           0 1.26.5 'ARG GO_VERSION=1.26.5' 'FROM golang:${GO_VERSION}-bookworm'
+t "unbraced \$VAR resolves"                1 1.26.5 'ARG GO_VERSION=1.24' 'FROM golang:$GO_VERSION-bookworm'
+t "ARG with trailing comment parses"      1 1.26.5 'ARG GO_VERSION=1.26.4 # keep in step' 'FROM golang:${GO_VERSION}-alpine'
+# luxfi/node ships this literally, to silence a buildx warning on a Dockerfile
+# that is never built with the default. It must not crash the gate.
+t "unparseable ARG default is skipped"    0 1.26.5 'ARG GO_VERSION=INVALID # silences a warning' 'FROM golang:${GO_VERSION}-bookworm'
+t "unversioned golang:alpine is skipped"  0 1.26.5 'FROM golang:alpine'
+t "golang:1-alpine is skipped"            0 1.26.5 'FROM golang:1-alpine'
+
+# --- module resolution ------------------------------------------------------
+# Multi-module repos build subdirectories against their OWN go.mod. Taking the
+# root's floor would report a mismatch that does not exist (or miss one that
+# does) — hanzoai/s3 is the live case.
+d="$tmp/multi"; mkdir -p "$d/sub"
+printf 'module root\n\ngo 1.26.5\n' > "$d/go.mod"
+printf 'module sub\n\ngo 1.24.0\n' > "$d/sub/go.mod"
+printf 'FROM golang:1.24-alpine\n' > "$d/sub/Dockerfile"
+out=$(cd "$d" && bash "$GOVER" sub/Dockerfile . 2>&1); rc=$?
+if [ "$rc" = 0 ]; then printf 'ok    %-56s rc=0\n' "nearest go.mod wins over the root"
+else printf 'FAIL  %-56s rc=%s\n      %s\n' "nearest go.mod wins over the root" "$rc" "$out"; fail=1; fi
+printf 'FROM golang:1.24-alpine\n' > "$d/Dockerfile"
+out=$(cd "$d" && bash "$GOVER" Dockerfile . 2>&1); rc=$?
+if [ "$rc" = 1 ]; then printf 'ok    %-56s rc=1\n' "root Dockerfile is judged by the root go.mod"
+else printf 'FAIL  %-56s rc=%s\n      %s\n' "root Dockerfile is judged by the root go.mod" "$rc" "$out"; fail=1; fi
+
+# --- no module at all -------------------------------------------------------
+d2="$tmp/nomod"; mkdir -p "$d2"
+printf 'FROM golang:1.20-alpine\n' > "$d2/Dockerfile"
+out=$(cd "$d2" && bash "$GOVER" Dockerfile . 2>&1); rc=$?
+if [ "$rc" = 0 ]; then printf 'ok    %-56s rc=0\n' "no go.mod: nothing to compare, stays silent"
+else printf 'FAIL  %-56s rc=%s\n      %s\n' "no go.mod: nothing to compare, stays silent" "$rc" "$out"; fail=1; fi
+
+# --- the remediation is in the message --------------------------------------
+# A gate that says only "no" costs the next person the same hour it cost the
+# last one.
+tmsg "error names the fix (pin + GOTOOLCHAIN=auto)" 'GOTOOLCHAIN=auto' 1.26.5 'FROM golang:1.26.4-alpine'
+tmsg "error quotes the runtime failure it prevents" 'go.mod requires go >=' 1.26.5 'FROM golang:1.26.4-alpine'
+
+# --- build context decides the module, not file location -------------------
+# hanzoai/s3's live shape: a Dockerfile under test/kafka/ built with
+# `context: ../..` that does `COPY go.mod go.sum ./` compiles the ROOT module.
+# Judging it by test/kafka/go.mod reads 1.25.0 where the truth is 1.26.5 — the
+# difference between "fine" and "cannot build".
+d3="$tmp/ctxwins"; mkdir -p "$d3/test/kafka"
+printf 'module root\n\ngo 1.26.5\n' > "$d3/go.mod"
+printf 'module sub\n\ngo 1.25.0\n' > "$d3/test/kafka/go.mod"
+printf 'FROM golang:1.25-alpine\nCOPY go.mod go.sum ./\nRUN go build ./...\n' > "$d3/test/kafka/Dockerfile.s3"
+out=$(cd "$d3" && bash "$GOVER" test/kafka/Dockerfile.s3 . 2>&1); rc=$?
+if [ "$rc" = 1 ]; then printf 'ok    %-56s rc=1\n' "context go.mod wins when Dockerfile COPYs it"
+else printf 'FAIL  %-56s rc=%s\n      %s\n' "context go.mod wins when Dockerfile COPYs it" "$rc" "$out"; fail=1; fi
+# ...and the converse: a subdir module built from its OWN directory as context,
+# copying its OWN go.mod, is still judged by its own floor.
+d4="$tmp/subctx"; mkdir -p "$d4/sidecar"
+printf 'module root\n\ngo 1.26.5\n' > "$d4/go.mod"
+printf 'module sidecar\n\ngo 1.24.0\n' > "$d4/sidecar/go.mod"
+printf 'FROM golang:1.24-alpine\nCOPY go.mod go.sum ./\n' > "$d4/sidecar/Dockerfile"
+out=$(cd "$d4/sidecar" && bash "$GOVER" Dockerfile . 2>&1); rc=$?
+if [ "$rc" = 0 ]; then printf 'ok    %-56s rc=0\n' "own-directory context keeps its own floor"
+else printf 'FAIL  %-56s rc=%s\n      %s\n' "own-directory context keeps its own floor" "$rc" "$out"; fail=1; fi
+# A Dockerfile that copies a SUBDIRECTORY's go.mod is judged by the nearest one,
+# not the context root — otherwise every multi-module repo reports false alarms.
+d5="$tmp/nocopy"; mkdir -p "$d5/svc"
+printf 'module root\n\ngo 1.26.5\n' > "$d5/go.mod"
+printf 'module svc\n\ngo 1.24.0\n' > "$d5/svc/go.mod"
+printf 'FROM golang:1.24-alpine\nCOPY svc/go.mod ./\n' > "$d5/svc/Dockerfile"
+out=$(cd "$d5" && bash "$GOVER" svc/Dockerfile . 2>&1); rc=$?
+if [ "$rc" = 0 ]; then printf 'ok    %-56s rc=0\n' "subdir go.mod copy is not the context root"
+else printf 'FAIL  %-56s rc=%s\n      %s\n' "subdir go.mod copy is not the context root" "$rc" "$out"; fail=1; fi
+
+echo
+[ $fail = 0 ] && echo "all gover tests passed" || echo "gover tests FAILED"
+exit $fail

bin/ignoretracked

@@ -0,0 +1,118 @@
+#!/usr/bin/env bash
+# ignoretracked — refuse a repo that ships bulk content its own .gitignore
+# claims to be ignoring. One implementation, every caller.
+#
+#   ignoretracked [dir]
+#
+# WHAT THIS CATCHES
+#
+# An ignore rule does not untrack what is already tracked. `.gitignore` is
+# consulted when git decides whether to ADD an untracked path; a path already
+# in the index is never reconsidered. So this arrangement is stable and silent:
+#
+#   .gitignore says   native/flags/target/
+#   the index says    855 files under native/flags/target/
+#   git status says   nothing
+#
+# hanzoai/cloud lived there for 6 days and 16 hours. 362 MB of orphaned cargo
+# output — three near-identical 37.8 MB staticlibs and a pile of .rlib — went
+# into every release, took the module past Go's 500 MiB ceiling (see
+# bin/modsize) and made it UNFETCHABLE for nine consecutive releases. The
+# `git archive` of that commit is 202 MB against 12.5 MB today: 16x.
+#
+# The causal story is worth knowing because it is not carelessness, it is a
+# race nobody could see. The ignore rule was REMOVED at 12:22 (the Rust
+# staticlib was being dropped for a Go evaluator), the 855 files were added at
+# 12:51 inside that 4.5-hour window when nothing was ignoring them, and the
+# rule was RE-ADDED at 16:48. Every individual step was reasonable. The state
+# they combined into is the defect, and no tool in the pipeline had an opinion
+# about it.
+#
+# WHY THIS GATES ON BYTES AND NOT ON PRESENCE
+#
+# The obvious gate — "any tracked path matched by .gitignore fails" — is
+# correct in principle and unshippable in fact. Measured across all 845 git
+# repos in the three orgs: 155 of them (18%) carry at least one tracked file
+# their .gitignore matches, and hanzoai/cloud's own origin/main is one of them
+# (a bare, unanchored `tools` pattern on .gitignore:62 catches 27 legitimately
+# tracked Go source files under apps/tools/). `CLAUDE.md` alone is ignored-and-
+# tracked in 40 repos and is the ONLY hit in 29 of them. Turning that on as a
+# hard fail breaks a fifth of the estate on day one, and a gate that fails what
+# ought to pass is a gate that gets switched off — after which we are worse off
+# than before it existed.
+#
+# So the gate is on the quantity that actually caused the outage. The byte
+# distribution separates cleanly, which is why this threshold can be a refusal
+# rather than a warning:
+#
+#     worst legitimate repo in the estate   61.5 MB   (hanzo/docs, vendored)
+#     ... next                              48.8 MB, 45.8, 45.2, 43.8, 39.8
+#     repos over 100 MB                     ZERO
+#     the defect this gate exists for      362.0 MB
+#
+# Default ceiling 100 MB: green on all 845 repos today with 62% headroom over
+# the worst honest case, and red on the real defect by 3.6x. Nothing to
+# baseline, no allowlist, no per-repo exemptions — the tail is REPORTED (so the
+# hygiene problem stays visible and shrinkable) and only the bulk is REFUSED.
+#
+# As repos are cleaned up, lower IGNORETRACKED_MAX_MB. It is a ratchet, and the
+# end state is 0 — at which point this becomes the pure presence gate that was
+# right all along. Do not start there.
+#
+# WHY core.excludesFile IS PINNED OFF
+#
+# `--exclude-standard` reads THREE sources: the repo's committed .gitignore
+# files, .git/info/exclude, and the user's global core.excludesFile. The last
+# is per-machine, so the same commit gets different verdicts on a laptop and a
+# runner — on this workstation a global bare `tags` pattern matched 1,271
+# Elixir source files in lux/explorer-v1 that CI would never flag. A gate whose
+# answer depends on whose machine asked is not a gate. Only committed
+# .gitignore is in scope, so the global file is pinned to /dev/null.
+# (.git/info/exclude is per-clone and is the stock all-comments template on a
+# fresh CI checkout; it cannot be overridden by -c, and is left alone.)
+#
+# EXIT: 0 clean or under the ceiling (findings still reported), 1 over it.
+set -uo pipefail
+
+MAX_MB=${IGNORETRACKED_MAX_MB:-100}
+root=${1:-.}
+cd "$root" 2>/dev/null || { echo "ignoretracked: no such directory: $root" >&2; exit 1; }
+git rev-parse --git-dir >/dev/null 2>&1 || exit 0   # not a repo: nothing to check
+
+tmp=$(mktemp -d); trap 'rm -rf "$tmp"' EXIT
+
+# -s gives "<mode> <sha> <stage>\t<path>", which carries the blob id — so the
+# size comes from cat-file and needs no working-tree stat (correct on a bare or
+# sparse checkout, and unaffected by anything a build has written).
+git -c core.excludesFile=/dev/null ls-files -s --cached --ignored --exclude-standard \
+  > "$tmp/ls" 2>/dev/null || exit 0
+[ -s "$tmp/ls" ] || { echo "ignoretracked: OK — nothing tracked that .gitignore ignores"; exit 0; }
+
+files=$(wc -l < "$tmp/ls")
+bytes=$(awk '{print $2}' "$tmp/ls" \
+  | git cat-file --batch-check='%(objectsize)' --buffer 2>/dev/null \
+  | awk '/^[0-9]+$/{s+=$1} END{print s+0}')
+mb=$(awk -v b="${bytes:-0}" 'BEGIN{printf "%.1f", b/1048576}')
+
+# WHICH .gitignore LINE is doing this. Plain `check-ignore` prints nothing for a
+# tracked path (it answers "would git ignore this if it were untracked", and a
+# tracked path short-circuits) — --no-index is what makes it answer for the
+# files we actually have. The output names source:line:pattern, so the report
+# points at the line to edit instead of at 855 paths to read.
+cut -f2- "$tmp/ls" | git -c core.excludesFile=/dev/null check-ignore --no-index -v --stdin \
+  > "$tmp/why" 2>/dev/null || true
+
+echo "ignoretracked: ${files} tracked file(s), ${mb} MB, matched by this repo's own .gitignore"
+if [ -s "$tmp/why" ]; then
+  echo "  by rule (top 10):"
+  awk -F'\t' '{n[$1]++} END{for (k in n) printf "%8d  %s\n", n[k], k}' "$tmp/why" \
+    | sort -rn | head -10
+fi
+
+limit=$(( MAX_MB * 1048576 ))
+if [ "${bytes:-0}" -ge "$limit" ]; then
+  echo "::error::${mb} MB of tracked content is matched by this repo's own .gitignore — over the ${MAX_MB} MB ceiling. An ignore rule does not untrack what is already tracked, so this ships in every release and every module zip while \`git status\` stays clean. Fix: \`git rm -r --cached <path>\` and commit (the working tree is untouched). If the content is meant to be tracked, un-ignore it instead — negate the rule with \`!<path>\` — so the two stop disagreeing."
+  exit 1
+fi
+echo "ignoretracked: OK — ${mb} MB is under the ${MAX_MB} MB ceiling (reported, not blocking)"
+exit 0

bin/modsize

@@ -0,0 +1,123 @@
+#!/usr/bin/env bash
+# modsize — refuse a Go module that is approaching the size at which Go can no
+# longer fetch it. One implementation, every caller.
+#
+#   modsize [dir]        # default: every module in the repo, from the root
+#
+# WHAT THIS CATCHES
+#
+# Go's module ceiling is not a soft limit and not a warning. From
+# golang.org/x/mod/zip (and, identically, cmd/go/internal/modfetch/codehost):
+#
+#   MaxZipFile = 500 << 20     // 524288000 bytes, 500 MiB
+#
+# and it is enforced THREE ways on the same number — the zip file itself, the
+# total uncompressed size of the files inside it, and (in CheckDir) the running
+# sum of the source tree's file sizes:
+#
+#   "module source tree too large (max size is 524288000 bytes)"
+#   "total uncompressed size of module contents too large (...)"
+#
+# hanzoai/cloud crossed it and became UNFETCHABLE for nine consecutive
+# releases. Nothing said so. The module publishes fine — the ceiling is
+# enforced on the CONSUMER, at `go get`, so the failure surfaces in someone
+# else's repo, at a version they did not choose, long after the release that
+# caused it. There is no signal at the publishing end at all, which is why nine
+# releases went out before anybody knew.
+#
+# WHY THIS SUMS RAW BYTES AND WHY THAT IS EXACT, NOT AN APPROXIMATION
+#
+# It would be reasonable to assume the limit is on the compressed zip and that
+# summing uncompressed bytes over-counts. It does not: zip.CheckDir accumulates
+# `info.Size()` — the raw, uncompressed size of each regular file — and fails
+# when that running total exceeds MaxZipFile. So the sum of file sizes IS one
+# of the three quantities Go bounds, and a git blob's size is exactly that
+# file's uncompressed size. This gate therefore measures the same number Go
+# measures, not a proxy for it.
+#
+# WHAT IT EXCLUDES, AND WHY EACH EXCLUSION IS REQUIRED FOR CORRECTNESS
+#
+#   • Nested modules. A subdirectory with its own go.mod is a DIFFERENT module
+#     and its bytes are not in the parent's zip. Counting them would fail a
+#     repo that is nowhere near the limit — hanzoai/s3 is this shape (it builds
+#     s3-rdma-sidecar/ and telemetry/server/ from their own go.mod files), and
+#     a gate that fails a repo that would have worked is a gate people learn to
+#     skip. Each nested module is instead checked on its own terms.
+#   • Symlinks and gitlinks (submodules). zip.CheckDir skips both — symlinks
+#     explicitly (golang.org/issue/27093), submodules because they are not
+#     files. Counting a gitlink's 20-byte entry would be harmless; counting a
+#     symlink's target as content would not.
+#
+# It reads tracked content only (git ls-tree), because that is what a module
+# zip is built from: the proxy serves what the VCS has at that tag, not what a
+# working tree happens to contain.
+#
+# THE THRESHOLD IS BELOW THE CEILING ON PURPOSE
+#
+# Failing AT 500 MiB would be useless — at that point the module is already
+# unfetchable and the only question left is how many releases shipped broken.
+# The gate refuses at MODSIZE_MAX_PCT (default 80%, ~419 MiB), which is the
+# "warn well before" — spelled as a refusal, because a warning about a cliff
+# nobody is watching is the same defect one level up. 105 MiB of headroom is
+# several releases' worth of honest growth, so this fires with room to fix it
+# calmly and never fires the release it would have broken.
+#
+# EXIT: 0 clean, 1 when a module is at or past the threshold.
+set -uo pipefail
+
+# 500 << 20, from golang.org/x/mod/zip. Not a guess and not rounded: the
+# constant is quoted so a reader can check it against the source.
+CEILING=$((500 << 20))
+PCT=${MODSIZE_MAX_PCT:-80}
+REF=${MODSIZE_REF:-HEAD}
+
+root=${1:-.}
+cd "$root" 2>/dev/null || { echo "modsize: no such directory: $root" >&2; exit 1; }
+git rev-parse --git-dir >/dev/null 2>&1 || exit 0   # not a repo: nothing to measure
+
+# Every go.mod in the tree, at REF. The root module is "go.mod"; anything else
+# is a nested module and marks a prefix the parent must not count.
+mods=$(git ls-tree -r --name-only "$REF" 2>/dev/null | grep -E '(^|/)go\.mod$' | sort) || exit 0
+[ -z "$mods" ] && exit 0
+
+# path<TAB>size for every regular tracked file. Mode 100644/100755 only:
+# 120000 is a symlink and 160000 a gitlink, both of which zip.CheckDir omits.
+# `git ls-tree -l` separates the path with a TAB, so split on that rather than
+# on whitespace: a path with spaces in it must survive intact.
+sizes=$(git ls-tree -r -l "$REF" 2>/dev/null \
+  | sed -n 's/^\([0-9]\{6\}\) blob \([0-9a-f]*\) *\([0-9-]*\)\t\(.*\)$/\1\t\3\t\4/p' \
+  | awk -F'\t' '$1=="100644"||$1=="100755"{print $3 "\t" $2}')
+
+human() { awk -v b="$1" 'BEGIN{ printf "%.1f MiB", b/1048576 }'; }
+
+rc=0
+for gm in $mods; do
+  if [ "$gm" = "go.mod" ]; then mdir=""; else mdir="${gm%/go.mod}/"; fi
+  # The prefixes this module must NOT count: every OTHER module nested under it.
+  nested=$(printf '%s\n' "$mods" | while read -r o; do
+    [ "$o" = "$gm" ] && continue
+    od="${o%go.mod}"
+    case "$od" in "$mdir"?*) printf '%s\n' "$od";; esac
+  done)
+  total=$(printf '%s\n' "$sizes" | awk -F'\t' -v m="$mdir" -v nl="$nested" '
+    BEGIN{ n=split(nl, arr, "\n") }
+    {
+      p=$1
+      if (m != "" && index(p, m) != 1) next          # not in this module
+      for (i=1; i<=n; i++) if (arr[i] != "" && index(p, arr[i]) == 1) next  # nested module
+      s += $2
+    }
+    END{ print s+0 }')
+  limit=$(( CEILING * PCT / 100 ))
+  name=${mdir:-./}
+  if [ "$total" -ge "$CEILING" ]; then
+    echo "::error file=${gm}::module ${name} is $(human "$total") of tracked content — PAST Go's $(human $CEILING) module ceiling. It is already unfetchable: \`go get\` fails with 'module source tree too large (max size is ${CEILING} bytes)' in every consumer, at every version that carries it. Find the bulk with: git ls-tree -r -l ${REF} | sort -k4 -n | tail -20"
+    rc=1
+  elif [ "$total" -ge "$limit" ]; then
+    echo "::error file=${gm}::module ${name} is $(human "$total") of tracked content — ${PCT}% of Go's $(human $CEILING) ceiling, $(human $((CEILING-total))) of headroom left. Past the ceiling the module stops being fetchable AT THE CONSUMER, so the break shows up in someone else's build and not in this one. Find the bulk with: git ls-tree -r -l ${REF} | sort -k4 -n | tail -20"
+    rc=1
+  else
+    echo "modsize: OK — ${name} $(human "$total") ($(( total * 100 / CEILING ))% of $(human $CEILING))"
+  fi
+done
+exit $rc

bin/publishable

@@ -0,0 +1,46 @@
+#!/usr/bin/env bash
+# publishable — refuse a `build_secrets` name that does not declare itself public.
+#
+# Usage: publishable <hanzo.yml>   (reads images[].build_secrets, rc=1 on refusal)
+#
+# WHY A NAME AND NOT A VALUE. A build_secret is handed to buildx as
+# `--build-arg NAME=value`, and a build-arg is IN THE PUBLISHED IMAGE: `docker
+# history` prints it to anyone who can pull. So the only value that may sit
+# here is one that is public on purpose — a Vite/Next static export has no
+# server to read an env from, so its ingest key must be inlined at build, and
+# inlining it is what publishing it means.
+#
+# The value cannot be the test. At the moment ci reads hanzo.yml the value does
+# not exist yet (KMS has not been called), and guessing secrecy from a string's
+# shape is a heuristic that is wrong in both directions. The name is what a
+# reviewer reads, it is in git, and it is decided by the person who knows the
+# answer. So the name carries the assertion.
+#
+# The fleet had already started saying it this way — hanzoai/docs renamed
+# EVENT_INGEST_KEY -> PUBLISHABLE_KEY, and hanzoai/world's four are VITE_*,
+# which a bundler inlines by construction. This turns that convention into the
+# mechanism. Before it, the ONE repo whose value is genuinely publishable
+# (hanzoai/ui, a `pk-…` key) asserted the prefix inside its own Dockerfile, so
+# the check existed once, for one image, and any repo adding a real credential
+# got no check at all.
+set -uo pipefail
+
+f=${1:-hanzo.yml}
+[ -r "$f" ] || exit 0   # no config, nothing declared, nothing to refuse
+
+names=$(yq -r '[(.images // [])[] | (.build_secrets // [])[]] | unique | .[]' "$f" 2>/dev/null) || exit 0
+[ -n "$names" ] || exit 0
+
+rc=0
+for n in $names; do
+  case "$n" in
+    # Prefixes a bundler already treats as client-side, plus an explicit
+    # self-declaration for everything else. Anything outside this set has not
+    # claimed to be public, so it is not baked.
+    PUBLISHABLE_*|PUBLIC_*|NEXT_PUBLIC_*|EXPO_PUBLIC_*|NUXT_PUBLIC_*|VITE_*|REACT_APP_*|*_PUBLISHABLE|*_PUBLIC) ;;
+    *)
+      echo "::error::build_secret '$n' does not declare itself publishable, and a build_secret is baked into the image as a --build-arg where \`docker history\` reveals it. Rename it (PUBLISHABLE_*, PUBLIC_*, NEXT_PUBLIC_*, VITE_*, REACT_APP_*) if the value is public on purpose; if it is a real credential it cannot be a build_secret at all." >&2
+      rc=1 ;;
+  esac
+done
+exit $rc

bin/publishable_test.sh

@@ -0,0 +1,65 @@
+#!/usr/bin/env bash
+# Tests for bin/publishable. Offline and deterministic: every case is a
+# hanzo.yml written into a temp dir. Run: bash bin/publishable_test.sh
+set -uo pipefail
+cd "$(dirname "$0")/.."
+PUB="$PWD/bin/publishable"
+tmp=$(mktemp -d); trap 'rm -rf "$tmp"' EXIT
+fail=0
+
+# t <name> <want-rc> <build_secrets yaml-inline list>
+t() {
+  local name=$1 want=$2 list=$3
+  local d="$tmp/$RANDOM$RANDOM"; mkdir -p "$d"
+  { echo 'images:'; echo '  - name: app'; echo '    repo: ghcr.io/hanzoai/app'
+    [ -n "$list" ] && echo "    build_secrets: $list"; } > "$d/hanzo.yml"
+  out=$(bash "$PUB" "$d/hanzo.yml" 2>&1); rc=$?
+  if [ "$rc" = "$want" ]; then printf 'ok    %-56s rc=%s\n' "$name" "$rc"
+  else printf 'FAIL  %-56s rc=%s (want %s)\n      %s\n' "$name" "$rc" "$want" "$out"; fail=1; fi
+}
+
+echo "--- refused: a name that never claimed to be public ---"
+# The live case. hanzoai/ui declares exactly this, and its value IS publishable
+# — but nothing outside its own Dockerfile could know that.
+t "EVENT_INGEST_KEY is refused"              1 '[EVENT_INGEST_KEY]'
+t "a real credential is refused"             1 '[STRIPE_SECRET_KEY]'
+t "a token is refused"                       1 '[GITHUB_TOKEN]'
+t "a password is refused"                    1 '[DB_PASSWORD]'
+t "a private key is refused"                 1 '[SIGNING_PRIVATE_KEY]'
+t "one bad name among good ones is refused"  1 '[VITE_GTM_ID, EVENT_INGEST_KEY]'
+
+echo "--- allowed: the name declares it ---"
+# These are the fleet's real declarations, verbatim.
+t "PUBLISHABLE_KEY (hanzoai/docs)"           0 '[PUBLISHABLE_KEY]'
+t "VITE_MAPBOX_TOKEN (hanzoai/world)"        0 '[VITE_MAPBOX_TOKEN]'
+t "VITE_SENTRY_DSN (hanzoai/world)"          0 '[VITE_SENTRY_DSN]'
+t "world's four together"                    0 '[VITE_MAPBOX_TOKEN, VITE_SENTRY_DSN, VITE_ANALYTICS_WEBSITE_ID, VITE_GTM_ID]'
+t "NEXT_PUBLIC_ prefix"                      0 '[NEXT_PUBLIC_INGEST_KEY]'
+t "REACT_APP_ prefix"                        0 '[REACT_APP_MAP_KEY]'
+t "EXPO_PUBLIC_ prefix"                      0 '[EXPO_PUBLIC_API_KEY]'
+t "NUXT_PUBLIC_ prefix"                      0 '[NUXT_PUBLIC_API_KEY]'
+t "PUBLIC_ prefix"                           0 '[PUBLIC_ANALYTICS_ID]'
+t "_PUBLISHABLE suffix"                      0 '[STRIPE_PUBLISHABLE]'
+t "_PUBLIC suffix"                           0 '[ANALYTICS_ID_PUBLIC]'
+
+echo "--- silent: nothing declared, nothing to say ---"
+# 44 of the fleet's 47 repos are this case and must be byte-for-byte unchanged.
+t "no build_secrets key at all"              0 ''
+t "empty build_secrets list"                 0 '[]'
+
+echo "--- a missing file is not a refusal ---"
+out=$(bash "$PUB" "$tmp/does-not-exist.yml" 2>&1); rc=$?
+if [ "$rc" = 0 ]; then printf 'ok    %-56s rc=0\n' "absent hanzo.yml is silent"
+else printf 'FAIL  %-56s rc=%s\n' "absent hanzo.yml is silent" "$rc"; fail=1; fi
+
+echo "--- the refusal says what to do about it ---"
+d="$tmp/msg"; mkdir -p "$d"
+printf 'images:\n  - name: app\n    build_secrets: [EVENT_INGEST_KEY]\n' > "$d/hanzo.yml"
+out=$(bash "$PUB" "$d/hanzo.yml" 2>&1)
+for pat in "EVENT_INGEST_KEY" "docker history" "PUBLISHABLE_" "cannot be a build_secret"; do
+  if printf '%s' "$out" | grep -qF "$pat"; then printf 'ok    %-56s\n' "message names '$pat'"
+  else printf 'FAIL  %-56s\n      got: %s\n' "message names '$pat'" "$out"; fail=1; fi
+done
+
+[ "$fail" = 0 ] && echo "PASS" || echo "FAIL"
+exit $fail

bin/sitedeploy

@@ -0,0 +1,238 @@
+#!/usr/bin/env bash
+# sitedeploy — publish a built static export to the Hanzo PaaS Sites plane.
+# One implementation, every static site.
+#
+#   sitedeploy <slug> <dir>      # e.g. sitedeploy hanzo-ai out
+#
+# WHY THIS IS A SCRIPT AND NOT INLINE SHELL: the same forty lines of enqueue →
+# upload → complete were about to be pasted into hanzo.ai, hanzo.app, hips,
+# computer and every static surface after them. Written N times it is right N-1
+# times and then wrong once — which is exactly how `sha-<short>` became the only
+# tag eleven repos ever published (see bin/imgver). The plane's contract lives
+# here, once.
+#
+# THE THREE STEPS, and why the bytes never pass through the API:
+#
+#   POST /v1/projects/<slug>/deploy            -> 202 {id, bucket, prefix, upload}
+#   POST <upload.url> per file                 -> the bytes, straight to S3
+#   POST /v1/projects/<slug>/deployments/<id>/complete
+#
+# A real export is large — hanzo.ai is 128 MB across 8403 files — and cloud's
+# BodyLimit is 16 MiB, so an artifact POST is refused by fasthttp BEFORE any
+# handler runs, and it fails as an opaque 400 "Error when parsing request" that
+# reads like a malformed payload rather than a size cap. The git source is the
+# documented route for exactly this shape.
+#
+# NO STANDING S3 CREDENTIAL. The 202 carries `upload`: a presigned POST policy
+# that is prefix-scoped (starts-with $key "<org>/<slug>/", enforced by S3 itself),
+# short-lived (30 min) and size-bounded. That replaced handing every repo the
+# bucket's own long-lived access key — one key for a bucket whose only tenant
+# separation is the key prefix, so every repo holding it could overwrite EVERY
+# org's site (cloud apps/projects/grant.go). Do not reintroduce SITES_S3_* here.
+# HANZO_DEPLOY_TOKEN is the ONE credential this needs.
+#
+# DELETION IS THE SERVER'S. The grant authorizes writes only, so CI cannot remove
+# a file; `keys` in the completion is the manifest cloud reconciles the prefix
+# against, and it deletes what the build no longer produces. That is where
+# `aws s3 sync --delete` went. It fails CLOSED on an empty manifest, and so does
+# this script — a build that enumerated nothing has failed, and honouring it
+# literally would delete the live site.
+#
+# ENV: HANZO_DEPLOY_TOKEN (required)  the org-scoped `sk-` key; mint at POST /v1/keys
+#      HANZO_API           (https://api.hanzo.ai)
+#      SITEDEPLOY_JOBS     (24)  parallel uploads
+#      SITEDEPLOY_COMMIT / SITEDEPLOY_BRANCH  recorded on the deployment
+#      SITEDEPLOY_PLAN=1   print the manifest and exit; no network. The test seam.
+set -euo pipefail
+
+slug="${1:?usage: sitedeploy <slug> <dir>}"
+dir="${2:?usage: sitedeploy <slug> <dir>}"
+api="${HANZO_API:-https://api.hanzo.ai}"
+jobs="${SITEDEPLOY_JOBS:-24}"
+
+[ -d "$dir" ] || { echo "::error::$dir is not a directory — the build produced no export"; exit 1; }
+
+# ---- content type -----------------------------------------------------------
+# The presigned POST carries no Content-Type condition, so whatever CI sends is
+# what the object stores — and what it stores is what the edge serves. Send
+# nothing and every page is application/octet-stream, which a browser DOWNLOADS
+# instead of rendering: a green deploy that serves an unusable site.
+ctype() {
+  case "${1##*.}" in
+    html|htm) echo 'text/html; charset=utf-8' ;;
+    css)      echo 'text/css; charset=utf-8' ;;
+    js|mjs)   echo 'text/javascript; charset=utf-8' ;;
+    json)     echo 'application/json; charset=utf-8' ;;
+    xml)      echo 'application/xml; charset=utf-8' ;;
+    txt)      echo 'text/plain; charset=utf-8' ;;
+    svg)      echo 'image/svg+xml' ;;
+    png)      echo 'image/png' ;;
+    jpg|jpeg) echo 'image/jpeg' ;;
+    gif)      echo 'image/gif' ;;
+    webp)     echo 'image/webp' ;;
+    avif)     echo 'image/avif' ;;
+    ico)      echo 'image/x-icon' ;;
+    woff)     echo 'font/woff' ;;
+    woff2)    echo 'font/woff2' ;;
+    ttf)      echo 'font/ttf' ;;
+    otf)      echo 'font/otf' ;;
+    wasm)     echo 'application/wasm' ;;
+    pdf)      echo 'application/pdf' ;;
+    webmanifest) echo 'application/manifest+json' ;;
+    map)      echo 'application/json' ;;
+    *)        echo 'application/octet-stream' ;;
+  esac
+}
+
+# ---- cache control ----------------------------------------------------------
+# Mirrors cloud's apps/sites.CacheControlFor so a site cached the same whichever
+# route its bytes took. bin/sitedeploy_test.sh pins these strings; if the server
+# changes its policy the test is what catches the drift.
+#
+# A fingerprinted asset (Vite/Next/webpack emit app.4f3a9c21.js) is immutable: a
+# new build changes the hash, so the old URL can be cached forever.
+#
+# The class is written `[._-]` with the dash LAST and the pattern held in a
+# variable. Go's regexp spells the same set `[.\-_]`, and transcribing that
+# literally into `[[ =~ ]]` is a silent defect twice over: a backslash is literal
+# inside a POSIX bracket expression, so `\-_` reads as the RANGE \…_ and the shell
+# rejects it as "invalid character range" — and because the `if` merely evaluates
+# false, every fingerprinted asset quietly fell back to max-age=3600 instead of
+# immutable. An unquoted inline pattern also has its own quoting hazards; the
+# variable form is the one that is read as a regex rather than a glob.
+fingerprint_re='[._-][0-9a-fA-F]{8,}\.[a-z0-9]+$'
+cachectl() {
+  local k="$1" base="${1##*/}"
+  case "${k##*.}" in
+    html|htm) echo 'public, max-age=60, s-maxage=86400' ;;
+    js|mjs|css|woff|woff2|png|jpg|jpeg|gif|svg|webp|avif|ico|ttf|otf|wasm|data|pck|unityweb|mem)
+      if [[ "$base" =~ $fingerprint_re ]]; then
+        echo 'public, max-age=31536000, immutable'
+      else
+        echo 'public, max-age=3600'
+      fi ;;
+    *) echo 'public, max-age=3600' ;;
+  esac
+}
+
+# ---- the manifest -----------------------------------------------------------
+# Paths RELATIVE to the export root, which is exactly what the completion's
+# `keys` must carry (cloud reconciles `keep[rel]` against them).
+#
+# CNAME does not travel. It is a GitHub Pages artifact that means nothing to S3
+# and would ship a stale hostname claim into the bucket.
+manifest=$(cd "$dir" && find . -type f ! -name CNAME | sed 's|^\./||' | LC_ALL=C sort)
+count=$(printf '%s' "$manifest" | grep -c . || true)
+[ "$count" -gt 0 ] || { echo "::error::$dir contains no files — refusing to deploy an empty manifest"; exit 1; }
+
+if [ -n "${SITEDEPLOY_PLAN:-}" ]; then
+  printf 'slug=%s dir=%s files=%s\n' "$slug" "$dir" "$count"
+  while IFS= read -r k; do [ -n "$k" ] && printf '%s\t%s\t%s\n' "$k" "$(ctype "$k")" "$(cachectl "$k")"; done <<< "$manifest"
+  exit 0
+fi
+
+: "${HANZO_DEPLOY_TOKEN:?HANZO_DEPLOY_TOKEN is unset. It is the ONE credential this needs; set it on the forge (git.hanzo.ai), which is what reads .hanzo/workflows — not on GitHub. Mint: POST /v1/keys {\"type\":\"secret\"}}"
+
+# ---- 0. ensure the project exists (self-provision) --------------------------
+# A brand-new slug has no project, and the enqueue below 404s on a missing one —
+# which is why every never-before-deployed site failed its first run. Create it
+# idempotently here instead: 200/201 the first time, 409 every time after, both
+# success. So a new site needs no out-of-band `POST /v1/projects`; committing the
+# workflow is enough. The repo is linked because the git-source enqueue requires
+# a linked project (deployGit rejects an unlinked one); SITEDEPLOY_REPO overrides
+# the origin for a forge checkout whose remote is not the canonical repo.
+repo="${SITEDEPLOY_REPO:-$(git remote get-url origin 2>/dev/null || true)}"
+pcode=$(curl -sS -o /tmp/sd-proj.json -w '%{http_code}' \
+  -X POST "$api/v1/projects" \
+  -H "Authorization: Bearer $HANZO_DEPLOY_TOKEN" -H 'Content-Type: application/json' \
+  -d "$(jq -nc --arg s "$slug" --arg u "$repo" --arg b "${SITEDEPLOY_BRANCH:-main}" \
+        '{slug:$s, name:$s} + (if $u=="" then {} else {repo:{url:$u, branch:$b}} end)')")
+case "$pcode" in
+  200|201|409) : ;;  # created now, or already there — either is the state we need
+  *) echo "::error::ensure project $slug returned HTTP $pcode"; head -c 400 /tmp/sd-proj.json; echo; exit 1 ;;
+esac
+
+# ---- 1. enqueue -------------------------------------------------------------
+# 202 Accepted is the success code: the deployment is queued, not live. bucket
+# and prefix come FROM cloud (sitePrefix(org, slug) is server-side) — never guess
+# them, or the upload lands where nothing is served the moment an org or slug
+# changes.
+code=$(curl -sS -o /tmp/sd-enq.json -w '%{http_code}' \
+  -X POST "$api/v1/projects/$slug/deploy" \
+  -H "Authorization: Bearer $HANZO_DEPLOY_TOKEN" -H 'Content-Type: application/json' \
+  -d "{\"source\":\"git\",\"commit\":\"${SITEDEPLOY_COMMIT:-}\",\"branch\":\"${SITEDEPLOY_BRANCH:-main}\"}")
+if [ "$code" != "202" ]; then
+  echo "::error::enqueue $api/v1/projects/$slug/deploy returned HTTP $code"; head -c 600 /tmp/sd-enq.json; echo; exit 1
+fi
+dep=$(jq -r '.id' /tmp/sd-enq.json)
+prefix=$(jq -r '.prefix' /tmp/sd-enq.json)
+upload_url=$(jq -r '.upload.url // empty' /tmp/sd-enq.json)
+if [ -z "$upload_url" ]; then
+  echo "::error::the 202 carried no upload grant, so there is no way to write the bytes."
+  echo "         cloud mints one only when presigning is configured (S3_ADMIN_* on the cloud deployment)."
+  exit 1
+fi
+jq -c '{id,version,status,bucket,prefix}' /tmp/sd-enq.json
+
+# A build that dies after this point would leave the deployment "queued" and the
+# project stuck "building" forever. Report the failure so cloud records an honest
+# terminal state instead of a lie by omission.
+fail() {
+  curl -sS -X POST "$api/v1/projects/$slug/deployments/$dep/complete" \
+    -H "Authorization: Bearer $HANZO_DEPLOY_TOKEN" -H 'Content-Type: application/json' \
+    -d '{"status":"error","message":"CI upload failed"}' >/dev/null 2>&1 || true
+  echo "::error::marked deployment $dep as error"
+}
+trap 'fail' ERR
+
+# ---- 2. the bytes -----------------------------------------------------------
+# `file` goes LAST: S3 ignores every field after the file part, so a grant field
+# trailing the body is silently dropped and the signature check fails.
+#
+# `key` is DROPPED from the grant's fields and re-sent per object. The grant
+# carries key="<org>/<slug>/" — the starts-with PLACEHOLDER, not a destination —
+# and forwarding it verbatim alongside the real key posts `key` twice, which S3
+# answers 400 for every object. That is the whole of the first end-to-end run:
+# 8403 files, 8403 400s. Everything else in the map (bucket, policy, x-amz-*) is
+# covered by the signature and must travel untouched.
+jq -r '.upload.fields | to_entries[] | select(.key != "key") | "-F\n\(.key)=\(.value)"' /tmp/sd-enq.json > /tmp/sd-fields
+put() {
+  local rel="$1" args=() line
+  # A read loop, NOT `mapfile`: mapfile is bash 4+, and macOS ships bash 3.2, so
+  # on a dev box it fails as `command not found`, the array stays EMPTY, and every
+  # upload goes out with no policy or signature at all. S3 then rejects it for a
+  # malformed X-Amz-Credential — an error that points at the credential rather
+  # than at the array that never got built.
+  while IFS= read -r line; do args+=("$line"); done < /tmp/sd-fields
+  curl -sS --fail-with-body -o /dev/null \
+    -X POST "$UP_URL" \
+    -F "key=$PREFIX/$rel" "${args[@]}" \
+    -F "Content-Type=$(ctype "$rel")" -F "Cache-Control=$(cachectl "$rel")" \
+    -F "file=@$DIR/$rel" \
+    || { echo "::error::upload failed: $rel"; return 1; }
+}
+export -f put ctype cachectl
+export UP_URL="$upload_url" PREFIX="$prefix" DIR="$dir" fingerprint_re
+
+echo "uploading $count files to s3://$(jq -r .bucket /tmp/sd-enq.json)/$prefix ($jobs parallel)"
+printf '%s\n' "$manifest" | grep . | xargs -P "$jobs" -I{} bash -c 'put "$@"' _ {}
+
+# ---- 3. flip it live --------------------------------------------------------
+# `wc -c`, not `stat`: the size flag is spelled -f%z on BSD and -c%s on GNU, and a
+# `stat -f%z || stat -c%s` fallback does not work — on Linux the first arm fails
+# INSIDE the pipeline, awk still exits 0, and the `||` never fires, so the byte
+# count silently reports 0. wc is the one spelling both agree on.
+bytes=$(cd "$dir" && find . -type f ! -name CNAME -exec wc -c {} + | awk '$2!="total"{s+=$1} END{print s+0}')
+jq -n --arg c "${SITEDEPLOY_COMMIT:-}" --argjson f "$count" --argjson b "${bytes:-0}" \
+      --args '{status:"live",commit:$c,files:$f,bytes:$b,keys:$ARGS.positional}' \
+      $(printf '%s\n' "$manifest" | grep .) > /tmp/sd-done.json
+
+code=$(curl -sS -o /tmp/sd-resp.json -w '%{http_code}' \
+  -X POST "$api/v1/projects/$slug/deployments/$dep/complete" \
+  -H "Authorization: Bearer $HANZO_DEPLOY_TOKEN" -H 'Content-Type: application/json' \
+  --data-binary @/tmp/sd-done.json)
+trap - ERR
+if [ "$code" != "200" ]; then
+  echo "::error::complete returned HTTP $code"; head -c 600 /tmp/sd-resp.json; echo; fail; exit 1
+fi
+jq -c '{status,liveUrl,version,files,bytes}' /tmp/sd-resp.json

bin/sitedeploy_test.sh

@@ -0,0 +1,80 @@
+#!/usr/bin/env bash
+# Tests for bin/sitedeploy. Runs OFFLINE: SITEDEPLOY_PLAN=1 stops the script
+# before the first network call and prints the manifest it would upload, so every
+# case here is deterministic and needs no token, no bucket and no cluster.
+# Run: bash bin/sitedeploy_test.sh
+set -uo pipefail
+cd "$(dirname "$0")/.."
+SD="$PWD/bin/sitedeploy"
+tmp=$(mktemp -d); trap 'rm -rf "$tmp"' EXIT
+fail=0
+
+plan() { SITEDEPLOY_PLAN=1 bash "$SD" a-slug "$1" 2>&1; }
+t() { # t <name> <got> <want>
+  if [ "$2" = "$3" ]; then printf 'ok    %-56s -> %s\n' "$1" "$2"
+  else printf 'FAIL  %-56s -> %s (want %s)\n' "$1" "$2" "$3"; fail=1; fi
+}
+# field <dir> <key> <col>  — the ctype (2) or cachectl (3) column for one key
+field() { plan "$1" | awk -F'\t' -v k="$2" -v c="$3" '$1==k{print $c}'; }
+
+site="$tmp/site"; mkdir -p "$site/assets" "$site/nested/deep"
+echo '<h1>hi</h1>'  > "$site/index.html"
+echo 'body{}'       > "$site/assets/app.4f3a9c21.css"
+echo 'x'            > "$site/assets/plain.css"
+echo 'y'            > "$site/assets/chunk-AB12CD34.js"
+echo '{}'           > "$site/data.json"
+echo 'z'            > "$site/nested/deep/page.html"
+echo 'hanzo.ai'     > "$site/CNAME"
+
+# --- the manifest ------------------------------------------------------------
+# Keys are RELATIVE to the export root: cloud reconciles keep[rel] against them,
+# so a leading ./ or an absolute path would match nothing and the completion
+# would prune the entire live site.
+t "keys are relative, no leading ./"  "$(plan "$site" | awk -F'\t' 'NR>1&&$1~/^\.?\//{print "ABS"}' | head -1)" ""
+t "nested paths keep their subdirs"   "$(plan "$site" | awk -F'\t' '$1=="nested/deep/page.html"{print "yes"}')" "yes"
+# CNAME is a GitHub Pages artifact: it means nothing to S3 and would ship a stale
+# hostname claim into the bucket.
+t "CNAME does not travel"             "$(plan "$site" | awk -F'\t' '$1=="CNAME"{print "leaked"}')" ""
+t "file count excludes CNAME"         "$(plan "$site" | head -1 | grep -o 'files=[0-9]*')" "files=6"
+
+# --- content type ------------------------------------------------------------
+# The presigned POST carries no Content-Type condition, so what CI sends is what
+# the object stores and what the edge serves. Send nothing and a browser
+# DOWNLOADS every page instead of rendering it.
+t "html"  "$(field "$site" index.html 2)"              "text/html; charset=utf-8"
+t "css"   "$(field "$site" assets/plain.css 2)"        "text/css; charset=utf-8"
+t "js"    "$(field "$site" assets/chunk-AB12CD34.js 2)" "text/javascript; charset=utf-8"
+t "json"  "$(field "$site" data.json 2)"               "application/json; charset=utf-8"
+
+# --- cache control: mirrors cloud apps/sites.CacheControlFor -----------------
+# These strings are the SERVER's policy, pinned here so the two cannot drift
+# apart silently. If cloud changes CacheControlFor, this is what goes red.
+t "html is short-lived, long at the edge" "$(field "$site" index.html 3)"        "public, max-age=60, s-maxage=86400"
+t "unfingerprinted asset is an hour"      "$(field "$site" assets/plain.css 3)"  "public, max-age=3600"
+# The regression this pins: Go spells the class [.\-_], and transcribing that
+# into [[ =~ ]] makes the shell reject it as an invalid character range. The `if`
+# then merely evaluates false, so every hashed asset silently lost `immutable`.
+t "fingerprinted .hash. is immutable"  "$(field "$site" assets/app.4f3a9c21.css 3)"   "public, max-age=31536000, immutable"
+t "fingerprinted -HASH- is immutable"  "$(field "$site" assets/chunk-AB12CD34.js 3)"  "public, max-age=31536000, immutable"
+
+# --- fail closed -------------------------------------------------------------
+# reconcilePrefix deletes whatever the manifest omits, so an empty manifest is a
+# request to delete the live site. A build that enumerated nothing has failed.
+empty="$tmp/empty"; mkdir -p "$empty"
+plan "$empty" >/dev/null 2>&1
+t "empty export is refused"  "$?"  "1"
+only_cname="$tmp/onlycname"; mkdir -p "$only_cname"; echo x > "$only_cname/CNAME"
+plan "$only_cname" >/dev/null 2>&1
+t "a dir holding only CNAME is empty too"  "$?"  "1"
+plan "$tmp/does-not-exist" >/dev/null 2>&1
+t "missing export dir is refused"  "$?"  "1"
+
+# --- the credential ----------------------------------------------------------
+# Not in PLAN mode (that is the offline seam), but a real run must refuse to
+# start rather than enqueue a deployment it cannot complete.
+out=$(HANZO_DEPLOY_TOKEN= bash "$SD" a-slug "$site" 2>&1); rc=$?
+t "no token: exits non-zero"          "$rc"  "1"
+t "no token: says which secret"       "$(printf '%s' "$out" | grep -c HANZO_DEPLOY_TOKEN)"  "1"
+
+[ $fail -eq 0 ] && echo "PASS" || echo "FAIL"
+exit $fail

go.mod

@@ -1,3 +1,3 @@
 module github.com/hanzoai/ci
 
-go 1.24
+go 1.26.5

hanzo.yml

@@ -59,6 +59,60 @@ test:
         exit 1
       fi
       echo "OK: .github and .hanzo copies are one file ($(wc -l < .github/workflows/build.yml) lines)"
+  - name: gate-runs-before-delegate
+    # `mode: delegate` chooses WHERE the image is built. It must never choose
+    # WHETHER the commit was tested. It did: the delegate step was evaluated
+    # fourth, ahead of every toolchain and ahead of `test:`, and every other step
+    # carried `if: inputs.mode != 'delegate'` — so a delegated run skipped the
+    # gate along with the build and finished green in seconds having proven
+    # nothing. The seam was right and the ORDER was wrong, which is the kind of
+    # defect that reads as correct in every diff that touches one step at a time.
+    #
+    # Two assertions, because either one alone can be satisfied while the gate
+    # still does not run: the delegate POST must come AFTER the test gate, and
+    # the test gate must not be delegate-guarded.
+    run: |
+      set -e
+      f=.github/workflows/build.yml
+      t=$(grep -n '^      - name: Test (per hanzo.yml)$'                       "$f" | cut -d: -f1)
+      d=$(grep -n '^      - name: Delegate build to platform (mode=delegate)$' "$f" | cut -d: -f1)
+      [ -n "$t" ] && [ -n "$d" ] || { echo "::error::cannot find the test gate ($t) or the delegate step ($d) — a rename broke this assertion, fix the assertion"; exit 1; }
+      [ "$d" -gt "$t" ] || { echo "::error::the delegate step (line $d) runs BEFORE the test gate (line $t) — a delegated build would ship an ungated commit"; exit 1; }
+      if sed -n "${t}p;$((t+1)),$((t+80))p" "$f" | grep -m1 '^        if: ' | grep -q "mode != 'delegate'"; then
+        echo "::error::the test gate is guarded by \`inputs.mode != 'delegate'\` — delegate would skip it"; exit 1
+      fi
+      echo "OK: test gate at line $t, delegate POST at line $d, gate not delegate-guarded"
+  - name: publishable
+    # bin/publishable refuses a `build_secrets` name that has not declared itself
+    # public. That matters because a build_secret is baked in as a --build-arg,
+    # which `docker history` prints to anyone who can pull — so the key is a
+    # publishing decision wearing the word "secret". Until this, the only check
+    # in the fleet lived inside hanzoai/ui's own Dockerfile, for one image.
+    run: bash bin/publishable_test.sh
+  - name: publishable-rule-is-one-rule
+    # The rule is spelled twice on purpose, and this is what keeps it one rule.
+    #
+    # build.yml cannot call bin/publishable, because the tools checkout and the
+    # workflow resolve from DIFFERENT places: a caller pins the workflow at a ref
+    # its own forge resolves, while the tools step derives its ref from
+    # GITHUB_WORKFLOW_REF — which git.hanzo.ai does not set, so it falls back to
+    # `v1` and clones github.com. Measured on run 36473: `derived ref=v1`,
+    # `cloned https://github.com/hanzoai/ci@v1`. So a step calling a NEW file
+    # under $CI_HOME is broken on every forge run until a tag moves on a host the
+    # caller never named. The pipeline has to carry its own rule.
+    #
+    # Which leaves the pattern in two files, which is the same shape as the two
+    # copies of build.yml and gets the same treatment: demand they are identical
+    # and let the gate, not a reader, be the thing that notices.
+    run: |
+      set -e
+      a=$(grep -oE '^[[:space:]]*PUBLISHABLE_\*\|[^)]*\)' .github/workflows/build.yml | tr -d '[:space:]')
+      b=$(grep -oE '^[[:space:]]*PUBLISHABLE_\*\|[^)]*\)' bin/publishable          | tr -d '[:space:]')
+      [ -n "$a" ] && [ -n "$b" ] || { echo "::error::publishable rule not found in build.yml ($a) or bin/publishable ($b) — an edit renamed it, fix this assertion"; exit 1; }
+      [ "$a" = "$b" ] || { echo "::error::the publishable rule differs between build.yml and bin/publishable — build.yml is what runs, bin/publishable is what is tested, so a difference means the tested rule is not the enforced one:
+        build.yml:       $a
+        bin/publishable: $b"; exit 1; }
+      echo "OK: one publishable rule, two spellings — $a"
   - name: imgver
     # bin/imgver decides the version EVERY image in the fleet publishes — this
     # workflow's build lane calls it, and so does the imgver composite action the
@@ -67,6 +121,22 @@ test:
     # IfNotPresent never picks up and no reader can see. Offline and
     # deterministic: the registry floor is injected, so it needs no network.
     run: bash bin/imgver_test.sh
+  - name: gover
+    # bin/gover is the gate the build lane runs against every Dockerfile before
+    # it builds: it refuses a Go builder image older than the go.mod it
+    # compiles. That failure is not hypothetical — the golang images set
+    # GOTOOLCHAIN=local, so the mismatch is a hard mid-build death, and
+    # hanzoai/visor v1.108.16 shipped it. A sweep of the orgs found 54 more
+    # Dockerfiles already below their own go.mod.
+    #
+    # The gate is only worth having if it is exact in BOTH directions: a false
+    # negative lets the next visor through, and a false positive blocks a build
+    # that would have worked, which is how gates get skipped. So the suite pins
+    # the refusals AND the allowances — a newer image than the floor is fine, an
+    # alpine suffix is not a Go patch, a floating tag warns instead of failing,
+    # and a multi-module repo is judged by its NEAREST go.mod. Offline and
+    # deterministic: temp dirs, no registry, no network.
+    run: bash bin/gover_test.sh
 
 # No `deploy:` ON PURPOSE. Rollout is a reviewed tag pin in hanzoai/universe
 # (infra/k8s/operator/crs/ci.yaml), the same rule cloud and git follow: a