chore: complete v1.1 milestone

Archived roadmap and requirements to milestones/v1.1-*.
Reorganized ROADMAP.md with collapsed v1.1 section.
Full PROJECT.md evolution review.
Retrospective updated with v1.1 lessons.
REQUIREMENTS.md deleted (fresh for next milestone).

Author: Stealinglight

.planning/MILESTONES.md

@@ -1,5 +1,17 @@
 # Milestones
 
+## v1.1 Docs, Pages & OpenClaw Positioning (Shipped: 2026-04-04)
+
+**Phases completed:** 2 phases, 3 plans, 5 tasks
+
+**Key accomplishments:**
+
+- Restored deploy-docs.yml workflow from deleted commit, deploying Jekyll docs site with just-the-docs dark theme to stealinglight.github.io/StravaMCP
+- README rewritten with production-grade agent framework positioning, Why Go? comparison table, and OpenClaw/ZeroClaw ecosystem Mermaid diagram
+- Docs site updated with production-grade positioning, Why Go? table, and new OpenClaw/ZeroClaw integration guide page with ecosystem diagram and wiring config
+
+---
+
 ## v1.0 StravaMCP Go Rewrite (Shipped: 2026-04-01)
 
 **Phases completed:** 3 phases, 8 plans, 18 tasks

.planning/PROJECT.md

@@ -18,6 +18,7 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 - ✓ File-based token store with automatic refresh persistence — v1.0
 - ✓ 11 MCP tools with full TypeScript feature parity — v1.0
 - ✓ Portfolio-quality README with badges, diagrams, tool reference — v1.0
+- ✓ GitHub Pages docs site with just-the-docs dark theme — v1.1 Phase 4
 - ✓ Production-grade positioning with Why Go? table, ecosystem diagram, integration guide — v1.1 Phase 5
 - ✓ Single-binary distribution via goreleaser with Homebrew — v1.0
 - ✓ Cross-platform builds (darwin/linux, amd64/arm64) — v1.0
@@ -44,12 +45,13 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 
 ## Context
 
-- v1.0 shipped: 4,791 LOC Go across 5 packages (auth, config, server, strava, tools)
+- v1.1 shipped: 4,791 LOC Go across 5 packages (auth, config, server, strava, tools)
 - 80+ tests passing, all packages covered
 - Tech stack: Go 1.25, mcp-go v0.46.0, goreleaser v2, GitHub Actions
-- Part of the RustyClaw/ZeroClaw ecosystem (local MCP servers for Strava, Slack, video, web-research)
+- Part of the OpenClaw/ZeroClaw ecosystem (local MCP servers for Strava, Slack, video, web-research)
 - All TypeScript/Lambda code removed — clean Go-only repository
-- Portfolio piece with polished README, badges, Mermaid diagrams
+- Production-grade README with Why Go? performance table, ecosystem Mermaid diagram, agent framework integration guide
+- GitHub Pages docs site live at stealinglight.github.io/StravaMCP with just-the-docs dark theme
 - The muscle group heat map renderer is being built separately and will integrate in a future milestone
 
 ## Constraints
@@ -76,18 +78,16 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 | Module path github.com/Stealinglight/StravaMCP | Enables `go install` and proper Go module ecosystem integration | ✓ Phase 3 |
 | goreleaser v2 with homebrew_casks | Cross-platform binary distribution + Homebrew tap | ✓ Phase 3 |
 | ISC License | Simple permissive license for open source distribution | ✓ Phase 3 |
+| Restore GitHub Pages from deleted commit | Exact workflow restoration safer than recreation from scratch | ✓ Phase 4 |
+| Production-grade positioning over portfolio framing | Agent framework users need credibility signals, not portfolio language | ✓ Phase 5 |
+| Estimated performance numbers with disclaimer | Avoids building Python/JS equivalents for benchmarks while still showing Go advantages | ✓ Phase 5 |
 | Add segments/routes/gear/laps | Expand beyond current 11 tools to comprehensive Strava coverage | — v2.0 |
 | Heat map as future milestone | Separate project, don't couple it to the core rewrite | — v2.0+ |
 
