# Release Management Optimization

**Created**: 2026-01-06
**Status**: Planning → Ready to implement
**Priority**: High (blocks v0.10.0 release)

## Quick Summary

Enhance release management with robust validation using the schema system we just built. Creates a perfect showcase: **validate CHANGELOG.md with a changelog schema**.

## Critical Issues Found

1. **setuptools-scm bug**: Missing tag_regex → `markitect --version` returns "unknown"
2. **Missing v0.9.0 tag**: CHANGELOG says v0.9.0 released but git tag never created
3. **No validation**: No checks for CHANGELOG format or version-tag consistency

## Solution

Create **changelog-schema-v1.0.md** to validate Keep a Changelog format, integrate into release workflow. Demonstrates schema evolution in action!

## Staged Approach

- **Stage 1** (45 min): Critical fixes → unblock v0.10.0 release
- **Stage 2** (2.5 hrs): CHANGELOG schema → showcase feature
- **Stage 3** (2 hrs): Release tooling enhancements
- **Stage 4** (optional): Schema extensions (hooks/agents)

**Recommended**: Standard Track (Stages 1-3) = 5 hours for production-ready release management

## Files

- `WORKPLAN.md` - Detailed staged implementation plan
- `DONE.md` - Completion checklist (when finished)

## Philosophy

> "Use the tools we build to improve the tools we build."

Release v0.10.0 becomes: **The release that validates itself** 🎯
