docs(sharing): the booster needs two sections, and the guide promised it at one level

The write-level row listed "a vaccination dose and the booster reminder it
suggests" three paragraphs under a section table that puts the vaccination
record in Health background. Read together, that tells a self-hoster a
health-background WRITE grant can plan a booster — which the route beside it
now refuses, because the reminder it mints lives under Readings. The row lists
the dose alone, and the exceptions paragraph, which is where a reader looks for
exactly this, carries the two-section case and says the dose logs either way.

With it, the small things the same pass turned up:

The cycle-insights fixture asserted a property it could not show. Its docblock
claims the cycle-native answer survives the fence, and it seeded no symptom at
all, so `symptomPatterns` was empty in every leg and a regression that emptied
it along with the foreign columns would have passed green. One catalogue
symptom on the luteal days, asserted on the owner leg and on the cycle-only
one.

The immunization rows matched on a bare `role="button"`, which passes vacuously
the day the card becomes a real button and fails for the wrong reason if
anything else in the subtree grows one. They carry the same stable marker the
visit card took.

`/api/cycle/calendar` reads the same wrist-temperature channel the crosstab
does and is deliberately not fenced, and it was the only one of the pair with
nothing saying why: no value from it reaches the response.

The encrypted export's new 403 documented the switch refusal and not the
narrow-scope one it answers first, unlike the two settings operations beside
it. Both sheets say at the top that their Save and Delete are gated at the
caller, so a third mount reads the constraint before it violates it. And one
docblock line ran past the wrap.

src/app/api/cycle/calendar/route.ts