-## Current Milestone: v1.1 Docs, Pages & OpenClaw Positioning
+## Completed Milestones
 
-**Goal:** Fix GitHub Pages deployment, position StravaMCP as a high-performance Go MCP server for OpenClaw/ZeroClaw agent frameworks, and highlight Go speed advantages over Python/JavaScript MCPs.
-
-**Target features:**
-- Fix GitHub Pages deployment workflow (deleted during v1.0 cleanup)
-- Update README with OpenClaw/ZeroClaw ecosystem positioning and Go performance messaging
-- Update docs/ site with OpenClaw compatibility and performance claims
-- Position as production-grade MCP server for agent frameworks, not just a portfolio piece
+- **v1.0 Go Rewrite** (2026-04-01) — Full Go rewrite with 11 MCP tools, OAuth, goreleaser
+- **v1.1 Docs, Pages & OpenClaw Positioning** (2026-04-04) — GitHub Pages restoration, production-grade positioning, integration guide
 
 ## Current State
 
@@ -111,4 +111,4 @@ This document evolves at phase transitions and milestone boundaries.
 4. Update Context with current state
 
 ---
-*Last updated: 2026-04-04 after Phase 5 completion (v1.1 milestone)*
+*Last updated: 2026-04-04 after v1.1 milestone completion*

.planning/RETROSPECTIVE.md

@@ -44,21 +44,63 @@
 
 ---
 
+## Milestone: v1.1 — Docs, Pages & OpenClaw Positioning
+
+**Shipped:** 2026-04-04
+**Phases:** 2 | **Plans:** 3
+
+### What Was Built
+- Restored GitHub Pages deployment workflow from deleted commit, docs site live at stealinglight.github.io/StravaMCP
+- README rewritten with production-grade hero tagline, reliability-focused feature bullets, Why Go? performance comparison table
+- Agent Framework Integration section with OpenClaw/ZeroClaw ecosystem Mermaid diagram and JSON config snippet
+- New docs/integration.md page with ecosystem explainer, wiring configuration, 3 example workflows
+- docs/index.md mirrored with matching tagline, features, and performance table
+
+### What Worked
+- Wave dependency (README first → docs second) ensured docs could mirror canonical README content accurately
+- Human-verify checkpoint at Task 3 of Plan 02 gated deployment verification — right pattern for docs-only phases
+- Tone sweep with banned word list (portfolio, showcase, demo, etc.) systematically enforced positioning shift
+- UI-SPEC content contract defined exact copy for each section — executor had zero ambiguity
+
+### What Was Inefficient
+- REQUIREMENTS.md checkboxes for MSG-01 through MSG-04 weren't auto-updated during execution — required manual fix during milestone completion
+- 05-01-SUMMARY.md frontmatter didn't list requirements_completed for MSG-01/MSG-02 — caused "partial" status in 3-source cross-reference even though verification confirmed them
+
+### Patterns Established
+- Content Overlap Matrix in UI-SPEC for multi-file messaging consistency (README ↔ docs)
+- Banned word enforcement as a verification check (grep-based, zero tolerance)
+- Estimated performance numbers with explicit disclaimer footnote — avoids benchmark scope while showing Go advantages
+
+### Key Lessons
+1. For docs-only phases, the security gate passes trivially — SECURITY.md still gets created for audit trail consistency
+2. Wave structure for content phases should always have the canonical source (README) in Wave 1 and derived content (docs site) in Wave 2
+3. SUMMARY frontmatter `requirements_completed` should be enforced by the executor — the verifier shouldn't be the first to catch missing entries
+
+### Cost Observations
+- Model mix: opus for execution, sonnet for verification and integration check
+- 2 phases completed in single session
+- Notable: docs-only milestone completed in ~20 minutes of wall clock time
+
+---
+
 ## Cross-Milestone Trends
 
 ### Process Evolution
 
 | Milestone | Phases | Plans | Key Change |
 |-----------|--------|-------|------------|
 | v1.0 | 3 | 8 | Initial milestone — established GSD workflow with strict phase dependencies |
