[docs] Fix pre-existing markdownlint errors across 15 files (NateBJones-Projects#161)

* Fix pre-existing markdownlint errors across 15 files

Add blank lines around headings (MD022), fenced code blocks (MD031),
and between adjacent blockquotes (MD028). Fix broken link fragment
(MD051) and remove extra blank line (MD012). No content changes.

These errors were blocking CI on all open PRs since the lint check
runs repo-wide.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* [docs] Preserve README links during markdown cleanup

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Jonathan Edwards <justfinethanku@gmail.com>

Author: 3 people

docs/03-faq.md

@@ -173,6 +173,7 @@ When you generate a new key on openrouter.ai/keys, the old key is revoked immedi
 **Places your OpenRouter key lives (update ALL of them):**
 
 1. **Supabase Edge Function secrets** — This is the most common one to miss. Your MCP server reads the key from here at runtime.
+
    ```bash
    supabase secrets set OPENROUTER_API_KEY=sk-or-v1-your-new-key
    ```

docs/05-tool-audit.md

@@ -81,6 +81,7 @@ Once you've identified bloat, here are the patterns for consolidating.
 Instead of 5 separate tools per table, expose one tool with an `action` parameter:
 
 **Before (5 tools):**
+
 ```
 create_recipe
 get_recipe
@@ -90,6 +91,7 @@ list_recipes
 ```
 
 **After (1 tool):**
+
 ```
 manage_recipe
   action: "create" | "read" | "update" | "delete" | "list"
@@ -107,6 +109,7 @@ manage_recipe
 A gentler consolidation that preserves clear intent:
 
 **Before (5 tools):**
+
 ```
 create_recipe
 get_recipe
@@ -116,6 +119,7 @@ search_recipes
 ```
 
 **After (2 tools):**
+
 ```
 save_recipe       — creates or updates (upsert pattern)
 query_recipes      — search, filter, get by ID, list all
@@ -132,6 +136,7 @@ This maps to how people actually talk to their AI: "save this" or "find that." T
 For tables with similar schemas (all your Open Brain extension tables follow the same `user_id` + timestamps + domain fields pattern), you can go further:
 
 **Before (20+ tools across 4 extensions):**
+
 ```
 add_household_item, search_household_items, get_item_details,
 add_vendor, list_vendors,
@@ -140,6 +145,7 @@ search_maintenance_history, add_family_member, ...
 ```
 
 **After (2–3 tools):**
+
 ```
 save_entity
   entity_type: "household_item" | "vendor" | "maintenance_task" | ...
@@ -177,6 +183,7 @@ Merging tools reduces count within a server. Scoping splits tools across servers
 Most Open Brain users' workflows fall into three modes:
 
 #### Capture server (write-heavy)
+
 **When you use it:** Quick capture moments — jotting down a thought, logging a contact interaction, saving a recipe.
 
 **Tools to include:**
@@ -189,6 +196,7 @@ Most Open Brain users' workflows fall into three modes:
 **Context cost:** ~5–8 tools, ~1,500–3,000 tokens.
 
 #### Query server (read-heavy)
+
 **When you use it:** Research, recall, weekly reviews, planning sessions — any time you're pulling information out rather than putting it in.
 
 **Tools to include:**
@@ -202,6 +210,7 @@ Most Open Brain users' workflows fall into three modes:
 **Context cost:** ~8–12 tools, ~3,000–5,000 tokens.
 
 #### Admin server (rarely used)
+
 **When you use it:** Occasional maintenance — bulk updates, deletions, schema changes, data cleanup.
 
 **Tools to include:**

integrations/slack-capture/README.md

@@ -240,6 +240,8 @@ Replace the values with:
 
 > SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY are automatically available inside Edge Functions — you don't need to set them.
 
+<!-- -->
+
 > **If you ever rotate your OpenRouter key:** you must re-run `supabase secrets set OPENROUTER_API_KEY=...` with the new key. This Edge Function reads the key from Supabase secrets at runtime — updating it on openrouter.ai alone won't propagate here. See the [FAQ on key rotation](../../docs/03-faq.md#api-key-rotation) for the full checklist.
 
 ### Deploy

recipes/grok-export-import/README.md

@@ -37,24 +37,28 @@ FROM OPENROUTER
    - Find the Grok JSON file in the export
 
 2. **Copy this recipe folder** and install dependencies:
+
    ```bash
    cd grok-export-import
    npm install
    ```
 
 3. **Create `.env`** with your credentials (see `.env.example`):
+
    ```env
    SUPABASE_URL=https://your-project.supabase.co
    SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
    OPENROUTER_API_KEY=sk-or-v1-your-key
    ```
 
 4. **Preview what will be imported** (dry run):
+
    ```bash
    node import-grok.mjs /path/to/grok-export.json --dry-run
    ```
 
 5. **Run the import:**
+
    ```bash
    node import-grok.mjs /path/to/grok-export.json
    ```

recipes/instagram-import/README.md

@@ -53,30 +53,35 @@ FROM OPENROUTER
    - Look for the `your_instagram_activity/` folder
 
 2. **Copy this recipe folder** and install dependencies:
+
    ```bash
    cd instagram-import
    npm install
    ```
 
 3. **Create `.env`** with your credentials (see `.env.example`):
+
    ```env
    SUPABASE_URL=https://your-project.supabase.co
    SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
    OPENROUTER_API_KEY=sk-or-v1-your-key
    ```
 
 4. **Preview what will be imported** (dry run):
+
    ```bash
    node import-instagram.mjs /path/to/instagram-export --dry-run
    ```
 
 5. **Import specific types only** (optional):
+
    ```bash
    node import-instagram.mjs /path/to/instagram-export --types messages
    node import-instagram.mjs /path/to/instagram-export --types comments,posts
    ```
 
 6. **Run the full import:**
+
    ```bash
    node import-instagram.mjs /path/to/instagram-export
    ```

recipes/journals-blogger-import/README.md

@@ -48,6 +48,7 @@ FROM OPENROUTER
    - If you have multiple blogs, export each one
 
 2. **Place all `.atom` files in a folder:**
+
    ```
    blogger-exports/
    ├── my-tech-blog.atom
@@ -56,24 +57,28 @@ FROM OPENROUTER
    ```
 
 3. **Copy this recipe folder** and install dependencies:
+
    ```bash
    cd journals-blogger-import
    npm install
    ```
 
 4. **Create `.env`** with your credentials (see `.env.example`):
+
    ```env
    SUPABASE_URL=https://your-project.supabase.co
    SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
    OPENROUTER_API_KEY=sk-or-v1-your-key
    ```
 
 5. **Preview what will be imported** (dry run):
+
    ```bash
    node import-blogger.mjs /path/to/blogger-exports --dry-run
    ```
 
 6. **Run the import:**
+
    ```bash
    node import-blogger.mjs /path/to/blogger-exports
    ```

recipes/life-engine-video/README.md

@@ -7,6 +7,8 @@ An add-on for [Life Engine](../life-engine/) that replaces (or supplements) text
 > [!IMPORTANT]
 > **Built for [Claude Code](https://claude.ai/download), but not exclusive to it.** The Life Engine core requires Claude Code (it depends on `/loop` and skills), but this video add-on — the Remotion rendering, ElevenLabs TTS, and pipeline scripting — can be driven by any capable AI coding agent. ChatGPT handles Remotion well; other agents may work too. If you're adapting this to a different tool, the architecture and components in this guide give you everything you need.
 
+<!-- -->
+
 > [!NOTE]
 > **Expect iteration.** Your first rendered video will have timing issues, subtitle drift, or a voiceover script that sounds stilted. That's normal. Each render gives you feedback — adjust the VO script guidelines, tweak the subtitle chunking, tune the ElevenLabs voice settings. The structured data flowing from your Open Brain means the *content* improves automatically as your knowledge base grows. The *presentation* improves as you and your agent dial in the rendering pipeline together.
 
@@ -320,6 +322,7 @@ export const SubtitleBar: React.FC<{
   );
 };
 ```
+
 </details>
 
 <details>
@@ -341,6 +344,7 @@ export const ProgressBar: React.FC = () => {
   );
 };
 ```
+
 </details>
 
 <details>
@@ -390,6 +394,7 @@ export const TaskCard: React.FC<{
   );
 };
 ```
