chore(release): v1.0.0

[wizzomafizzo]

Prepares the first stable release.

Changes

• Bump package.json from 0.1.1-dev.21 to 1.0.0.
• Consolidate the Unreleased and never-tagged 0.1.0 changelog sections into a single 1.0.0 entry, with compare links.
• Mark pre-release tags as pre-releases in the release workflow.

Why the pre-release guard

The README tells users to install from releases/latest/download/Zaparoo.zip. Without an explicit flag, pushing a v1.1.0-rc.1 tag would create a release that GitHub promotes to latest, silently serving a release candidate to every manual installer. Tags containing a hyphen now get --prerelease; plain vX.Y.Z tags get --latest.

Validation

• pnpm check - 91 frontend tests, 71 backend tests, pyright, ruff, build. All pass.
• pnpm package - produces out/Zaparoo-v1.0.0.zip with the expected 8-file Zaparoo/ layout.
• Tag-match guard verified: test "v1.0.0" = "v$(node --print "require('./package.json').version")" passes.
• Pre-release branch logic verified: v1.0.0 and v1.2.3 resolve to --latest, v1.0.0-rc.1 to --prerelease.
• Packaged package.json reports 1.0.0 and matches the backend PLUGIN_VERSION_PATTERN.

Tagging v1.0.0 after merge triggers the release workflow, which publishes the versioned ZIP plus the stable Zaparoo.zip asset.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 4 minutes

Limit details: You’ve used the included review currently available. Your 90 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 82f38c91-9ff0-42e2-9b43-87a33403798f

📥 Commits

Reviewing files that changed from the base of the PR and between b392f8a and 651bf9c.

📒 Files selected for processing (3)

• .github/workflows/release.yml
• CHANGELOG.md
• package.json

---

_{Comment @coderabbitai help to get the list of available commands.}