docs+tools: workflow flowchart harness (P4) + drivers Tier-1/Tier-2 split

- tools/flowgen.py: generates docs/workflows/<name>.md — one outcome-first mermaid
  flowchart per workflow the SDK tests (hpmcu watchdog, modbus read, cru ladder,
  rga offload, relay drive, freshness contract), each stamped with its benchmark
  ns/op or 100% MC/DC result. Deterministic; reads the cargo-bench trend json.
- drivers/README.md: honest Tier-1 (relays + freshness, 100% MC/DC here now) vs
  Tier-2 (modbus/rga — serious testing + fault-injection + benchmarks via sim
  models; driver sources migrate in with the flare-edge unification) per ADR-0002/0005.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf

docs/workflows/cru-reset-ladder.md

@@ -0,0 +1,15 @@
+# CRU reset ladder: cause + boot-mode survival
+
+> **Outcome tested:** Reset cause is attributable and the boot-mode register survives a warm reset.
+
+**Benchmark** (`cru_poll`): 23.0 ns/op
+
+```mermaid
+flowchart TD
+  A[poll] --> B{global reset asserted?}
+  B -- no --> A
+  B -- yes --> C[record cause]
+  C --> D{power-on vs warm?}
+  D -- POR --> E[boot-mode cleared]
+  D -- warm --> F[boot-mode preserved]
+```