feat(records): complete eAkte reference journey

docs/EAKTE_ARCHITECTURE.md

@@ -40,10 +40,14 @@ packages tracked by Records #2-#6:
 - tenant administration for versioned file-plan nodes and record classes,
   explicit volume management, and lifecycle controls in the eAkte workspace.
 
-The remaining boundary is intentionally visible rather than implied: Records
-#7 requires selection and target testing of an archive/xdomea endpoint and
-conformance profile; #8 completes the cross-module reference journey and
-production evidence. Restricted per-record access grants also remain a
+The cross-module reference journey from Records #8 is executable: equivalent
+assisted and authenticated digital permit records preserve exact form,
+attachment, case/representation, decision, delivery, and correction evidence;
+exercise closure, retention, hold, approval, and simulated transfer; and prove
+search and temporal reconstruction after database backup/restore. The
+remaining boundary is intentionally visible rather than implied: Records #7
+requires selection and target testing of an archive/xdomea endpoint and
+conformance profile. Restricted per-record access grants also remain a
 dedicated access-policy slice. Destruction is represented only as an approved
 pending state; no content deletion or real archive effect is currently
 claimed.
@@ -234,6 +238,10 @@ available in an evidence/details view.
 5. Add destruction/recovery, TR-ESOR provider integration, migration, and
    signed reference-journey evidence.
 
-The first reference package should file the digital and assisted variants of
-the same service-to-decision journey into equivalent records and prove search,
-historical reconstruction, hold, transfer, restore, and access explanation.
+The first reference package files the digital and assisted variants of the
+resident-parking-permit service-to-decision journey into equivalent records.
+Its fixture and regression test prove search, historical reconstruction, hold,
+independent approval, simulated transfer, restore, current access explanation,
+source digest revalidation, and transfer-manifest integrity. Its UI contract
+pins URL-based resume, exact-source filing presets, governance context,
+evidence semantics, lifecycle actions, and recovery inspection.

docs/RECORDS_DOMAIN_BOUNDARY.md

@@ -38,8 +38,8 @@ The native kernel currently provides:
 - independent valid and recorded time with current/at/all temporal reads;
 - tenant, purpose, actor/capacity, source authority, institutional context,
   provenance, and idempotency fields;
-- provider-neutral exact-source capabilities, initially implemented by Files
-  file versions and Cases revisions;
+- provider-neutral exact-source capabilities implemented by Files versions,
+  Cases revisions, Forms Runtime submissions, and Decisions revisions;
 - tenant APIs, search projection, uninstall/retirement guards, and a Records
   workspace using shared WebUI controls.
 - immutable close/reopen, retention, hold, appraisal, and independently
@@ -49,6 +49,9 @@ The native kernel currently provides:
 - Core recovery-ledger adoption, atomic terminal evidence, Audit projection,
   source and package restore diagnostics, catalog administration, volumes, and
   lifecycle UI.
+- an executable assisted/digital resident-parking-permit reference package
+  that proves equivalent filing semantics, URL resume, search, temporal
+  reconstruction, and evidence integrity after database backup/restore.
 
 Restricted object grants remain a separate governed slice. A target-tested
 archive adapter and any destructive effect remain deliberately unimplemented;
@@ -73,12 +76,13 @@ immutable retention evidence; the current record fact receives a
 non-executable manual-review action. Actual correction, closure, appraisal,
 hold, disposition, or transfer must use the governed eAkte lifecycle.
 
-## First Implementation Slice
+## Next Boundary Slice
 
 Complete restricted access and one target-tested archive provider without
-moving source-module ownership into Records. Extend the executable reference
-journey across assisted service, decision, filing, hold, restore, search, and
-archive simulation before claiming production maturity.
+moving source-module ownership into Records. The executable reference journey
+already covers assisted/digital intake, decision, filing, hold, restore,
+search, and archive simulation; it is evidence for the native boundary, not a
+claim of target archive conformance or transferred custody.
 
 The complete native/external boundary, temporal and purpose-aware record model,
 disposition lifecycle, German public-sector provider profiles, and staged