fix: correct README docker image tags and version badge; update bump-version skill

- Replace all :main image references with :latest (CI publishes :latest on main merges, not :main)
- Fix version badge from /release/ to /tag/ endpoint — CI creates git tags, not GitHub Releases
- Update stale version format note (now {major}.{minor}.{patch} via version.properties)
- Add Step 8 to bump-version skill: README pre-PR checklist for image tag and badge verification

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: jpicklyk

.claude/skills/bump-version.md

@@ -211,7 +211,39 @@ block instead of executing it.
 
 ---
 
-## Step 8 — Print Summary
+## Step 8 — Pre-PR Checklist
+
+Before printing the summary, verify these items in the README and fix any that are stale. Do NOT stage extra files — if fixes are needed, include them in the same staged set before the PR is created.
+
+**README checks (run grep to verify):**
+
+```bash
+grep -n "ghcr.io/jpicklyk/task-orchestrator" README.md
+```
+
+Every Docker image reference must use `:latest` — never a branch name (`:main`, `:overhaul`, etc.) or a hardcoded version tag. The CI workflow publishes `:latest` on every merge to `main`; pinned semver tags (e.g., `:2.0.1`) are also published but should not appear in the Quick Start instructions.
+
+**Version badge** (line ~7 in README):
+
+The badge must use the `shields.io/github/v/tag/` endpoint (not `/release/`) because the CI workflow creates git tags, not GitHub Releases:
+
+```
+[![Version](https://img.shields.io/github/v/tag/jpicklyk/task-orchestrator?sort=semver)](...)
+```
+
+The badge auto-updates when CI pushes the `vX.Y.Z` tag after merge — no manual update needed.
+
+**If fixes are required**, make the edits, then:
+
+```bash
+git add README.md version.properties CHANGELOG.md
+```
+
+and re-confirm `git status` shows only those three files staged.
+
+---
+
+## Step 9 — Print Summary
 
 Output a brief summary:
 

README.md

@@ -4,7 +4,7 @@
 
 An orchestration framework for AI coding assistants that solves context pollution and token exhaustion — enabling your AI to work on complex projects without running out of memory.
 
-[![Version](https://img.shields.io/github/v/release/jpicklyk/task-orchestrator?include_prereleases)](https://github.com/jpicklyk/task-orchestrator/releases)
+[![Version](https://img.shields.io/github/v/tag/jpicklyk/task-orchestrator?sort=semver)](https://github.com/jpicklyk/task-orchestrator/releases)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 [![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-purple)](https://modelcontextprotocol.io)
 
@@ -64,7 +64,7 @@ claude mcp add-json mcp-task-orchestrator '{
     "-v", "mcp-task-data:/app/data",
     "-v", "${workspaceFolder}:/project:ro",
     "-e", "AGENT_CONFIG_DIR=/project",
-    "ghcr.io/jpicklyk/task-orchestrator:main"
+    "ghcr.io/jpicklyk/task-orchestrator:latest"
   ]
 }'
 ```
@@ -85,7 +85,7 @@ Add to `.mcp.json` in your project root (checked into source control so teammate
         "-v", "mcp-task-data:/app/data",
         "-v", "${workspaceFolder}:/project:ro",
         "-e", "AGENT_CONFIG_DIR=/project",
-        "ghcr.io/jpicklyk/task-orchestrator:main"
+        "ghcr.io/jpicklyk/task-orchestrator:latest"
       ]
     }
   }
@@ -97,7 +97,7 @@ The `mcp-task-data` Docker volume persists the SQLite database across container
 ### Option C: Other MCP Clients
 
 ```bash
-docker pull ghcr.io/jpicklyk/task-orchestrator:main
+docker pull ghcr.io/jpicklyk/task-orchestrator:latest
 ```
 
 Configure your client with the same JSON above. STDIO transport works with any MCP-compatible client.
@@ -403,7 +403,7 @@ See [Contributing Guidelines](CONTRIBUTING.md) for detailed development setup.
 - [Watch releases](../../releases) — Get notified of new versions
 - [View changelog](CHANGELOG.md) — See what's changed
 
-**Version format**: `{major}.{minor}.{patch}.{git-commit-count}-{qualifier}`
+**Version format**: `{major}.{minor}.{patch}` — managed via `version.properties`; bumped manually before merge using `/bump-version`
 
 ---
 
@@ -422,7 +422,7 @@ AI coding tools, AI pair programming, Model Context Protocol, MCP server, Claude
 **Ready to build complex features without context limits?**
 
 ```bash
-docker pull ghcr.io/jpicklyk/task-orchestrator:main
+docker pull ghcr.io/jpicklyk/task-orchestrator:latest
 ```
 
 Then follow the [Quick Start Guide](current/docs/quick-start.md) to configure your AI platform.