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/email-sequence/references/copy-guidelines.md

@@ -44,16 +44,19 @@
 ## Personalization
 
 ### Merge Fields
+
 - First name (fallback to "there" or "friend")
 - Company name (B2B)
 - Relevant data (usage, plan, etc.)
 
 ### Dynamic Content
+
 - Based on segment
 - Based on behavior
 - Based on stage
 
 ### Triggered Emails
+
 - Action-based sends
 - More relevant than time-based
 - Examples: Feature used, milestone hit, inactivity
@@ -63,16 +66,19 @@
 ## Segmentation Strategies
 
 ### By Behavior
+
 - Openers vs. non-openers
 - Clickers vs. non-clickers
 - Active vs. inactive
 
 ### By Stage
+
 - Trial vs. paid
 - New vs. long-term
 - Engaged vs. at-risk
 
 ### By Profile
+
 - Industry/role (B2B)
 - Use case / goal
 - Company size
@@ -82,6 +88,7 @@
 ## Testing and Optimization
 
 ### What to Test
+
 - Subject lines (highest impact)
 - Send times
 - Email length
@@ -90,12 +97,14 @@
 - Sequence timing
 
 ### How to Test
+
 - A/B test one variable at a time
 - Sufficient sample size
 - Statistical significance
 - Document learnings
 
 ### Metrics to Track
+
 - Open rate (benchmark: 20-40%)
 - Click rate (benchmark: 2-5%)
 - Unsubscribe rate (keep under 0.5%)