feat: add Stone Quarry gathering node

[ael-dev3]

Summary

• Add the Genesis Tier-I Stone Quarry gathering node as a Stone-only resource family.
• Pin the canonical 96-site heath catalog and policy digest 4d620da061b7a90d1e8e17e66dfabf8ef5d7907ee525caaa735dd766e1ab388e.
• Add server-owned public Stone sites and occupancy, private 30-day expeditions, scheduler lifecycle, one-Stone-per-minute awards, reservation caps, and owner-bound dispatch/claim reducers.
• Wire the generated bindings, player connection/provider state, Realm map scene, Three.js node layer, fallback markers, Stone inspection panel, and resource presentation budget.
• Refresh the Stone Quarry inspection art from the supplied reference as a 1254×1254 transparent WebP, with updated provenance, deterministic installer, and runtime integrity checks.
• Keep the existing Stone Quarry GLB runtime contract unchanged. The supplied LOD files already match the committed runtime assets, so this PR adds no duplicate binaries.

Safety and rollout

• Site selection, occupancy, timing, route costs, awards, and lifecycle transitions remain server-derived; browser inputs are identifiers or idempotency keys only.
• Public subscriptions expose site and occupancy projections, while expedition state and inventory remain owner-private.
• The Stone surface fails closed against pre-v9 deployments.
• No seed, deploy, merge, or production activation was performed.

Validation

• node_modules/.bin/tsx --test spacetimedb/tests/*.test.ts — 182 passed.
• node_modules/.bin/vitest run --reporter=dot — 181 files / 1,637 tests passed.
• Focused Stone record-art tests — 4 passed.
• scripts/verify-runtime-assets.mjs — 40 runtime assets and 4 provenance masters verified.
• Frontend and backend TypeScript checks passed.
• spacetime build --module-path spacetimedb passed.
• Generated binding verification passed.
• Exact Stone Quarry runtime LOD verification passed.
• Vite production build and git diff --check passed.

[ael-dev3]

Superseded by merged PR #72. The Stone Quarry feature was integrated with corrected canonical coordinates, cross-boundary catalog attestation, shared footprint checks, privacy tests, and guarded v10 rollout controls.