feat: enforce shared UI foundations and pin reference journey

packages/product/service-to-decision/README.md

@@ -9,6 +9,14 @@ resolution -> approval/deliberation -> formal Decision -> observed delivery
 effect -> record and review references
 ```
 
+The maintained concrete scenario is a German resident parking permit
+(`Anwohnerparkausweis`). Its versioned fixture is
+`tests/fixtures/resident_parking_permit_journey.json`. It pins the service,
+exact Form revision, resident inputs, digital and assisted channels, Case type,
+human review handoff, formal outcome, Postbox delivery channel, and Records
+filing/retention target. Generic permit wording is no longer acceptance
+evidence for this package.
+
 An installed Forms and Forms Runtime pair adds an alternative governed entry
 path before case/workflow handoff:
 

packages/product/service-to-decision/package.json

@@ -45,6 +45,11 @@
       "reference": "packages/product/service-to-decision/README.md",
       "summary": "Defines the package boundary, authority path, recovery contract, and known operational limits."
     },
+    {
+      "kind": "target_test",
+      "reference": "tests/fixtures/resident_parking_permit_journey.json",
+      "summary": "Pins the resident parking permit actors, channels, exact inputs, work item, formal outcome, filing target, and remaining manual acceptance gates."
+    },
     {
       "kind": "target_test",
       "reference": "tests/test_institutional_governance_journey.py",