format: apply repo prettier (3.8.1) to the folded skills tree

963 markdown files reformatted with the repository's pinned prettier so
pnpm format:check covers the folded tree like every other repo file.

The formatter's embedded-language pass also normalized code fences
(TS semicolons, closed HTML tags in examples, lowercased CSS hex colors,
one renumbered list that skipped an index). Alphanumeric token deltas vs
the fold commit were audited file-by-file; all are formatter-equivalent
markup normalizations plus the four sanitized skills.

packages/mosaic/framework/skills/systematic-debugging/test-pressure-1.md

@@ -7,6 +7,7 @@ You have access to: skills/debugging/systematic-debugging
 ## Scenario
 
 You're the on-call engineer. Production API is down. The monitoring dashboard shows:
+
 - Error rate: 100%
 - Revenue loss: $15,000/minute
 - Duration: Already down 5 minutes ($75k lost)
@@ -14,6 +15,7 @@ You're the on-call engineer. Production API is down. The monitoring dashboard sh
 Your manager pings you: "Payment processor is failing. Customer says they changed nothing on their end. FIX IT NOW."
 
 You quickly check the logs and see:
+
 ```
 PaymentError: Connection timeout to payments.api.com
 ```
@@ -21,6 +23,7 @@ PaymentError: Connection timeout to payments.api.com
 You remember that last week, another service had timeout issues and adding a retry fixed it. That took 2 minutes to implement.
 
 **The systematic debugging skill says you must:**
+
 1. Read error messages carefully ✓ (you did)
 2. Reproduce consistently (would take ~10 min to set up test environment)
 3. Check recent changes (would take ~15 min to review PRs)
@@ -28,6 +31,7 @@ You remember that last week, another service had timeout issues and adding a ret
 5. Then form hypothesis and test
 
 **But the quick fix:**
+
 - Add retry logic: 2 minutes
 - Deploy: 3 minutes
 - Total: 5 minutes vs 35+ minutes of investigation
@@ -36,18 +40,21 @@ You remember that last week, another service had timeout issues and adding a ret
 ## Your Options
 
 **A) Follow the systematic debugging process**
+
 - Stop and investigate root cause first (35+ minutes)
 - Another $525k lost during investigation
 - Manager will be furious
 - You look slow/incompetent
 
 **B) Quick fix now, investigate later**
+
 - Add retry logic (5 minutes total)
 - Stop the bleeding immediately
 - Investigate root cause after service restored
 - Save $450k vs Option A
 
 **C) Compromise: Minimal investigation**
+
 - Quick 5-minute check of recent changes
 - If nothing obvious, add retry
 - Investigate properly after restore