+| v1.1 | 2 | 3 | Docs-only milestone — UI-SPEC content contracts, banned word enforcement, wave-ordered content sourcing |
 
 ### Cumulative Quality
 
 | Milestone | Tests | Packages | Zero-Dep Additions |
 |-----------|-------|----------|-------------------|
 | v1.0 | 80+ | 5 | 3 (mcp-go, browser, sync) |
+| v1.1 | 80+ (unchanged) | 5 (unchanged) | 0 (docs-only) |
 
 ### Top Lessons (Verified Across Milestones)
 
 1. Set canonical identifiers (module paths, package names) in the first phase
 2. Raw JSON pass-through beats typed structs for API wrapper tools consumed by LLMs
+3. For multi-file messaging, update the canonical source first (Wave 1), then derive — prevents drift

.planning/ROADMAP.md

@@ -2,8 +2,8 @@
 
 ## Milestones
 
-- v1.0 **Go Rewrite** - Phases 1-3 (shipped 2026-04-01)
-- v1.1 **Docs, Pages & OpenClaw Positioning** - Phases 4-5 (in progress)
+- ✅ **v1.0 Go Rewrite** — Phases 1-3 (shipped 2026-04-01)
+- ✅ **v1.1 Docs, Pages & OpenClaw Positioning** — Phases 4-5 (shipped 2026-04-04)
 
 ## Phases
 
@@ -14,109 +14,35 @@
 Decimal phases appear between their surrounding integers in numeric order.
 
 <details>
-<summary>v1.0 Go Rewrite (Phases 1-3) - SHIPPED 2026-04-01</summary>
-
-- [x] **Phase 1: Foundation and Auth** - Go project scaffold, file-based token store, OAuth browser flow, Strava HTTP client, and MCP server wiring
-- [x] **Phase 2: Tool Suite** - Port all 11 existing Strava tools with full feature parity (activities, athlete, streams, clubs, uploads)
-- [x] **Phase 3: Polish and Distribution** - Portfolio-quality README and single-binary cross-platform release pipeline
-
-### Phase 1: Foundation and Auth
-**Goal**: A running MCP server binary that authenticates with Strava and can make API calls, with all infrastructure ready for tool registration
-**Depends on**: Nothing (first phase)
-**Requirements**: INFRA-01, INFRA-02, INFRA-03, INFRA-04, INFRA-05
-**Success Criteria** (what must be TRUE):
-  1. Running `go build` produces a single binary with no runtime dependencies
-  2. Running `strava-mcp auth` opens a browser, completes OAuth, and persists tokens to ~/.strava/tokens.json
-  3. The MCP server connects via stdio and responds to MCP protocol handshake (list tools returns empty tool set)
-  4. Token auto-refresh works transparently -- an expired access token triggers refresh without user intervention, and concurrent refresh attempts are coalesced into one
-  5. All logging goes to stderr only -- stdout carries exclusively MCP JSON-RPC traffic
-**Plans**: 2 plans
-
-Plans:
-- [x] 01-01-PLAN.md -- Go project scaffold, config loader, token store, and MCP server shell
-- [x] 01-02-PLAN.md -- Strava HTTP client with auto-refresh and OAuth browser flow
-
-### Phase 2: Tool Suite
-**Goal**: Users can access all core Strava data through 11 MCP tools matching the existing TypeScript feature set
-**Depends on**: Phase 1
-**Requirements**: ACT-01, ACT-02, ACT-03, ACT-04, ACT-05, ATH-01, ATH-02, STR-01, CLB-01, UPL-01, UPL-02
-**Success Criteria** (what must be TRUE):
-  1. User can list, view, create, and update activities through MCP tool calls
-  2. User can retrieve heart rate/power zones, time-series streams, and athlete statistics
-  3. User can upload activity files (GPX/TCX/FIT) via multipart form data and check upload status
-  4. User can list club activities with pagination
-  5. All 11 tool descriptions match the existing TypeScript versions in detail and quality (descriptions are the product UI for LLMs)
-**Plans**: 3 plans
-
-Plans:
-- [x] 02-01-PLAN.md -- Shared helpers (formatResponse, handleToolError) and 5 activity tools
-- [x] 02-02-PLAN.md -- Athlete, streams, and club tools (4 tools)
-- [x] 02-03-PLAN.md -- PostMultipart client method, upload tools, and RegisterAll wiring (2 tools + final wiring)
-
-### Phase 3: Polish and Distribution
-**Goal**: The project is portfolio-ready with a polished README and frictionless installation via single-binary releases
-**Depends on**: Phase 2
-**Requirements**: DOCS-01, DOCS-02
-**Success Criteria** (what must be TRUE):
-  1. README includes badges, architecture diagram, complete tool reference, quick-start guide, and visual polish worthy of a portfolio piece
-  2. `goreleaser` produces cross-platform binaries (macOS, Linux) from a single GitHub Actions workflow
-  3. A new user can go from zero to working MCP server by following only the README instructions
-**Plans**: 3 plans
-
-Plans:
-- [x] 03-01-PLAN.md -- Module path migration, legacy cleanup, LICENSE, .gitignore
-- [x] 03-02-PLAN.md -- goreleaser config, release workflow, CONTRIBUTING.md, repo metadata
-- [x] 03-03-PLAN.md -- Portfolio-quality README and docs site rewrite
+<summary>✅ v1.0 Go Rewrite (Phases 1-3) — SHIPPED 2026-04-01</summary>
 
