chore(compat): move the three stale reader rows to their newest published patch

[dobby-coder]

Closes #379.

Moves the three stale rows in COMPATIBILITY.md's reader list to the highest published patch of their line, and moves both gates' copies with them.

row	was	now
crates.io pg-core	0.6.3 0.5.10	0.6.5 0.5.10
npm @e4a/pg-wasm	0.6.1	0.6.5
npm @e4a/pg-js	2.3.3 1.11.0	2.4.0 1.11.0

0.5.10 and 1.11.0 are the highest in their lines and do not move. Each of the three is a replacement rather than an addition, as no_two_pinned_readers_share_a_minor_line requires. The "Checked against the registries" line reads 2026-08-31, re-measured today against crates.io and npm rather than copied from the issue body.

0.6.5 ships the deprecation

The issue asked for the comment in reader! to be re-checked rather than carried forward, and the claim in it has flipped. Published pg-core 0.6.5 does carry #[deprecated] on VERSION_V3 (pg-core-0.6.5/src/consts.rs:38 in the crates.io tarball); 0.6.3 carried none. So the two #[allow(deprecated)] the comment was written for are load bearing now instead of inert. Dropping the one on the import fails the build:

error: use of deprecated constant `pg_core::consts::VERSION_V3`: the name is one higher than the wire value it holds; use VERSION_2

The comment now records that instead of its opposite. 0.5.10 still contains no #[deprecated] at all, so in that module both allows stay inert.

WIRE_VERSION did not move: it is still 2 on both sides, and every reader opened every case it is meant to, so the moved versions speak the same container version.

Beyond the seven files the issue lists

Two JS tests name a reader by its id and would have thrown no reader configured the moment the pin moved: WASM_READER in test/gate-teeth.test.mjs, and the last assertion in test/manifest.test.mjs. The version literals in test/failures.test.mjs and the synthetic documents in support_window.rs and manifest.test.mjs are labels and fixtures rather than readers, so they are untouched.

Both gate READMEs name the pinned versions in their open-one-case command and in the reader table, so those follow the pins. One further line in pg-compat-js/README.md: its "adding a version" walkthrough used "pg-js-2-4-0": "npm:@e4a/pg-js@2.4.0" as the hypothetical, which this change turns into a real entry in package.json. It now reads 2.5.0, the way pg-compat/README.md uses an unpublished 0.7.0 for the same job. Revert that line if you would rather the example stayed as it was.

Testing

Both acceptance checks, against a sample set sealed by HEAD:

cargo test --manifest-path pg-compat/Cargo.toml --locked   # 18 passed
cd pg-compat-js && npm ci && npm test                      # 26 passed

Also green: cargo clippy --manifest-path pg-compat/Cargo.toml --all-targets --locked -- -D warnings, cargo fmt --check on pg-compat, and the pg-core, pg-pkg, pg-cli and pg-ffi suites as CI runs them.

Both lockfiles were regenerated by building (cargo check, npm install), not hand-edited.

Reviewed by dobby: the code-comments rule over the full diff (no breach — the only comment touched is the reader! deprecation rewrite, which records a live constraint in an already densely commented file), plus a correctness pass over all 11 files — cargo test --workspace --locked 394 passed, pg-compat 18 passed, pg-compat-js 26 passed, clippy -D warnings and cargo fmt --check clean — approve, with the two findings fixed in this PR at 948ad99.
Fixed: pg-compat-js/src/readers.mjs:61 — installedPackage's doc comment used pg-js-2-4-0 as a hypothetical alias, which this PR turns into a live entry resolving to the opposite package; moved to 2.5.0/pg-js-2-5-0, the second occurrence of the collision the body already caught for README.md.
Fixed: pg-compat-js/package-lock.json — npm install had left the hoisted transitive @e4a/pg-wasm at 0.6.1 (both pg-js readers declare ^0.6.1), so the two @e4a/pg-js legs unsealed through a version the reader list no longer declares while a fresh @e4a/pg-js@2.4.0 install gets 0.6.5; npm update @e4a/pg-wasm moves it, lockfile only, and the gate still opens every case.
Attention: nothing pins or asserts that hoisted transitive, so the next pin move can silently re-split it — installedPackage() checks only the alias, and pg-compat-js/test/manifest.test.mjs compares only what it returns. Worth an overrides entry or one assertion there, in its own PR.