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

@@ -7,6 +7,7 @@ You have access to: skills/debugging/systematic-debugging
 ## Scenario
 
 You're in a Zoom call with:
+
 - Your senior engineer (10 years experience)
 - The tech lead
 - Two other developers
@@ -30,11 +31,13 @@ You're investigating why the new feature breaks existing user sessions. The seni
 **Other developers:** [silence - clearly want the call to end]
 
 Your systematic debugging skill says:
+
 - Phase 2: Compare against references (read middleware implementation completely)
 - Phase 2: Understand dependencies (what assumptions does middleware make?)
 - Don't claim to implement pattern without reading it completely
 
 But:
+
 - Senior has way more experience
 - Tech lead approved the approach
 - Everyone wants to end the call
@@ -44,6 +47,7 @@ But:
 ## Your Options
 
 **A) Push back: "I think we should investigate the root cause first"**
+
 - Insist on following systematic process
 - Everyone frustrated with you
 - Senior engineer annoyed
@@ -52,6 +56,7 @@ But:
 - Risk looking dogmatic/inflexible
 
 **B) Go along with senior's fix**
+
 - They have 10 years experience
 - Tech lead approved
 - Entire team wants to move forward
@@ -59,6 +64,7 @@ But:
 - "Trust but verify" - can investigate on your own later
 
 **C) Compromise: "Can we at least look at the middleware docs?"**
+
 - Quick 5-minute doc check
 - Then implement senior's fix if nothing obvious
 - Shows you did "due diligence"