chore: complete v1.0 milestone

- Archive ROADMAP.md and REQUIREMENTS.md to milestones/
- Create MILESTONES.md with accomplishments
- Evolve PROJECT.md with validated requirements and current state
- Delete original ROADMAP.md and REQUIREMENTS.md (fresh for next milestone)

Author: Stealinglight

.planning/MILESTONES.md

@@ -0,0 +1,18 @@
+# Milestones
+
+## v1.0 StravaMCP Go Rewrite (Shipped: 2026-04-01)
+
+**Phases completed:** 3 phases, 8 plans, 18 tasks
+
+**Key accomplishments:**
+
+- Go binary with mcp-go stdio server shell, file-based token store with atomic writes, and env-var config loader with validation
+- Strava HTTP client with singleflight token refresh and browser OAuth flow with GET /athlete end-to-end validation
+- FormatResponse/HandleToolError shared helpers plus 5 activity MCP tools (get, get_by_id, create, update, zones) with map-based partial update and 18 tests
+- 4 MCP tools (athlete profile/stats, activity streams, club activities) with auto-fetch athlete ID and array-to-CSV key joining, all following Plan 01 closure-over-client pattern
+- PostMultipart client method, create_upload/get_upload MCP tools with extension auto-detection, and RegisterAll wiring all 11 tools from 5 resource files
+- Go module migrated to github.com/Stealinglight/StravaMCP, all TypeScript/Lambda artifacts deleted, ISC license created, .gitignore rewritten for Go
+- goreleaser v2 cross-platform release config with Homebrew cask distribution, tag-triggered GitHub Actions workflow, and Go-focused CONTRIBUTING.md
+- Portfolio-quality README with 8 badges, dual Mermaid architecture diagrams, 11-tool reference table, and simplified Go-focused docs site
+
+---

.planning/PROJECT.md

@@ -12,21 +12,14 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 
 ### Validated
 
-<!-- Inferred from existing TypeScript codebase -->
-
-- ✓ List athlete activities with date filtering and pagination — existing
-- ✓ Get detailed activity by ID — existing
-- ✓ Create manual activities — existing
-- ✓ Update existing activities (name, description, gear, metadata) — existing
-- ✓ Get activity heart rate and power zones — existing
-- ✓ Get authenticated athlete profile — existing
-- ✓ Get athlete aggregate statistics — existing
-- ✓ Get activity time-series streams (HR, GPS, power, cadence, etc.) — existing
-- ✓ Get club activities — existing
-- ✓ Upload activity files (GPX, TCX, FIT) — existing
-- ✓ Check upload status — existing
-- ✓ Automatic OAuth token refresh with expiry buffer — existing
-- ✓ File-based token storage (Rusty Claw pattern) — existing in RustyClaw
+- ✓ Full rewrite in Go with stdio MCP transport — v1.0
+- ✓ Go MCP SDK integration (mcp-go v0.46.0) — v1.0
+- ✓ Built-in OAuth browser flow for initial token acquisition — v1.0
+- ✓ 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
+- ✓ Single-binary distribution via goreleaser with Homebrew — v1.0
+- ✓ Cross-platform builds (darwin/linux, amd64/arm64) — v1.0
 
 ### Active
 
@@ -37,15 +30,6 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 - [ ] Gear tools: gear details, manage equipment
 - [ ] Laps & efforts tools: activity laps, segment efforts, best efforts
 
-### Validated in v1.0 Milestone
-
-- ✓ Full rewrite in Go with stdio MCP transport — Phase 1
-- ✓ Go MCP SDK integration (mcp-go v0.46.0) — Phase 1
-- ✓ Built-in OAuth browser flow for initial token acquisition — Phase 1
-- ✓ File-based token store with automatic refresh persistence — Phase 1
-- ✓ Portfolio-quality README with badges, architecture diagram, feature highlights, and visual polish — Phase 3
-- ✓ Single-binary distribution (go build, no runtime dependencies) — Phase 3
-- ✓ goreleaser cross-platform release pipeline with Homebrew distribution — Phase 3
 
 ### Out of Scope
 
@@ -59,12 +43,13 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 
 ## Context
 
