Migrate Commet v8 to v9

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

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

1. Confirm the boundary

Inspect dependency manifests, lockfiles, imports, SDK calls, raw REST requests, webhook handlers, CLI use, explicit API or webhook pins, and every Offer or Market selection path across Node, Python, Go, Java, and PHP project files.

Confirm that the active integration is on the v8 to v9 boundary. Classify how each Offer is selected from existing behavior and persisted inputs; do not infer the selection channel from an Offer's phase shape.

2. Install and read the target contract

Upgrade only the active language SDK to its v9 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. Upgrade Node integration packages only to releases whose installed peer ranges support the selected @commet/node version.

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