docs: align valuation history wording fixture hash
The coordinated Docs33 correction removes an unsupported guarantee that every valuation run persists history and corrects two account-targeting descriptions to match the already documented account_id and existing handler behavior.
Update only the releases OpenAPI source hash in lib/contracts/fixtures/published-docs.json to 6294c1dfb36539d3279a2d4ae8b1f650dfcaf81f2611f44a5dfb928c3b141e22. The full API fixture is byte-identical to the corrected Docs example fixture (SHA256 2149e39d89f7b7a9ed9b4b1170ed377032e1dc8f80d894e94b06cb1a17a8667e). Examples, schemas, authorization policy, production behavior and other hashes are unchanged.
Validation: original paired checker fails before the hash update and passes afterward; 296 existing published-fixture tests across 25 suites pass; formatting and diff checks pass. Independent review PASS. JSON metadata only.
Related to recoupable/mono#326 and recoupable/mono#360. Draft for coordinated review only. No merge, deployment, hosted validation or global Docs pin promotion. Docs owner separately assesses the full inventory delta before selecting a new global API pin. Native acceptance and release ordering remain unchanged.
Summary by cubic
Updates the published Docs fixture hash for releases.json so the paired documentation-fixture checker passes after a coordinated Docs correction removed the guarantee that every valuation run persists history.
No TypeScript source, contracts, or other hashes change; only the metadata entry in lib/contracts/fixtures/published-docs.json is updated to match the corrected Docs source.