docs: sync version references and archive stale docs for v0.3.1

Author: ppiankov

CHANGELOG.md

@@ -16,6 +16,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [0.3.1] - 2026-02-11
+
+### Fixed
+
+- README version badge updated from 0.2.5 to 0.3.0
+- Hardcoded "0.2.0" version strings in apply bundle and policy validation
+- Documentation references to "v2.0" corrected to match actual versioning
+- Pro-monitor v0.3.0 spec status changed from DRAFT to SHIPPED
+- Node footprint TODO clarified: requests are the correct default, Prometheus percentile is optional overlay
+
+### Changed
+
+- Stale root-level working docs archived to `docs/archive/`
+- `SPIKE-ANALYSIS.md` moved to `docs/spike-analysis.md`
+- Migration guide version references corrected (v1.x/v2.0 → v0.1.x/v0.2+)
+
+---
+
 ## [0.3.0] - 2026-02-11
 
 ### Added
@@ -873,7 +891,8 @@ Kubernetes cluster analysis tool combining deterministic cost optimization with
 
 ## Links
 
-- [Unreleased]: https://github.com/ppiankov/kubenow/compare/v0.3.0...HEAD
+- [Unreleased]: https://github.com/ppiankov/kubenow/compare/v0.3.1...HEAD
+- [0.3.1]: https://github.com/ppiankov/kubenow/compare/v0.3.0...v0.3.1
 - [0.3.0]: https://github.com/ppiankov/kubenow/compare/v0.2.7...v0.3.0
 - [0.2.7]: https://github.com/ppiankov/kubenow/compare/v0.2.6...v0.2.7
 - [0.2.6]: https://github.com/ppiankov/kubenow/compare/v0.2.5...v0.2.6

README.md

