[sanjevirau]

Prepares 0.2.5, as PUBLISHING.md's "Subsequent releases" step 1 asks. Nothing is published from this PR.

What changes

File	Change
packages/cli/package.json	The CLI and its five native packages: 0.2.4 → 0.2.5
server.json	The MCP Registry entry's two versions: 0.2.5
packages/cli/release.json	engineRevision → 6683b3edb53941a8e7fd34b89a45855b9fff0b50, main after every 0.2.5 pull request merged (the merge of #248). Rust stays 1.100.0.
packaging/CHANGELOG.md	The 0.2.5 section

Tested on the pinned engine

On main at 6683b3ed:

Check	Run	Result
CI	43582162294	passed, CI result included, 12.5 min
Five-platform packed install	43582162275	6 of 6 jobs passed: linux-x64, linux-arm64, darwin-arm64, darwin-x64, win32-x64 and the artifact check
Real SDK clients: Android, iOS (fresh and kept cache) and the web	43582182279	4 of 4 passed, 30.1 min

The conformance record: 6,791 recorded answers in 43 sets; 6,439 compared exactly, 351 compared and different on purpose, and 1 listed under #247. In 0.2.4, 26 were listed (#229).

This is the first release under #245: since this PR differs from the pinned commit only in the release's own fields, its CI, packed-install and SDK-client checks link the runs above instead of running them again, and so will the release run's quality job. The release run still builds, tests and installs all five platforms from a clean checkout.

0.2.5 in short

• Firestore: a transaction's queries are checked at commit, so two transactions that find nothing no longer both create (Firestore: a transactional query that matches nothing is not conflict-checked at commit, so two transactions both insert #235).
• Security Rules: compile errors answered as the official emulator answers them, every problem after the first included, 119 of 120 recorded (Rules reload: 26 compile errors still answered otherwise than the official emulator #229); warnings logged as the official CLI logs them, and at start too.
• Storage: a download token the Admin SDK names is kept (Storage object does not use download tag assigned with Admin SDK #221).
• Start after a crash: no four-second wait on Windows (Windows: emulators:start takes about 4 s to open the Firestore port, the engine alone 47 ms #181).
• The release check asks firenook.dev and is counted by version and platform only (Count active installs through the update check on firenook.dev #240); DO_NOT_TRACK=1 turns it off.
• No data format changed.

After this merges (release owner)

1. Create the annotated tag npm-v0.2.5 at the merge commit.
2. Dispatch Reviewed npm release on main with that tag, latest on, as 0.2.4 was.
3. Approve the npm-release environment after reviewing the artifacts.
4. npm dist-tag add firenook@0.2.5 next.

🤖 Generated with Claude Code

https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g