From fe345a98bf8db6f7eee0b973ee8918f68fccf49c Mon Sep 17 00:00:00 2001 From: John McLear Date: Fri, 8 May 2026 16:05:19 +0100 Subject: [PATCH] docs(admin): fix stale "Section 3" reference in spec (#7693) Drafting numbered the design walkthrough; final spec uses titled sections. Update the back-reference accordingly. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../specs/2026-05-08-issue-7693-admin-openapi-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/superpowers/specs/2026-05-08-issue-7693-admin-openapi-design.md b/docs/superpowers/specs/2026-05-08-issue-7693-admin-openapi-design.md index 91e211996..3e7868742 100644 --- a/docs/superpowers/specs/2026-05-08-issue-7693-admin-openapi-design.md +++ b/docs/superpowers/specs/2026-05-08-issue-7693-admin-openapi-design.md @@ -66,7 +66,7 @@ module. ### Why merge in `dump-spec.ts` rather than at `openapi-typescript` time `openapi-typescript` only accepts one input. We could run it twice and emit -two `.d.ts` files, but the chosen design (Section 3, codegen) is a single +two `.d.ts` files, but the chosen design (see "Codegen merge" below) is a single merged `schema.d.ts` so the admin UI's `$api` instance has one `paths` interface covering both surfaces. The merge therefore happens at JSON-dump time, before `openapi-typescript` runs.