docs: refresh audience platform reference fixture

Merged
SI
1mo ago
+1-1

API #1082 is merged as 7d5c98f7bde08773765d7605109600363c918b89. Its audience validation accepts the existing 14 names, trims whitespace, defaults omitted/blank inputs to Instagram and rejects invalid names before authentication, artist resolution, credit checks or research dispatch. Refresh the source hash for that coordinated public research reference in the existing shared documentation fixture.

This branch is rebased onto that actual API merge at exact head 5ac4e76720171386fd52be4946d4d4a384ed639d. Its one-value fixture patch is byte-identical to the previously accepted candidate; runtime, schemas, example bodies and every other fixture field remain unchanged. Both fixture copies match. Fresh 171 contract tests/19 files, response type checking, lint, formatting and whitespace pass. Independent Spec/Standards each report zero findings. All current-head required CI and preview checks pass, including the full unit run and response-contract type check. GitHub reports MERGEABLE/CLEAN with zero unresolved review threads.

Under Mono #358 / original API #644. Coordinator owns acceptance and release. After this actual fixture merge, Marketing #215 must pin the accepted API source; Docs #396 then refreshes from Marketing's actual merge. Normal publication readback follows each release. This does not establish hosted data coverage/commercial activation or original PR closure. No customer/provider/database/credit/credential/authentication or manual deployment operation occurred.


Summary by cubic

Refreshes the research.json source hash in the published docs fixture so it matches the audience API contract, which now validates the platform field against the 14 supported names and returns a 400 for unknown values instead of accepting arbitrary strings.

This changes one hash value; executable API behavior, schemas, example bodies, and all other fixture fields are unchanged.