revenue-cloud-docs

Grep the Help snapshot under docs/salesforce/{release}/help/articles/ for the feature's key terms, read the matching article for full context, and confirm the claim matches the article wording. Cite the article ID from the snapshot frontmatter rather than guessing a URL.

Run the release-specific CCI task, for example cci task run snapshot_billing_help_264 -o mode discover, then run the full capture. The task uses Playwright with a shadow-DOM walker and writes per-article markdown plus a manifest.json index.

The Help snapshot covers admin and seller workflows like feature setup and configuration, while the Developer Guide snapshot covers object and field API names, Business APIs, Apex, Metadata types, and CML syntax. Ground developer claims against dev-guide and admin claims against help.

A zero count means either the root article ID is wrong or the sidebar walker failed before the SPA finished hydrating. Read the Discovered line in the task output: zero total before prefix filter indicates a bad root, while nonzero total with zero kept indicates a wrong prefix.

No, the capture task overwrites all article files on refresh. The only exception is a verified glued-link artifact, which requires updating the manifest body_length and total_captured_body_chars to stay consistent. Put annotations in sibling note files instead.

Neither snapshot documents usage runtime semantics such as drawdown order or what each bucket decrements. Establish those rules by live verification in an org, then record them in the data-model skill's usage domain notes.