docs: refresh recorded tool count contract hash
The released main workflow records a tool count for the accumulated assistant reply. The two public usage fields still describe that number as calls “in this step”, which can mislead readers about pending/failed requests and resumed replies.
This fixture-only companion refreshes the accounts specification source hash for the two corrected descriptions in Marketing #219. The wording describes all top-level tool entries in the accumulated reply, including pending/failed and retained resumed entries, excludes nested subagent entries, and qualifies omitted-count defaults and historical records. It does not change field types, nullability, examples, operations, billing or runtime code.
Runtime API #1091 is merged as 06ceed29ece8bb2155e1861fc01ed538396dadc6; its entire tree matches accepted 9364e765d5b38b51fed75dd2801c396cdccc5616. This candidate is based on that actual merge. The API and Marketing fixtures are byte-identical; only the accounts source hash changes.
Validation: 186 contract and account/admin usage tests, response-contract typecheck, lint, fixture formatting and whitespace pass. Independent Spec and Standards reviews report zero findings at 84085be6ae6c88fd7a374d567db86ef5c54fd214 and Marketing 67dc1b9e0986355c31884d2dfd53c8f4bad4736a. Current API CI and preview checks pass, with no unresolved review threads.
Ready for Records/coordinator acceptance and guarded merge. After actual merge, Marketing must refresh its API source pin and pass the narrow review/check/build gates; retained Docs follows actual Marketing. Docs does not merge. No live workflow/database/provider/customer/charge operation, historical backfill or original-ticket closure is established by this fixture-only change.
Summary by cubic
Updates the accounts.json source hash in the shared published-docs fixture to match the corrected tool call count contract documentation from API #1091. No runtime code changes; all 186 tests pass.