release(v4.0.0): Shade GA — V3.x consolidation + audit prep

V3.1 → V3.12 consolidated and tagged for the first GA release. Wire
format unchanged from 0.4.x — 4.0 peers interoperate with 0.4.x peers
byte-for-byte. The version bump is semantic: audit-cycle complete,
opt-in surface fully exposed, threat model refreshed for every new
surface.

Highlights:
- All 24 @shade/* packages bumped to 4.0.0 in lockstep.
- CHANGELOG 4.0.0 section is the canonical manifest of what landed.
- THREAT-MODEL extended (§10 fingerprint gates, §11 WebRTC P2P, §12
  Web-Worker boundary) + residual-risks table refreshed.
- OpenAPI now covers all 27 routes: prekey, transfer, KT, inbox,
  bridge, observer, /metrics, /healthz, /ready.
- MIGRATION 0.3.x → 4.0 documented + smoke-tested against
  shade migrate-storage on a real SQLite DB.
- docs/audit/REVIEW-BUNDLE.md + SCOPE.md ready for external reviewer.
- scripts/soak.ts harness for the GA-stable 2-week soak window.
- All V*.md plans archived under docs/archive/ with Status: Done.
- Voice/Video carved out into V5.0; 4.0 audit focuses on the frozen
  non-realtime stack.

Tests: TS 1000/1000 + Kotlin 11/11 cross-platform vectors green.
Docker: gt.zyon.no/stian/shade-prekey:4.0.0 builds and reports
  version 4.0.0 on /health.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

packages/shade-dashboard/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shade/dashboard",
-  "version": "0.3.0",
+  "version": "4.0.0",
   "type": "module",
   "scripts": {
     "dev": "vite",

packages/shade-dashboard/src/stubs/bun-sqlite.ts

@@ -0,0 +1,12 @@
+// Browser-build stub for `bun:sqlite`. The dashboard never instantiates a
+// SQLite database — it talks to the prekey server over HTTP. Importing
+// transitive code paths from `@shade/storage-sqlite` is fine; calling
+// `new Database(...)` would throw, but the dashboard does not.
+
+export class Database {
+  constructor() {
+    throw new Error(
+      'bun:sqlite is not available in the dashboard browser bundle. The dashboard talks to the prekey server over HTTP — instantiating a SQLite database here is a bug.',
+    );
+  }
+}

packages/shade-dashboard/vite.config.ts

@@ -1,9 +1,22 @@
 import { defineConfig } from 'vite';
 import react from '@vitejs/plugin-react';
+import { resolve } from 'node:path';
 
+// `@shade/widgets` re-exports from `@shade/sdk`, which transitively imports
+// `@shade/storage-sqlite` (and therefore `bun:sqlite`). Vite externalizes
+// `bun:sqlite` for browser builds, but the `import { Database } from
+// 'bun:sqlite'` named-import then fails to resolve. Alias the module to an
+// in-tree stub — the dashboard never executes the storage code path
+// (it talks to the prekey server via `Shade.send` / `fetch`), so the stub
+// is never reached at runtime.
 export default defineConfig({
   plugins: [react()],
   base: '/dashboard/',
+  resolve: {
+    alias: {
+      'bun:sqlite': resolve(__dirname, 'src/stubs/bun-sqlite.ts'),
+    },
+  },
   build: {
     outDir: 'dist',
     emptyOutDir: true,