Registry API
Workspaces
Workspace revisions, published workspaces, forks and drift reports.
Workspace revisions are the desired state `wl pull` reads. Published workspaces are the catalog entity behind `wl publish-workspace`, `wl fork` and `wl visibility --workspace`.
A drift report sends a workspace’s drift status (clean or dirty) and raises drift.detected or drift.cleared. CI tokens carry the reader role, and readers may report drift.
Operations
| Request | What it does |
|---|---|
| POST /v1/workspaces/revisions | Create workspace revisionin spec |
| GET /v1/workspaces/revisions | List all workspace revisionsin spec |
| GET /v1/workspaces/{workspaceId}/revisions/current | Get current workspace revisionin spec |
| POST /v1/workspaces | Publish a workspace to the catalog |
| GET /v1/workspaces | List published workspaces |
| GET /v1/workspaces/catalog/{id} | Get a published workspace manifest to fork |
| PATCH /v1/workspaces/{id}/visibility | Set a published workspace public or private |
| POST /v1/workspaces/{id}/drift-report | Report a workspace’s drift status |
Operations are the routes the server registers; this site checks its list against the route definitions. Operations marked “in spec” are also described in the committed OpenAPI file (apps/api/openapi.json), which does not yet cover every route. Only the public catalog and the health check work without a token.