Flag people who cannot simply be dismissed

Works council members, expectant mothers, parents on leave, registered
disabled employees, apprentices — each has its own rules that come
before a dismissal. The tool does not judge whether one is lawful, but
it must not stay quiet about it either, and looking it up on the
contract tab is exactly the step that gets skipped under time pressure.

So: a checkbox, an optional end date, and a red warning at the top of
the termination panel naming the date — or saying plainly that no end
was recorded. It shows for a no-show too; the protection runs from the
start of the contract, not the first day worked.

The date is optional on purpose. A works council mandate has a known
end, a pregnancy does not, and a mandatory field would force an invented
number. A constraint says only what cannot be: an end date without the
flag, which would be a leftover nobody could interpret.

The field goes the whole way through — hire, data change, contract
sheet, export, report criteria (as a yes/no and as a date range), and
the import. A field that exists in one screen and not the next is how
people stop trusting the numbers.

Terminating is now offered for planned entries as well, labelled "Nicht
angetreten", with No Show preselected. Without it a person who never
turned up stayed a planned entry forever, since nothing else can end
one.

One finding worth recording: tsc has been reporting success on a broken
program. A generated file under .next got corrupted when a build ran
against a live dev server, and its syntax errors suppressed semantic
checking everywhere else — two genuine type errors in this change went
unreported until I typechecked with .next excluded. The file is removed
and the ordinary typecheck is meaningful again.

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

components/employees/panels/TerminatePanel.tsx

@@ -8,7 +8,7 @@ import { SelectField, TextField, TextareaField } from "@/components/ui/Field";
 import { SlideOver } from "@/components/ui/SlideOver";
 import { useToast } from "@/components/ui/Toast";
 import type { Database } from "@/lib/supabase/types";
-import { fmtName } from "@/lib/format";
+import { fmtDate, fmtName } from "@/lib/format";
 
 type EmployeeRow = Database["public"]["Tables"]["employees"]["Row"];
 
@@ -37,7 +37,10 @@ export function TerminatePanel({ open, onClose, employee, directReportCount }: T
   const { showToast } = useToast();
   const router = useRouter();
   const [exitDate, setExitDate] = useState("");
-  const [reason, setReason] = useState(EXIT_REASONS[0]);
+  // Wer noch gar nicht angefangen hat, tritt fast nie aus einem anderen Grund
+  // aus. Die Vorbelegung nimmt den wahrscheinlichen Fall vorweg, ohne die
+  // übrigen zu verstellen.
+  const [reason, setReason] = useState(employee.status === "Geplant" ? NO_SHOW : EXIT_REASONS[0]);
   const [note, setNote] = useState("");
   const [checked, setChecked] = useState<boolean[]>(CHECKLIST_ITEMS.map(() => false));
   const [pending, setPending] = useState(false);
@@ -79,7 +82,7 @@ export function TerminatePanel({ open, onClose, employee, directReportCount }: T
     <SlideOver
       open={open}
       onClose={onClose}
-      title="Austritt"
+      title={istNoShow ? "Nicht angetreten" : "Austritt"}
       subtitle={`${fmtName(employee.first_name, employee.last_name)} · ${employee.job_title}`}
       footer={
         <>
@@ -93,6 +96,21 @@ export function TerminatePanel({ open, onClose, employee, directReportCount }: T
       }
     >
       <div className="flex flex-col gap-4">
+        {/* Zuerst, und nicht zu übersehen: bei besonderem Kündigungsschutz
+            gelten eigene Regeln, bevor beendet werden darf. Die Anwendung
+            entscheidet das nicht — sie darf es aber auch nicht verschweigen,
+            und im Vertragsblatt nachzusehen ist genau der Schritt, den man
+            unter Zeitdruck auslässt. */}
+        {employee.has_kuendigungsschutz && (
+          <div className="rounded border border-danger-solid bg-danger-bg px-3 py-2 text-sm font-semibold text-danger-text">
+            Achtung: besonderer Kündigungsschutz
+            {employee.kuendigungsschutz_bis ? ` bis ${fmtDate(employee.kuendigungsschutz_bis)}` : " (Ende nicht erfasst)"}.
+            <span className="block font-normal">
+              Vor einer Beendigung ist zu prüfen, ob sie zulässig ist — je nach Grund braucht es eine Zustimmung des
+              Betriebsrats oder des Gerichts.
+            </span>
+          </div>
+        )}
         {directReportCount > 0 && (
           <div className="rounded bg-warning-bg px-3 py-2 text-sm text-warning-text">
             {directReportCount} direkte Berichte werden automatisch der nächsthöheren Führungskraft zugeordnet.