-- This MCP is part of the RustyClaw/ZeroClaw ecosystem, which runs multiple local MCP servers (Strava, Slack, video, web-research) as stdio-based tools
-- The existing TypeScript version at `src/` has 11 Strava tools and a full AWS Lambda deployment stack
-- The RustyClaw version at `mcp-servers/strava-mcp/` is already a simplified local-only TypeScript version — the Go rewrite follows this pattern
-- The Go rewrite adds expanded Strava API coverage (segments, routes, gear, laps) beyond the current 11 tools
-- Chris wants this as a portfolio piece — clean code, excellent README, architecture documentation
-- The muscle group heat map renderer is being built separately and will integrate with this MCP in a future milestone
+- v1.0 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)
+- All TypeScript/Lambda code removed — clean Go-only repository
+- Portfolio piece with polished README, badges, Mermaid diagrams
+- The muscle group heat map renderer is being built separately and will integrate in a future milestone
 
 ## Constraints
 
@@ -87,12 +72,15 @@ A fast, self-contained Go binary that gives any MCP client full access to the St
 | Raw JSON responses (no Go structs for Strava data) | D-01: pass through Strava JSON with pretty-printing, avoid schema coupling | ✓ Phase 2 |
 | Map-based PUT body for update_activity | Avoids Go zero-value trap — only sends user-provided fields | ✓ Phase 2 |
 | Auto-detect upload data_type from file extension | D-04: .gpx/.fit/.tcx/.tcx.gz mapped automatically, explicit override available | ✓ Phase 2 |
-| Add segments/routes/gear/laps | Expand beyond current 11 tools to comprehensive Strava coverage | — Pending |
-| Heat map as future milestone | Separate project, don't couple it to the core rewrite | — Pending |
+| 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 |
+| 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 State
 
-v1.0 milestone complete — All three phases delivered. Phase 1 built the Go project scaffold, OAuth browser flow, token store, and MCP server wiring. Phase 2 ported all 11 Strava tools with full feature parity. Phase 3 migrated the module path to `github.com/Stealinglight/StravaMCP`, cleaned up all TypeScript/Lambda legacy artifacts, created the goreleaser release pipeline with Homebrew cask distribution, and delivered a portfolio-quality README with badges, Mermaid diagrams, and comprehensive documentation. 80+ tests passing. Ready for first release tag.
+v1.0 milestone shipped (2026-04-01). Complete Go rewrite with 11 MCP tools, OAuth browser flow, singleflight token refresh, goreleaser cross-platform release pipeline with Homebrew distribution, and portfolio-quality README. 4,791 LOC Go, 80+ tests, all TypeScript/Lambda artifacts removed. Ready for first `v1.0.0` release tag and v2.0 planning (expanded Strava API coverage: segments, routes, gear, laps).
 
 ---
-*Last updated: 2026-04-01 after Phase 3 completion*
+*Last updated: 2026-04-01 after v1.0 milestone completion*

.planning/STATE.md

@@ -4,7 +4,7 @@ milestone: v1.0
 milestone_name: milestone
 status: executing
 stopped_at: Phase 3 context gathered
-last_updated: "2026-04-01T21:08:51.217Z"
+last_updated: "2026-04-01T21:19:26.541Z"
 last_activity: 2026-04-01
 progress:
   total_phases: 3

.planning/milestones/v1.0-REQUIREMENTS.md

