Remove Supabase

The database moved to a container of our own; the platform is gone.
This takes out what was left of it — and, where the leftovers were load
bearing, moves rather than deletes.

Moved, not deleted:

  supabase/migrations/  -> db/migrations/      the schema's source of truth
  supabase/build-org.ts -> scripts/build-org.ts
  lib/supabase/types.ts -> lib/types.ts        52 import sites repointed

The bookkeeping needed care. It lived in `supabase_migrations.schema_migrations`,
and simply renaming the schema would have left the runner facing an empty
table: it would have called all 67 migrations pending and replayed them
against a database that is long since current. So the runner now creates
`migrationen.schema_migrations` and, once, copies the old rows across —
guarded so a second run does nothing and a fresh database skips it entirely.
Only then does migration 20260907100000 drop the old schema.

Deleted: the CLI config, the seed, the historical schema/function dumps
(nothing read them), scripts/umzug-von-supabase.sh (the move is done), and
both Supabase packages plus the CLI. Nothing in the application imported
them — the build now succeeds with no environment variables at all, which
is the proof.

Integration tests: six of them signed in through Supabase Auth and asserted
against the anon key and the service role. That model is gone, so the tests
were not portable — they are deleted. session-context and
employee-status-filter already ran on pg and are untouched; om-reporting is
ported to a direct connection because it guards a real risk (the reporting
line rule exists twice, once in SQL and once in TypeScript).

CI: the integration job started a Supabase stack. It now runs a postgres
service, applies deploy/db-init and every migration to an empty database —
that was the valuable part, and it still holds — then checks that a second
run is a no-op, which is what proves the bookkeeping works.

Docs: security-review.md audited a service-role key, a cookie adapter and
auth.users, none of which exist. Restating findings about removed components
would suggest today's system had been reviewed; it has not. It now records
what was removed and says a fresh review is due. data-model.md was already
marked obsolete and described the pre-OM schema; azure-migration.md was a
plan for a route not taken. Both deleted.

Verified: npm ci, typecheck, lint, 445 tests, build — all clean without the
packages. Integration tests skip cleanly with no database. Migration SQL and
the runner are reviewed but NOT executed: no Docker here, and the old
instance no longer resolves.

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

db/migrations/20260826120000_anwendungsrolle_rechte.sql

