feat(body-sites): record a body site on conditions and add a body-site view

A condition (illness episode) can carry where on the body it sits, in the
person's own words and encrypted at rest, plus an optional side (LEFT,
RIGHT, BOTH). Same enum, codec and reasoning as the procedure's site.

- migration 0354: two nullable columns on illness_episodes, reusing the
  laterality type from 0349
- create and edit accept bodySite and laterality; on PATCH an absent key
  keeps the stored value, so an edit from the shipped iPhone app, which
  never sends either field, leaves them untouched
- GET /api/body-sites: the sites the record holds across visits and
  conditions, folded after the decrypt and bounded per kind; with site
  (and laterality) the visits and conditions there, one hop to their
  documents, lab results and visits. Read in the profile section;
  conditions only under an illness grant with the module on, and links
  into ungranted sections come back as unlabelled placeholders
- the link service reads document and visit links from the condition's
  end of the two existing tables
- /checkups gains a Body sites tab; the visit and condition forms share
  one body-site field pair that suggests sites already used; a
  condition's page links its site into the view
- the doctor report, the clinician page and the MCP doctor-visit summary
  name the site on conditions; the Coach illness block carries it
  sanitised, and MCP get_illness_recovery returns it fenced
- backup and restore carry both fields in both file kinds; the site is
  registered as ciphertext and rotates with the key
- i18n in all seven locales, OpenAPI regenerated

Refs #1025

src/app/checkups/page-client.tsx

@@ -13,6 +13,8 @@ import { Tabs, TabsContent, TabsList, TabsTrigger } from "@/components/ui/tabs";
 import { VorsorgeSection } from "@/components/measurement-reminders/vorsorge-section";
 import { VisitsSection } from "@/components/encounters/visits-section";
 import { ProceduresSection } from "@/components/encounters/procedures-section";
+import { BodySitesSection } from "@/components/body-sites/body-sites-section";
+import type { BodySiteSide } from "@/hooks/use-body-sites";
 import { useTranslations } from "@/lib/i18n/context";
 import { invalidateKeys, queryKeys } from "@/lib/query-keys";
 
@@ -36,6 +38,11 @@ import { invalidateKeys, queryKeys } from "@/lib/query-keys";
  * so it sits beside the visits rather than behind a nav entry of its own, and
  * its read hangs off the same `["encounters"]` root the pull already evicts.
  *
+ * v1.39.2 — a fourth tab, the body-site view: procedures and conditions by
+ * where on the body they are, with what is linked to them. It starts from the
+ * visits (a procedure is one), so it sits here rather than under the illness
+ * journal, and its read hangs off the same `["encounters"]` root.
+ *
  * The pull invalidates both reads. Refreshing one and leaving the other stale
  * is how a page ends up showing a visit that closed a checkup still listed as
  * due.
@@ -47,8 +54,21 @@ export default function CheckupsPageClient() {
   const { t } = useTranslations();
   // A link to one visit (`?visit=<id>`, from a document's link chip) lands on
   // the visits tab, where the section opens it.
-  const linkedVisit = useSearchParams()?.get("visit");
-  const [view, setView] = useState(linkedVisit ? "visits" : "vorsorge");
+  const searchParams = useSearchParams();
+  const linkedVisit = searchParams?.get("visit");
+  // A link to one body site (`?site=<text>&side=<LEFT|RIGHT|BOTH>`, from a
+  // condition's page) lands on the body-site tab with that site picked.
+  const linkedSite = searchParams?.get("site")?.trim() || null;
+  const linkedSideParam = searchParams?.get("side");
+  const linkedSide: BodySiteSide =
+    linkedSideParam === "LEFT" ||
+    linkedSideParam === "RIGHT" ||
+    linkedSideParam === "BOTH"
+      ? linkedSideParam
+      : null;
+  const [view, setView] = useState(
+    linkedVisit ? "visits" : linkedSite ? "body-sites" : "vorsorge",
+  );
 
   const refresh = useCallback(
     () =>
@@ -78,6 +98,9 @@ export default function CheckupsPageClient() {
           <TabsTrigger value="procedures" data-testid="checkups-tab-procedures">
             {t("checkups.tabProcedures")}
           </TabsTrigger>
+          <TabsTrigger value="body-sites" data-testid="checkups-tab-body-sites">
+            {t("checkups.tabBodySites")}
+          </TabsTrigger>
         </TabsList>
         <TabsContent value="vorsorge">
           <VorsorgeSection enabled={isAuthenticated} variant="page" />
@@ -90,6 +113,13 @@ export default function CheckupsPageClient() {
         <TabsContent value="procedures">
           <ProceduresSection enabled={isAuthenticated} />
         </TabsContent>
+        <TabsContent value="body-sites">
+          <BodySitesSection
+            enabled={isAuthenticated}
+            initialSite={linkedSite}
+            initialSide={linkedSide}
+          />
+        </TabsContent>
       </Tabs>
     </div>
   );