+
 </details>
 
 <details>
@@ -435,6 +440,7 @@ export const SectionHeader: React.FC<{
   );
 };
 ```
+
 </details>
 
 ### 2.3 Scene Components
@@ -486,6 +492,7 @@ export const TitleScene: React.FC<{
   );
 };
 ```
+
 </details>
 
 ### 2.4 Main Composition
@@ -761,15 +768,19 @@ Place in `public/music.mp3`. The composition plays it at 12-15% volume under the
 ## Going Further
 
 ### Dynamic Scene Assembly
+
 Instead of fixed scene types, let Claude decide which scenes to include based on the data. If there are no habits, skip the habits scene. If there's a lot of OB1 context for a meeting, add an extra context scene. The composition adapts to the data.
 
 ### Weekly Recap Videos
+
 Every Sunday, render a 60-second recap of the week: meetings attended, habits completed, mood trends, and highlights. Use chart/graph animations for habit streaks.
 
 ### Voice Briefings (Audio Only)
+
 Skip the video render entirely and just send the TTS audio as a voice message via Telegram. Much faster (seconds instead of minutes), still personal. Good for quick habit reminders.
 
 ### Screen Recording Integration
+
 For meeting prep, capture a screenshot of the client's website or relevant dashboard and animate it into the prep briefing video. Use `@remotion/gif` to embed Chrome GIF captures.
 
 ---

