Files
web-terminal/relay-web/src/errors.ts
Yaojia Wang 2af57e6686 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.
2026-07-02 06:10:16 +02:00

42 lines
1.3 KiB
TypeScript

/**
* relay-web local error taxonomy. Typed, explicit errors (coding-style.md "Error Handling")
* so callers never swallow failures or render partial objects.
*/
/** Base class for every relay-web boundary error. */
export class RelayWebError extends Error {
constructor(message: string) {
super(message)
this.name = 'RelayWebError'
}
}
/** Thrown by readConfig when the origin is not a valid tenant subdomain (fail-fast, T1). */
export class ConfigError extends RelayWebError {
constructor(message: string) {
super(message)
this.name = 'ConfigError'
}
}
/** Discriminated kinds for control-plane API failures (T2). */
export type ApiErrorKind =
| 'unauthenticated' // 401 — session missing/expired; surface re-login
| 'forbidden' // 403 — INV1/INV6 upstream denial (foreign host_id etc.)
| 'http' // other non-2xx
| 'parse' // response failed Zod validation (never return a torn object)
| 'network' // fetch itself rejected
/** Control-plane HTTP client error. `kind` drives the UI response (re-login, error banner, …). */
export class ApiError extends RelayWebError {
readonly kind: ApiErrorKind
readonly status: number | null
constructor(kind: ApiErrorKind, message: string, status: number | null = null) {
super(message)
this.name = 'ApiError'
this.kind = kind
this.status = status
}
}