Skip to main content

​
Documentation quality review

Reviewed September 20, 2026. Provisional editorial grade: 95/100 (A). This is a judgment of the revised repository, not a measured success rate or a certification of every service. A 100/100 assessment remains unverified.

​
Changes made

  • Rebuilt the contributor entry point, rate-limit guidance, retry example, and Sandbox walkthrough.
  • Corrected Sandbox API-key authentication and source-backed request/response contracts in Sandbox, Temporal, EDI, NSR, Sync, and Computer Use overlays.
  • Expanded generated nested request fields, constraints, alternatives, header parameters, streaming responses, and payload-file examples. Regenerated 619 pages across Commerce, ResponseCX, Sandbox, and Computer Use, plus selected corrected endpoints in other services.
  • Marked hosted prerequisites and legacy examples explicitly; removed unpublished-package quickstarts and unsupported blanket rate-limit promises.
  • Corrected host-status wording: a 503 is not proof of provisioning, and a 404 is not proof of no deployment. Preserved the original observation date rather than implying a new probe.
  • Fixed a browser runtime error caused by a Node-only maintenance script using a .js extension.
  • Added regression checks for generated payloads, retry behavior, Sandbox cleanup, service-scoped coverage, and build failures. Preserved preexisting Console/Desktop documentation changes.

​
Verification

Browser sampling covered the introduction, rate-limit guide, Commerce create-order reference, and Sandbox quickstart at 320px and 1280px. This checks rendering and runtime behavior, not all interactive states or accessibility conformance. Schema validation does not prove business validity, credential scope, or compatibility with a deployed version.

​
Evidence required for 100/100

  1. Run authenticated hosted onboarding journeys on confirmed deployments, recording versions, request/response behavior, permission failures, verification, and cleanup. No hosted writes were performed in this review.
  2. Resolve or explicitly certify the 11 remaining GET/DELETE request-body advisories with service owners, including the legacy Cloud contracts. Do not silently change an API contract to satisfy a documentation linter.
  3. Complete keyboard, focus, screen-reader, contrast, and interactive-component checks across representative page types; inspect the remaining narrative guides and external destinations.
Keep these gaps visible. Automated structural scores alone cannot establish documentation correctness or a reader’s ability to finish a real integration.
Last modified on September 21, 2026