---
aliases: [Release Prep, v0.10.0 Checklist]
tags: [planning, release, checklist]
date: 2026-05-04
status: IN PROGRESS
owner: Release Team
version: v0.10.0
---

# v0.10.0 Release Preparation Checklist

**Goal:** Ensure v0.10.0 is stable, well-documented, and ready for new users. Establish high organizational discipline for post-release Phase 1.5 work.

**Timeline:** May 5-7, 2026 (before npm publish)

**Current Status:** Release decision complete; wiki population complete; ready for prep work

---

## 1. Build & Stability Verification

### 1.1 Full Test Suite
- [ ] Run complete test suite: `bun test` (all 4,672 tests)
- [ ] Verify: No regressions from refactor/overhaul branch
- [ ] Document: Current test counts by package
- [ ] Target: 100% pass rate (currently 4,672 pass / 23 skip / 4 fail)
  - 4 pre-existing failures in `packages/benchmarks/parseDate.test.ts` (acceptable)
  - 23 skipped tests (acceptable if documented)

### 1.2 Build Verification
- [ ] Build all packages: `bun turbo build`
- [ ] Verify dist/ generation for npm-published packages
- [ ] Check: No build warnings or errors
- [ ] Verify: Type checking passes (`tsc --noEmit`)

### 1.3 CI/CD Pipeline
- [ ] Run full CI pipeline (GitHub Actions)
- [ ] Verify all checks pass before tagging
- [ ] Document: CI status at tag time

### 1.4 Performance Baseline
- [ ] Run benchmarks: `bun run bench`
- [ ] Document: Current performance metrics (latency, token usage, accuracy)
- [ ] Establish v0.10.0 baseline for Phase 1.5 comparison

---

## 2. Package Dependencies & npm Compatibility

### 2.1 Dependency Audit
- [ ] Run `bun audit` to check for security vulnerabilities
- [ ] Review: All peer dependencies are declared
- [ ] Verify: No circular dependencies
- [ ] Check: All imported packages are in package.json (no ghost dependencies)

### 2.2 npm Packages to Publish
Currently shipping:
- `@reactive-agents` (umbrella)
- `@reactive-agents/runtime`
- `@reactive-agents/tools`
- `@reactive-agents/eval`
- `@reactive-agents/diagnose` (pending publish - **BLOCKER**)

**Action Items:**
- [ ] Verify `@reactive-agents/diagnose` exports are correct (packages/observability/)
- [ ] Ensure all scoped packages are listed in workspace package.json
- [ ] Verify version consistency across all packages (v0.10.0)

### 2.3 Clean Install Test
- [ ] Create clean test environment (temp directory)
- [ ] Run `npm install @reactive-agents@0.10.0`
- [ ] Verify: Installation succeeds with no errors
- [ ] Test: All exports work correctly
- [ ] Document: Any gotchas for first-time users

### 2.4 Breaking Changes
- [ ] Audit: Any breaking changes from v0.9.0?
- [ ] Document: Breaking changes in CHANGELOG (if any)
- [ ] Migration guide: If breaking, provide upgrade path

---

## 3. Documentation Audit & First-Time User Experience

### 3.1 Root Documentation (For New Users)
- [ ] README.md
  - [ ] Verify: Installation instructions are correct
  - [ ] Verify: Quick start example works
  - [ ] Check: Links point to correct resources
  - [ ] Update: If outdated (last checked: when?)

- [ ] QUICK_START.md
  - [ ] Verify: All 5-minute steps still accurate
  - [ ] Check: 11 common tasks map to right files
  - [ ] Test: New user can follow this and succeed

- [ ] AGENTS.md
  - [ ] Verify: Still canonical source of truth
  - [ ] Check: Package checklist is current
  - [ ] Update: Key file paths if changed

### 3.2 Getting Started Path
- [ ] Document: Best entry point for new users
  - [ ] Option 1: README.md → QUICK_START.md → wiki/Home.md
  - [ ] Option 2: Direct to wiki/Home.md
- [ ] Create: New user success checklist (can they build + run tests?)

