Drop agent tooling files and neutralise spec references

- Removed CLAUDE.md, AGENTS.md and NEXTJS_REBUILD_SUPERPROMPT.md, and
  untracked .claude/ (now ignored locally via .git/info/exclude rather than
  .gitignore, so the repo carries no reference to it either).
- The Next.js 16 warning that lived in AGENTS.md is kept where it is
  actually useful, in the README tech-stack section.
- Source and migration comments referred to "the consolidation master
  prompt" and "NEXTJS_REBUILD_SUPERPROMPT.md" by name; both now read "spec",
  keeping the section numbers that made the cross-references worth having.
- README no longer lists Playwright, which is not installed, and now
  describes the three test layers that actually exist.

.gitignore

@@ -50,13 +50,6 @@ next-env.d.ts
 # hand-written lib/supabase/types.ts — never itself imported
 /lib/supabase/types.generated.ts
 
-# per-machine (permission allowlists) and must stay out of the repo
-
-# playwright
-/playwright-report
-/test-results
-/blob-report
-
 # local scratch scripts/screenshots (ad-hoc verification against a real or
 # seeded DB — can carry HR data or use SUPABASE_SERVICE_ROLE_KEY; never commit)
 .scratch_*

README.md

@@ -19,14 +19,16 @@ auf explizit aktivierte HR-Benutzer:innen beschränkt (siehe
 ## Tech-Stack
 
 - Next.js 16 (App Router) — **Achtung:** Next.js 16 hat Breaking Changes
-  gegenüber älteren Versionen (u. a. `proxy.ts` statt `middleware.ts`, siehe
-  `AGENTS.md`). Vor Änderungen an Framework-nahen Dateien die lokalen Docs
-  unter `node_modules/next/dist/docs/` konsultieren.
+  gegenüber älteren Versionen (u. a. `proxy.ts` statt `middleware.ts`).
+  Vor Änderungen an Framework-nahen Dateien die lokalen Docs unter
+  `node_modules/next/dist/docs/` konsultieren; sie sind maßgeblich, ältere
+  Anleitungen im Netz beschreiben teils überholte APIs.
 - React 19, TypeScript
 - Supabase (Postgres, Auth, RLS) — Datenhaltung liegt vollständig in
   Supabase, nicht im Next.js-Prozess.
 - Tailwind CSS v4
-- Vitest (Unit + Integrationstests), Playwright (E2E)
+- Vitest — Unit- (Node), Komponenten- (jsdom) und Integrationstests
+  (gegen ein lokales Supabase)
 
 ## Setup
 

supabase/migrations/20260714120600_data_integrity_guards.sql

@@ -1,4 +1,5 @@
--- Two data-integrity rules named explicitly in the spec (§3.7, §11 test scenarios #14 and #17) that had no enforcement
+-- Two data-integrity rules named explicitly in the spec (§3.7, §11 test
+-- scenarios #14 and #17) that had no enforcement
 -- anywhere — not in the UI, not in a Server Action, not as a DB constraint:
 --
 --   1. "Rückkehr darf nicht vor Beginn der Karenz liegen" — there was no