docs: publish nullable song metadata reference

Merged
SI
2d ago
+33-15

An integration checking GET /api/songs against the published schema can reject a valid result when name, album or notes is null. Publish the retained copy of the released Marketing correction, which explicitly permits those three existing null values and explains unavailable information. API behavior and caller code are unchanged; this does not fill or backfill song data.

Generated from actual Marketing #218 ab87d89355f4d3ce55a43d90e2cea1dc9d9a8a9a, whose complete tree matches accepted 9bfeb1c587a2207630e9da5b46810f0d4311f5f5. It follows actual Docs #398 74f46f4d1d04d858949167b9e307b915b9f50370. All 241 file bytes/hashes match that actual source. Only releases.json and the complete AI file change among managed files; provenance records the actual Marketing commit. The other 239 copied hashes, navigation and entire host configuration are unchanged. Other release operations, schema fields, components and required lists remain unchanged; metadata-only, Slack, audience, Context and catalog contracts are preserved.

Validation: the actual-source checker verifies all 241 files and navigation; whitespace passes and the worktree is clean after commit. The complete AI file matches source byte-for-byte (SHA-256 3f96a73da5672d69dfd5c3bbe7e69abfba0bb092c88413b721d2dc7cea390b60). Prior authored-source checks/build/full and reference-delta reviews carry through exact Marketing tree identity. Independent Spec and Standards reviews of this exact retained copy each found zero issues. Current-head source CI and CodeRabbit pass; there are no unresolved review threads. Ready for Records/coordinator acceptance and guarded merge. Draft Mintlify SKIPPED is not retained-host publication.

Records/coordinator owns acceptance and guarded merge; Docs does not merge or deploy manually. Normal website Song publication passes five ordinary public GET checks. Offline saved-corpus comparison matches all 238 complete documentation bodies and 213 ordered complete operation sections, with only declared URL/whitespace/title normalization; the individual Songs Markdown schema exactly matches actual source. Retained publication follows actual Docs merge. Already-accepted metadata/Slack/audience publication checks are not repeated. No provider/customer/database operation, authentication/access change, backfill, full Song-response reconciliation, capture reliability or original #687/Mono #358 closure is implied. The earlier specification-link suspicion was disproved; no wrapper change is included.

Summary by cubic

Publishes the retained Marketing correction for the song metadata reference so the published GET /api/songs schema explicitly permits null for name, album, and notes.

An integration validating responses against the published schema could previously reject a valid result when those fields were null. The schema now declares ["string", "null"] for each and describes the value as null when unavailable. API behavior and caller code are unchanged; this does not fill or backfill song data.

  • Updates SOURCE-PROVENANCE.json, api-reference/openapi/releases.json, and llms-full.txt; all copied file hashes match the actual Marketing source.
  • No other release operations, schema fields, components, or required lists change.