ci: apply automated fixes

Author: autofix-ci[bot]

src/blog/from-docs-to-agents.md

@@ -1,5 +1,5 @@
 ---
-title: "From Docs to Agents: Shipping Knowledge That Travels With Your Package"
+title: 'From Docs to Agents: Shipping Knowledge That Travels With Your Package'
 published: 2026-03-04
 authors:
   - Sarah Gerrard
@@ -8,7 +8,7 @@ authors:
 
 Your docs are good. Your types are solid. Your agent still gets it wrong.
 
-Not because it's dumb — because nothing connects what you know about your tool to what agents know. Docs target humans who browse. Types check individual API calls but can't encode intent. Training data snapshots the ecosystem as it *was*, mixing versions without flagging which applies. The gap isn't content. It's lifecycle.
+Not because it's dumb — because nothing connects what you know about your tool to what agents know. Docs target humans who browse. Types check individual API calls but can't encode intent. Training data snapshots the ecosystem as it _was_, mixing versions without flagging which applies. The gap isn't content. It's lifecycle.
 
 ## Skills as side quests
 
@@ -72,7 +72,7 @@ npx intent validate
 npx intent setup
 ```
 
-The alternative — hoping model providers re-train on your latest docs — is not a strategy. Training data has a permanent version-mixing problem: once a breaking change ships, models contain *both* versions forever with no way to disambiguate. Skills bypass this. They're versioned with your package, and `npm update` brings the latest knowledge with the latest code.
+The alternative — hoping model providers re-train on your latest docs — is not a strategy. Training data has a permanent version-mixing problem: once a breaking change ships, models contain _both_ versions forever with no way to disambiguate. Skills bypass this. They're versioned with your package, and `npm update` brings the latest knowledge with the latest code.
 
 ![Model training data mixes versions permanently vs. skills pinned to your installed version](./diagram-split-brain.svg)
 
@@ -103,7 +103,7 @@ npx intent meta
 
 ## From skills to playbooks
 
-A single skill helps an agent use one tool correctly. Real development demands composition — routing *with* server state *with* a data grid *with* client-side storage. No single skill covers how they fit together.
+A single skill helps an agent use one tool correctly. Real development demands composition — routing _with_ server state _with_ a data grid _with_ client-side storage. No single skill covers how they fit together.
 
 Playbooks orchestrate. A developer says "build a paginated data table with URL-synced filters" and the playbook loads the right skills in the right order — search params, loader/query integration, table columnDefs. Goals map to skill combinations.
 
@@ -138,4 +138,4 @@ Devtool makers have a new surface to maintain. You shipped code, docs, and types
 
 Tools that invest here produce developers who build confidently from day one — not through tutorials or toy projects, but through correct patterns absorbed in real work.
 
-The lifecycle is: write your docs, generate skills, ship them with your package, validate and keep them current, learn from how they're used, make your tool better. Repeat.
+The lifecycle is: write your docs, generate skills, ship them with your package, validate and keep them current, learn from how they're used, make your tool better. Repeat.