hanzoteam/server is hanzoai/team now. The old path still resolves through
GitHub's rename redirect, so a clone from it works and nothing says the name
in this file is stale — which is the shape this section exists to warn about.
The forge line is untouched: git.hanzo.ai answers anonymous requests with 404
whether or not the repository is there, so nothing here could measure it.
Co-authored-by: Hanzo Dev <[email protected]>
Two facts about this repo are not discoverable from inside it, and both cost a
day. The canonical remote is git.hanzo.ai — GitHub is a copy with no push mirror
keeping it current, so it drifts, and it had sat nine releases behind while
accepting pushes that shipped nothing. And the API is served at /v1/workspace,
where anything built against upstream's server/public addresses /api/v4 and gets
a 404.
Both have a decoy. A forge API probe spelled /api/v1/ returns 404 for a repo that
exists, because the base is /v1/ — which reads as "the forge does not have this
repo". And /v1/<anything> returns 200 text/html from the SPA catch-all, so a
wrong API path looks alive.
The inherited AGENTS.md describes upstream's workflow and says nothing about
either, which is why there was nothing to read.
Co-authored-by: Hanzo Dev <[email protected]>
* Migrate store diagnostics to request context
Co-authored-by: Ben Schumacher <[email protected]>
* Keep store context rule only in server AGENTS
Co-authored-by: Ben Schumacher <[email protected]>
---------
Co-authored-by: Ben Schumacher <[email protected]>
Co-authored-by: Mattermost Build <[email protected]>
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev