From df37b95ff7ba8b9d98c9c72dd178c00589949e0f Mon Sep 17 00:00:00 2001 From: Hermes Date: Wed, 12 Aug 2026 07:23:54 -0700 Subject: [PATCH] DC-062: auto-claim (autonomous build pick tick) --- DC-PRODUCTION-GRADE-BACKLOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/DC-PRODUCTION-GRADE-BACKLOG.md b/DC-PRODUCTION-GRADE-BACKLOG.md index cf31ae8..e5ba39c 100644 --- a/DC-PRODUCTION-GRADE-BACKLOG.md +++ b/DC-PRODUCTION-GRADE-BACKLOG.md @@ -21,6 +21,7 @@ ### DC-062: OpenAPI spec is stale — update to match actual v1.15.0 API surface - **status:** pending +- **status:** in-progress (auto-claimed at 20260812T142348Z) - **details:** `openapi.yaml` says `version: 1.0.0` and describes only a fraction of the API. Since DC-046/047 (auth providers), DC-053 (share), DC-055 (billing), DC-058 (share UI), and the tailscale-admin routes were added, the spec is significantly out of date. A stale spec is worse than no spec — it misleads API consumers and breaks any code generation from it. Fix: audit all route files (`grep -rn 'router\.\(get\|post\|put\|delete\|patch\)' routes/`), update openapi.yaml with every endpoint, bump version to 1.15.0, add it to the test suite (DC-017-style source-of-truth test that fails if a route exists but has no spec entry). Effort: ~3 hr. - **impact:** Public API trust. No paying customer can integrate against an undocumented API.