@@ -0,0 +1,73 @@
+-- Rechte der Anwendungsrolle alpenwerk_app.
+--
+-- Auf Supabase wurden diese Rechte von Hand im Dashboard vergeben und standen
+-- deshalb in keiner Migration. Beim Umzug in einen eigenen Container fiel das
+-- auf: das Schema entstand vollstaendig aus den Migrationen, die Rolle hatte
+-- aber weder Tabellen- noch Funktionsrechte — die Anwendung scheiterte mit
+-- "permission denied for table profiles", bevor die Anmeldeseite erschien.
+--
+-- Ohne diese Datei laesst sich das Projekt auf einer leeren Datenbank nicht
+-- in Betrieb nehmen. Genau das ist aber das Ziel: ein Container, den der
+-- Kunde selbst hochfaehrt.
+--
+-- Die Rolle bleibt **ohne BYPASSRLS**. Diese Rechte sagen nur, welche Objekte
+-- sie ueberhaupt anfassen darf; welche Zeilen sie sieht, entscheiden weiterhin
+-- die 58 RLS-Policies.
+
+-- ── Tabellen und Sequenzen ────────────────────────────────────────────
+grant select, insert, update, delete on all tables in schema public to alpenwerk_app;
+grant usage, select, update on all sequences in schema public to alpenwerk_app;
+
+-- Damit kuenftige Migrationen mit neuen Tabellen nicht dieselbe Panne
+-- ausloesen.
+alter default privileges in schema public grant select, insert, update, delete on tables to alpenwerk_app;
+alter default privileges in schema public grant usage, select, update on sequences to alpenwerk_app;
+
+-- ── Funktionen ────────────────────────────────────────────────────────
+-- Bewusst die einzeln aufgezaehlte Liste aus dem Supabase-Bestand und kein
+-- pauschales "on all routines": 20260727150000 hat EXECUTE bei einem Teil der
+-- SECURITY-DEFINER-Funktionen absichtlich entzogen. Eine Pauschalvergabe
+-- machte das rueckgaengig.
+grant execute on function public.add_employee_dependent(payload jsonb) to alpenwerk_app;
+grant execute on function public.add_employee_note(payload jsonb) to alpenwerk_app;
+grant execute on function public.adjust_karenz_return(payload jsonb) to alpenwerk_app;
+grant execute on function public.app_aenderung(p_liste jsonb, p_feld text, p_vorher text, p_nachher text) to alpenwerk_app;
+grant execute on function public.app_aenderungsfelder(p_liste jsonb) to alpenwerk_app;
+grant execute on function public.app_current_user_id() to alpenwerk_app;
+grant execute on function public.app_feld_karte() to alpenwerk_app;
+grant execute on function public.app_upsert_user(p_external_id text, p_email text, p_full_name text) to alpenwerk_app;
+grant execute on function public.apply_due_pending_changes() to alpenwerk_app;
+grant execute on function public.change_employee_data(payload jsonb) to alpenwerk_app;
+grant execute on function public.complete_employee_note(payload jsonb) to alpenwerk_app;
+grant execute on function public.create_position(payload jsonb) to alpenwerk_app;
+grant execute on function public.current_actor_name() to alpenwerk_app;
+grant execute on function public.current_hr_user_id() to alpenwerk_app;
+grant execute on function public.delete_employee_dependent(payload jsonb) to alpenwerk_app;
+grant execute on function public.delete_history_entry(payload jsonb) to alpenwerk_app;
+grant execute on function public.delete_position(payload jsonb) to alpenwerk_app;
+grant execute on function public.fn_check_history_not_before_entry() to alpenwerk_app;
+grant execute on function public.fn_touch_profiles_updated_at() to alpenwerk_app;
+grant execute on function public.fn_touch_updated_at() to alpenwerk_app;
+grant execute on function public.fn_validate_employee_svnr() to alpenwerk_app;
+grant execute on function public.generate_company_email(p_first_name text, p_last_name text) to alpenwerk_app;
+grant execute on function public.hire_employee(payload jsonb) to alpenwerk_app;
+grant execute on function public.is_hr_admin() to alpenwerk_app;
+grant execute on function public.is_hr_user() to alpenwerk_app;
+grant execute on function public.is_valid_svnr(p_svnr text, p_birth_date date) to alpenwerk_app;
+grant execute on function public.next_position_number() to alpenwerk_app;
+grant execute on function public.om_reporting_lines(p_as_of date) to alpenwerk_app;
+grant execute on function public.promote_employee(payload jsonb) to alpenwerk_app;
+grant execute on function public.record_karenz_return(payload jsonb) to alpenwerk_app;
+grant execute on function public.rehire_employee(payload jsonb) to alpenwerk_app;
+grant execute on function public.require_hr_admin() to alpenwerk_app;
+grant execute on function public.rls_auto_enable() to alpenwerk_app;
+grant execute on function public.set_offboarding_task(payload jsonb) to alpenwerk_app;
+grant execute on function public.set_onboarding_task(payload jsonb) to alpenwerk_app;
+grant execute on function public.set_position_cost_center(payload jsonb) to alpenwerk_app;
+grant execute on function public.start_karenz(payload jsonb) to alpenwerk_app;
+grant execute on function public.start_offboarding(payload jsonb) to alpenwerk_app;
+grant execute on function public.start_onboarding(payload jsonb) to alpenwerk_app;
+grant execute on function public.terminate_employee(payload jsonb) to alpenwerk_app;
+grant execute on function public.transfer_employee(payload jsonb) to alpenwerk_app;
+grant execute on function public.update_history_entry(payload jsonb) to alpenwerk_app;
+grant execute on function public.update_position(payload jsonb) to alpenwerk_app;