docs: refresh nullable song metadata contract fixture

Merged
SI
1mo ago
+1-1

A client using the published Songs schema can reject a valid response when a song has no name, album or notes yet. The database types allow null for those fields, the selector passes them through unchanged, and GET /api/songs returns the selector result directly. Marketing #218 corrects those three existing response types; this PR updates only the matching releases.json hash in the shared fixture.

Both fixture copies match exactly. All other fixture values and examples are unchanged. API #1088 introduced no public route, request or response change; this is a confirmed pre-existing documentation mismatch found during its source inspection.

Validation: 177 existing contract/song-handler tests across 20 files, response-contract typecheck, required lint, fixture formatting and whitespace pass. Independent Spec and Standards reviews found zero issues at e8b68bb0454422f4d6b0a2b21e30ec578c7cf66f. Current required CI, CodeRabbit and Vercel checks pass, with no unresolved review threads. This candidate is ready for Records/coordinator acceptance; Docs does not merge.

Release order: merge this accepted fixture first, refresh Marketing #218 to the actual API merge commit and complete its final checks/review, then generate retained Docs from actual Marketing after Docs #398. The local built Songs page already shows the three nullable descriptions and the correct specification download link; no wrapper edit is needed.

This does not change API behavior, fill missing information, backfill songs, change captures or callers, verify a live database/provider/customer result, reconcile every Song response detail, or close original #687/Mono #358.


Summary by cubic

Refreshes the releases.json source hash in the shared published-docs fixture so the contract fixture reflects the nullable song metadata correction in the API docs.

Runtime API behavior is unchanged; only the fixture's recorded docs hash is updated.