take the release version from the tag

Publishing a GitHub release with the tag v<version> is enough to release:
the release check takes the version from the tag (instead of requiring
package.json to match it), npm, JSR and the docs are built with it, and
for regular releases a final job commits it to the default branch on top
of whatever was merged since, so package.json there shows the latest
release. Prereleases and fixes for older majors leave the branch alone.

scripts/version.js sets the version and keeps its copies (jsr.json,
src/version.ts) in sync; the build and `npm version` use it too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ljnxm1Qjrocq1izGajLx8J

credit third party code

the slice-by-16 crc32 comes from Arjun Barrett's gist, parts of the JPEG
codec are translated from libjpeg (IJG) and follow pdf.js' decoder, the
glyph rasterizer is translated from font-rs. THIRD_PARTY_NOTICES.md lists
them with their licenses (full Apache-2.0 text and libjpeg's README in
licenses/), the derived files say so in /*! */ headers that survive the
build, which used to strip fflate's notice from dist

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ljnxm1Qjrocq1izGajLx8J

chore: bump version

1.3.1

refactor: adjust flip test for deno

1.3.0

1.2.18

1.2.17

fix(license): clarify dual licensing use

1.2.16