docs: refresh Slack webhook response contract fixture

Merged
SI
1mo ago
+1-1

The Content Agent webhook reference omits Slack signature/timestamp headers and rejected setup responses, and describes ordinary event acknowledgement as JSON {ok: true}. Its coordinated Marketing #216 correction documents verified JSON setup challenges, plain-text event acknowledgement and signature rejection messages; this changes the content specification’s source hash.

Refresh only that one hash in the existing shared documentation fixture. Runtime, schemas, example bodies and all other fixture fields are unchanged. Both fixture copies are byte-identical. The companion patch is identical before and after its refresh onto actual API #1084 merge b10c117bbe206cc346d4a2539b1e11e6f1b39c2d, whose whole tree matches the accepted runtime candidate.

Validation: 171 API contract tests/19 files, response type checking, required lint, fixture formatting and whitespace pass. Independent Spec and Standards reviews both report zero findings for exact head 62e6b6779c7c3a91c84e24f9ec965daa95b767d8. Current-head test/format/lint/compatibility CI and Vercel preview pass; no unresolved current review threads. Ready for Records/coordinator acceptance and guarded merge. Docs does not merge this PR.

Dependency order: after this actual merge, refresh/review Marketing #216’s inventory pin from that actual API source, then refresh/review Docs #397 provenance from actual Marketing. Their final pins and normal public readback remain outstanding. Preserve audience14, Context/catalog, other/internal webhook classifications and existing credentials. Original recoupable/api#297 / recoupable/mono#358 startup and live Slack acceptance remain separate; source checks establish no configured-app delivery, provider/customer operation or manual deployment.


Summary by cubic

Refreshes the content.json source hash in lib/contracts/fixtures/published-docs.json so the fixture matches the corrected Slack webhook reference, which now documents the signature/timestamp headers, setup 401 response, and plain-text ok acknowledgement. Only that one hash changes; runtime behavior, schemas, and all other fixture fields are untouched.