chore: release server 0.8.65

[vivek7405]

Releases @webjsdev/server 0.8.65, carrying the #1423 elision fix.

What is in it

One user-facing change since 0.8.64, which is what commit_count: 1 in the changelog reflects:

• fix: a parenthesised type annotation no longer reads as a top-level call (fix: a parenthesised type annotation no longer reads as a top-level call #1424). A TypeScript type annotation like readonly (readonly [number, number, number])[] read as a top-level call to the elision analyser, so a module of pure typed data was classified as running code at module scope. Every route module importing such a helper was downgraded from inert to shipping whole, and a component carrying one was forced to ship along with the display-only children it renders. Silent: no error, no warning, identical behaviour, only bytes.

Why server only

ui is NOT due, and I want to record why, because my first pass said otherwise. I counted unreleased commits with git log --grep="chore: release <pkg>" to find each package's last release, which matched an OLD single-package release subject (chore: release ui 0.3.9, mcp 0.1.10, cli 0.10.43) rather than the current combined form (chore: release core 0.7.51, server 0.8.64 and ui 0.3.14). The range therefore started too far back and swept in already-released work. Reading the changelog files instead, which is what scripts/backfill-changelog.js does, ui has zero qualifying commits since 0.3.14 and core, cli, mcp, and intellisense are clean too.

Bump level and ranges

Patch, matching how this package is kept in a single minor line. Every in-repo dependent pins ^0.8.0 (packages/cli, packages/mcp, examples/blog, website, gallery), so a patch stays inside every caret and no dependent range needed editing. package-lock.json regenerated with npm install --package-lock-only.

@webjsdev/intellisense is not bumped, so the webjs.nvim vendored copy needs no re-vendor.

Changelog

changelog/server/0.8.65.md generated by the pre-commit hook, not hand-written. Merging this adds it to main, which triggers release.yml to npm publish and cut the GitHub Release (idempotent).