Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/superpowers/plans/2026-05-26-web-api-communication.md`:
- Around line 486-489: The markdown code fence containing the two-path snippet
("apps/web/app/api/" and "apps/api/openapi.json") is unlabeled and triggers
MD040; update that fence to specify a language label (use "text") so the block
becomes a fenced code block with ```text at the start and ``` at the end,
preserving the existing lines inside exactly as shown; locate the unlabeled
fence around the snippet and add the language token to fix the markdownlint
warning.

In `@docs/superpowers/specs/2026-05-26-web-api-communication-design.md`:
- Line 5: Update the design status line "Status: Approved (design);
implementation pending" to indicate implementation is complete by replacing it
with a clear implemented state (e.g., "Status: Implemented" or "Status:
Implemented — [YYYY-MM-DD]") and optionally add an explicit implementation date
or state transition note so the document reflects the delivered implementation;
look for the exact phrase "Status: Approved (design); implementation pending" in
the document and modify it accordingly.
- Around line 75-89: The fenced architecture block that begins with the line
"NestJS controllers + `@nestjs/swagger` decorators" is missing a language tag;
update the opening fence from ``` to ```text (and keep the closing fence as ```)
so the block is marked as plain text to satisfy markdownlint MD040.

---

Nitpick comments:
In `@apps/api/src/entrypoints/tests/generate-open-api.e2e.test.ts`:
- Around line 36-43: The test currently only asserts property names on the
OpenAPI schema for 'GetApiInfoResponse' (variable schema) but doesn't assert
which fields are required; update the test to also assert schema.required
contains the exact required field names (e.g.,
['commit','name','nodeEnv','uptimeSeconds','version']) so the contract fails if
any field becomes optional. Locate the assertion block around the schema
variable in generate-open-api.e2e.test.ts and add a check that schema.required
(sorted) strictly equals the expected required fields.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/web/.claude/CLAUDE.md`:
- Line 100: The example in the useFetch invocation incorrectly references a
non-existent local identifier apiBase; update the example to call
useRuntimeConfig().public.apiBase instead so the baseURL is read from runtime
config. Locate the useFetch example (symbol: useFetch<T>('/v1/...', { baseURL:
apiBase, transform })) and replace the baseURL value with
useRuntimeConfig().public.apiBase, ensuring the example imports or assumes
useRuntimeConfig is available in component scope.
- Line 102: The documentation incorrectly states that useAPI is a createUseFetch
instance bound to $api; locate the section referencing useAPI/createUseFetch in
CLAUDE.md and update it to reflect the actual implementation: note that
apps/web/app/plugins/api.ts exposes $api via $fetch.create and that there is no
useAPI or createUseFetch in the repo today — either remove the createUseFetch
claim, mark useAPI as a future/optional idea (not implemented), or reword to
explain that $api exists but no useAPI helper is provided; reference the symbols
useAPI, createUseFetch, $api, and apps/web/app/plugins/api.ts when making the
edit.

---

Nitpick comments:
In `@apps/web/.claude/CLAUDE.md`:
- Around line 63-69: The generated types/schemas (e.g. GetApiInfoResponse,
zGetApiInfoResponse from openapi.json) include the full path prefix
"/api/v1/...", but runtime calls use the $api fetch instance which already
applies apiBase (so call sites should use "/v1/..." not "/api/v1/..."); update
the documentation to explicitly state this mismatch and instruct developers to
omit the "/api" prefix when calling $api (and to continue validating responses
with the generated Zod schemas in transform), and mention $api and apiBase by
name so readers can find the fetch plugin and the generated schemas.