Fix the Sone 2 documentation build

[sopenlaz0]

Summary

The documentation still referenced Sone 1.4 and the removed dist/node.d.mts declaration after the Sone 2 migration.

This updates the dependency and API generator, and fixes four incomplete entries that prevented type-checking. Lockfile and generated API changes are mechanical.

Validation

• Documentation install, API generation, type-checking, and production build passed
• Autoreview completed with no actionable findings

[vercel]

@sopenlaz0 is attempting to deploy a commit to the Seanghay Yath's projects Team on Vercel.

A member of the Team first needs to authorize it.

[sopenlaz0]

Review notes:

• .github/workflows/tests.yaml: keep pull_request.types including synchronize—that event is what gives fork PRs CI on updates. Scope the other trigger instead:

  push:
    branches: [main]

  This avoids redundant branch-push runs while retaining CI coverage when fork PRs update.

• src/index.ts:102 now contradicts the docs this PR ships. Low severity.

  CanvasKit has no system fonts, so at least one font must be registered before rendering any text.

  That's the 1.x rule that the README and fonts.mdx correctly stop asserting here. Since core.ts JSDoc is already being edited, this is worth the one-line fix.

Nits (non-blocking):

• npm ci --prefix docs alone doesn't install Sone's runtime dependencies (skia, yoga-layout, etc.). Because file:.. symlinks the root package, it relies on root node_modules and dist already existing. CI and the existing vercel-build script both perform the root install/build first, so this is correct as shipped; it is just an unstated ordering requirement for contributors. I specifically tested whether this creates release-blocking lockfile coupling by adding and bumping root dependencies, then rerunning npm ci --prefix docs; it does not—npm doesn't validate the linked .. snapshot.
• Rewriting the dated 1.4 blog post's “What's next” section as “What changed in 2.0” is a little revisionist when the version banner already provides that context. Your call.

[seanghay]

please make the changes small. and please dont modify the workflows

[sopenlaz0]

Understood — I’ll revert the workflow changes and keep the PR focused. Thanks.