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.