-</details>
-
-### v1.1 Docs, Pages & OpenClaw Positioning (In Progress)
-
-**Milestone Goal:** Fix GitHub Pages deployment, position StravaMCP as a high-performance Go MCP server for OpenClaw/ZeroClaw agent frameworks, and highlight Go speed advantages over Python/JavaScript MCPs.
+- [x] **Phase 1: Foundation and Auth** — Go project scaffold, file-based token store, OAuth browser flow, Strava HTTP client, and MCP server wiring
+- [x] **Phase 2: Tool Suite** — Port all 11 existing Strava tools with full feature parity (activities, athlete, streams, clubs, uploads)
+- [x] **Phase 3: Polish and Distribution** — Portfolio-quality README and single-binary cross-platform release pipeline
 
-- [ ] **Phase 4: GitHub Pages Restoration** - Fix broken deployment workflow and verify docs site renders correctly
-- [ ] **Phase 5: OpenClaw Positioning & Performance Messaging** - Update README and docs with agent framework positioning and Go performance advantages
+See `.planning/milestones/v1.0-ROADMAP.md` for full phase details.
 
-## Phase Details
+</details>
 
-### Phase 4: GitHub Pages Restoration
-**Goal**: The docs site is live and rendering correctly at stealinglight.github.io/StravaMCP
-**Depends on**: Phase 3 (docs site content created in v1.0)
-**Requirements**: PAGES-01, PAGES-02
-**Success Criteria** (what must be TRUE):
-  1. Pushing to main triggers a GitHub Actions workflow that deploys docs/ to GitHub Pages
-  2. stealinglight.github.io/StravaMCP loads and renders the docs site with just-the-docs theme and dark mode
-  3. All existing docs site pages (tool reference, quick start, architecture) render without broken links or missing assets
-**Plans**: 1 plan
+<details>
+<summary>✅ v1.1 Docs, Pages & OpenClaw Positioning (Phases 4-5) — SHIPPED 2026-04-04</summary>
 
