Files

tegwick 5e3646fdff feat: complete schema-evolution topic with ADR schema and markdown support

This commit closes the schema-evolution topic (260105) by adding the final
deliverable (ADR schema) and fixing markdown schema support across commands.

**ADR Schema Created**:
- Comprehensive Architecture Decision Record validation schema
- 12 section classifications (7 required, 2 recommended, 2 optional, 3 improper/discouraged)
- Content pattern validation for ADR formatting rules (status dates, decision statements, rationale structure)
- Quality metrics for completeness (word counts, sentence counts)
- Follows title case naming convention (Status, Context, Decision, etc.)

**Markdown Schema Support Fixed**:
- Fixed `markitect validate` command to support .md schemas
  - Added load_schema_from_path() for both .json and .md files
  - Updated structural and semantic validation to use schema dict
- Fixed `markitect generate-stub` command to support .md schemas
  - Uses load_schema_from_path() instead of direct JSON loading
- Created DocumentWrapper class in semantic_validator.py
  - Extracts headings from AST tokens (heading_open, inline)
  - Provides get_headings_by_level() interface expected by validators
  - Enables section validation to work with real documents

**Topic Closure**:
- Updated SCHEMA_EVOLUTION_WORKPLAN.md with completion summary
  - Phases 1-3: 100% complete (via Schema-of-Schemas and Semantic Validation)
  - Phase 4: Deferred as future enhancement (15-20 sessions)
  - Phase 5: 70% complete (docs done, CI/CD templates deferred)
- Created DONE.md with comprehensive task checklist
- Generated ADR template stub (examples/templates/adr-template.md)
- Moved topic from roadmap/ to history/260105-schema-evolution/

**Files Changed**:
- markitect/cli.py: Added markdown schema support to validate and generate-stub
- markitect/semantic_validator.py: Added DocumentWrapper class for AST parsing
- markitect/schemas/adr-schema-v1.0.md: New ADR validation schema (560 lines)
- examples/templates/adr-template.md: Generated ADR template stub
- history/260105-schema-evolution/: Moved completed topic to history

**Status**: Schema evolution topic successfully closed with ADR schema as final deliverable.
All schema commands now support markdown schemas. Section validation working correctly.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-01-06 12:32:38 +01:00

eat-the-frog

chore: roadmap cleanup

2026-01-05 20:37:18 +01:00

README.md

docs: standardize on yymmdd- timestamp prefix format

2026-01-06 03:57:42 +01:00

README.md

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