coulomb/markitect-main
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
markitect-main/CHANGELOG.md

259 lines
16 KiB
Markdown
Raw Normal View History

release: prepare v0.4.0 - Enhanced Edit Mode & Version Tracking Key improvements: - Fixed critical md-render --edit functionality that was broken - Enhanced version tracking with git commit hash, timestamps, and local changes detection - Comprehensive regression tests to prevent future breaks - Repository cleanup completed 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-25 20:13:41 +02:00
# Changelog
docs: complete CHANGELOG.md with missing historical versions - Add standard Keep a Changelog header with format description - Add Unreleased section following standard format - Add comprehensive entries for versions 0.1.0, 0.2.0, and 0.3.0 - Research and document historical features using git log analysis - Follow Keep a Changelog categories (Added, Changed, Fixed) - Maintain chronological order with proper release dates - Update TODO.md to reflect completed changelog enhancement work 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 20:09:02 +01:00
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
feat: fix contents panel scrollbar and consolidate control architecture ## Major Changes - Fixed contents panel scrollbar behavior to only span content area when reaching max-height - Eliminated duplicate control files across testdrive-jsui/static/ and markitect/static/ - Consolidated all control files to single source of truth in capabilities/testdrive-jsui/js/controls/ - Refactored contents control to use proper base class architecture ## Technical Details - Moved overflow-y: auto from control-content-container to control-content-body - Updated all HTML templates and plugin references to use capabilities/ paths - Enhanced resize handle positioning (moved from -4px to 1px/2px from right edge) - Improved CSS flex layout with proper min-height: 0 constraints ## Files Affected - 10 duplicate control files removed - 8+ reference files updated with new paths - CHANGELOG.md updated with all changes This eliminates confusion about which files to edit and ensures the UI behaves correctly when panels reach viewport height limits. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 23:55:52 +01:00
### Added
chore: establish schema-of-schemas workplan and reorganize roadmap This commit sets up the comprehensive workplan for implementing a markdown-first schema management system with naming conventions, versioning, and self-validation capabilities. ## Directory Reorganization - Renamed `todo/` → `roadmap/` for better organization - Created `roadmap/schema-of-schemas/` subdirectory - Moved schema management planning artifacts to dedicated directory ## Planning Artifacts Created ### Workplan & Documentation - **WORKPLAN.md** (19KB) - Comprehensive 6-phase implementation plan - **SCHEMA_MANAGEMENT_PROPOSAL.md** - Full analysis with 4 options - **SCHEMA_MANAGEMENT_SUMMARY.md** - Executive summary - **README.md** - Quick reference guide ### Example Schema - **examples/schemas/manpage-schema-v1.md** - Demonstrates markdown format ## Schema Management System Design ### Naming Convention **Format:** `{domain}-schema-v{major}.{minor}.md` **Examples:** - `manpage-schema-v1.0.md` - `terminology-schema-v1.0.md` - `api-documentation-schema-v1.0.md` ### Markdown-First Format Schemas will be markdown files with: - YAML frontmatter for metadata - Rich documentation sections - Embedded JSON schema in code block - Version history and examples ### Implementation Phases (8-10 days) **Phase 0:** Planning & Setup ✅ (0.5 days) - COMPLETE **Phase 1:** Filename Convention (1 day) - NEXT **Phase 2:** Markdown Loader (2-3 days) **Phase 3:** Schema-for-Schemas (2 days) **Phase 4:** Schema Migration (1-2 days) **Phase 5:** CLI & Documentation (1 day) **Phase 6:** Testing & Validation (1 day) ### Goals 1. ✅ Establish naming convention 2. ⏳ Implement filename validation 3. ⏳ Create markdown schema loader 4. ⏳ Build schema-for-schemas metaschema 5. ⏳ Migrate 5 existing schemas (remove 2 duplicates) 6. ⏳ Update CLI and documentation ## Updated Tracking ### TODO.md - Added Schema-of-Schemas as active work item - Documented Phase 1 tasks and timeline - Paused capability extraction work ### CHANGELOG.md - Added schema management system to [Unreleased] - Documented directory reorganization - Added "In Progress" section for current work ## Next Steps Begin Phase 1: 1. Implement schema_naming.py with validation 2. Add unit tests 3. Update CLI schema-ingest command 4. Create naming specification document ## Files Changed - CHANGELOG.md - Added unreleased schema management features - TODO.md - Updated active work tracking - roadmap/ - Reorganized from todo/ - roadmap/schema-of-schemas/ - New planning directory - examples/schemas/ - Example markdown schema 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-04 23:47:02 +01:00
- **Schema Management System**: Comprehensive schema management infrastructure with naming conventions and versioning
- Naming convention: `{domain}-schema-v{major}.{minor}.md` for all schemas
- Markdown-first schema format with embedded JSON (documentation + schema in one file)
- Schema catalog (`markitect/schemas/schema-catalog.yaml`) for metadata and discovery
- Terminology validation example (`examples/terminology/`) demonstrating schema usage beyond manpages
- Schema-for-schemas workplan in `roadmap/schema-of-schemas/` directory
- **Enhanced schema-list Command**: Now displays creation timestamps in all output formats
- Default format shows timestamps inline: `schema-name.json (added: 2026-01-04T23:01:19)`
- Table format includes Created/Updated columns
- Cleaner timestamp formatting (removed microseconds)
feat: fix contents panel scrollbar and consolidate control architecture ## Major Changes - Fixed contents panel scrollbar behavior to only span content area when reaching max-height - Eliminated duplicate control files across testdrive-jsui/static/ and markitect/static/ - Consolidated all control files to single source of truth in capabilities/testdrive-jsui/js/controls/ - Refactored contents control to use proper base class architecture ## Technical Details - Moved overflow-y: auto from control-content-container to control-content-body - Updated all HTML templates and plugin references to use capabilities/ paths - Enhanced resize handle positioning (moved from -4px to 1px/2px from right edge) - Improved CSS flex layout with proper min-height: 0 constraints ## Files Affected - 10 duplicate control files removed - 8+ reference files updated with new paths - CHANGELOG.md updated with all changes This eliminates confusion about which files to edit and ensures the UI behaves correctly when panels reach viewport height limits. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 23:55:52 +01:00
- Enhanced control panel UI with better resize handle positioning for improved user interaction
### Changed
chore: establish schema-of-schemas workplan and reorganize roadmap This commit sets up the comprehensive workplan for implementing a markdown-first schema management system with naming conventions, versioning, and self-validation capabilities. ## Directory Reorganization - Renamed `todo/` → `roadmap/` for better organization - Created `roadmap/schema-of-schemas/` subdirectory - Moved schema management planning artifacts to dedicated directory ## Planning Artifacts Created ### Workplan & Documentation - **WORKPLAN.md** (19KB) - Comprehensive 6-phase implementation plan - **SCHEMA_MANAGEMENT_PROPOSAL.md** - Full analysis with 4 options - **SCHEMA_MANAGEMENT_SUMMARY.md** - Executive summary - **README.md** - Quick reference guide ### Example Schema - **examples/schemas/manpage-schema-v1.md** - Demonstrates markdown format ## Schema Management System Design ### Naming Convention **Format:** `{domain}-schema-v{major}.{minor}.md` **Examples:** - `manpage-schema-v1.0.md` - `terminology-schema-v1.0.md` - `api-documentation-schema-v1.0.md` ### Markdown-First Format Schemas will be markdown files with: - YAML frontmatter for metadata - Rich documentation sections - Embedded JSON schema in code block - Version history and examples ### Implementation Phases (8-10 days) **Phase 0:** Planning & Setup ✅ (0.5 days) - COMPLETE **Phase 1:** Filename Convention (1 day) - NEXT **Phase 2:** Markdown Loader (2-3 days) **Phase 3:** Schema-for-Schemas (2 days) **Phase 4:** Schema Migration (1-2 days) **Phase 5:** CLI & Documentation (1 day) **Phase 6:** Testing & Validation (1 day) ### Goals 1. ✅ Establish naming convention 2. ⏳ Implement filename validation 3. ⏳ Create markdown schema loader 4. ⏳ Build schema-for-schemas metaschema 5. ⏳ Migrate 5 existing schemas (remove 2 duplicates) 6. ⏳ Update CLI and documentation ## Updated Tracking ### TODO.md - Added Schema-of-Schemas as active work item - Documented Phase 1 tasks and timeline - Paused capability extraction work ### CHANGELOG.md - Added schema management system to [Unreleased] - Documented directory reorganization - Added "In Progress" section for current work ## Next Steps Begin Phase 1: 1. Implement schema_naming.py with validation 2. Add unit tests 3. Update CLI schema-ingest command 4. Create naming specification document ## Files Changed - CHANGELOG.md - Added unreleased schema management features - TODO.md - Updated active work tracking - roadmap/ - Reorganized from todo/ - roadmap/schema-of-schemas/ - New planning directory - examples/schemas/ - Example markdown schema 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-04 23:47:02 +01:00
- **Directory Reorganization**: Renamed `todo/` → `roadmap/` for better organization of planning documents
- Created `roadmap/schema-of-schemas/` subdirectory for schema management planning artifacts
- Moved schema management proposals and workplan to dedicated directory
feat: fix contents panel scrollbar and consolidate control architecture ## Major Changes - Fixed contents panel scrollbar behavior to only span content area when reaching max-height - Eliminated duplicate control files across testdrive-jsui/static/ and markitect/static/ - Consolidated all control files to single source of truth in capabilities/testdrive-jsui/js/controls/ - Refactored contents control to use proper base class architecture ## Technical Details - Moved overflow-y: auto from control-content-container to control-content-body - Updated all HTML templates and plugin references to use capabilities/ paths - Enhanced resize handle positioning (moved from -4px to 1px/2px from right edge) - Improved CSS flex layout with proper min-height: 0 constraints ## Files Affected - 10 duplicate control files removed - 8+ reference files updated with new paths - CHANGELOG.md updated with all changes This eliminates confusion about which files to edit and ensures the UI behaves correctly when panels reach viewport height limits. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 23:55:52 +01:00
- Refactored contents control architecture to use base class pattern properly for better code organization
- Updated all file references and paths to point to single source of truth in capabilities/testdrive-jsui/js/controls/ directory
### Fixed
- Duplicate file structure issue by eliminating duplicate control files and consolidating to capabilities/ directory
- Contents panel scrollbar behavior - moved overflow-y: auto to correct container level so scrollbar only spans content area when panel reaches max-height
feat: remove legacy DocumentControls component Remove deprecated DocumentControls from TestDrive JSUI plugin system: - Remove document-controls.js from plugin asset list - Remove script reference from HTML template - Delete legacy document-controls files - Consolidate all functionality into enhanced control panels All control panel functionality now provided by enhanced controls: - ContentsControl (NW): Table of contents and navigation - StatusControl (E): Document status and metrics - DebugControl (SE): Debug messages and system info - EditControl (NE): Editing tools including Reset All button 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 15:46:50 +01:00
### Removed
- **BREAKING**: Legacy DocumentControls component from TestDrive JSUI plugin system - all control panel functionality now provided by enhanced control panels (ContentsControl, StatusControl, DebugControl, EditControl) with Reset All button functionality moved to EditControl for better maintainability and elimination of code duplication
chore: establish schema-of-schemas workplan and reorganize roadmap This commit sets up the comprehensive workplan for implementing a markdown-first schema management system with naming conventions, versioning, and self-validation capabilities. ## Directory Reorganization - Renamed `todo/` → `roadmap/` for better organization - Created `roadmap/schema-of-schemas/` subdirectory - Moved schema management planning artifacts to dedicated directory ## Planning Artifacts Created ### Workplan & Documentation - **WORKPLAN.md** (19KB) - Comprehensive 6-phase implementation plan - **SCHEMA_MANAGEMENT_PROPOSAL.md** - Full analysis with 4 options - **SCHEMA_MANAGEMENT_SUMMARY.md** - Executive summary - **README.md** - Quick reference guide ### Example Schema - **examples/schemas/manpage-schema-v1.md** - Demonstrates markdown format ## Schema Management System Design ### Naming Convention **Format:** `{domain}-schema-v{major}.{minor}.md` **Examples:** - `manpage-schema-v1.0.md` - `terminology-schema-v1.0.md` - `api-documentation-schema-v1.0.md` ### Markdown-First Format Schemas will be markdown files with: - YAML frontmatter for metadata - Rich documentation sections - Embedded JSON schema in code block - Version history and examples ### Implementation Phases (8-10 days) **Phase 0:** Planning & Setup ✅ (0.5 days) - COMPLETE **Phase 1:** Filename Convention (1 day) - NEXT **Phase 2:** Markdown Loader (2-3 days) **Phase 3:** Schema-for-Schemas (2 days) **Phase 4:** Schema Migration (1-2 days) **Phase 5:** CLI & Documentation (1 day) **Phase 6:** Testing & Validation (1 day) ### Goals 1. ✅ Establish naming convention 2. ⏳ Implement filename validation 3. ⏳ Create markdown schema loader 4. ⏳ Build schema-for-schemas metaschema 5. ⏳ Migrate 5 existing schemas (remove 2 duplicates) 6. ⏳ Update CLI and documentation ## Updated Tracking ### TODO.md - Added Schema-of-Schemas as active work item - Documented Phase 1 tasks and timeline - Paused capability extraction work ### CHANGELOG.md - Added schema management system to [Unreleased] - Documented directory reorganization - Added "In Progress" section for current work ## Next Steps Begin Phase 1: 1. Implement schema_naming.py with validation 2. Add unit tests 3. Update CLI schema-ingest command 4. Create naming specification document ## Files Changed - CHANGELOG.md - Added unreleased schema management features - TODO.md - Updated active work tracking - roadmap/ - Reorganized from todo/ - roadmap/schema-of-schemas/ - New planning directory - examples/schemas/ - Example markdown schema 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-04 23:47:02 +01:00
### In Progress
feat: implement Phase 3 - Schema-for-Schemas Metaschema Completed Phase 3 of the schema-of-schemas implementation with a comprehensive metaschema that validates all MarkiTect schema files against conventions and standards. Metaschema Implementation (schema-schema-v1.0.md - 650+ lines): - Validates core JSON Schema fields ($schema, $id, title, description) - Validates MarkiTect version field (SemVer: major.minor.patch) - Validates $id URL format (HTTPS with version path) - Validates MarkiTect extensions: - x-markitect-sections: section classifications and content rules - x-markitect-content-control: pattern and quality validation - x-markitect-metadata: status, authors, tags - x-markitect-source: loader metadata (auto-added) - Section classification validation (required, recommended, optional, discouraged, improper) - Content control pattern validation - Comprehensive documentation with examples and usage guides CLI Command (markitect schema-validate): - Validates schema files against metaschema - Supports both markdown and JSON schema files - Detailed error reporting with schema paths - Structure validation recommendations - Exit codes for CI/CD integration Test Coverage (tests/test_schema_metaschema.py - 12 tests, 100% passing): - Metaschema self-validation - Manpage schema validation - Required fields enforcement - Version format validation (valid and invalid cases) - $id format validation (valid and invalid cases) - Section classification validation - Complete schema with all extensions Validation Results: - ✅ Metaschema validates itself successfully - ✅ Manpage schema (v1.0.md) validates successfully - ⚠️ Terminology schema needs migration (missing version, incorrect $id) Progress Tracking: - Updated TODO.md with Phase 3 completion - Updated CHANGELOG.md with implementation details - Next: Phase 4 - Schema Migration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-05 03:10:49 +01:00
- **Schema-of-Schemas Implementation** (Phase 3 of 6 - Completed ✅)
feat: implement Phase 2 - Markdown Schema Loader Completed Phase 2 of the schema-of-schemas implementation with full markdown schema support. This enables schemas to be authored as markdown files with rich documentation and embedded JSON schemas. Core Implementation (markitect/schema_loader.py): - MarkdownSchemaLoader class with comprehensive parsing capabilities - YAML frontmatter extraction with error handling - JSON code block extraction with section preference (## Schema Definition) - Metadata merging with x-markitect-source tracking - Schema saving with template support and round-trip capability - Helper methods: list_json_blocks(), validate_schema_structure() Test Coverage (tests/test_schema_loader.py): - 35 comprehensive unit tests (100% passing) - Tests for loading, parsing, saving, round-trip conversion - Edge case handling (empty files, binary files, malformed blocks) - Fixed binary file test to use invalid UTF-8 sequences Example Schema (markitect/schemas/manpage-schema-v1.0.md): - First markdown schema following naming convention - Complete manpage schema with frontmatter + documentation + JSON - Demonstrates section classification and content control - Shows proper structure for future schema authors Documentation (roadmap/schema-of-schemas/SCHEMA_LOADER_GUIDE.md): - Comprehensive user guide (600+ lines) - API reference with examples - Best practices and troubleshooting - Integration patterns for CLI and validator Progress Tracking: - Updated TODO.md with Phase 2 completion - Updated CHANGELOG.md with implementation details - Next: Phase 3 - Schema-for-Schemas Metaschema 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-05 00:02:15 +01:00
- ✅ Phase 1: Filename validation for schema naming convention (`markitect/schema_naming.py`, 50 tests)
- ✅ Phase 2: Markdown schema loader to parse `.md` schema files (`markitect/schema_loader.py`, 35 tests)
feat: implement Phase 3 - Schema-for-Schemas Metaschema Completed Phase 3 of the schema-of-schemas implementation with a comprehensive metaschema that validates all MarkiTect schema files against conventions and standards. Metaschema Implementation (schema-schema-v1.0.md - 650+ lines): - Validates core JSON Schema fields ($schema, $id, title, description) - Validates MarkiTect version field (SemVer: major.minor.patch) - Validates $id URL format (HTTPS with version path) - Validates MarkiTect extensions: - x-markitect-sections: section classifications and content rules - x-markitect-content-control: pattern and quality validation - x-markitect-metadata: status, authors, tags - x-markitect-source: loader metadata (auto-added) - Section classification validation (required, recommended, optional, discouraged, improper) - Content control pattern validation - Comprehensive documentation with examples and usage guides CLI Command (markitect schema-validate): - Validates schema files against metaschema - Supports both markdown and JSON schema files - Detailed error reporting with schema paths - Structure validation recommendations - Exit codes for CI/CD integration Test Coverage (tests/test_schema_metaschema.py - 12 tests, 100% passing): - Metaschema self-validation - Manpage schema validation - Required fields enforcement - Version format validation (valid and invalid cases) - $id format validation (valid and invalid cases) - Section classification validation - Complete schema with all extensions Validation Results: - ✅ Metaschema validates itself successfully - ✅ Manpage schema (v1.0.md) validates successfully - ⚠️ Terminology schema needs migration (missing version, incorrect $id) Progress Tracking: - Updated TODO.md with Phase 3 completion - Updated CHANGELOG.md with implementation details - Next: Phase 4 - Schema Migration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-05 03:10:49 +01:00
- ✅ Phase 3: Schema-for-schemas metaschema for schema validation (`schema-schema-v1.0.md`, 12 tests)
feat: implement Phase 2 - Markdown Schema Loader Completed Phase 2 of the schema-of-schemas implementation with full markdown schema support. This enables schemas to be authored as markdown files with rich documentation and embedded JSON schemas. Core Implementation (markitect/schema_loader.py): - MarkdownSchemaLoader class with comprehensive parsing capabilities - YAML frontmatter extraction with error handling - JSON code block extraction with section preference (## Schema Definition) - Metadata merging with x-markitect-source tracking - Schema saving with template support and round-trip capability - Helper methods: list_json_blocks(), validate_schema_structure() Test Coverage (tests/test_schema_loader.py): - 35 comprehensive unit tests (100% passing) - Tests for loading, parsing, saving, round-trip conversion - Edge case handling (empty files, binary files, malformed blocks) - Fixed binary file test to use invalid UTF-8 sequences Example Schema (markitect/schemas/manpage-schema-v1.0.md): - First markdown schema following naming convention - Complete manpage schema with frontmatter + documentation + JSON - Demonstrates section classification and content control - Shows proper structure for future schema authors Documentation (roadmap/schema-of-schemas/SCHEMA_LOADER_GUIDE.md): - Comprehensive user guide (600+ lines) - API reference with examples - Best practices and troubleshooting - Integration patterns for CLI and validator Progress Tracking: - Updated TODO.md with Phase 2 completion - Updated CHANGELOG.md with implementation details - Next: Phase 3 - Schema-for-Schemas Metaschema 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-05 00:02:15 +01:00
- ⏳ Phase 4: Migration of 5 existing schemas to new format (will remove 2 duplicates)
- ⏳ Phase 5: CLI updates and documentation
- ⏳ Phase 6: Integration testing and validation
chore: establish schema-of-schemas workplan and reorganize roadmap This commit sets up the comprehensive workplan for implementing a markdown-first schema management system with naming conventions, versioning, and self-validation capabilities. ## Directory Reorganization - Renamed `todo/` → `roadmap/` for better organization - Created `roadmap/schema-of-schemas/` subdirectory - Moved schema management planning artifacts to dedicated directory ## Planning Artifacts Created ### Workplan & Documentation - **WORKPLAN.md** (19KB) - Comprehensive 6-phase implementation plan - **SCHEMA_MANAGEMENT_PROPOSAL.md** - Full analysis with 4 options - **SCHEMA_MANAGEMENT_SUMMARY.md** - Executive summary - **README.md** - Quick reference guide ### Example Schema - **examples/schemas/manpage-schema-v1.md** - Demonstrates markdown format ## Schema Management System Design ### Naming Convention **Format:** `{domain}-schema-v{major}.{minor}.md` **Examples:** - `manpage-schema-v1.0.md` - `terminology-schema-v1.0.md` - `api-documentation-schema-v1.0.md` ### Markdown-First Format Schemas will be markdown files with: - YAML frontmatter for metadata - Rich documentation sections - Embedded JSON schema in code block - Version history and examples ### Implementation Phases (8-10 days) **Phase 0:** Planning & Setup ✅ (0.5 days) - COMPLETE **Phase 1:** Filename Convention (1 day) - NEXT **Phase 2:** Markdown Loader (2-3 days) **Phase 3:** Schema-for-Schemas (2 days) **Phase 4:** Schema Migration (1-2 days) **Phase 5:** CLI & Documentation (1 day) **Phase 6:** Testing & Validation (1 day) ### Goals 1. ✅ Establish naming convention 2. ⏳ Implement filename validation 3. ⏳ Create markdown schema loader 4. ⏳ Build schema-for-schemas metaschema 5. ⏳ Migrate 5 existing schemas (remove 2 duplicates) 6. ⏳ Update CLI and documentation ## Updated Tracking ### TODO.md - Added Schema-of-Schemas as active work item - Documented Phase 1 tasks and timeline - Paused capability extraction work ### CHANGELOG.md - Added schema management system to [Unreleased] - Documented directory reorganization - Added "In Progress" section for current work ## Next Steps Begin Phase 1: 1. Implement schema_naming.py with validation 2. Add unit tests 3. Update CLI schema-ingest command 4. Create naming specification document ## Files Changed - CHANGELOG.md - Added unreleased schema management features - TODO.md - Updated active work tracking - roadmap/ - Reorganized from todo/ - roadmap/schema-of-schemas/ - New planning directory - examples/schemas/ - Example markdown schema 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-04 23:47:02 +01:00
docs: update CHANGELOG for v0.9.0 plugin infrastructure release Major version 0.9.0 release documenting the complete plugin infrastructure implementation that enables JavaScript-first development. **Added:** - Plugin Infrastructure Foundation with RenderingEnginePlugin system - TestDrive JSUI Plugin for independent JavaScript UI development - CLI Engine Parameter (--engine) with intelligent defaults - Automatic Asset Deployment to _markitect/plugins/ structure - Complete JavaScript-Python separation with JSON configuration **Changed:** - BREAKING: Edit mode now defaults to testdrive-jsui plugin - Asset management now automatic (no --ship-assets flag needed) - JavaScript architecture fully modularized with clean separation **Fixed:** - JavaScript const redeclaration and loading conflicts resolved - Plugin asset deployment and accessibility issues fixed **Migration Guide:** - Existing users automatically get new testdrive-jsui for edit mode - Legacy behavior available with --engine standard - Assets deploy automatically to output directories This represents the largest architectural enhancement to date, enabling independent JavaScript development while maintaining clean integration with the Python markdown processing pipeline. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 09:36:04 +01:00
## [0.9.0] - 2025-11-14
docs: complete project documentation and task management cleanup ### Documentation Updates - Added comprehensive WORKSPACE_AND_DATABASES.md documentation explaining: - Markitect's workspace-based architecture concept - Database separation (markitect.db vs assets.db) and purposes - Configuration management and asset integration - Best practices for development, collaboration, and production ### Changelog Management - Updated CHANGELOG.md with complete release history coverage - Added missing v0.8.0 entry for setuptools-SCM integration and release automation - Added proper version comparison links for all releases - Documented all recent work in Unreleased section following Keep a Changelog format ### Task Management - Cleaned TODO.md file by removing all completed tasks - Reset to clean state referencing changelog for completed work - Maintained Keep a Todofile format for future development sessions This completes the documentation and task management improvements for the ChatGPT theme implementation, modular theme system, issue-facade bug fixes, and workspace architecture clarification work. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 14:34:54 +01:00
### Added
docs: update CHANGELOG for v0.9.0 plugin infrastructure release Major version 0.9.0 release documenting the complete plugin infrastructure implementation that enables JavaScript-first development. **Added:** - Plugin Infrastructure Foundation with RenderingEnginePlugin system - TestDrive JSUI Plugin for independent JavaScript UI development - CLI Engine Parameter (--engine) with intelligent defaults - Automatic Asset Deployment to _markitect/plugins/ structure - Complete JavaScript-Python separation with JSON configuration **Changed:** - BREAKING: Edit mode now defaults to testdrive-jsui plugin - Asset management now automatic (no --ship-assets flag needed) - JavaScript architecture fully modularized with clean separation **Fixed:** - JavaScript const redeclaration and loading conflicts resolved - Plugin asset deployment and accessibility issues fixed **Migration Guide:** - Existing users automatically get new testdrive-jsui for edit mode - Legacy behavior available with --engine standard - Assets deploy automatically to output directories This represents the largest architectural enhancement to date, enabling independent JavaScript development while maintaining clean integration with the Python markdown processing pipeline. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 09:36:04 +01:00
- **Plugin Infrastructure Foundation**: Extended existing MarkiTect plugin system with RenderingEnginePlugin base class and RENDERING plugin type
- **RenderingEngineManager**: Complete plugin discovery and lifecycle management system for UI rendering engines
- **RenderingConfig System**: Asset management and deployment configuration for plugin engines
- **TestDrive JSUI Plugin**: Complete independent JavaScript UI plugin extracted from core system with standalone development environment
- **Modular Component Architecture**: Compass-positioned controls with clean JSON configuration interface for Python-JavaScript data transfer
- **CLI Engine Parameter**: Added --engine parameter to markitect md-render command with engine validation and mode compatibility checking
- **Automatic Asset Deployment**: Production-ready asset deployment to _markitect/plugins/ structure with 18 total assets (12 JS, 3 CSS, 3 images)
docs: complete project documentation and task management cleanup ### Documentation Updates - Added comprehensive WORKSPACE_AND_DATABASES.md documentation explaining: - Markitect's workspace-based architecture concept - Database separation (markitect.db vs assets.db) and purposes - Configuration management and asset integration - Best practices for development, collaboration, and production ### Changelog Management - Updated CHANGELOG.md with complete release history coverage - Added missing v0.8.0 entry for setuptools-SCM integration and release automation - Added proper version comparison links for all releases - Documented all recent work in Unreleased section following Keep a Changelog format ### Task Management - Cleaned TODO.md file by removing all completed tasks - Reset to clean state referencing changelog for completed work - Maintained Keep a Todofile format for future development sessions This completes the documentation and task management improvements for the ChatGPT theme implementation, modular theme system, issue-facade bug fixes, and workspace architecture clarification work. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 14:34:54 +01:00
- **ChatGPT Document Theme**: New document theme with Inter font, 580px width, and #10a37f accent color with full CLI support (`markitect md-render --theme chatgpt`)
- **Modular Theme System Architecture**: File-based theme loading with YAML configuration and dynamic theme discovery
- **Theme Directory Structure**: Organized theme components (mode/, ui/, document/, branding/) for better maintainability
- **Database Architecture Documentation**: Comprehensive WORKSPACE_AND_DATABASES.md documenting workspace concepts and database purposes
### Changed
docs: update CHANGELOG for v0.9.0 plugin infrastructure release Major version 0.9.0 release documenting the complete plugin infrastructure implementation that enables JavaScript-first development. **Added:** - Plugin Infrastructure Foundation with RenderingEnginePlugin system - TestDrive JSUI Plugin for independent JavaScript UI development - CLI Engine Parameter (--engine) with intelligent defaults - Automatic Asset Deployment to _markitect/plugins/ structure - Complete JavaScript-Python separation with JSON configuration **Changed:** - BREAKING: Edit mode now defaults to testdrive-jsui plugin - Asset management now automatic (no --ship-assets flag needed) - JavaScript architecture fully modularized with clean separation **Fixed:** - JavaScript const redeclaration and loading conflicts resolved - Plugin asset deployment and accessibility issues fixed **Migration Guide:** - Existing users automatically get new testdrive-jsui for edit mode - Legacy behavior available with --engine standard - Assets deploy automatically to output directories This represents the largest architectural enhancement to date, enabling independent JavaScript development while maintaining clean integration with the Python markdown processing pipeline. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 09:36:04 +01:00
- **BREAKING**: Edit mode now defaults to testdrive-jsui plugin instead of legacy edit mode
- **Default Rendering Behavior**: testdrive-jsui for edit/insert modes, standard for view mode with graceful fallback
- **Asset Management Strategy**: Automatic plugin asset deployment eliminates need for manual --ship-assets flag
- **JavaScript Architecture**: Clean separation between Python backend and JavaScript frontend with modular design
docs: complete project documentation and task management cleanup ### Documentation Updates - Added comprehensive WORKSPACE_AND_DATABASES.md documentation explaining: - Markitect's workspace-based architecture concept - Database separation (markitect.db vs assets.db) and purposes - Configuration management and asset integration - Best practices for development, collaboration, and production ### Changelog Management - Updated CHANGELOG.md with complete release history coverage - Added missing v0.8.0 entry for setuptools-SCM integration and release automation - Added proper version comparison links for all releases - Documented all recent work in Unreleased section following Keep a Changelog format ### Task Management - Cleaned TODO.md file by removing all completed tasks - Reset to clean state referencing changelog for completed work - Maintained Keep a Todofile format for future development sessions This completes the documentation and task management improvements for the ChatGPT theme implementation, modular theme system, issue-facade bug fixes, and workspace architecture clarification work. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 14:34:54 +01:00
- **Theme Loading System**: Implemented dynamic theme discovery and loading with metadata preservation
- **Test Suite Organization**: Removed obsolete configuration CLI tests (490 lines) for cleaner codebase
### Fixed
docs: update CHANGELOG for v0.9.0 plugin infrastructure release Major version 0.9.0 release documenting the complete plugin infrastructure implementation that enables JavaScript-first development. **Added:** - Plugin Infrastructure Foundation with RenderingEnginePlugin system - TestDrive JSUI Plugin for independent JavaScript UI development - CLI Engine Parameter (--engine) with intelligent defaults - Automatic Asset Deployment to _markitect/plugins/ structure - Complete JavaScript-Python separation with JSON configuration **Changed:** - BREAKING: Edit mode now defaults to testdrive-jsui plugin - Asset management now automatic (no --ship-assets flag needed) - JavaScript architecture fully modularized with clean separation **Fixed:** - JavaScript const redeclaration and loading conflicts resolved - Plugin asset deployment and accessibility issues fixed **Migration Guide:** - Existing users automatically get new testdrive-jsui for edit mode - Legacy behavior available with --engine standard - Assets deploy automatically to output directories This represents the largest architectural enhancement to date, enabling independent JavaScript development while maintaining clean integration with the Python markdown processing pipeline. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 09:36:04 +01:00
- **JavaScript Loading Conflicts**: Resolved const redeclaration errors with MARKITECT_STRICT_MODE implementation
- **MarkitectMain Availability**: Fixed proper main-updated.js loading and JavaScript syntax errors
- **Plugin Asset Deployment**: Directory structure preservation with development vs production deployment strategies
docs: complete project documentation and task management cleanup ### Documentation Updates - Added comprehensive WORKSPACE_AND_DATABASES.md documentation explaining: - Markitect's workspace-based architecture concept - Database separation (markitect.db vs assets.db) and purposes - Configuration management and asset integration - Best practices for development, collaboration, and production ### Changelog Management - Updated CHANGELOG.md with complete release history coverage - Added missing v0.8.0 entry for setuptools-SCM integration and release automation - Added proper version comparison links for all releases - Documented all recent work in Unreleased section following Keep a Changelog format ### Task Management - Cleaned TODO.md file by removing all completed tasks - Reset to clean state referencing changelog for completed work - Maintained Keep a Todofile format for future development sessions This completes the documentation and task management improvements for the ChatGPT theme implementation, modular theme system, issue-facade bug fixes, and workspace architecture clarification work. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 14:34:54 +01:00
- **Issue-facade Click Framework Bug**: Resolved Sentinel bug in list command that was causing CLI failures
- **Issue-facade Version Command**: Fixed installation error preventing version command from working
- **Test Isolation Issues**: Improved test isolation with proper mocking to prevent cross-test interference
- **Theme Color Assertions**: Updated test assertions to work with new modular theme system
docs: update CHANGELOG for v0.9.0 plugin infrastructure release Major version 0.9.0 release documenting the complete plugin infrastructure implementation that enables JavaScript-first development. **Added:** - Plugin Infrastructure Foundation with RenderingEnginePlugin system - TestDrive JSUI Plugin for independent JavaScript UI development - CLI Engine Parameter (--engine) with intelligent defaults - Automatic Asset Deployment to _markitect/plugins/ structure - Complete JavaScript-Python separation with JSON configuration **Changed:** - BREAKING: Edit mode now defaults to testdrive-jsui plugin - Asset management now automatic (no --ship-assets flag needed) - JavaScript architecture fully modularized with clean separation **Fixed:** - JavaScript const redeclaration and loading conflicts resolved - Plugin asset deployment and accessibility issues fixed **Migration Guide:** - Existing users automatically get new testdrive-jsui for edit mode - Legacy behavior available with --engine standard - Assets deploy automatically to output directories This represents the largest architectural enhancement to date, enabling independent JavaScript development while maintaining clean integration with the Python markdown processing pipeline. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 09:36:04 +01:00
### Migration Guide
- **Existing Users**: Edit mode will automatically use new testdrive-jsui plugin for enhanced experience
- **Legacy Behavior**: Use `markitect md-render --engine standard --edit` to access previous edit mode
- **Asset Deployment**: Plugin assets now deploy automatically - no manual --ship-assets flag required
docs: complete project documentation and task management cleanup ### Documentation Updates - Added comprehensive WORKSPACE_AND_DATABASES.md documentation explaining: - Markitect's workspace-based architecture concept - Database separation (markitect.db vs assets.db) and purposes - Configuration management and asset integration - Best practices for development, collaboration, and production ### Changelog Management - Updated CHANGELOG.md with complete release history coverage - Added missing v0.8.0 entry for setuptools-SCM integration and release automation - Added proper version comparison links for all releases - Documented all recent work in Unreleased section following Keep a Changelog format ### Task Management - Cleaned TODO.md file by removing all completed tasks - Reset to clean state referencing changelog for completed work - Maintained Keep a Todofile format for future development sessions This completes the documentation and task management improvements for the ChatGPT theme implementation, modular theme system, issue-facade bug fixes, and workspace architecture clarification work. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 14:34:54 +01:00
## [0.8.0] - 2025-11-08
### Added
- **Setuptools-SCM Integration**: Automatic version management system replacing manual version tracking
- **Gitea Package Publishing**: Complete CI/CD pipeline for automated package publishing to Gitea
- **Enhanced Release Documentation**: Comprehensive documentation for package building and release process
### Changed
- **Release Script Architecture**: Modernized release workflow with setuptools-scm integration
- **Makefile Release Targets**: Updated release targets to support automated version management
- **Package Building Process**: Streamlined package creation with enhanced build targets
### Removed
- **Legacy Release Scripts**: Removed obsolete release_simplified.py in favor of unified release.py
Prepare release 0.7.0 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-08 19:24:52 +01:00
## [0.7.0] - 2025-11-08
### Added
- **Complete JavaScript Architecture Refactoring**: Full TDD-driven modular architecture with SectionManager and DOMRenderer components
- **Advanced Image Editor**: Rebuilt with full drag-n-drop functionality and staging workflow
- **Modular Component System**: Extracted comprehensive JavaScript components for better maintainability
- **Enhanced Edit Mode**: Improved robustness and user experience with better reset functionality
- **Insert Mode Protection**: Implemented insert mode with heading protection and content display fixes
- **Scroll Indicators**: Added scroll indicators with disabled state styling
- **Asset Shipping**: Comprehensive asset shipping for md-render command
### Fixed
- **Reset Button Functionality**: Implemented fully functional reset buttons for text and image sections
- **Image Rendering**: Fixed proper image rendering in modular architecture
- **DOM Content Updates**: Resolved DOM content updates and reset functionality
- **Section Click Functionality**: Enabled proper section click functionality for edit UI
- **Modular Integration**: Fixed integration of modular JavaScript architecture into application
- **Button Functionality**: Resolved accept, cancel, and reset button functionality issues
- **Critical JavaScript Errors**: Fixed errors preventing content rendering
### Changed
- **Edit Mode Organization**: Continued efforts to reorganize edit mode for better robustness
- **Example Directory Structure**: Reorganized examples directory with topic-based subdirectories
- **UI Panel Structure**: Eliminated floating status panel above editor menu for cleaner interface
### Maintenance
- **TODO Cleanup**: Cleaned up completed theme system refactor tasks
release: bump version to 0.6.0 with clean editor architecture Version 0.6.0 introduces comprehensive improvements: 🚀 Major Features: - Custom status modal system with theme consistency - HTML generation dogtag with user attribution - Enhanced link navigation (new tabs, no edit trigger) - Comprehensive UI framework documentation 🔧 Architecture: - Complete document_manager.py cleanup (-2000 lines) - Clean wrapper pattern maintaining compatibility - Enhanced database integration and AST processing 🎨 UI/UX: - Theme-aware modal dialogs - Standardized CSS naming conventions - Improved error handling and validation 🧪 Quality: - Updated test suite for clean implementation - Fixed JavaScript syntax and CSS escape issues - Enhanced front matter parsing integration This release establishes a solid foundation for maintainable, clean architecture while preserving all existing functionality. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-28 03:51:41 +01:00
## [0.6.0] - 2025-10-28
### Added
- **Custom Status Modal System**: Professional theme-consistent status dialogs replacing browser alerts with proper branding and accessibility
- **HTML Generation Dogtag**: Automatic attribution with timestamp and username linking for generated HTML documents
- **Enhanced Link Navigation**: All document links now open in new tabs without triggering edit mode for improved user experience
- **Comprehensive UI Framework Documentation**: Complete guide (UserInterfaceFramework.md) for consistent UI development patterns
- **Database Integration**: Added store_document method to CleanDocumentManager with proper front matter parsing
- **Enhanced AST Processing**: Improved title extraction from front matter and heading detection with cache file generation
### Changed
- **Complete Document Manager Cleanup**: Removed 2000+ lines of legacy code while maintaining full backward compatibility
- **Clean Architecture Implementation**: DocumentManager now extends CleanDocumentManager with clean wrapper pattern
- **Improved Error Handling**: Enhanced validation and graceful error recovery throughout the system
- **Standardized CSS Naming**: Consistent class naming conventions across all UI components
### Fixed
- **Test Suite Compatibility**: Updated all tests to work with clean implementation architecture
- **JavaScript Syntax Issues**: Resolved template literal and string escaping problems in generated HTML
- **Link Behavior**: Fixed issue where document links were incorrectly triggering edit mode
- **Front Matter Parsing**: Proper integration with FrontMatterParser for metadata extraction
### Technical
- Added --nodogtag CLI option for clean output when attribution is not desired
- Enhanced ingest_file method with proper title extraction from front matter and headings
- Implemented theme-aware modal overlay patterns with proper CSS styling
- Fixed CSS escape sequences and JavaScript syntax validation issues
release: bump version to 0.5.0 with clean TDD-driven editor This release represents a major milestone in MarkiTect's evolution, featuring a complete rewrite of the editor system using test-driven development principles and clean object-oriented architecture. Key highlights: - Clean TDD-driven editor architecture with Section/SectionManager/DOMRenderer classes - Multiple concurrent section editing with intelligent section splitting - Four-layer content management system (original, current, pending, editing) - Enhanced status dialog with repository info and version tracking - Comprehensive testing framework with separation of concerns - Elegant slide-in control panel and intelligent auto-sizing textarea - Complete legacy editor system replacement 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-26 07:53:45 +01:00
## [0.5.0] - 2025-10-26
### Added
- **Clean TDD-Driven Editor Architecture**: Complete rewrite with object-oriented JavaScript architecture featuring Section, SectionManager, and DOMRenderer classes
- **Enhanced Test Framework**: Comprehensive testing framework with clean separation of concerns for robust development
- **Multiple Concurrent Section Editing**: Support for editing multiple sections simultaneously with intelligent management
- **Intelligent Section Splitting**: Advanced heading detection and section management capabilities
- **Four-Layer Content Management**: Sophisticated content state management (original, current, pending, editing layers)
- **Enhanced Status Dialog**: Repository info display showing version, git commit status, and actual save filename
- **Elegant Slide-in Control Panel**: Floating control panel for edit mode with improved UX
- **Intelligent Auto-sizing Textarea**: Optimal editing experience with smart textarea resizing
- **Enhanced Empty Line Preservation**: Better markdown structure preservation with automatic paragraph separation
### Fixed
- **Textarea Sizing and Font Preservation**: Resolved sizing issues and maintained consistent font rendering
- **Markdown Structure Preservation**: Fixed roundtrip formatting issues in save functionality
- **Section Duplication Prevention**: Eliminated duplicate sections when saving edited content
- **Section Position Preservation**: Prevented unwanted section jumping during editing
- **CSS Embedding Issues**: Resolved import errors in HTML template generation
- **Control Panel UX**: Hidden control ribbon when panel is expanded for cleaner interface
### Changed
- **Action Semantics**: Proper implementation of Accept, Cancel, and Reset operations
- **Global Reset Functionality**: Enhanced reset capabilities across the editor
- **Makefile Organization**: Reorganized installation targets for better user experience
### Technical Improvements
- Complete legacy editor system replacement
- Test-driven development approach implementation
- Enhanced UI/UX with better section positioning
- Improved content management workflow
release: prepare v0.4.0 - Enhanced Edit Mode & Version Tracking Key improvements: - Fixed critical md-render --edit functionality that was broken - Enhanced version tracking with git commit hash, timestamps, and local changes detection - Comprehensive regression tests to prevent future breaks - Repository cleanup completed 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-25 20:13:41 +02:00
## [0.4.0] - 2025-10-25
### Added
- feat: add comprehensive testing and error tracking for edit mode
### Fixed
- fix: resolve md-render --edit functionality and add enhanced version tracking
- fix: resolve critical JavaScript syntax errors in md-render --edit
- fix: resolve md-ingest Path object conversion error
### Other
- chore: clean up repository documentation files for release
docs: complete CHANGELOG.md with missing historical versions - Add standard Keep a Changelog header with format description - Add Unreleased section following standard format - Add comprehensive entries for versions 0.1.0, 0.2.0, and 0.3.0 - Research and document historical features using git log analysis - Follow Keep a Changelog categories (Added, Changed, Fixed) - Maintain chronological order with proper release dates - Update TODO.md to reflect completed changelog enhancement work 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 20:09:02 +01:00
## [0.3.0] - 2025-10-25
### Added
- **Kaizen-agentic Framework Integration**: Integrated capability submodule for enhanced development workflow
- **Test Reorganization System**: Reorganized tests by capability with improved modularity
- **Capability Inclusion Management**: Comprehensive system for managing capability inclusions
- **Todofile System**: Implemented todofile system to replace NEXT.md for better task tracking
### Changed
- **Directory Organization**: Logical separation and reorganization of project structure
- **Historical File Organization**: Cleaner structure with better file organization
release: prepare v0.4.0 - Enhanced Edit Mode & Version Tracking Key improvements: - Fixed critical md-render --edit functionality that was broken - Enhanced version tracking with git commit hash, timestamps, and local changes detection - Comprehensive regression tests to prevent future breaks - Repository cleanup completed 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-25 20:13:41 +02:00
docs: complete CHANGELOG.md with missing historical versions - Add standard Keep a Changelog header with format description - Add Unreleased section following standard format - Add comprehensive entries for versions 0.1.0, 0.2.0, and 0.3.0 - Research and document historical features using git log analysis - Follow Keep a Changelog categories (Added, Changed, Fixed) - Maintain chronological order with proper release dates - Update TODO.md to reflect completed changelog enhancement work 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 20:09:02 +01:00
## [0.2.0] - 2025-10-20
### Added
- **GraphQL Interface**: Advanced querying capabilities with full GraphQL implementation
- **Full-text Search**: FTS5 backend integration for powerful search functionality
- **Plugin Architecture**: Extensible framework with comprehensive plugin support
- **Query Paradigms**: 14 different query paradigms for flexible data access
- **Cost Management**: Activity tracking and resource cost management
- **Template Rendering**: Template system with validation capabilities
- **CLI Consolidation**: Unified command-line interface
- **Production Asset Management**: Content-addressable storage system
- **17 Kaizen-agentic Agents**: Integrated development agent ecosystem
### Changed
- **Performance Optimization**: 60-85% performance improvement through system optimization
- **Error Handling**: Enterprise-grade error handling and recovery mechanisms
- **Resource Management**: Memory-efficient and scalable architecture
### Fixed
- **Cross-platform Validation**: Comprehensive validation for Unix/Windows/macOS
- **Type Safety**: Enhanced type safety and security validation
- **Test Coverage**: 1983/1983 tests passing (100% success rate)
## [0.1.0] - 2025-10-15
### Added
- **Development Infrastructure**: Comprehensive Makefile for development workflow
- **Project Documentation**: ProjectStatusDigest.md and ProjectDiary.md for tracking
- **TDD Workspace System**: Structured Test-Driven Development workflow implementation
- **Issue Management**: Gitea integration for issue tracking and management
- **Virtual Environment Management**: Enhanced venv detection and shell activation
- **Wiki Integration**: Submodule tracking for project documentation
- **Core Repository Setup**: Initial project structure and configuration
### Changed
- **Build System**: Enhanced build targets with venv Python and PYTHONPATH support
- **Target Naming**: Renamed workspace targets to TDD Workspace with tdd- prefix
release: prepare v0.4.0 - Enhanced Edit Mode & Version Tracking Key improvements: - Fixed critical md-render --edit functionality that was broken - Enhanced version tracking with git commit hash, timestamps, and local changes detection - Comprehensive regression tests to prevent future breaks - Repository cleanup completed 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-25 20:13:41 +02:00
docs: update CHANGELOG for v0.9.0 plugin infrastructure release Major version 0.9.0 release documenting the complete plugin infrastructure implementation that enables JavaScript-first development. **Added:** - Plugin Infrastructure Foundation with RenderingEnginePlugin system - TestDrive JSUI Plugin for independent JavaScript UI development - CLI Engine Parameter (--engine) with intelligent defaults - Automatic Asset Deployment to _markitect/plugins/ structure - Complete JavaScript-Python separation with JSON configuration **Changed:** - BREAKING: Edit mode now defaults to testdrive-jsui plugin - Asset management now automatic (no --ship-assets flag needed) - JavaScript architecture fully modularized with clean separation **Fixed:** - JavaScript const redeclaration and loading conflicts resolved - Plugin asset deployment and accessibility issues fixed **Migration Guide:** - Existing users automatically get new testdrive-jsui for edit mode - Legacy behavior available with --engine standard - Assets deploy automatically to output directories This represents the largest architectural enhancement to date, enabling independent JavaScript development while maintaining clean integration with the Python markdown processing pipeline. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-14 09:36:04 +01:00
[Unreleased]: https://github.com/worsch/markitect/compare/v0.9.0...HEAD
[0.9.0]: https://github.com/worsch/markitect/compare/v0.8.0...v0.9.0
docs: complete project documentation and task management cleanup ### Documentation Updates - Added comprehensive WORKSPACE_AND_DATABASES.md documentation explaining: - Markitect's workspace-based architecture concept - Database separation (markitect.db vs assets.db) and purposes - Configuration management and asset integration - Best practices for development, collaboration, and production ### Changelog Management - Updated CHANGELOG.md with complete release history coverage - Added missing v0.8.0 entry for setuptools-SCM integration and release automation - Added proper version comparison links for all releases - Documented all recent work in Unreleased section following Keep a Changelog format ### Task Management - Cleaned TODO.md file by removing all completed tasks - Reset to clean state referencing changelog for completed work - Maintained Keep a Todofile format for future development sessions This completes the documentation and task management improvements for the ChatGPT theme implementation, modular theme system, issue-facade bug fixes, and workspace architecture clarification work. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 14:34:54 +01:00
[0.8.0]: https://github.com/worsch/markitect/compare/v0.7.0...v0.8.0
[0.7.0]: https://github.com/worsch/markitect/compare/v0.6.0...v0.7.0
[0.6.0]: https://github.com/worsch/markitect/compare/v0.5.0...v0.6.0
[0.5.0]: https://github.com/worsch/markitect/compare/v0.4.0...v0.5.0
[0.4.0]: https://github.com/worsch/markitect/compare/v0.3.0...v0.4.0
[0.3.0]: https://github.com/worsch/markitect/compare/v0.2.0...v0.3.0
[0.2.0]: https://github.com/worsch/markitect/compare/v0.1.0...v0.2.0
[0.1.0]: https://github.com/worsch/markitect/releases/tag/v0.1.0
Reference in a new issue Copy permalink