feat(relay): rendezvous-relay service — 7 packages + plans (contracts/transport/agent/control-plane/e2e/auth/web)

Multi-tenant reverse-tunnel service ("ngrok for Claude Code" with E2E): a
host-agent dials OUT to an operator-run relay; external devices reach the host
THROUGH the relay, routed by per-tenant subdomain, forwarding ciphertext only
(the relay never sees plaintext). Lets a customer reach their own self-hosted
web-terminal from anywhere with zero networking setup.

Packages — all tsc-strict + vitest green (656 tests), cross-package integration verified:
- relay-contracts: frozen shared contracts (mux frame codec, data model,
  capability token, E2E envelope, pairing) — the src/types.ts analog
- term-relay:   native WS mux + stateless data plane (subdomain routing, ciphertext forward)
- agent:        host-agent (pairing, per-host Ed25519 + mTLS dial-out, forwards to 127.0.0.1:3000)
- control-plane: accounts/hosts registry, pairing-code flow, routing table, provisioning
- relay-e2e:    browser<->agent E2E (X25519 ECDH through relay, AEAD, anti-replay, recoverable replay key)
- relay-auth:   Passkey/WebAuthn, capability tokens, per-host certs, deny-by-default tenant isolation
- relay-web:    browser login + Web Crypto E2E + client-side preview rendering

Security invariants INV1-15 enforced; cross-tenant isolation CI tripwire live
(.github/workflows/relay-tripwire.yml). Design + implementation-level plans in
docs/PLAN_RELAY_*.md and docs/EXPLORE_RELAY_SERVICE.md.

NOTE: generated autonomously per the reviewed plans. The security-critical
packages (relay-e2e, relay-auth) REQUIRE expert security audit before any real
deployment — passing tests prove self-consistency, not resistance to attackers.
Base app (src/, public/) unchanged; concurrent desktop work left uncommitted.

control-plane/src/model/records.ts

@@ -0,0 +1,49 @@
+/**
+ * T2 — control-plane record types. The frozen §4.2/§4.5 shapes are RE-EXPORTED from
+ * relay-contracts, never redefined locally (INDEX §2 rule 1).
+ *
+ * OQ1 RESOLUTION: `AccountRecord`/`SessionRecord`/`PairingCodeRecord` were promoted into
+ * relay-contracts (`model/account.ts`, `pairing/enroll.ts`), so this module re-exports them
+ * instead of mirroring the SQL locally. The only P3-local additions are the INV8 companion
+ * status-version ROW types (OQ6 — pending INDEX promotion of the `*_status_versions` tables).
+ */
+export type {
+  AccountRecord,
+  AccountStatus,
+  SessionRecord,
+  HostRecord,
+  HostStatus,
+  PlanTier,
+  RouteEntry,
+} from 'relay-contracts'
+export type { PairingCodeRecord, EnrollResult } from 'relay-contracts'
+
+import type { AccountStatus, HostStatus } from 'relay-contracts'
+
+/** Append-only companion row for `accounts.status` versioning (INV8, OQ6). */
+export interface AccountStatusVersionRow {
+  readonly accountId: string
+  readonly version: number
+  readonly status: AccountStatus
+  readonly changedAt: string
+  readonly changedBy: string
+}
+
+/** Append-only companion row for `hosts.status`/`revoked_at` versioning (INV8, OQ6). */
+export interface HostStatusVersionRow {
+  readonly hostId: string
+  readonly version: number
+  readonly status: HostStatus
+  readonly revokedAt: string | null
+  readonly changedAt: string
+  readonly changedBy: string
+}
+
+/** Immutable metering sample row (append-only, INV8). */
+export interface MeteringSampleRow {
+  readonly hostId: string
+  readonly accountId: string
+  readonly nodeId: string
+  readonly concurrentViewers: number
+  readonly sampledAt: string
+}