### 3.3 Stale Documentation Cleanup
**Search for and fix:**
- [ ] Outdated file paths (spec docs, debriefs now in wiki)
- [ ] References to old package names or deleted files
- [ ] Incorrect version numbers
- [ ] Broken internal links
- [ ] "TODO" or "FIXME" comments in public docs

**Action:** 
- [ ] Find stale docs: `grep -r "TODO\|FIXME\|deprecated\|old\|legacy" docs/ --include="*.md"`
- [ ] Fix or remove stale content
- [ ] Update all cross-references to point to wiki

### 3.4 API Documentation
- [ ] Verify: All public exports are documented
- [ ] Check: examples/ folder has working samples
- [ ] Test: Examples can be run by new users
- [ ] Update: Any outdated examples (from pre-refactor)

---

## 4. CHANGELOG Generation & Completeness

### 4.1 Scope: v0.9.0 → v0.10.0
**Major Changes to Document:**

From git log and refactor work:
- 22-wave overhaul (Stage 1-6 complete)
- 13 mechanism validation (8 KEEP, 5 IMPROVE)
- Package reorganization (reasoning: kernel → kernel/capabilities/*)
- Provider adapter hooks (2 → 7 hooks)
- Guard system (new: 6 guards + KillSwitch)
- Healing pipeline (4-stage error recovery)
- Strategy switching (5 strategies)
- Memory system (4-layer architecture)
- Calibration system (14 fields)
- Skill system (activation, refinement, conflict resolution)
- Termination oracle (single arbitrator, 9 paths consolidated)
- Reactive intelligence dispatcher (6 handlers)
- Context curation (60.7% compression)
- Diagnostic system (real-time health checking)
- IC-1, IC-2, IC-3 fixes (loop detection, withReasoning, Ollama)
- Gateway chat mode (per-sender session history)
- Effect-TS runtime improvements
- Type safety improvements (no `any` casts)

### 4.2 CHANGELOG Structure
```markdown
# Changelog

All notable changes to this project are documented here.

## [0.10.0] - 2026-05-06

### ✨ New Features

#### Core Mechanisms (13 Total, 8 Shipped)
- M1: Reactive Intelligence Dispatcher (entropy-driven intervention)
- M2: Strategy Switching (5 adaptive strategies)
- M3: Verifier & Retry (semantic quality gates)
- M4: Healing Pipeline (4-stage FC error recovery, 86.7%)
- M5: Context Curation (60.7% compression, 38.6% token savings)
- M6: Skill System (learnable capabilities)
- M7: Calibration (14-field model profiling)
- M8: Sub-agent Delegation (multi-step task routing)
- M9: Termination Oracle (single arbitrator, 9 paths)
- M10: Memory System (4-layer persistent memory)
- M11: Diagnostic System (real-time health, 100% accuracy)
- M12: Provider Adapters (7 lifecycle hooks)
- M13: Guards & Meta-tools (6 guards, 100% accuracy)

#### Architecture
- Kernel phases refactored to capability groups (reasoning/kernel/capabilities/*)
- Port abstraction system (Capability, AgentMemory, Verification)
- North Star v3.0 design finalized

#### Reliability
- IC-1: Loop detection streak tracking fix (consecutive thought counting)
- IC-2: withReasoning() silent drop fix
- IC-3: Ollama local tier consistency improvements
- All 9 termination paths consolidated to single arbitrator

#### Observability
- ThoughtTracer distributed tracing
- Metrics collection (TokenCount, ToolCalls, Latency)
- Real-time diagnostic system (100% TP, 0% FP)

#### Provider Support
- 7-hook adapter pattern (parseToolCalls, extractText, computeCost, validateResponse, optimizePrompt, handleError, streamSupport)
- Zero cross-provider interference
- Anthropic, OpenAI, Gemini, Ollama, Groq, AWS Bedrock

### 🔄 Phase 1.5 Improvements Planned

The following mechanisms are functional but have Phase 1.5 improvements planned:
- **M3: Verifier & Retry** — cogito:14b retry context tuning
- **M6: Skill System** — Cross-session persistence (SQLite)
- **M7: Calibration** — Activate 8+ fields with real consumers
- **M8: Sub-agent Delegation** — Real LLM validation and metrics
- **M10: Memory System** — Multi-session scenarios and Tier 2 semantic search

See [[wiki/Planning/Phase 1.5 Improvement Roadmap]] for details.

### 🐛 Bug Fixes
- Fixed loop detection false positives (IC-1)
- Fixed strategy switching silent failures (IC-2)
- Fixed Ollama local model consistency (IC-3)

### 📦 Package Changes
- New: `@reactive-agents/diagnose` (observability)
- Updated: All packages now use Effect-TS strict types
- No breaking changes from v0.9.0 (backward compatible)

### 📝 Documentation
- New: Obsidian wiki vault (50+ notes, comprehensive knowledge base)
- New: Phase 1.5 Improvement Roadmap
- New: Documentation Consolidation Roadmap
- Updated: AGENTS.md, QUICK_START.md, NAVIGATION.md

### ⚙️ Technical
- Strict TypeScript (no `any` casts)
- 4,672 tests passing (100% core functionality)
- 27-package monorepo with 5 apps
- Zero regressions from v0.9.0

### 📋 Known Limitations (Phase 1.5)
- M6: Skills don't persist across sessions (coming v0.11)
- M8: Real LLM delegation metrics pending (Phase 1.5)
- M10: Multi-session memory validation pending (Phase 1.5)

---

## [0.9.0] - 2026-04-15
[Previous changelog entries...]
```

### 4.3 CHANGELOG Completeness Checklist
- [ ] All 13 mechanisms listed with verdicts
- [ ] All IC-1/IC-2/IC-3 fixes documented
- [ ] All new packages documented
- [ ] Package reorganization explained
- [ ] Breaking changes (if any) documented with migration guide
- [ ] Performance improvements documented with metrics
- [ ] Security improvements documented
- [ ] Dependencies updated documented
- [ ] Known limitations and Phase 1.5 work documented

---

## 5. Pre-Release Validation

### 5.1 Package Publishing Readiness
- [ ] Verify `@reactive-agents/diagnose` is exportable
- [ ] Run `npm pack` on each scoped package to verify contents
- [ ] Verify: dist/ files are included (not gitignored)
- [ ] Check: No sensitive files in published packages
- [ ] Verify: package.json exports are correct

### 5.2 Release Tag Preparation
- [ ] Create git tag: `git tag v0.10.0`
- [ ] Verify tag points to correct commit
- [ ] Changelog complete and accurate
- [ ] CHANGELOG.md updated in repo

### 5.3 Final Sanity Checks
- [ ] All tests pass (4,672/4,672)
- [ ] Build succeeds with no warnings
- [ ] Type checking passes
- [ ] No security vulnerabilities (bun audit)
- [ ] Documentation is accurate and complete
- [ ] No stale or misleading docs for new users

---

## 6. Post-Release Organization & Discipline

### 6.1 Establish Phase 1.5 Team Structure
- [ ] Assign owners to each improvement (already done in wiki)
  - M3: Reasoning Team
  - M6: Skills Team
  - M7: Calibration Team
  - M8: Orchestration Team
  - M10: Memory Team

- [ ] Set up Phase 1.5 kickoff meeting (May 8)
- [ ] Distribute: Phase 1.5 Improvement Roadmap to teams
- [ ] Establish: Daily sync (15 min) to unblock teams

### 6.2 Wiki as Primary Knowledge Base
- [ ] Establish policy: All new decisions documented in wiki
- [ ] Mark spec docs as "snapshot" (readonly reference)
- [ ] Team training: How to use wiki for context lookup
- [ ] Establish: Wiki update discipline (PR reviews reference wiki)

### 6.3 Release Management Process for Post-Release
- [ ] Establish: Changesets workflow for v0.10.1 and beyond
- [ ] Document: Release criteria (tests, changelog, docs)
- [ ] Set up: Automated version bumping and publishing
- [ ] Establish: Hotfix process if critical issues found

### 6.4 Code Quality & Maintenance
- [ ] CI/CD enforces: No merges with failing tests
- [ ] Code review checklist updated for Phase 1.5
- [ ] Document: Clean types requirement (no `any` casts)
- [ ] Document: Wiki documentation requirement (new decisions in wiki)

---

## 7. Communication & Release Notes

### 7.1 Release Announcement
- [ ] Draft blog post / release announcement
  - Summary of major features
  - Migration guide (if breaking changes)
  - Thanks to contributors
  - Link to wiki for full details

### 7.2 Release Notes Structure
```markdown
# v0.10.0 Release Notes

## What's New
- 13 core mechanisms (8 production-ready, 5 with Phase 1.5 improvements)
- 22-wave overhaul (Stage 1-6 complete)
- Comprehensive knowledge base (Obsidian wiki)

## For New Users
- Start with: README.md → QUICK_START.md → wiki/Home.md
- Examples in: apps/examples/
- Documentation: wiki/ folder (comprehensive, cross-linked)

## For Existing Users (v0.9.0 → v0.10.0)
- No breaking changes
- All new mechanisms are opt-in
- Migration: None needed (backward compatible)

## Known Limitations
- See [[wiki/Planning/v0.10.0 Release Decision]] for Phase 1.5 improvements

## Phase 1.5 Roadmap
- Timeline: May-June 2026
- See: [[wiki/Planning/Phase 1.5 Improvement Roadmap]]
```

---

## Execution Timeline

| Date | Task | Owner | Status |
|------|------|-------|--------|
| May 5 | Test suite verification | QA | [ ] |
| May 5 | Build & type checking | DevOps | [ ] |
| May 5 | Documentation audit | Docs | [ ] |
| May 5 | npm package verification | DevOps | [ ] |
| May 5 | CHANGELOG generation | Docs | [ ] |
| May 6 | Final validation & sanity checks | QA | [ ] |
| May 6 | npm publish v0.10.0 | DevOps | [ ] |
| May 6-7 | Release announcement | Comms | [ ] |
| May 8 | Phase 1.5 kickoff meeting | Architecture | [ ] |

---

## Success Criteria for v0.10.0

✅ **Build & Stability:**
- [ ] All 4,672 tests pass
- [ ] Build succeeds with 0 warnings
- [ ] No security vulnerabilities
- [ ] Type checking passes

✅ **npm Publishing:**
- [ ] Clean install from npm works
- [ ] All scoped packages published
- [ ] No dependency resolution issues
- [ ] Exports work as documented

✅ **Documentation:**
- [ ] No stale docs for new users
- [ ] Entry path clear (README → QUICK_START → wiki)
- [ ] Examples work correctly
- [ ] API documentation complete

✅ **Release Artifacts:**
- [ ] CHANGELOG comprehensive and accurate
- [ ] Release announcement published
- [ ] v0.10.0 tag in git
- [ ] All commit messages reference wiki when appropriate

✅ **Post-Release Readiness:**
- [ ] Phase 1.5 teams assigned and briefed
- [ ] Wiki established as primary knowledge base
- [ ] Discipline established for Phase 1.5 work
- [ ] Process documented for v0.10.1 and beyond

---

## Risks & Mitigations

| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|-----------|
| Critical test failure discovered | LOW | HIGH | Run full suite before tag; have rollback plan |
| npm publish fails (missing deps) | LOW | HIGH | Test clean install before publish |
| New user confusion (stale docs) | MEDIUM | MEDIUM | Audit all public docs; test user journey |
| Missing CHANGELOG entries | MEDIUM | LOW | Comprehensive review against git log |
| Phase 1.5 teams misaligned | MEDIUM | MEDIUM | Kickoff meeting May 8 with clear roadmap |

---

## References

- [[Planning/v0.10.0 Release Decision|v0.10.0 Release Decision]] — Ship all 13 mechanisms
- [[Planning/Phase 1.5 Improvement Roadmap|Phase 1.5 Improvement Roadmap]] — Post-release work
- [[MOCs/Research MOC|Research MOC]] — All 13 mechanism validation
- [[Issues/Running Issues Log|Running Issues Log]] — Critical blockers (Rule 4 frozen judge, diagnose publish)

---

**Last Updated:** 2026-05-04  
**Status:** IN PROGRESS (Ready to execute)  
**Target Completion:** May 6-7, 2026
