docs: explain recorded workflow tool counts
A reader reviewing account usage or admin credit events is told that tool_call_count counts calls “in this step”. The released main workflow records top-level tool entries in the accumulated assistant reply, including pending/failed requests and entries retained after a resume. Update both descriptions so integrations can interpret that number correctly.
Only those two descriptions are authored. The wording excludes nested subagent entries, distinguishes a reply snapshot from successful executions or new work after resume, qualifies an omitted count defaulting to zero and preserves historical records. Existing types, nullability, examples, required lists, operations, prices and charges stay unchanged. Generated fixture/inventory/complete-AI files follow the source; only two of 213 complete-AI operation sections change and the other 211 are exact. Song, metadata, Slack, audience, Context, catalog, navigation, manifest and host settings are preserved.
Released runtime: API #1091, actual 06ceed29ece8bb2155e1861fc01ed538396dadc6. Released fixture: API #1092, actual 0428bdedf6798a628e08f37f8095b28216fe8228. Both actual merge trees equal their accepted source. The inventory now pins actual API #1092; both fixtures are byte-identical. The final delta from prior accepted 67dc1b9e0986355c31884d2dfd53c8f4bad4736a changes only that API revision reference.
Validation: inventory and fixture checks, 28 producer tests, documentation generation/check, 506 Marketing tests, normal production build before commit and whitespace pass. Full-source and final-delta independent Spec and Standards reviews report zero findings. Current CI and Vercel preview pass at db877c8b419c2ffe96923d175d72da3c155c16d1, with no unresolved review threads. Actual API #1092 merge test and compatibility checks also pass.
Ready for Records/coordinator acceptance and guarded merge. Docs does not merge. Retained Docs follows the actual Marketing merge, preserving Docs #399 and host settings, then independent review/check/CI/acceptance and normal changed-content publication readback. No live database, workflow, provider/customer or billing operation, historical correction or original-ticket closure is inferred.
Summary by cubic
Clarifies the tool_call_count field descriptions in the account and admin usage API docs so owners and admins don't misread the value as tool calls made in a single step. The count covers tool entries in the accumulated assistant reply, including pending and failed requests and entries retained when a reply resumes, and excludes nested subagent entries. A zero count may reflect a writer default rather than proof that no tools were requested, older events retain their previously recorded counts, and the field does not affect credit or charge calculation.
Only the two descriptions in accounts.json are authored; llms-full.txt and the fixture source hashes in example-cases.json and operation-inventory.json are regenerated to stay in sync with the pinned released source.