fix: resolve markdownlint errors in 5 files

- quickstart.md: merge adjacent blockquotes (MD028)
- AGENTS.md: add language to fenced code block (MD040), blank line before list (MD032)
- FORK_DIVERGENCE.md: renumber ordered list items to be sequential (MD029)
- spec-driven.md: add blank lines before lists (MD032)
- personalize.md: add language to fenced code blocks (MD040)

Author: markhazleton

.documentation/quickstart.md

@@ -4,7 +4,7 @@ This guide will help you get started with Spec-Driven Development using Spec Kit
 
 > [!NOTE]
 > All automation scripts now provide both Bash (`.sh`) and PowerShell (`.ps1`) variants. The `specify` CLI auto-selects based on OS unless you pass `--script sh|ps`.
-
+>
 > [!TIP]
 > **Agent-Agnostic**: Spec Kit works identically with any of 17+ supported AI agents. The workflow below applies regardless of which agent you choose — canonical prompts live in `.documentation/commands/` and your agent gets thin shims that redirect there.
 

AGENTS.md

@@ -16,7 +16,7 @@ Spec Kit uses an **agnostic-by-default** architecture. All command prompts, scri
 
 ### File Layout
 
-```
+```text
 .documentation/
 ├── commands/                    ← Canonical command prompts (agent-agnostic)
 │   ├── speckit.specify.md
@@ -40,6 +40,7 @@ Spec Kit uses an **agnostic-by-default** architecture. All command prompts, scri
 ### Shim Behavior
 
 Each platform shim:
+
 1. Resolves the current git user (`git config user.name`, slug-normalized)
 2. Checks for a personalized override at `.documentation/{git-user}/commands/speckit.{cmd}.md`
 3. Falls back to the shared default at `.documentation/commands/speckit.{cmd}.md`

FORK_DIVERGENCE.md

@@ -43,20 +43,20 @@ This document tracks how **Spec Kit Spark** has diverged from and absorbed chang
    - `/speckit.release` - Release documentation management
    - `/speckit.personalize` - Per-user prompt customization
 
-5. **Documentation Structure**
+4. **Documentation Structure**
    - Renamed `.specify/` → `.documentation/` for clarity
    - Extensive migration guides and tooling
    - Constitution guide, critic usage guide, PR review implementation
    - Adaptive lifecycle documentation
 
-6. **Scripts & Automation**
+5. **Scripts & Automation**
    - `evolution-context.sh/ps1` - Constitution evolution support
    - `get-pr-context.sh/ps1` - PR context extraction
    - `quickfix-context.sh/ps1` - Lightweight fix workflow
    - `release-context.sh/ps1` - Release management
    - `site-audit.sh/ps1` - Website auditing
 
-7. **Repository Health**
+6. **Repository Health**
    - Git Spark reports (HTML/MD)
    - Enhanced branch protection documentation
    - Fork-specific release management

spec-driven.md

@@ -67,6 +67,7 @@ SDD is a methodology, not a tool — and Spec Kit embodies this principle throug
 The same specification workflow works identically whether your team uses Claude Code, GitHub Copilot, Gemini CLI, Cursor, or any of 17+ supported agents. Canonical prompts live in `.documentation/commands/` as a single source of truth; platform-specific directories (`.claude/`, `.github/`, `.cursor/`, etc.) contain only thin shims that redirect to the canonical content.
 
 This means:
+
 - **No agent lock-in** — switch tools without losing workflow structure
 - **Mixed-agent teams** — different team members can use their preferred AI assistant on the same project
 - **Consistent governance** — the same constitution and quality gates apply regardless of which agent executes them
@@ -76,6 +77,7 @@ This means:
 Teams share constitutions, specs, and workflow governance — but individuals can customize how they interact with those workflows. The `/speckit.personalize` command creates per-user prompt overrides in `.documentation/{git-user}/commands/` that take priority over shared defaults.
 
 This balances:
+
 - **Team benefit** — shared standards, consistent output quality, unified governance
 - **Individual freedom** — each developer can tune prompts to their thinking style, add personal checklists, or emphasize areas they care about
 - **Transparency** — personalized overrides are committed to git, so the team can see and review each other's customizations

templates/commands/personalize.md

@@ -56,7 +56,7 @@ over the shared defaults in `.documentation/commands/` when any speckit command
 
 4. **Create the user directory structure**:
 
-   ```
+   ```text
    .documentation/{git-user}/commands/
    ```
 
@@ -85,7 +85,7 @@ over the shared defaults in `.documentation/commands/` when any speckit command
 
 7. **Inform the user**:
 
-   ```
+   ```text
    Created personalized prompt:
      .documentation/{git-user}/commands/speckit.{command}.md