Removed the before/after plaintext-secrets Mermaid diagram (the bullets right below it already said the same thing more clearly) and the Architecture flowchart (its per-host labels were silently missing registry-token and Hawser-secret details that didn't fit in the boxes). Replaced the flowchart with an accurate, complete "who gets what" table sourced directly from Trilium, one sentence for the proxy-routing fact it was trying to show, and a new sequence diagram for the actual secret lifecycle (auth -> render -> read -> async rotation) - a genuinely different kind of diagram since that's process/time-ordered information a table can't represent well. Also restored real specificity Trilium had that the doc had flattened into vague language: the cert-renewal row now names Technitium specifically and states the actual incident (an expired cert silently served for 19 days before the auto-rebuild hook existed), and the audit trail row now states the real rotation policy (weekly, 8 generations).
327 KiB
327 KiB