codex-genesis-harness 0.1.5 → 0.1.7

package/.codex/skills/{genesis-release-orchestration → genesis-release}/observability/release-tracking.md

@@ -1,253 +1,253 @@
-# Release Tracking & Observability
-
-**Purpose**: Log, track, and analyze all release deployments  
-**Format**: Machine-readable for automation, human-readable for review  
-**Retention**: 12 months (archive older)
-
----
-
-## RELEASE_LOG.md Format
-
-```markdown
-# Release Deployment Log
-
-## v3.0.0 - May 31, 2026
-
-**Metadata**:
-- Date: 2026-05-31
-- Version: v3.0.0
-- Strategy: Canary (1%→10%→50%→100%)
-- Risk Score: 7/10 (HIGH)
-- Breaking Changes: 2
-- Approvals: Tech Lead (John Doe), Product Lead (Jane Smith)
-- Status: ✅ COMPLETE
-- Duration: 8 hours 30 minutes
-
-**Changes Summary**:
-- Removed: POST /users/:id/avatar endpoint
-- Changed: Response format { user: {...} } → { data: {...} }
-- Added: PATCH /users/:id/profile endpoint
-- Fixed: User role permission bug
-
-**Deployment Details**:
-- Stage 1: 1% traffic, 1 hour, ✅ PASS
-- Stage 2: 10% traffic, 2 hours, ✅ PASS
-- Stage 3: 50% traffic, 4 hours, ✅ PASS
-- Stage 4: 100% traffic, 24+ hours, ✅ PASS
-
-**Metrics**:
-- Error Rate: 0.08% (target <1%) ✅
-- Latency P95: 191ms (target <200ms) ✅
-- Availability: 99.92%
-- Issues: None
-- Rollback: Not required
-
-**Consumers Migrated**:
-- WebApp: ✅ Updated (deployed v[X] with response parsing fix)
-- Mobile: ✅ Already on v1.3+
-- Dashboard: ✅ Updated
-- Admin: ✅ Updated
-- Partners: ⏳ In progress (2/3 clients migrated)
-
-**Post-Deployment**:
-- Monitoring window: 24 hours
-- All checks: ✅ PASS
-- Team stood down: 2026-06-01 18:00 UTC
-- Previous version decommissioned: 2026-06-01 20:00 UTC
-
----
-
-## v2.5.3 - May 15, 2026
-
-**Status**: ✅ COMPLETE (patch release)
-...
-```
-
----
-
-## release-metrics.csv Format
-
-```csv
-date,version,strategy,risk_score,breaking_changes,affected_consumers,duration_hours,error_rate_pct,latency_p95_ms,issues_count,rollback_required,approval_chain,status
-2026-05-31,v3.0.0,canary,7,2,12,8.5,0.08,191,0,false,TL+PL,complete
-2026-05-15,v2.5.3,rolling,2,0,0,2.0,0.06,185,0,false,TL,complete
-2026-05-01,v2.5.2,rolling,1,0,0,1.5,0.07,187,0,false,auto,complete
-2026-04-15,v2.5.1,blue-green,3,1,3,3.0,0.09,192,1,false,TL+PL,complete
-2026-04-01,v2.5.0,canary,6,1,8,9.0,0.08,190,0,false,TL+PL+CTO,complete
-```
-
----
-
-## Monthly Health Report Template
-
-```markdown
-# Release Health Report - May 2026
-
-## Summary
-
-| Metric | May 2026 | April 2026 | Trend |
-|--------|----------|-----------|-------|
-| Releases | 5 | 4 | ↑ 25% |
-| Avg Risk Score | 3.8/10 | 4.2/10 | ↓ Improving |
-| Avg Error Rate | 0.077% | 0.081% | ↓ Improving |
-| Avg Latency P95 | 189ms | 194ms | ↓ Improving |
-| Rollback Rate | 0% | 0% | = Stable |
-| Avg Deploy Time | 3.5 hrs | 4.1 hrs | ↓ Faster |
-| Consumer Migration Success | 99.5% | 97% | ↑ Improving |
-
----
-
-## May Releases
-
-### v3.0.0 - May 31 (MAJOR)
-- Strategy: Canary
-- Duration: 8.5 hours
-- Status: ✅ Success
-- Issues: None
-
-### v2.5.3 - May 15 (PATCH)
-- Strategy: Rolling
-- Duration: 2 hours
-- Status: ✅ Success
-- Issues: None
-
-### v2.5.2 - May 1 (PATCH)
-- Strategy: Rolling
-- Duration: 1.5 hours
-- Status: ✅ Success
-- Issues: None (bug fix)
-
----
-
-## Performance Trends
-
-### Deployment Duration (Hours)
-
-```
-May 31: 8.5 (canary v3.0.0, complex)
-May 15: 2.0 (rolling v2.5.3, simple)
-May 1:  1.5 (rolling v2.5.2, simple)
-Apr 15: 3.0 (blue-green v2.5.1, medium)
-Apr 1:  9.0 (canary v2.5.0, complex)
-
-Average: 4.8 hours → Targeting: 3.5 hours
-```
-
-### Error Rates (%)
-
-```
-May avg: 0.077%
-Apr avg: 0.081%
-Mar avg: 0.095%
-
-Trend: ↓ Improving (better automation, earlier detection)
-Target: <0.05% by Q3 2026
-```
-
-### Rollback Rate (%)
-
-```
-May: 0% (5/5 successful, no rollbacks)
-Apr: 0% (4/4 successful, no rollbacks)
-Mar: 20% (1/5 rolled back due to API format issue)
-
-Trend: ↑ Improving (pre-deployment validation preventing failures)
-```
-
----
-
-## Improvement Opportunities
-
-1. **Deployment Automation**: Canary stages could be automated further (currently manual decisions)
-   - Expected savings: 2+ hours per release
-   - Effort: Medium (auto-go criteria definition)
-
-2. **Consumer Migration**: Manual tracking of consumer updates
-   - Expected savings: 1 hour per breaking change release
-   - Effort: High (requires consumer API integration)
-
-3. **Database Migrations**: Currently manual (could auto-rollback if data inconsistency detected)
-   - Expected savings: 30 min per migration
-   - Effort: High (complex, risky)
-
----
-
-## Queries & Analytics
-
-### Find all BREAKING releases in past 30 days
-```
-SELECT * FROM release_metrics 
-WHERE date > DATE('2026-05-01') 
-  AND breaking_changes > 0
-ORDER BY date DESC;
-
-Result: v3.0.0 (2 breaking), v2.5.1 (1 breaking)
-```
-
-### Find releases with longest deployment time
-```
-SELECT date, version, strategy, duration_hours, risk_score
-FROM release_metrics
-ORDER BY duration_hours DESC
-LIMIT 5;
-
-Result:
-- v2.5.0: 9.0 hours (canary, risk 6)
-- v3.0.0: 8.5 hours (canary, risk 7)
-- v2.5.1: 3.0 hours (blue-green, risk 3)
-```
-
-### Calculate average deployment time by strategy
-```
-SELECT strategy, COUNT(*) as count, AVG(duration_hours) as avg_duration
-FROM release_metrics
-GROUP BY strategy
-ORDER BY avg_duration DESC;
-
-Result:
-- Canary: avg 8.75 hours (2 releases)
-- Blue-Green: avg 3.0 hours (1 release)
-- Rolling: avg 1.67 hours (2 releases)
-```
-
-### Find releases with issues
-```
-SELECT date, version, issues_count, rollback_required, status
-FROM release_metrics
-WHERE issues_count > 0 OR rollback_required = true;
-
-Result: None in May 2026 (all clean)
-```
-
----
-
-## Monthly Highlights
-
-✅ **Successes**:
-- 5 releases completed without rollbacks
-- v3.0.0 (major, breaking) deployed successfully with canary strategy
-- 99.5% consumer migration success rate
-- Error rates improving month-over-month
-
-⚠️ **Opportunities**:
-- Reduce canary deployment time (currently 8+ hours for high-risk)
-- Automate consumer migration tracking
-- Enhance pre-deployment validation
-
-🎯 **Targets for June**:
-- Reduce avg deployment time to 3 hours (vs 4.8 current)
-- Maintain 0% rollback rate
-- 100% consumer migration for breaking changes
-- Implement auto-canary-stage-progression
-
----
-
-## Archive Strategy
-
-- **Recent** (< 3 months): Keep in RELEASE_LOG.md + release-metrics.csv
-- **Aging** (3-12 months): Archive to release-metrics-2026-Q1.csv.gz
-- **Archived** (> 12 months): Store in S3, reference in historical reports
-
-Example:
-- 2026 Q1: release-metrics-2026-Q1.csv.gz (archived May 2026)
-- 2025 Q4: release-metrics-2025-Q4.csv.gz (archived Feb 2026)
+# Release Tracking & Observability
+
+**Purpose**: Log, track, and analyze all release deployments  
+**Format**: Machine-readable for automation, human-readable for review  
+**Retention**: 12 months (archive older)
+
+---
+
+## RELEASE_LOG.md Format
+
+```markdown
+# Release Deployment Log
+
+## v3.0.0 - May 31, 2026
+
+**Metadata**:
+- Date: 2026-05-31
+- Version: v3.0.0
+- Strategy: Canary (1%→10%→50%→100%)
+- Risk Score: 7/10 (HIGH)
+- Breaking Changes: 2
+- Approvals: Tech Lead (John Doe), Product Lead (Jane Smith)
+- Status: ✅ COMPLETE
+- Duration: 8 hours 30 minutes
+
+**Changes Summary**:
+- Removed: POST /users/:id/avatar endpoint
+- Changed: Response format { user: {...} } → { data: {...} }
+- Added: PATCH /users/:id/profile endpoint
+- Fixed: User role permission bug
+
+**Deployment Details**:
+- Stage 1: 1% traffic, 1 hour, ✅ PASS
+- Stage 2: 10% traffic, 2 hours, ✅ PASS
+- Stage 3: 50% traffic, 4 hours, ✅ PASS
+- Stage 4: 100% traffic, 24+ hours, ✅ PASS
+
+**Metrics**:
+- Error Rate: 0.08% (target <1%) ✅
+- Latency P95: 191ms (target <200ms) ✅
+- Availability: 99.92%
+- Issues: None
+- Rollback: Not required
+
+**Consumers Migrated**:
+- WebApp: ✅ Updated (deployed v[X] with response parsing fix)
+- Mobile: ✅ Already on v1.3+
+- Dashboard: ✅ Updated
+- Admin: ✅ Updated
+- Partners: ⏳ In progress (2/3 clients migrated)
+
+**Post-Deployment**:
+- Monitoring window: 24 hours
+- All checks: ✅ PASS
+- Team stood down: 2026-06-01 18:00 UTC
+- Previous version decommissioned: 2026-06-01 20:00 UTC
+
+---
+
+## v2.5.3 - May 15, 2026
+
+**Status**: ✅ COMPLETE (patch release)
+...
+```
+
+---
+
+## release-metrics.csv Format
+
+```csv
+date,version,strategy,risk_score,breaking_changes,affected_consumers,duration_hours,error_rate_pct,latency_p95_ms,issues_count,rollback_required,approval_chain,status
+2026-05-31,v3.0.0,canary,7,2,12,8.5,0.08,191,0,false,TL+PL,complete
+2026-05-15,v2.5.3,rolling,2,0,0,2.0,0.06,185,0,false,TL,complete
+2026-05-01,v2.5.2,rolling,1,0,0,1.5,0.07,187,0,false,auto,complete
+2026-04-15,v2.5.1,blue-green,3,1,3,3.0,0.09,192,1,false,TL+PL,complete
+2026-04-01,v2.5.0,canary,6,1,8,9.0,0.08,190,0,false,TL+PL+CTO,complete
+```
+
+---
+
+## Monthly Health Report Template
+
+```markdown
+# Release Health Report - May 2026
+
+## Summary
+
+| Metric | May 2026 | April 2026 | Trend |
+|--------|----------|-----------|-------|
+| Releases | 5 | 4 | ↑ 25% |
+| Avg Risk Score | 3.8/10 | 4.2/10 | ↓ Improving |
+| Avg Error Rate | 0.077% | 0.081% | ↓ Improving |
+| Avg Latency P95 | 189ms | 194ms | ↓ Improving |
+| Rollback Rate | 0% | 0% | = Stable |
+| Avg Deploy Time | 3.5 hrs | 4.1 hrs | ↓ Faster |
+| Consumer Migration Success | 99.5% | 97% | ↑ Improving |
+
+---
+
+## May Releases
+
+### v3.0.0 - May 31 (MAJOR)
+- Strategy: Canary
+- Duration: 8.5 hours
+- Status: ✅ Success
+- Issues: None
+
+### v2.5.3 - May 15 (PATCH)
+- Strategy: Rolling
+- Duration: 2 hours
+- Status: ✅ Success
+- Issues: None
+
+### v2.5.2 - May 1 (PATCH)
+- Strategy: Rolling
+- Duration: 1.5 hours
+- Status: ✅ Success
+- Issues: None (bug fix)
+
+---
+
+## Performance Trends
+
+### Deployment Duration (Hours)
+
+```
+May 31: 8.5 (canary v3.0.0, complex)
+May 15: 2.0 (rolling v2.5.3, simple)
+May 1:  1.5 (rolling v2.5.2, simple)
+Apr 15: 3.0 (blue-green v2.5.1, medium)
+Apr 1:  9.0 (canary v2.5.0, complex)
+
+Average: 4.8 hours → Targeting: 3.5 hours
+```
+
+### Error Rates (%)
+
+```
+May avg: 0.077%
+Apr avg: 0.081%
+Mar avg: 0.095%
+
+Trend: ↓ Improving (better automation, earlier detection)
+Target: <0.05% by Q3 2026
+```
+
+### Rollback Rate (%)
+
+```
+May: 0% (5/5 successful, no rollbacks)
+Apr: 0% (4/4 successful, no rollbacks)
+Mar: 20% (1/5 rolled back due to API format issue)
+
+Trend: ↑ Improving (pre-deployment validation preventing failures)
+```
+
+---
+
+## Improvement Opportunities
+
+1. **Deployment Automation**: Canary stages could be automated further (currently manual decisions)
+   - Expected savings: 2+ hours per release
+   - Effort: Medium (auto-go criteria definition)
+
+2. **Consumer Migration**: Manual tracking of consumer updates
+   - Expected savings: 1 hour per breaking change release
+   - Effort: High (requires consumer API integration)
+
+3. **Database Migrations**: Currently manual (could auto-rollback if data inconsistency detected)
+   - Expected savings: 30 min per migration
+   - Effort: High (complex, risky)
+
+---
+
+## Queries & Analytics
+
+### Find all BREAKING releases in past 30 days
+```
+SELECT * FROM release_metrics 
+WHERE date > DATE('2026-05-01') 
+  AND breaking_changes > 0
+ORDER BY date DESC;
+
+Result: v3.0.0 (2 breaking), v2.5.1 (1 breaking)
+```
+
+### Find releases with longest deployment time
+```
+SELECT date, version, strategy, duration_hours, risk_score
+FROM release_metrics
+ORDER BY duration_hours DESC
+LIMIT 5;
+
+Result:
+- v2.5.0: 9.0 hours (canary, risk 6)
+- v3.0.0: 8.5 hours (canary, risk 7)
+- v2.5.1: 3.0 hours (blue-green, risk 3)
+```
+
+### Calculate average deployment time by strategy
+```
+SELECT strategy, COUNT(*) as count, AVG(duration_hours) as avg_duration
+FROM release_metrics
+GROUP BY strategy
+ORDER BY avg_duration DESC;
+
+Result:
+- Canary: avg 8.75 hours (2 releases)
+- Blue-Green: avg 3.0 hours (1 release)
+- Rolling: avg 1.67 hours (2 releases)
+```
+
+### Find releases with issues
+```
+SELECT date, version, issues_count, rollback_required, status
+FROM release_metrics
+WHERE issues_count > 0 OR rollback_required = true;
+
+Result: None in May 2026 (all clean)
+```
+
+---
+
+## Monthly Highlights
+
+✅ **Successes**:
+- 5 releases completed without rollbacks
+- v3.0.0 (major, breaking) deployed successfully with canary strategy
+- 99.5% consumer migration success rate
+- Error rates improving month-over-month
+
+⚠️ **Opportunities**:
+- Reduce canary deployment time (currently 8+ hours for high-risk)
+- Automate consumer migration tracking
+- Enhance pre-deployment validation
+
+🎯 **Targets for June**:
+- Reduce avg deployment time to 3 hours (vs 4.8 current)
+- Maintain 0% rollback rate
+- 100% consumer migration for breaking changes
+- Implement auto-canary-stage-progression
+
+---
+
+## Archive Strategy
+
+- **Recent** (< 3 months): Keep in RELEASE_LOG.md + release-metrics.csv
+- **Aging** (3-12 months): Archive to release-metrics-2026-Q1.csv.gz
+- **Archived** (> 12 months): Store in S3, reference in historical reports
+
+Example:
+- 2026 Q1: release-metrics-2026-Q1.csv.gz (archived May 2026)
+- 2025 Q4: release-metrics-2025-Q4.csv.gz (archived Feb 2026)