Migrate Commet v7 to v8

Use the versioned changelog as the boundary definition: https://commet.co/changelog/offers-and-pricing

This skill sequences the migration. It does not duplicate the changelog's method, field, route, error, or webhook inventory.

1. Confirm the boundary

Inspect dependency manifests, lockfiles, imports, client initialization, exported Commet types, raw REST requests, webhook handlers, CLI use, and explicit API or webhook pins across Node, Python, Go, Java, and PHP project files.

Confirm that the active integration is on the v7 to v8 boundary. If it is older, apply earlier migration guidance first. If it is already newer, do not force this migration onto it.

2. Install and read the target contract

Upgrade only the active language SDK to its v8 major using that ecosystem's package manager. Resolve docs/manifest.json from the installed target artifact, read its entrypoint, and use its generated reference and types for every replacement.

When Node is present, run commet doctor --output agent after installing and resolve failed package, documentation, compatibility, API-version, or project-context checks.