mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
The Go port took 24 entries from a Python dict that held 40. Sixteen repos were in NEITHER sync leg afterwards -- not pull mirrors, so nothing brought them in, and absent from this table, so nothing pushed them forward -- which is the exact shape the port was written to eliminate, reintroduced by the port itself. The worst of them is hanzoai/ci. Every repo in three orgs imports it as `hanzoai/ci/...@v1`, and a stale pipeline runs GREEN, so a caller cannot tell a current pipeline from one months old. It had already sat 18 commits behind once for exactly this reason. The rest: console and namespace (shipping services whose inbound leg was never written down), the five hanzo-apps surfaces, hanzo-go/sdk and hanzo-rs/sdk (published SDKs that `go get` and `cargo` resolve against the forge copy -- 16 and 10 commits behind when they were found), hanzo-dart, hanzokv, hanzozt, hanzo-docs/team and luxfi/aml. Two guards, because a table that quietly loses rows is not a thing to notice twice. One asserts every declared org is in the allowlist -- without it an entry in a new org is refused and the only symptom is a smaller "N of M resolved". The other asserts the count and names five of the entries that went missing. The allowlist gains hanzo-inc, and the live run is why. Three declared repos -- auto, blog and visor -- have been transferred there, and the run refused all three by name rather than pushing into an org nobody had listed. That is the guard working: it is an allowlist so that an unknown org is a question, not an assumption. hanzo-inc is ours (created 2026-07-24, all three private and pushed within the week), so it is listed now and the refusal goes away. Measured against live GitHub: 40 of 40 resolve, exit 0. EIGHT only resolve because names are RESOLVED and never matched against a listing -- three moved to hanzo-apps, three to hanzo-inc, esign became sign, kms-v1 became kms. A listing would have reported eight absences, and an absent name raises nothing. Co-authored-by: Hanzo Dev <[email protected]>