recipes/live-retrieval/live-retrieval.skill.md

@@ -61,6 +61,7 @@ Do NOT fire on:
 Append a brief note to your response. Maximum 3 lines. Do not interrupt flow.
 
 Format:
+
 ```
 [OB1: Found 2 related thoughts]
 - "ACT NOW: [summary]" (captured March 14)

recipes/obsidian-vault-import/README.md

@@ -63,30 +63,38 @@ FILE LOCATION
 1. **Clone or copy this recipe folder** to your local machine.
 
 2. **Install Python dependencies:**
+
    ```bash
    cd recipes/obsidian-vault-import
    pip install -r requirements.txt
    ```
 
 3. **Create your `.env` file** from the example:
+
    ```bash
    cp .env.example .env
    ```
+
    Edit `.env` and fill in your Supabase URL, API key, and OpenRouter API key. Find your Supabase credentials in the dashboard under Settings → API.
 
 4. **Run a dry run first** to see what would be imported:
+
    ```bash
    python import-obsidian.py /path/to/your/vault --dry-run --verbose
    ```
+
    This scans your vault, shows how many notes pass filters, how many thoughts would be generated, and flags any notes containing potential secrets — without inserting anything.
 
 5. **Start with a small batch** to verify everything works:
+
    ```bash
    python import-obsidian.py /path/to/your/vault --limit 20 --verbose
    ```
+
    The script runs a preflight check before any import — it verifies your Supabase connection and OpenRouter API key before spending time on chunking or embeddings.
 
 6. **Run the full import** once you're satisfied:
+
    ```bash
    python import-obsidian.py /path/to/your/vault --verbose
    ```
@@ -132,6 +140,7 @@ The script automatically skips notes that wouldn't make useful thoughts. Run wit
 **Date-filtered notes** — when using `--after YYYY-MM-DD`, notes not modified after that date are skipped.
 
 **Additional folder exclusions** — use `--skip-folders` for vault-specific directories you don't want imported:
+
 ```bash
 # Skip framework reference materials, archive, and attachments
 python import-obsidian.py /path/to/vault --skip-folders "Archive,Files,patterns"

recipes/perplexity-conversation-import/README.md

@@ -222,6 +222,7 @@ For a typical export with 100 conversations and 50 memory entries, total cost is
 ## Troubleshooting
 
 **"No module named 'openpyxl'"**
+
 ```bash
 pip install openpyxl>=3.1
 ```
@@ -230,16 +231,19 @@ pip install openpyxl>=3.1
 Your export may use different sheet names. Open the file in a spreadsheet app and check the sheet tabs. The script looks for exact names "Conversations" and "Memory".
 
 **"OPENROUTER_API_KEY environment variable required"**
+
 ```bash
 export OPENROUTER_API_KEY="sk-or-v1-your-key"
 ```
+
 Or use `--model ollama` for local summarization (embeddings still need OpenRouter).
 
 **Summarization returns empty thoughts**
 Some Q&A pairs are too simple (e.g., "what time is it?"). This is expected — the LLM is designed to be selective. Try `--verbose` to see what's being skipped.
 
 **"Failed to generate embedding"**
 Check your OpenRouter API key has credits and access to `text-embedding-3-small`. Test with:
+
 ```bash
 curl https://openrouter.ai/api/v1/embeddings \
   -H "Authorization: Bearer $OPENROUTER_API_KEY" \