@@ -6,7 +6,7 @@
 [![Go Report Card](https://goreportcard.com/badge/github.com/ppiankov/kubenow)](https://goreportcard.com/report/github.com/ppiankov/kubenow)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
-**Version 0.2.5** — Deterministic resource analysis, policy-gated apply, and real-time monitoring for Kubernetes clusters.
+**Version 0.3.1** — Deterministic resource analysis, policy-gated apply, and real-time monitoring for Kubernetes clusters.
 
 ---
 
@@ -332,7 +332,7 @@ Available for Linux (amd64, arm64), macOS (amd64, arm64), and Windows (amd64).
 
 ```bash
 kubenow version
-# kubenow version 0.2.5
+# kubenow version 0.3.1
 ```
 
 ---
@@ -440,8 +440,8 @@ MIT License — see [LICENSE](LICENSE) for details.
 ## Documentation
 
 - [Architecture](docs/architecture.md)
-- [Pro-Monitor Spec](docs/spec-pro-monitor-v0.2.0.md)
-- [Spike Analysis Guide](SPIKE-ANALYSIS.md)
+- [Pro-Monitor Spec](docs/spec-pro-monitor-v0.3.0.md)
+- [Spike Analysis Guide](docs/spike-analysis.md)
 - [Changelog](CHANGELOG.md)
 - [Contributing](CONTRIBUTING.md)
 - [Manifesto](MANIFESTO.md)

docs/architecture.md

@@ -1,6 +1,6 @@
 # kubenow Architecture
 
-This document describes the architecture, design decisions, and implementation details of kubenow v2.0.
+This document describes the architecture, design decisions, and implementation details of kubenow.
 
 ---
 
@@ -592,7 +592,7 @@ Result:
 
 ## Exit Code Strategy
 
-kubenow v2.0 uses standardized exit codes for automation-friendly behavior.
+kubenow uses standardized exit codes for automation-friendly behavior.
 
 | Code | Constant | Meaning | Use Case |
 |------|----------|---------|----------|

CI-CD-READY.md docs/archive/CI-CD-READY.mdCI-CD-READY.md renamed to docs/archive/CI-CD-READY.md

@@ -1,12 +1,12 @@
-# Migration Guide: kubenow v1.x → v2.0
+# Migration Guide: kubenow v0.1.x → v0.2+
 
-This guide helps you migrate from kubenow v1.x to v2.0.
+This guide helps you migrate from kubenow v0.1.x to v0.2+.
 
 ---
 
 ## Overview
 
-**v2.0 introduces a new Cobra-based CLI structure** with subcommands instead of the `--mode` flag. This breaking change provides better organization, improved help text, and consistency with the spectre tools family.
+**v0.2 introduced a new Cobra-based CLI structure** with subcommands instead of the `--mode` flag. This breaking change provides better organization, improved help text, and consistency with the spectre tools family.
 
 **Migration Difficulty:** Low
 **Estimated Time:** 5-10 minutes to update scripts
@@ -21,74 +21,74 @@ The `--mode` flag has been removed. Each mode is now a dedicated subcommand.
 
 #### Incident Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode incident --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow incident --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
 #### Pod Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode pod --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow pod --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
 #### Teamlead Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode teamlead --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow teamlead --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
 #### Compliance Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode compliance --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow compliance --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
 #### Chaos Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode chaos --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow chaos --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
 #### Default Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode default --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 # or just
 kubenow --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow default --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 ```
@@ -99,12 +99,12 @@ kubenow default --llm-endpoint http://localhost:11434/v1 --model mixtral:8x22b
 
 **Global flags** (like `--kubeconfig`, `--namespace`, `--verbose`) must now appear **before** the subcommand.
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --mode incident --namespace production --llm-endpoint ...
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow --namespace production incident --llm-endpoint ...
 ```
@@ -126,9 +126,9 @@ kubenow pod --namespace prod --llm-endpoint ...
 
 ### 3. Exit Codes
 
-v2.0 uses standardized exit codes across all commands.
+v0.2+ uses standardized exit codes across all commands.
 
-| Exit Code | Meaning | v1.x Behavior | v2.0 Behavior |
+| Exit Code | Meaning | v0.1.x Behavior | v0.2+ Behavior |
 |-----------|---------|---------------|---------------|
 | 0 | Success | Same | Same |
 | 1 | Policy failure | Used for all errors | Reserved (not used yet) |
@@ -141,12 +141,12 @@ v2.0 uses standardized exit codes across all commands.
 
 ### 4. Help Command
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow --help
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow --help                    # Show all commands
 kubenow incident --help           # Show incident command help
@@ -156,7 +156,7 @@ kubenow analyze requests-skew --help  # Show requests-skew help
 
 ---
 
-## New Features in v2.0
+## New Features in v0.2+
 
 ### Deterministic Analysis Commands
 
@@ -200,18 +200,18 @@ kubenow analyze node-footprint --prometheus-url http://prometheus:9090
 - [ ] Replace `--mode` flag with subcommand
 - [ ] Move global flags before subcommand
 - [ ] Update exit code handling (if checking exit codes)
-- [ ] Test all scripts with v2.0
+- [ ] Test all scripts with v0.2+
 
 ### For CI/CD Pipelines
 
-- [ ] Update kubenow installation (download v2.0 binary)
+- [ ] Update kubenow installation (download v0.2+ binary)
 - [ ] Update command syntax in pipeline scripts
 - [ ] Verify exit code handling
 - [ ] Test pipeline end-to-end
 
 ### For Kubernetes Jobs/CronJobs
 
-- [ ] Update container image to v2.0
+- [ ] Update container image to v0.2+
 - [ ] Update command in pod spec
 - [ ] Test job execution
 
@@ -221,7 +221,7 @@ kubenow analyze node-footprint --prometheus-url http://prometheus:9090
 
 ### Example 1: Simple Script
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 #!/bin/bash
 kubenow \
@@ -236,7 +236,7 @@ if [ $? -ne 0 ]; then
 fi
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 #!/bin/bash
 kubenow incident \
@@ -258,7 +258,7 @@ fi
 
 ### Example 2: Kubernetes CronJob
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```yaml
 apiVersion: batch/v1
 kind: CronJob
@@ -285,7 +285,7 @@ spec:
             - /reports/compliance-report.json
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```yaml
 apiVersion: batch/v1
 kind: CronJob
@@ -315,7 +315,7 @@ spec:
 
 ### Example 3: Watch Mode
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow \
   --mode incident \
@@ -325,7 +325,7 @@ kubenow \
   --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow incident \
   --watch-interval 1m \
@@ -338,7 +338,7 @@ kubenow incident \
 
 ### Example 4: With Filters
 
-**Before (v1.x):**
+**Before (v0.1.x):**
 ```bash
 kubenow \
   --mode pod \
@@ -349,7 +349,7 @@ kubenow \
   --model mixtral:8x22b
 ```
 
-**After (v2.0):**
+**After (v0.2+):**
 ```bash
 kubenow --namespace production pod \
   --include-pods "payment-*,checkout-*" \
@@ -407,30 +407,30 @@ echo $?  # Should be 2
 
 ## Rollback Plan
 
-If you need to roll back to v1.x:
+If you need to roll back to v0.1.x:
 
 ### Option 1: Keep Both Versions
 
 ```bash
-# Rename v2.0 binary
+# Rename v0.2+ binary
 mv /usr/local/bin/kubenow /usr/local/bin/kubenow2
 
-# Install v1.x as kubenow
+# Install v0.1.x as kubenow
 curl -LO https://github.com/ppiankov/kubenow/releases/download/v1.2.0/kubenow_1.2.0_linux_amd64.tar.gz
 tar -xzf kubenow_1.2.0_linux_amd64.tar.gz
 sudo mv kubenow /usr/local/bin/
 
-# Use v1.x: kubenow
-# Use v2.0: kubenow2
+# Use v0.1.x: kubenow
+# Use v0.2+: kubenow2
 ```
 
 ### Option 2: Downgrade
 
 ```bash
-# Remove v2.0
+# Remove v0.2+
 rm /usr/local/bin/kubenow
 
-# Install v1.x
+# Install v0.1.x
 curl -LO https://github.com/ppiankov/kubenow/releases/download/v1.2.0/kubenow_1.2.0_linux_amd64.tar.gz
 tar -xzf kubenow_1.2.0_linux_amd64.tar.gz
 sudo mv kubenow /usr/local/bin/
@@ -450,20 +450,20 @@ sudo mv kubenow /usr/local/bin/
 
 ## FAQ
 
-**Q: Can I use both v1.x and v2.0 side by side?**
+**Q: Can I use both v0.1.x and v0.2+ side by side?**
 A: Yes, install them as separate binaries (`kubenow` and `kubenow2`).
 
-**Q: Will v1.x continue to receive updates?**
-A: No, v1.x is end-of-life. All future development is on v2.x.
+**Q: Will v0.1.x continue to receive updates?**
+A: No, v0.1.x is end-of-life. All future development is on v0.2+.
 
 **Q: Do I need to migrate immediately?**
-A: We recommend migrating within 30 days. v1.x will not receive security updates.
+A: We recommend migrating within 30 days. v0.1.x will not receive security updates.
 
 **Q: Are there any feature differences besides CLI syntax?**
-A: v2.0 adds new `analyze` commands. All v1.x LLM features remain unchanged.
+A: v0.2+ adds new `analyze` commands. All v0.1.x LLM features remain unchanged.
 
 **Q: Will my old scripts break?**
-A: Yes, if you don't update them. The `--mode` flag no longer exists in v2.0.
+A: Yes, if you don't update them. The `--mode` flag no longer exists in v0.2+.
 
 **Q: Can I automate the migration?**
 A: Yes, with sed/awk:
@@ -474,4 +474,4 @@ sed -i 's/kubenow --mode incident/kubenow incident/g' my-script.sh
 
 ---
 
-**Migration complete? Welcome to kubenow v2.0!** 🎉
+**Migration complete? Welcome to kubenow v0.2+!** 🎉