Build & Artifacts

The CI/CD surface — what got built, what’s stored, and re-run a failed build. Reads run under your identity; the two writes (retry a build, delete an image version) are approval-gated.

Cloud Build

• list_builds(project_id) — the most recent builds, each with a short id and status (success, failure, working…).
• list_build_triggers(project_id) — the build triggers in a project, flagged if disabled.
• retry_build(build_id, project_id) — write. Re-runs a build by id — the one-move fix when a build failed on a flake. Use list_builds to find the id.

Artifact Registry

• list_artifact_repositories(location, project_id) — the repositories in a location, with their format (Docker, etc.).
• list_artifact_images(repository, location, project_id) — the Docker images in a repository with their tags (first 20).
• delete_artifact_version(package, version, repository, location, project_id) — write. Deletes one image version — targeted registry cleanup, not a bulk purge.

Scope by design

enoki never deploys a function or pushes an image — deploying needs a source upload and build, which is exactly the free-form surface the Guardrails forbid. It reports what built and stored, retries a failed build, and cleans up a version — bounded, typed actions, each write bound to the exact plan you approve.

Next: Guardrails.