@@ -0,0 +1,146 @@
+# Requirements Archive: v1.0 StravaMCP Go Rewrite
+
+**Archived:** 2026-04-01
+**Status:** SHIPPED
+
+For current requirements, see `.planning/REQUIREMENTS.md`.
+
+---
+
+# Requirements: StravaMCP Go Rewrite
+
+**Defined:** 2026-03-26
+**Core Value:** A fast, self-contained Go binary that gives any MCP client full access to the Strava API with zero cloud infrastructure required.
+
+## v1 Requirements (Milestone 1 — Core Go Rewrite)
+
+### Infrastructure
+
+- [x] **INFRA-01**: Go project scaffolded with mcp-go SDK, stderr-only logging, go.mod initialized
+- [x] **INFRA-02**: File-based token store with atomic write-then-rename at configurable path (~/.strava/tokens.json)
+- [x] **INFRA-03**: Built-in OAuth browser flow that opens system browser, runs ephemeral localhost callback, exchanges code, persists tokens
+- [x] **INFRA-04**: Strava HTTP client with automatic token refresh (5-min buffer), concurrent refresh protection (singleflight), and rate limit header tracking
+- [x] **INFRA-05**: MCP server wired with mcp-go ServeStdio, all tools registered declaratively
+
+### Activity Tools (Port)
+
+- [x] **ACT-01**: User can list recent activities with date filtering (before/after) and pagination
+- [x] **ACT-02**: User can get detailed activity by ID including laps, splits, segment efforts
+- [x] **ACT-03**: User can create manual activities with name, sport type, start time, elapsed time
+- [x] **ACT-04**: User can update existing activities (name, description, sport type, gear, trainer, commute, hide)
+- [x] **ACT-05**: User can get heart rate and power zone distribution for an activity
+
+### Athlete Tools (Port)
+
+- [x] **ATH-01**: User can get authenticated athlete profile (name, gear, preferences)
+- [x] **ATH-02**: User can get athlete aggregate statistics (recent/YTD/all-time run/ride/swim totals)
+
+### Stream Tools (Port)
+
+- [x] **STR-01**: User can get activity time-series streams (HR, GPS, power, cadence, altitude, etc.)
+
+### Club Tools (Port)
+
+- [x] **CLB-01**: User can list recent activities from a club's members with pagination
+
+### Upload Tools (Port)
+
+- [x] **UPL-01**: User can upload activity files (GPX, TCX, FIT) via proper multipart form data
+- [x] **UPL-02**: User can check upload processing status and get resulting activity ID
+
+### Presentation
+
+- [x] **DOCS-01**: Portfolio-quality README with badges, architecture diagram, feature list, quick start, visual polish
+- [x] **DOCS-02**: Single-binary distribution via go install and goreleaser (multi-platform builds)
+
+## v2 Requirements (Milestone 2 — Expanded Strava Coverage)
+
+### Segment Tools
+
+- [ ] **SEG-01**: User can list their starred segments with pagination
+- [ ] **SEG-02**: User can get detailed segment info (distance, elevation, grade, climb category)
+- [ ] **SEG-03**: User can explore segments near a GPS coordinate with filters
+- [ ] **SEG-04**: User can star/unstar a segment
+- [ ] **SEG-05**: User can list all efforts on a segment (filtered by athlete, date range)
+- [ ] **SEG-06**: User can get detailed segment effort (elapsed time, moving time, PR rank)
+- [ ] **SEG-07**: User can get segment streams (altitude, distance, latlng)
+- [ ] **SEG-08**: User can get segment effort streams (time-series for a specific effort)
+
+### Route Tools
+
+- [ ] **RTE-01**: User can list their routes with pagination
+- [ ] **RTE-02**: User can get route details (distance, elevation, estimated time, map)
+- [ ] **RTE-03**: User can export a route as GPX
+- [ ] **RTE-04**: User can export a route as TCX
+- [ ] **RTE-05**: User can get route streams (elevation, distance, latlng)
+
+### Gear Tools
+
+- [ ] **GEAR-01**: User can get gear details by ID (distance tracked, name, brand, model)
+- [ ] **GEAR-02**: User can list all their shoes with mileage (extracted from athlete profile)
+- [ ] **GEAR-03**: User can list all their bikes (extracted from athlete profile)
+
+### Laps & Zones
+
+- [ ] **LAP-01**: User can get activity laps (pace, HR, cadence per lap)
+- [ ] **ZONE-01**: User can get their configured HR/power zone boundaries
+
+### Extended Club Tools
+
+- [ ] **CLB-02**: User can list clubs they belong to
+- [ ] **CLB-03**: User can get club details (member count, sport type, location)
+
+### Social Tools
+
+- [ ] **SOC-01**: User can get activity comments with pagination
+- [ ] **SOC-02**: User can get activity kudos with pagination
+- [ ] **SOC-03**: User can get activity photos (note: uses undocumented endpoint, verify stability)
+
+## Out of Scope
+
+| Feature | Reason |
+|---------|--------|
+| AWS Lambda deployment | Simplifying to local binary only — drop all cloud infrastructure |
+| DynamoDB / any database | File-based token store is sufficient for local MCP |
+| SSE / HTTP transport | Stdio only — MCP standard for local tool servers |
+| Segment leaderboard | Undocumented endpoint, requires Strava Summit subscription, may break |
+| Activity deletion | Destructive operation with no undo — too risky for LLM tool |
+| Webhook subscriptions | Requires public HTTP endpoint — contradicts zero-infrastructure design |
+| Bulk operations | Rate limit risk and amplifies AI mistake potential |
+| Data caching / local DB | Adds staleness complexity; API rate limits are generous for interactive use |
+| Multi-athlete support | One MCP instance per athlete; coaching multiple athletes = separate instances |
+| Training plan generation | LLM/agent layer concern, not a tool concern |
+| Muscle group heat map | Separate project, future milestone integration |
+| OpenAI-compatible tool defs | Go version is MCP-native only |
+
+## Traceability
+
+| Requirement | Phase | Status |
+|-------------|-------|--------|
+| INFRA-01 | Phase 1 | Complete |
+| INFRA-02 | Phase 1 | Complete |
+| INFRA-03 | Phase 1 | Complete |
+| INFRA-04 | Phase 1 | Complete |
+| INFRA-05 | Phase 1 | Complete |
+| ACT-01 | Phase 2 | Complete |
+| ACT-02 | Phase 2 | Complete |
+| ACT-03 | Phase 2 | Complete |
+| ACT-04 | Phase 2 | Complete |
+| ACT-05 | Phase 2 | Complete |
+| ATH-01 | Phase 2 | Complete |
+| ATH-02 | Phase 2 | Complete |
+| STR-01 | Phase 2 | Complete |
+| CLB-01 | Phase 2 | Complete |
+| UPL-01 | Phase 2 | Complete |
+| UPL-02 | Phase 2 | Complete |
+| DOCS-01 | Phase 3 | Complete |
+| DOCS-02 | Phase 3 | Complete |
+
+**Coverage:**
+- v1 requirements: 18 total
+- Mapped to phases: 18/18
+- Unmapped: 0
+
+---
+*Requirements defined: 2026-03-26*
+*Last updated: 2026-03-26 after roadmap creation*

