tsdevstack
Medium

v0.2.8

Released: April 25, 2026

MCP — deploy_kong follow-up hint after backend removal

After infra:remove-service on a backend service, Kong still holds stale routes pointing at the deleted service until the next Kong deploy. The CLI command deliberately doesn't redeploy Kong (single-responsibility principle), so the MCP layer is where the follow-up is surfaced — the remove_service_cloud tool description now tells agents to suggest deploy_kong with the same env afterwards.

GCP cloud-secrets remove — structural parity with AWS / Azure

Extracted the inline GCP implementation out of the command file into dedicated utility files (utils/gcp/remove-secret.ts + utils/gcp/remove-secret-by-name.ts) matching the AWS / Azure structure, with matching unit tests.

Doc cleanups

  • SchedulerGuard class docstring no longer claims AWS / Azure are "not yet implemented" (both have shipped with shared-secret validation since v0.1.x).