@@ -111,6 +111,12 @@ export const GET = apiHandler(async (request: NextRequest) => {
     // Apple Watch wrist/skin temperature feeds the temperature-trend
     // ovulation layer. Read the WRIST_TEMPERATURE measurements as nightly
     // values; the engine derives the trailing-mean deviation itself.
+    //
+    // This is a measurements read on a route declared under `cycle`, and it
+    // needs no section predicate for one reason: no value from it reaches the
+    // response. It goes into `predictCycle` and what comes out the other side
+    // is a shifted date. The crosstab next door reads the same channel and IS
+    // fenced, because there the values are the answer.
     prisma.measurement.findMany({
       where: {
         userId: user.id,

src/components/__tests__/delegated-write-affordances.test.tsx

@@ -714,11 +714,15 @@ describe("the immunization log's add, edit and delete", () => {
     });
   };
 
+  /** The row carries the edit affordance only while it opens something. */
+  const rowIsTappable = (html: string) =>
+    html.includes('data-slot-open="vaccination-row-open"');
+
   it("offers all three in the caller's own record", () => {
     const html = render(OWN_RECORD, <VaccinationsView />, seedList);
     expect(html).toContain('data-slot="vaccination-add"');
     // The row opens the edit sheet, which is where the delete lives.
-    expect(html).toContain('role="button"');
+    expect(rowIsTappable(html)).toBe(true);
   });
 
   it("offers a read-only delegate none of them", () => {
@@ -730,7 +734,7 @@ describe("the immunization log's add, edit and delete", () => {
       seedList,
     );
     expect(html).not.toContain('data-slot="vaccination-add"');
-    expect(html).not.toContain('role="button"');
+    expect(rowIsTappable(html)).toBe(false);
   });
 
   it("offers a WRITE delegate the add and not the row", () => {
@@ -740,8 +744,8 @@ describe("the immunization log's add, edit and delete", () => {
       seedList,
     );
     expect(html).toContain('data-slot="vaccination-add"');
-    expect(html, "editing and deleting a dose are MANAGE").not.toContain(
-      'role="button"',
+    expect(rowIsTappable(html), "editing and deleting a dose are MANAGE").toBe(
+      false,
     );
   });
 
@@ -752,7 +756,7 @@ describe("the immunization log's add, edit and delete", () => {
       seedList,
     );
     expect(html).toContain('data-slot="vaccination-add"');
-    expect(html).toContain('role="button"');
+    expect(rowIsTappable(html)).toBe(true);
   });
 
   it("offers a MANAGE delegate outside the section neither", () => {
@@ -764,7 +768,7 @@ describe("the immunization log's add, edit and delete", () => {
       seedList,
     );
     expect(html).not.toContain('data-slot="vaccination-add"');
-    expect(html).not.toContain('role="button"');
+    expect(rowIsTappable(html)).toBe(false);
   });
 
   it("offers the empty state's add on the same rule", () => {

src/components/encounters/encounter-sheet.tsx

@@ -20,6 +20,16 @@
  * saved and a plain sentence saying the checkup stayed open. That is reported
  * rather than skipped in silence: somebody who believes a checkup was closed
  * will not look at it again.
+ *
+ * Capability note: this sheet carries no capability check of its own, by
+ * decision. Save is a create on one mount and an edit on the other, and Delete
+ * exists only in edit mode — so the question belongs to whoever opens it.
+ * `VisitsSection` hands it a record only under `canManageDomain("profile")`,
+ * and the two mounts that can only create (`EpisodeVisitsCard`,
+ * `VorsorgeSection`) pass `encounter={null}` behind their own write check. A
+ * THIRD mount that hands this sheet a record without asking the manage
+ * question reintroduces an ungated Delete, and nothing here will fail. Ask at
+ * the caller, or move the check in here for everyone.
  */
 import { useState } from "react";
 import { Trash2 } from "lucide-react";

src/components/layout/capture-picker.tsx

@@ -58,9 +58,11 @@ type CaptureKind = "measurement" | "medication" | "mood";
  * offered whenever the grant could write anywhere — and that answer is the
  * grant's LEVEL with no scope term at all. A WRITE grant scoped to `["labs"]`
  * read as true and got a weight form the server refuses; one scoped to
- * `["documents"]`, which takes no delegated write at any level, got both. `writableDomains` is already the level × scope × route-table
- * intersection, so asking it per section answers both cases and the mood
- * entry's MANAGE-only create as well.
+ * `["documents"]`, which takes no delegated write at any level, got both.
+ *
+ * `writableDomains` is already the level × scope × route-table intersection,
+ * so asking it per section answers both cases and the mood entry's
+ * MANAGE-only create as well.
  */
 const CAPTURE_KIND_DOMAIN: Readonly<Record<CaptureKind, ShareDomain>> = {
   measurement: "measurements",

src/components/vaccinations/vaccination-list.tsx

@@ -157,6 +157,10 @@ function DoseRow({
     <Card
       className="hover:bg-muted/40 gap-0 transition-colors"
       data-slot="vaccination-row"
+      // A second, stable marker for the state rather than for the row: the
+      // `role` is markup that could legitimately change, and a guard matching
+      // on it would pass the day a real `<button>` replaced the card.
+      data-slot-open={onEdit ? "vaccination-row-open" : undefined}
       data-vaccination-id={record.id}
       onClick={onEdit ? () => onEdit(record) : undefined}
       role={onEdit ? "button" : undefined}

src/components/vaccinations/vaccination-sheet.tsx

@@ -10,6 +10,13 @@
  * On a successful create the caller may raise the booster-mint prompt; this
  * sheet completes and closes regardless of what the person does with it. The
  * mint is an offer, never a step.
+ *
+ * Capability note: the same posture as the visit sheet. No check here; Delete
+ * renders only in edit mode, and the one mount that can reach edit mode
+ * (`VaccinationsView`) asks `canManageDomain("profile")` before handing over a
+ * record, while its create path asks `canWriteDomain("profile")`. A second
+ * mount that skips either question reintroduces an ungated control with
+ * nothing failing.
  */
 import { useState } from "react";
 import { Trash2 } from "lucide-react";

src/lib/openapi/routes/export.ts

@@ -310,7 +310,9 @@ export const exportPaths: NonNullable<ZodOpenApiObject["paths"]> = {
           },
         },
         "403": {
-          description: SHARING_NOT_PERMITTED_DESCRIPTION,
+          description:
+            "The Bearer token carries a narrow scope. The encrypted archive needs a cookie session or a full-access token; the refusal happens before any second-factor proof is looked at.\n\n" +
+            SHARING_NOT_PERMITTED_DESCRIPTION,
           content: { "application/json": { schema: errorEnvelope } },
         },
         ...stdResponses,