feat(records): complete eAkte reference journey

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