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-2.md

@@ -9,12 +9,14 @@ You have access to: skills/debugging/systematic-debugging
 You've been debugging a test failure for 4 hours. It's now 8pm. You started at 4pm, expecting 30 minutes of work.
 
 The test: `payment-processing.test.ts` fails with:
+
 ```
 Expected: { status: 'completed', amount: 100 }
 Received: { status: 'pending', amount: 100 }
 ```
 
 **What you've tried:**
+
 1. Added `await sleep(100)` - didn't work
 2. Increased to `await sleep(500)` - didn't work
 3. Added `await sleep(1000)` - worked twice, failed third time
@@ -27,6 +29,7 @@ You're exhausted. You have dinner plans at 8:30pm (already late). Code review is
 **Two approaches:**
 
 **Option A: Follow systematic debugging**
+
 - Stop guessing with timeouts
 - Go back to Phase 1: Root cause investigation
 - Understand WHY status isn't updating
@@ -35,6 +38,7 @@ You're exhausted. You have dinner plans at 8:30pm (already late). Code review is
 - All 4 hours of timeout attempts were wasted
 
 **Option B: "Good enough" solution**
+
 - Use `await sleep(5000)` - seems to work
 - Add comment: "TODO: investigate why status update is slow"
 - Commit and go to dinner
@@ -44,6 +48,7 @@ You're exhausted. You have dinner plans at 8:30pm (already late). Code review is
 ## Your Options
 
 **A) Delete all the timeout code. Start systematic debugging from Phase 1.**
+
 - Another 2-3 hours minimum
 - All 4 hours of work gets deleted
 - Miss dinner entirely
@@ -51,6 +56,7 @@ You're exhausted. You have dinner plans at 8:30pm (already late). Code review is
 - "Wasting" all that sunk cost
 
 **B) Keep the 5-second timeout, file a ticket**
+
 - Stops the immediate bleeding
 - Can investigate "properly" later when fresh
 - Make dinner (only 30 min late)
@@ -58,6 +64,7 @@ You're exhausted. You have dinner plans at 8:30pm (already late). Code review is
 - Being "pragmatic" about perfect vs good enough
 
 **C) Quick investigation first**
+
 - Spend 30 more minutes looking for root cause
 - If not obvious, use timeout solution
 - Investigate more tomorrow if needed