phase-0: foundation, both apps boot end to end

Monorepo (pnpm workspaces) with two deployable apps and three pure packages.

apps/api (Hono on Node): Zod validated env that fails fast and names the problem,
Kysely factories for SQLite and Postgres chosen by DATABASE_URL scheme, portable
migrations covering the whole SPEC section 5 schema, Better Auth with the four
roles and seeded demo accounts, localized error envelope, /healthz and /readyz,
graceful SIGTERM drain. Dialect specific SQL is confined to the two factories.

apps/web (Next.js App Router): locale routed shell in es and en with a language
switcher, sign in screen, and a runtime /api proxy so the browser only ever sees
one origin and cookies stay first party.

packages/i18n ships both catalogs complete; es is generated from COPY.md and a
test re-derives it from the document on every run so it cannot drift.
packages/contracts holds the Zod schemas and the typed client the web app uses.

Verified: 43 vitest tests, 14 Playwright tests on mobile and desktop, typecheck
and lint clean, migrate and seed from a clean database, sign in through the proxy
with CSRF rejection of foreign origins.

Not verified here: docker compose. This user has no access to the docker socket.

RULES.md is absent from docs/, so packages/rules exports only RULES_VERSION and
no tax rule, check digit or deadline was invented. See DECISIONS.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

apps/api/src/http/health.ts

@@ -0,0 +1,46 @@
+import { sql } from 'kysely';
+import { pendingMigrations } from '../db/migrator';
+import type { AppDeps } from './context';
+
+export type CheckState = 'ok' | 'error' | 'pending';
+
+/**
+ * Liveness: the process is up and the event loop is turning. Never touches the
+ * database, so a database blip does not get the container killed.
+ */
+export function liveness(draining: boolean): { ok: boolean } {
+  return { ok: !draining };
+}
+
+/**
+ * Readiness: this replica can serve traffic. Checked by the orchestrator and flipped
+ * to not-ready as soon as SIGTERM arrives, so the load balancer stops sending work
+ * while in flight requests drain.
+ */
+export async function readiness(
+  deps: AppDeps,
+  draining: boolean,
+): Promise<{ ok: boolean; checks: Record<string, CheckState> }> {
+  if (draining) return { ok: false, checks: { draining: 'error' } };
+
+  const checks: Record<string, CheckState> = {};
+
+  try {
+    await sql`select 1`.execute(deps.handle.db);
+    checks['database'] = 'ok';
+  } catch {
+    checks['database'] = 'error';
+  }
+
+  if (checks['database'] === 'ok') {
+    try {
+      checks['migrations'] = (await pendingMigrations(deps.handle)).length === 0 ? 'ok' : 'pending';
+    } catch {
+      checks['migrations'] = 'error';
+    }
+  } else {
+    checks['migrations'] = 'error';
+  }
+
+  return { ok: Object.values(checks).every((state) => state === 'ok'), checks };
+}