The README documented what algonaut does but never stated how it compares
to the reference SDK or what it is verified against, so a reader had no way
to judge coverage or find the gaps without reading the source.

Add a Compatibility section with two reference points:

- The cross-SDK algorand-sdk-testing acceptance suite: per-feature status
  for all 30 upstream features (13/13 integration, 5/17 unit), the 274/0
  fresh-harness result, and the rationale behind every skipped scenario.
- js-algorand-sdk v3.7.0: a surface-by-surface capability matrix across
  clients, transactions, signing, groups/ABI, and tooling.

Gaps are stated explicitly rather than omitted — algod 5.0 / Falcon-1024
post-quantum accounts and resource access lists, TEAL signing, ufixedNxM
and anonymous tuples in contract! (#345), the 12 unit features awaiting
step definitions, and the lack of a pluggable HTTP transport.

clippy 1.97 promotes `useless_borrows_in_formatting` to fire on
`write!(f, "{}", &BASE64.encode(..))`. CI pins `rust-toolchain@stable`,
so this fails the clippy job as runners pick up the new release, and it
already fails the pre-commit hook locally.

Updates the requirements on [vue-router](https://github.com/vuejs/router) to permit the latest version.
- [Release notes](https://github.com/vuejs/router/releases)
- [Commits](https://github.com/vuejs/router/compare/v5.2.0...v5.3.0)

---
updated-dependencies:
- dependency-name: vue-router
  dependency-version: 5.3.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Updates the requirements on [@vue/compiler-sfc](https://github.com/vuejs/core/tree/HEAD/packages/compiler-sfc) to permit the latest version.
- [Release notes](https://github.com/vuejs/core/releases)
- [Changelog](https://github.com/vuejs/core/blob/main/CHANGELOG.md)
- [Commits](https://github.com/vuejs/core/commits/v3.5.42/packages/compiler-sfc)

---
updated-dependencies:
- dependency-name: "@vue/compiler-sfc"
  dependency-version: 3.5.42
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

'share' in the header row, faint until hovered, brass on hover like every
button; '✓ copied' in signal for 1.2s once the link is on the clipboard —
the same readout Copyable gives.

A share glyph on a section's header POSTs the exchange — prompt, her reply,
its view blocks — to /api/share, which strips, hashes (sha256, 48 bits, the
preimage is everything the card displays), and stores it in KV for 90 days.
First write wins: an offline hash collision becomes a failed share, never a
hijack. /s/[hash] is a static server-rendered page — the exchange as a
poster, her line marked as shared, and one button into the Explorer with the
question prefilled — plus a Satori OG image on the brand palette, immutable
by content hash. Nothing from a payload ever enters a visitor's session or
the model's context; the visitor re-asks live.

The explorer routes move into an (explorer) route group so the share page
renders without the client-only shell, and both OG routes read vendored
JetBrains Mono (OFL) instead of scraping Google Fonts CSS per render.