tegwick
4e9117ddcb
Created comprehensive staged workplan for enhancing release management infrastructure with robust validation using the schema system. **Critical Issues Identified**: - setuptools-scm missing tag_regex configuration - markitect --version returns 'unknown' instead of actual version - CHANGELOG shows v0.9.0 (2025-11-14) but git tag never created - No validation for CHANGELOG format or version-tag consistency **Solution Approach**: Create changelog-schema-v1.0.md to validate Keep a Changelog format, demonstrating schema evolution in real-world use case. **Staged Workplan**: - Stage 1 (45 min): Critical fixes to unblock v0.10.0 release - Stage 2 (2.5 hrs): CHANGELOG schema creation and validation - Stage 3 (2 hrs): Release capability enhancements - Stage 4 (optional): Schema system extensions **Showcase Feature**: 'The release that validates itself' - v0.10.0 uses its own schema system to validate its CHANGELOG - Perfect demonstration of schema evolution practical value **Next Version**: v0.10.0 (not v0.9.0) - CHANGELOG already shows v0.9.0 as released - Must maintain version history integrity
MarkiTect Project Roadmap
This roadmap directory contains planning directories for roadmap topics.
- When starting to implement a topic its directory will be timestamped
- If implementing multiple topics in parallel use branches
- Keep current state of what's next to implement in TODO.md
- See ../history directory for closed topics
Naming Convention
Directory Format: yymmdd-topic-name
- Use 2-digit year prefix (e.g.,
260106-for 2026-01-06) - Lowercase topic names with hyphens
- Examples:
260106-semantic-document-validation,260105-schema-evolution
This convention keeps names concise while maintaining chronological sorting.
Purpose
This planning documentation serves multiple purposes:
- Implementation State Awareness: Allow for recovery after breaks or breakdowns
- Minimal Plan-Implement Loop: Don't complicate agentic coding with issue tracking if unnecessary
- Planning Info Analysis: Keeping the planning info allows for retrospective analyses to optimize
- Clean Repo Structure: Using roadmap/ for planning and TODO.md as current state helps stay organized
xxx