docs(records): record lifecycle and endpoint coverage

docs/REFERENCE_JOURNEY_PROGRAM.md

@@ -39,6 +39,15 @@ identify the journey it improves, or provide security, operability, recovery,
 accessibility, or usability evidence that those journeys require. Work that
 does neither stays in the backlog until a concrete consumer exists.
 
+The Records vertical now supplies the journey's native file plan, immutable
+record and item revisions, chronology, close/reopen, retention calculation,
+holds, appraisal, independent disposition approval, recovery-ledger evidence,
+and archive-neutral package simulation. The executable Records fixture proves
+those native transitions without claiming archival custody. The journey still
+needs Forms Runtime/Decisions filing, resumable user handoffs, search
+reconstruction in the pinned composition, and one target-tested archive
+profile.
+
 ## Why this sequence
 
 The sequence grows one connected product rather than advancing repositories in

docs/STRATEGY_STATUS.md

@@ -84,7 +84,7 @@ reconciliation, publication/export, and guided handoff evidence.
 | --- | --- | --- |
 | No reference-ready product package | The platform cannot yet make a bounded supported-product claim | Complete one named target composition and evidence bundle |
 | Human-work spine incomplete | Users still navigate modules and remember unfinished work | Task/work inbox, resumable guided journey, deadlines and handoffs |
-| Records/eAkte shallow | Institutional memory and disposition remain fragmented | Native record lifecycle plus external DMS/archive overlay |
+| Records/eAkte target integration incomplete | Native lifecycle, retention, holds, approval, recovery, and transfer simulation are implemented, but real custody is not proved | Target-test one archive/xdomea profile and complete the assisted reference journey |
 | Cross-cutting governance adoption uneven | Historical and purpose-sensitive behavior varies by module | Enforced adoption declarations and route/query/effect migration |
 | Explicit help/accessibility depth incomplete | German/reference and F1 association gates now pass, but generic fallback remains too common | High-risk German help content and browser/a11y matrix |
 | Real federation absent | Cross-institution exchange remains connector-specific | Paired-instance signed exchange and reconciliation proof |

tools/inventory/endpoint-surface-declarations.json

@@ -1336,28 +1336,81 @@
       "repository": "govoplan-projects"
     },
     {
-      "category": "missing_ui",
+      "category": "ui_reachable",
       "method": "POST",
-      "path": "/records/catalog/classes",
-      "rationale": "The first Records workspace consumes governed record classes; catalog administration remains tracked by the eAkte epic.",
-      "repository": "govoplan-records",
-      "tracking_issue": "https://git.add-ideas.de/GovOPlaN/govoplan-records/issues/1"
+      "path": "/records/{}/appraise",
+      "rationale": "The Records lifecycle panel invokes the record appraisal action through a dynamically constructed record path.",
+      "repository": "govoplan-records"
     },
     {
-      "category": "missing_ui",
+      "category": "ui_reachable",
       "method": "POST",
-      "path": "/records/catalog/file-plan",
-      "rationale": "The first Records workspace consumes the file plan; governed file-plan administration remains tracked by the eAkte epic.",
-      "repository": "govoplan-records",
-      "tracking_issue": "https://git.add-ideas.de/GovOPlaN/govoplan-records/issues/1"
+      "path": "/records/{}/close",
+      "rationale": "The Records lifecycle panel invokes the record closure action through a dynamically constructed record path.",
+      "repository": "govoplan-records"
     },
     {
-      "category": "missing_ui",
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/dispositions",
+      "rationale": "The Records lifecycle panel proposes a governed disposition through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/dispositions/{}/finalize",
+      "rationale": "The Records lifecycle panel finalizes an approved disposition through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/dispositions/{}/withdraw",
+      "rationale": "The Records lifecycle panel withdraws a pending disposition through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/holds",
+      "rationale": "The Records lifecycle panel applies a hold through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/holds/{}/release",
+      "rationale": "The Records lifecycle panel releases a hold through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/reopen",
+      "rationale": "The Records lifecycle panel invokes the record reopen action through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/transfer-packages",
+      "rationale": "The Records lifecycle panel prepares an archive-neutral transfer package through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
+      "method": "POST",
+      "path": "/records/{}/transfer-packages/{}/dispatch",
+      "rationale": "The Records lifecycle panel runs an explicitly simulated transfer through a dynamically constructed record path.",
+      "repository": "govoplan-records"
+    },
+    {
+      "category": "ui_reachable",
       "method": "POST",
       "path": "/records/{}/volumes",
-      "rationale": "The first workspace supports record-level filing without a volume; explicit volume management remains tracked by the eAkte epic.",
-      "repository": "govoplan-records",
-      "tracking_issue": "https://git.add-ideas.de/GovOPlaN/govoplan-records/issues/1"
+      "rationale": "The Records filing dialog creates explicit record volumes through a dynamically constructed record path.",
+      "repository": "govoplan-records"
     },
     {
       "category": "missing_ui",