mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
zooqueenandHanzo Dev
3f156028b7
Swept the table against both hosts: 32 of 40 in sync, 8 out of step. Working through the 8 rather than reporting them: RECONCILED. o11y was one commit out — the forge was ahead and GitHub was its strict ancestor, so GitHub moved up. kms had touched disjoint files on the two sides (forge: CI and deps; GitHub: a README notice) and merged with nothing to resolve. python-sdk looked like 14-vs-2 and was the same work done twice: both sides had applied the same 2,213-file consolidation, and `git cherry` showed the other GitHub commit already present under a different sha. Merged -s ours so the histories join while the tree stays the newer regeneration; a tree-level merge would have resurrected ~140 generated modules both sides had deleted, and models/__init__.py imports one of them, so the obvious resolution breaks the package. Verified it imports afterwards. DROPPED. cloud, gui and kms cannot satisfy what `native` asserts. gui and kms are ARCHIVED on GitHub — an archived repo refuses pushes, so those two can never converge by pushing and the forge is canonical by construction. cloud is inverted: its GitHub repo was created 2026-08-06 with 8 commits while the forge root is 2026-05-18 with 5001, and the forge is what CI and CD read. Dropped rather than left red, because a row that can never go green teaches people to ignore the job — which is the failure this whole component exists to end. Named in LLM.md with reasons instead of silently deleted, the same way universe's kustomization names its deliberate exclusions. Two genuinely split repos remain for a person: hanzo-apps/id and hanzoai/hanzo.network, neither sharing a common ancestor with its namesake. Co-authored-by: Hanzo Dev <[email protected]>