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/internal-comms/SKILL.md

@@ -5,7 +5,9 @@ license: Complete terms in LICENSE.txt
 ---
 
 ## When to use this skill
+
 To write internal communications, use this skill for:
+
 - 3P updates (Progress, Plans, Problems)
 - Company newsletters
 - FAQ responses
@@ -20,13 +22,14 @@ To write any internal communication:
 
 1. **Identify the communication type** from the request
 2. **Load the appropriate guideline file** from the `examples/` directory:
-    - `examples/3p-updates.md` - For Progress/Plans/Problems team updates
-    - `examples/company-newsletter.md` - For company-wide newsletters
-    - `examples/faq-answers.md` - For answering frequently asked questions
-    - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
+   - `examples/3p-updates.md` - For Progress/Plans/Problems team updates
+   - `examples/company-newsletter.md` - For company-wide newsletters
+   - `examples/faq-answers.md` - For answering frequently asked questions
+   - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
 3. **Follow the specific instructions** in that file for formatting, tone, and content gathering
 
 If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
 
 ## Keywords
+
 3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms