say Hanzo Git, which is what it is

"Forge" named nothing in this estate. The product is Hanzo Git, the address is
git.hanzo.ai, and the in-cluster service is hanzo-git.hanzo.svc. A generic word
invented for it sends a reader looking for a system that does not exist.

Comments only. ("unforgeable" stays — different word.)

.hanzo/workflows/cicd.yml

@@ -21,7 +21,7 @@ on:
     tags: ['v*']
   pull_request:
   # THE RELEASE POKES THE PROJECTION, and workflow_dispatch is how, because it
-  # is the dispatch verb this forge HAS. Two shapes were tried and neither could
+  # is the dispatch verb Hanzo Git HAS. Two shapes were tried and neither could
   # work: cloud posted `repository_dispatch: spec-update` at api.github.com,
   # where these callers ask for a label github.com has no runner for, so twelve
   # accepted events ran nothing; then this file grew a nightly `schedule:`,

.hanzo/workflows/sync-from-github.yml

@@ -9,7 +9,7 @@ name: Sync from GitHub
 # no-op because GitHub already has it. No echo, no loop.
 #
 # ONE deterministic direction per job: an in-cluster PULL. The runner reaches
-# both ends (GitHub outbound, this forge via the instance URL actions/checkout
+# both ends (GitHub outbound, Hanzo Git via the instance URL actions/checkout
 # already uses), so the sync has no ingress dependency.
 #
 # Fast-forward ONLY. A divergence fails LOUDLY here rather than force-pushing
@@ -51,7 +51,7 @@ jobs:
             #
             # It dispatched `deploy.yml`, which this repo does not have and never
             # had: these are libraries, they publish to PyPI and deploy nothing.
-            # The forge answered 404 every time, `|| echo ... (non-fatal)` ate it,
+            # Hanzo Git answered 404 every time, `|| echo ... (non-fatal)` ate it,
             # and the job went green. So every commit synced from GitHub landed
             # here having triggered NOTHING, and the gate this repo declares in
             # hanzo.yml has no runs at all to show for it.