-
revert(openapi): keep tracker a distinct /v1/tracker — it's a per-org issue tracker, not analytics
z released this
2026-07-17 03:23:16 +00:00 Coordinator confirmed against cloud source (clients/tracker): tracker is a
Linear-style projects+issues tracker, NOT event/web-analytics. Revert the
tracker->analytics fold from the prior commit:- git restore tracker/openapi.yaml (projects + issues, 4 routes, 8 schemas)
- remove the tracker: analytics collapsed entry; re-add tracker to the
applications domain list as a normal spec.
Kept distinct as its own /v1/tracker — NOT folded into projects/team (that is
a separate flagged review item, not forced here). The other 6 collapses stay:
featuregate->featureflags, ads->marketing, cms->content, cron->tasks,
connectorruntime->automations, gojabase->goja.merge.py green — back to 68 services, 1810 paths, 1000 schemas; hanzo.yaml +
CAPABILITIES.md regenerated.Downloads