docs: convert standard diagrams from draw.io PNGs to inline Mermaid

Gitea renders mermaid inline, so the flow/state/hierarchy/DAG diagrams move to text-in-markdown: auto-layout (removes the manual overlap-prone draw.io step), diffable source, no committed binaries, and a dark-text theme so labels stay legible. Keep draw.io PNGs only for the two complex bespoke diagrams (logical architecture, env2 topology) where pixel control still wins. All 24 mermaid blocks validated by rendering.
2026-06-01 00:23:00 -04:00
parent e3ca5ac0cf
commit 43228185b4
65 changed files with 848 additions and 2145 deletions
@@ -22,8 +22,47 @@ Central cluster only. The site-side deployment responsibilities (receiving confi

 ## Deployment Flow

-![deployment-flow](diagrams/deployment-flow.png)
-<!-- source: diagrams/deployment-flow.drawio — edit, then re-export with export-drawio.sh -->
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'textColor':'#111111','lineColor':'#555555','edgeLabelBackground':'#ffffff','fontSize':'15px'}}}%%
+flowchart TD
+    engineer(["Engineer (UI)"])
+
+    subgraph DMC["Deployment Manager (Central)"]
+        step1["1. Request validated and flattened config from Template Engine<br/>(validation: flattening, script compilation, trigger references,<br/>connection binding completeness)"]
+        step2{"2. Validation fails?"}
+        step2fail(["Return errors to UI, stop"])
+        step3["3. Send config to site via Communication Layer"]
+        step8[("8. Update deployment status in config DB")]
+    end
+
+    subgraph SR["Site Runtime (Deployment Manager Singleton)"]
+        step4[("4. Store new flattened config locally (SQLite)")]
+        step5["5. Compile scripts at site"]
+        step6["6. Create/update Instance Actor<br/>(with child Script + Alarm Actors)"]
+        step7["7. Report success/failure back to central"]
+    end
+
+    engineer --> step1
+    step1 --> step2
+    step2 -->|yes| step2fail
+    step2 -->|no| step3
+    step3 -->|config| step4
+    step4 --> step5
+    step5 --> step6
+    step6 --> step7
+    step7 -. "report success/failure" .-> step8
+
+    classDef start fill:#d5e8d4,stroke:#82b366,color:#111111;
+    classDef proc fill:#dae8fc,stroke:#6c8ebf,color:#111111;
+    classDef dec fill:#fff2cc,stroke:#d6b656,color:#111111;
+    classDef bad fill:#f8cecc,stroke:#b85450,color:#111111;
+    class engineer start
+    class step1,step5,step6,step7 dec
+    class step2,step2fail bad
+    class step3 dec
+    class step8 proc
+    class step4 start
+```

 ## Deployment Identity & Idempotency