Universe is hanzo-inc/universe

The private fleet declarations moved from hanzoai to hanzo-inc; name the
repository where it lives.

fleet.go

@@ -14,7 +14,7 @@ import (
 //
 // Four values answer it, and they are one causal line rather than four opinions.
 // A push moves HEAD; the run on that commit builds and proves an image, which is
-// BUILT; the same run writes the tag and digest into hanzoai/universe, which is
+// BUILT; the same run writes the tag and digest into hanzo-inc/universe, which is
 // DECLARED; Hanzo CD reconciles that pin onto the cluster, which is RUNNING.
 //
 //	head ──build──▶ built ──pin──▶ declared ──reconcile──▶ running
@@ -218,7 +218,7 @@ func (s *Pipeline) assess() {
 
 // ───────────────────────────── assembly ─────────────────────────────
 
-// pin is one service as hanzoai/universe declares it.
+// pin is one service as hanzo-inc/universe declares it.
 type pin struct {
 	Name      string
 	Namespace string

git.go

@@ -11,7 +11,7 @@ import (
 )
 
 // git.go reads the two things Hanzo Git knows that the run list does not: what
-// hanzoai/universe declares, and which commit last produced a proved image.
+// hanzo-inc/universe declares, and which commit last produced a proved image.
 //
 // Both come from the same host over the same token this service already holds.
 // The universe repo lives on Hanzo Git, so the declared state of the fleet is a

main.go

@@ -8,7 +8,7 @@
 //
 // Build and deploy are one event on this fleet, and the page says so. A push
 // runs the pipeline this repo publishes; that pipeline's `image` job produces the
-// artifact and its `rollout` job writes the tag and digest into hanzoai/universe,
+// artifact and its `rollout` job writes the tag and digest into hanzo-inc/universe,
 // which cd.hanzo.ai reconciles onto the cluster. So the last jobs of a run ARE
 // the deploy, and showing a run without showing whether its pin took effect is
 // reporting on the first half of an event.