fix(store): dash capability IDs + .chain bundles (chain catalog conformance)

chain's catalog charset (naming.rs check_segment, capability-namespaces.yaml)
allows only [a-z0-9-] per dot-segment — underscores are rejected by
`chain validate`. Repack all 8 modules with the dash capability form
(econ.skm-score, law.benefit-score, …) and align the store index, flows,
app strings and docs to match. Bundles now use the .chain extension
(content-addressed; legacy .fai would still install).

- store/store.yaml: name: dash, wasm_url .chain, refreshed sha256
- store/SHA256.txt: 8 new .chain hashes
- flows + app/lib + RUN.md + MACHBARKEITSSTUDIE.md: capability refs _ -> -
- left untouched: text_akoma_normalize.wasm artifact, DB field skm_score,
  backlog module law.skm_score

Signed-off-by: flemming-it <sf@flemming.it>

flows/durchstich-gewo-14.yaml

@@ -1,11 +1,11 @@
 # Phase-0 vertikaler Durchstich für GewO §14.
 #
 # Minimaler Pfad zum ersten echten flow.completed-Event im
-# Audit-Log — http.request → text.akoma_normalize →
-# stats.cohort_size → system.approval. Beweist, dass die
+# Audit-Log — http.request → text.akoma-normalize →
+# stats.cohort-size → system.approval. Beweist, dass die
 # Recl∆Im-Pipeline live gegen den Ch∆In-Hub läuft. Die
-# komplexen Bewertungs-Schritte (econ.skm_score,
-# law.benefit_score, graph.shapley_attribution) bündeln wir in
+# komplexen Bewertungs-Schritte (econ.skm-score,
+# law.benefit-score, graph.shapley-attribution) bündeln wir in
 # einem zweiten Flow, wenn dieser hier durchläuft.
 #
 # Voraussetzung — alle Module installieren:
@@ -31,13 +31,13 @@ steps:
       method: "GET"
 
   - id: normalize
-    use: text.akoma_normalize@^0
+    use: text.akoma-normalize@^0
     with:
       content: $pull.body
       mime: "application/xml"
 
   - id: cohort
-    use: stats.cohort_size@^0
+    use: stats.cohort-size@^0
     with:
       cohort_id: $inputs.cohort_id