Keep the sparq comparison in the README current as sparq evolves

[jeswr]

🤖 Opened by an agent on behalf of @jeswr (agent-assisted).

What

#1959 adds a > [!NOTE] banner at the top of the README pointing eye-js users at sparq. That notice carries several point-in-time facts about sparq that will drift as sparq evolves and need to stay accurate:

1. Bundle sizes — sparq's deployed reasoning wasm (measured ≈2.6 MB / ≈0.9 MB gzip on 2026-07-04) vs eye-js's ≈3.8 MB wasm + data / ≈4.1 MB bundle. sparq is actively shrinking its wasm (a release-wasm profile recently cut the raw build ~17%), so these numbers move.
2. DeepTaxonomy-1k benchmark — the notice quotes sparq (native Rust) ≈7 ms engine / ≈70 ms end-to-end vs eye-js (WASM build of EYE) ≈390 ms end-to-end. This is a native-vs-WASM comparison because sparq does not yet publish a WASM DeepTaxonomy timing. When sparq publishes a WASM DT number, the notice should switch to a true wasm-vs-wasm line. eye-js's own number should also be re-measured as its engine/build changes.
3. sparq's project state — currently described as "experimental, pre-1.0." Update as sparq approaches/ships a stable release, and as its shipped N3/SPARQL/SHACL feature set changes.

Relationship to #1960

#1960 is the narrow tracker for one specific line in the notice: swapping the general "npm package tracked in sparq-org/sparq#1499" pointer for a concrete npm install <name> + drop-in n3reasoner(...) snippet once that package publishes. That stays as-is.

This issue is the broader tracker: keep the notice's figures (bundle size, DT timings) and state (pre-1.0 → stable, feature set, native-vs-WASM framing) current as sparq changes. The two do not overlap — #1960 is blocked on the npm package shipping; this one is ongoing maintenance of the comparison.

Done when

• Bundle-size figures re-verified against sparq's current deployed/shipped artifacts
• DeepTaxonomy figures re-measured; switched to wasm-vs-wasm once sparq publishes a WASM DT timing
• sparq's state/feature description updated (e.g. once it ships a stable / 1.0 release)
• (via Update the sparq migration pointer in the README once the npm package ships #1960) migration npm package pointer made concrete once published

Refs #1959, #1960.