[benbrandt]

Summary

Restore a consistent last-published baseline after the failed 2.0.0 npm publication and subsequent deletion of its GitHub release/tag.

• Reset package.json, both root version fields in package-lock.json, and .release-please-manifest.json from 2.0.0 to the actually published 1.9.0.
• Remove the unpublished 2.0.0 changelog section so the bot can regenerate it without a duplicate entry.
• Preserve all SDK changes, dependency fixes, migration guidance, and the publishing fix from ci: fix npm 12 package checks and simplify publishing #297. No CI, workflow, dependency-graph, schema, or runtime changes.

This is release bookkeeping, not a proposal to publish the current code as 1.9.0 or to roll back the SDK changes.

Why

Release Please run 39319396548 reports:

No latest release found for path: ., component: , but a previous version (2.0.0) was specified in the manifest.

It then opened #298 as release 1.0.0, with historical release notes. Do not merge #298 in that state. npm still reports latest: 1.9.0, and the v1.9.0 GitHub release/tag still exists.

After merging this reset, inspect the regenerated release PR before taking any release action: it should propose 2.0.0, compare from v1.9.0, retain the correct breaking-change notes, and include the publishing fix. Actual regeneration has not been verified yet; it depends on the reset reaching main. Do not merge a regenerated proposal if those checks fail.

Validation

• All four version markers agree on 1.9.0.
• Lockfile dependency graph unchanged; existing published changelog history is byte-for-byte unchanged.
• CI=true npm run check: 488 tests, generation verification, lint, formatting, spellcheck, typecheck, production build, package validation, and all four TypeDoc verification profiles passed.
• git diff --check passed.
• Verified no changes under src, schema, or .github/workflows.

No tags/releases were changed, no workflows were retriggered, and nothing was merged or published by this work.