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
@@ -143,8 +143,33 @@ EF Core's DbContext naturally provides unit-of-work semantics:

 ### Example Transactional Flow

-![configdb-transactional-flow](diagrams/configdb-transactional-flow.png)
-<!-- source: diagrams/configdb-transactional-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
+    start(["Template Engine: Create Template"])
+    add1["repository.AddTemplate(template)<br/>// template is a Commons POCO"]
+    add2["repository.AddAttributes(attributes)<br/>// attributes are Commons POCOs"]
+    add3["repository.AddAlarms(alarms)<br/>// alarms are Commons POCOs"]
+    add4["repository.AddScripts(scripts)<br/>// scripts are Commons POCOs"]
+    save["repository.SaveChangesAsync()<br/>// single transaction commits all"]
+    db[("Configuration DB<br/>(MS SQL)")]
+
+    start --> add1
+    add1 --> add2
+    add2 --> add3
+    add3 --> add4
+    add4 --> save
+    save -. "single transaction" .-> db
+
+    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 muted fill:#f5f5f5,stroke:#999999,color:#666666;
+    class start start
+    class add1,add2,add3,add4 proc
+    class save dec
+    class db muted
+```

 ---

@@ -177,8 +202,31 @@ Audit entries are written **synchronously** within the same database transaction

 ### Integration Example

-![configdb-integration-example](diagrams/configdb-integration-example.png)
-<!-- source: diagrams/configdb-integration-example.drawio — edit, then re-export with export-drawio.sh -->
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'textColor':'#111111','lineColor':'#555555','edgeLabelBackground':'#ffffff','fontSize':'15px'}}}%%
+flowchart TD
+    start(["Template Engine: Update Template"])
+    upd["repository.UpdateTemplate(template)"]
+    audit["auditService.LogAsync(user, &quot;Update&quot;, &quot;Template&quot;,<br/>template.Id, template.Name, template)"]
+    save["repository.SaveChangesAsync()"]
+    note["both the change and audit entry<br/>commit together"]
+
+    start --> upd
+    upd --> audit
+    audit --> save
+    save -.- note
+
+    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 warn fill:#ffe6cc,stroke:#d79b00,color:#111111;
+    classDef alt fill:#e1d5e7,stroke:#9673a6,color:#111111;
+    class start start
+    class upd proc
+    class audit alt
+    class save dec
+    class note warn
+```

 ### Audit Entry Schema