.planning/milestones/v1.0-ROADMAP.md

@@ -0,0 +1,78 @@
+# Roadmap: StravaMCP Go Rewrite
+
+## Overview
+
+This roadmap delivers a complete Go rewrite of the Strava MCP server in three phases: first, build all infrastructure (project scaffold, token management, OAuth browser flow, Strava HTTP client, MCP server wiring); second, port all 11 existing tools to Go with full feature parity; third, polish the README and set up single-binary distribution for portfolio presentation. The dependency chain is strict -- no tool can work without the infrastructure layer, and the README cannot be finalized until all tools are implemented.
+
+## Phases
+
+**Phase Numbering:**
+- Integer phases (1, 2, 3): Planned milestone work
+- Decimal phases (2.1, 2.2): Urgent insertions (marked with INSERTED)
+
+Decimal phases appear between their surrounding integers in numeric order.
+
+- [x] **Phase 1: Foundation and Auth** - Go project scaffold, file-based token store, OAuth browser flow, Strava HTTP client, and MCP server wiring (completed 2026-03-27)
+- [x] **Phase 2: Tool Suite** - Port all 11 existing Strava tools with full feature parity (activities, athlete, streams, clubs, uploads)
+- [ ] **Phase 3: Polish and Distribution** - Portfolio-quality README and single-binary cross-platform release pipeline
+
+## Phase Details
+
+### 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
+
+## Progress
+
+**Execution Order:**
+Phases execute in numeric order: 1 -> 2 -> 3
+
+| Phase | Plans Complete | Status | Completed |
+|-------|----------------|--------|-----------|
+| 1. Foundation and Auth | 2/2 | Complete   | 2026-03-27 |
+| 2. Tool Suite | 3/3 | Complete | 2026-03-27 |
+| 3. Polish and Distribution | 1/3 | In progress | - |