chore(docs): finalize markdownlint cleanups and branding

- apply remaining markdown formatting fixes in docs and agent prompts
- remove trailing-space and list-spacing markdownlint issues in repo docs
- update CLI tagline branding text

Author: markhazleton

.github/agents/speckit.harvest.agent.md

@@ -29,6 +29,7 @@ Harvest valuable knowledge from completed specs, stale documentation, and in-pro
 Additionally, scan source code for comments that reference completed specs, plans, or tasks and rewrite them as self-contained code documentation.
 
 The output is:
+
 1. Updated living documents (CHANGELOG, Guide.md) with harvested knowledge
 2. Cleaned code comments (spec references → self-contained descriptions)
 3. Stale files moved to `.archive/` with preserved folder structure
@@ -125,6 +126,7 @@ For each file in `.documentation/` (recursive, never `.archive/`):
 | **Living Reference** | Top-level `.documentation/*.md`, Guide.md, CHANGELOG.md | Keep — may update |
 
 **Never archive:**
+
 - `/.documentation/memory/constitution.md`
 - `/.documentation/scripts/` and `/.documentation/templates/`
 - `/.documentation/Guide.md` — update it instead
@@ -206,6 +208,7 @@ If the user says **modify**, apply their changes to the plan and re-present befo
 #### 4a. Update CHANGELOG.md
 
 For each completed spec NOT already in CHANGELOG:
+
 1. Read the spec's `spec.md`, `plan.md`, and `tasks.md`
 2. Extract: spec number, key changes, what was delivered
 3. Prepend a new entry above existing content:
@@ -225,6 +228,7 @@ Never modify existing CHANGELOG entries.
 #### 4b. Update .documentation/Guide.md
 
 If completed specs introduced:
+
 - New patterns or conventions → update the relevant section
 - New directories or files in `.documentation/` → update the directory map
 - Deprecated old patterns → note the deprecation
@@ -234,6 +238,7 @@ The guide describes the **current state only** — no historical content.
 #### 4c. Update .github/copilot-instructions.md (if it exists)
 
 If completed specs introduced:
+
 - New import paths, module names, or architectural patterns
 - New document schemas or field names
 - Deprecations of old patterns
@@ -249,6 +254,7 @@ For each spec/task reference identified in the pre-scan:
 3. Apply the edit
 
 **Rules**:
+
 - Never remove a comment without understanding its purpose first
 - If the comment accurately describes behavior but just has a spec prefix, strip only the prefix
 - If the comment is a pure task marker with no behavioral value, remove it entirely
@@ -268,6 +274,7 @@ For each spec/task reference identified in the pre-scan:
 6. After moving, verify no active file references the archived paths
 
 **Do not move:**
+
 - `/.documentation/memory/constitution.md`
 - `/.documentation/scripts/`
 - `/.documentation/templates/`

CONTRIBUTING.md

@@ -106,6 +106,7 @@ To test your templates, commands, and other changes locally, follow these steps:
 ```
 
 Interactive mode provides:
+
 - Detailed commit analysis (author, date, files changed, diff stats)
 - Implications explained for each category (AUTO/ADAPT/IGNORE/EVALUATE)
 - Conflict detection with Spark-specific files

README.md

@@ -1169,6 +1169,7 @@ See **[FORK_DIVERGENCE.md](./FORK_DIVERGENCE.md)** for:
 ```
 
 This mode:
+
 - Shows full commit details and file changes
 - Explains implications for Spark architecture
 - Detects potential conflicts with Spark-specific files

extensions/README.md

@@ -10,14 +10,16 @@ Community-contributed extensions for [Spec Kit Spark](https://github.com/MarkHaz
 
 ## Adding Your Extension
 
-Extensions provide a way to add specialized workflows and commands to Spec Kit Spark without modifying the core. 
+Extensions provide a way to add specialized workflows and commands to Spec Kit Spark without modifying the core.
 
 **For Extension Developers:**
+
 - Extensions can provide custom commands, hooks, and templates
 - Package your extension as a GitHub repository with proper structure
 - Submit to the community catalog via pull request
 
 **For Extension Users:**
+
 - Browse available extensions in `catalog.community.json`
 - Install extensions to add domain-specific workflows (regulatory compliance, specialized testing, etc.)
 - Extensions work alongside Spark's built-in commands (`/speckit.critic`, `/speckit.quickfix`, etc.)

release_notes.md

@@ -28,17 +28,20 @@ You can use these releases with your agent of choice. We recommend using the Spe
 ## Recent Changes
 
 ### Version 1.1.0 (February 8, 2026)
+
 - New `specify upgrade` command for simplified project upgrades
 - Migration scripts for Windows (PowerShell) and Linux/Mac (Bash)
 - Comprehensive migration documentation and guides
 - Auto-detection of AI assistants and migration needs
 - Dry-run mode and safety checks for upgrade process
 
 ### Version 1.0.3 (February 6, 2026)
+
 - Fixed critical double documentation path bug
 - Enhanced path transformation regex patterns
 
 ### Version 1.0.0 (February 3, 2026)
+
 - First major release with standard semantic versioning
 - Transition to `.documentation/` directory structure
 - Constitution-powered commands

src/specify_cli/__init__.py

@@ -241,7 +241,7 @@ def _format_rate_limit_error(status_code: int, headers: httpx.Headers, url: str)
 ╚══════╝╚═╝     ╚══════╝ ╚═════╝╚═╝╚═╝        ╚═╝   
 """
 
-TAGLINE = "GitHub Spec Kit - Spec-Driven Development Toolkit"
+TAGLINE = "Spec Kit Spark (markhazleton) - Spec-Driven Development Toolkit"
 class StepTracker:
     """Track and render hierarchical steps without emojis, similar to Claude Code tree output.
     Supports live auto-refresh via an attached refresh callback.