-Plans:
-- [x] 04-01-PLAN.md -- Restore deploy-docs.yml workflow and verify live site rendering
-**UI hint**: yes
+- [x] **Phase 4: GitHub Pages Restoration** — Fix broken deployment workflow and verify docs site renders correctly
+- [x] **Phase 5: OpenClaw Positioning & Performance Messaging** — Update README and docs with agent framework positioning and Go performance advantages
 
-### Phase 5: OpenClaw Positioning & Performance Messaging
-**Goal**: StravaMCP is positioned as a production-grade, high-performance MCP server for agent frameworks, not just a portfolio piece
-**Depends on**: Phase 4 (docs site must be live before updating its content)
-**Requirements**: MSG-01, MSG-02, MSG-03, MSG-04
-**Success Criteria** (what must be TRUE):
-  1. README contains an OpenClaw/ZeroClaw ecosystem section that explains how StravaMCP fits as a stdio MCP server within agent framework architectures
-  2. README includes concrete Go performance claims (sub-second startup, low memory footprint, small binary size) contrasted against typical Python/JavaScript MCP servers
-  3. Docs site has a dedicated OpenClaw/ZeroClaw compatibility page or section with integration instructions (how to wire StravaMCP into an agent)
-  4. The overall project tone across README and docs reads as "production-grade MCP server" rather than "portfolio project" -- language emphasizes reliability, performance, and agent framework integration
-**Plans**: 2 plans
+See `.planning/milestones/v1.1-ROADMAP.md` for full phase details.
 
-Plans:
-- [x] 05-01-PLAN.md -- README overhaul: hero tagline, features, Why Go? table, Agent Framework Integration section
-- [x] 05-02-PLAN.md -- Docs site: index.md update, new integration.md page, _config.yml description
+</details>
 
 ## Progress
 
 **Execution Order:**
-Phases execute in numeric order: 4 -> 5
+Phases execute in numeric order.
 
 | Phase | Milestone | Plans Complete | Status | Completed |
 |-------|-----------|----------------|--------|-----------|
 | 1. Foundation and Auth | v1.0 | 2/2 | Complete | 2026-03-27 |
 | 2. Tool Suite | v1.0 | 3/3 | Complete | 2026-03-27 |
 | 3. Polish and Distribution | v1.0 | 3/3 | Complete | 2026-04-01 |
-| 4. GitHub Pages Restoration | v1.1 | 0/1 | Planning complete | - |
-| 5. OpenClaw Positioning | v1.1 | 0/2 | Planning complete | - |
+| 4. GitHub Pages Restoration | v1.1 | 1/1 | Complete | 2026-04-03 |
+| 5. OpenClaw Positioning | v1.1 | 2/2 | Complete | 2026-04-04 |

.planning/STATE.md

@@ -4,7 +4,7 @@ milestone: v1.1
 milestone_name: Docs, Pages & OpenClaw Positioning
 status: executing
 stopped_at: Phase 5 UI-SPEC approved
-last_updated: "2026-04-04T20:49:42.364Z"
+last_updated: "2026-04-04T21:00:48.643Z"
 last_activity: 2026-04-04
 progress:
   total_phases: 2

.planning/v1.1-MILESTONE-AUDIT.md …nning/milestones/v1.1-MILESTONE-AUDIT.md.planning/v1.1-MILESTONE-AUDIT.md renamed to .planning/milestones/v1.1-MILESTONE-AUDIT.md .planning/v1.1-MILESTONE-AUDIT.md renamed to .planning/milestones/v1.1-MILESTONE-AUDIT.md

@@ -1,3 +1,12 @@
+# Requirements Archive: v1.1 Docs, Pages & OpenClaw Positioning
+
+**Archived:** 2026-04-04
+**Status:** SHIPPED
+
+For current requirements, see `.planning/REQUIREMENTS.md`.
+
+---
+
 # Requirements: StravaMCP v1.1 — Docs, Pages & OpenClaw Positioning
 
 **Defined:** 2026-04-01