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>
This commit completes Phase 2 of schema evolution work and establishes
a new example demonstrating schema usage for terminology documents.
## New Features
### Terminology Validation Example (examples/terminology/)
- Complete example terminology document with proper structure
- JSON schema with MarkiTect extensions for validation
- Demonstrates schema usage beyond manpages (glossaries, lexicons)
- Validates term structure: Definition, Synonyms, Related Terms, Examples
- Includes content control and quality validation rules
- Full documentation with usage examples and best practices
### Schema Registration System
- Registered terminology schema in markitect database
- Created schema catalog (markitect/schemas/schema-catalog.yaml)
- Copied schema to official location (markitect/schemas/)
- Provides metadata, features, and usage info for all schemas
### Improved schema-list Command
- Now displays creation timestamps in default output
- Table format includes Created/Updated columns
- Cleaner timestamp formatting (removed microseconds)
- Better visibility into when schemas were added
## Files Changed
Added:
- examples/terminology/README.md - Complete documentation
- examples/terminology/terminology-example.md - Example glossary
- examples/terminology/terminology-schema.json - Validation schema
- markitect/schemas/terminology-schema.json - Registered schema
- markitect/schemas/schema-catalog.yaml - Schema registry
Modified:
- markitect/cli.py - Enhanced schema-list with timestamps
- TODO.md - Documented Phase 2 completion and new example
Moved:
- SCHEMA_EVOLUTION_WORKPLAN.md → todo/ directory
## Schema Features Demonstrated
- Heading hierarchy validation (H1 → H2 → H3)
- Term structure validation with required/optional fields
- Content quality metrics (word counts, readability targets)
- MarkiTect extensions (x-markitect-sections, x-markitect-content-control)
- Classification system (required/recommended/optional/discouraged/improper)
## Usage
```bash
# List schemas with timestamps
markitect schema-list
# Validate terminology document
markitect validate glossary.md --schema terminology-schema.json
# View in table format
markitect schema-list --format table
```
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add comprehensive example showcasing schema validation with self-documenting
manpage system:
- markdown-manpage-schema.json: Reusable schema for Unix manpage structure
- markdown-schema-validation.1.md: Complete manual about schema validation
- README.md: Usage guide, integration examples, and best practices
- SCHEMA_EVOLUTION_WORKPLAN.md: Roadmap for enhanced schema system
The manual validates against its own schema, demonstrating dogfooding
principle. Workplan outlines 5-phase evolution from rigid structural
validation to flexible content control with blueprints.
Key features demonstrated:
- Schema-driven documentation structure
- Self-validating documentation
- Reusable validation patterns
- Classification system design (required/recommended/optional/discouraged/improper)
This sets foundation for Phase 1 implementation: enhanced schema format
with section classification and content control.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Document plan to extract the implicit 'capability-capability' from issue-facade
into a separate reusable-capability repository.
Issue-facade currently provides two capabilities:
1. issue-tracking (explicit) - Issue management across platforms
2. capability-capability (implicit) - Patterns for creating/managing capabilities
The capability-capability includes:
- Feedback pattern and tooling
- Detachment facility
- Integration scripts
- CAPABILITY-*.yaml specification format
- ReusableCapabilitiesArchitecture.md
- Directory conventions (_family/implementation, visible/hidden)
Extraction plan divided into 4 phases:
Phase 1: Specification & Planning
- Create CAPABILITY-capability.yaml to declare the implicit capability
- Define boundaries between families
- Document API surface
- Identify files to extract
- Plan extraction strategy
Phase 2: Repository Creation
- Create reusable-capability repo
- Extract all capability-capability files
- Create canonical CAPABILITY-capability.yaml
Phase 3: Integration & Testing
- Integrate reusable-capability into issue-facade
- Test functionality still works
- Update documentation
Phase 4: Dogfooding & Validation
- Use in another capability
- Validate and refine based on real usage
Also documented completed tasks from today's architecture refactoring.
Current step: Phase 1, Task 1 - Create CAPABILITY-capability.yaml
### 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>
- Update TODO.md to reflect completed issue-facade capability fixes
- Archive old CLI structure files that were moved to capabilities/issue-facade
- Reorganize remaining CLI components into issue_tracker/ package
- Add test coverage for issue #166 substack theme implementation
- Update document manager and markdown command plugins with latest improvements
- Complete project reorganization following capability-based architecture
This commit finalizes the issue-facade capability enhancement project and
ensures the main repository reflects the current state of all completed work.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Extract JavaScript UI framework functionality into dedicated testdrive-jsui capability
while maintaining 100% functionality preservation and integrating JavaScript tests
into the main Python test suite.
Phase 1 (Foundation Setup) - COMPLETED:
- Created capability directory structure with proper Python package layout
- Configured pyproject.toml with Node.js subprocess dependencies
- Set up package.json with Jest + JSDOM testing framework
- Implemented Python-JavaScript bridge for seamless test integration
- Created comprehensive capability Makefile with all testing targets
- Added detailed README documentation for capability usage
Phase 2 (Integration Layer) - COMPLETED:
- Built Python test wrappers for JavaScript test execution via subprocess
- Integrated with pytest discovery system for unified test experience
- Added capability targets to main Makefile delegation system
- Verified test integration works with main test suite
Phase 3 (Safe Migration) - COMPLETED:
- Copied (not moved) all JavaScript files to capability using safe copy-first approach
- Migrated 4 core JavaScript components and 11 test files (2,840+ lines)
- Verified all tests work in new location (11 Python tests + 7 JavaScript tests passing)
- Maintained dual-track testing capability for safety during transition
Phase 4 (Framework Enhancement) - COMPLETED:
- Enhanced testing framework with Python integration and coverage reporting
- Achieved 59% Python test coverage and 100% JavaScript test coverage
- Added performance benchmarking and component documentation
Phase 5 (Production Integration) - COMPLETED:
- Added standard 'test' target to capability Makefile for discovery system compatibility
- Integrated JavaScript tests into main Makefile with new targets:
* test-js: Run JavaScript UI tests
* test-all: Run all tests (Python + JavaScript + Capabilities)
- Updated help documentation to include new testing workflows
- Verified capability auto-discovery works via 'make test-capabilities'
Key Achievements:
- Zero-risk migration completed with copy-first safety approach
- Full Python-JavaScript test integration with 18 total passing tests
- JavaScript UI framework successfully extracted to dedicated capability
- Enhanced CI/CD integration with unified test command interface
- Clean architecture enabling future JavaScript framework evolution
Testing Status:
- ✅ All Python integration tests passing (11/11)
- ✅ All JavaScript component tests passing (7/7)
- ✅ Capability discovery integration working
- ✅ Main test suite integration complete
- ✅ Test coverage reporting functional (59% Python, 100% JavaScript)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Save current state before major JavaScript architecture refactoring.
Current state:
- Monolithic 5,188-line editor.js with all functionality
- Working floating menu system and section editing
- Debug panel implementation (with server-side generation issues)
- All TDD-recovered features integrated
Issues to address in refactoring:
- Debug messages generated during HTML rendering instead of client-side
- Monolithic architecture violates separation of concerns
- Tight coupling prevents independent component testing
- JavaScript changes affecting Python md-render code
Next: Implement modular JavaScript architecture with:
- Component separation (core/, components/, utils/, tests/)
- Pure client-side debug system
- Independent testing capability
- Proper architectural boundaries
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
This commit implements 5 major JavaScript features that were lost during
refactoring, using systematic Test-Driven Development methodology:
**Core Features Implemented:**
- Advanced EditState enum with pending changes preservation
- Keyboard shortcuts (Ctrl+Enter accept, Escape cancel)
- Section splitting with dynamic heading detection
- Real-time status tracking with 2-second periodic updates
- Intelligent filename generation with 4-method fallback system
**Technical Improvements:**
- Comprehensive TDD test suites for all functionality
- Professional status panel with color-coded indicators
- Smart filename generation (options→title→URL→heading→timestamp)
- Event-driven architecture with custom event emission
- State preservation during editing transitions
**Files Added:**
- markitect/static/editor.js - Complete JavaScript functionality
- test_*.js - Comprehensive TDD test suites
- LOST_FUNCTIONALITY_ANALYSIS.md - Detailed feature comparison
- TEST_ENVIRONMENT.md - TDD setup documentation
**Updated Documentation:**
- TODO.md - Status tracking and progress documentation
All features are fully tested and integrated into the existing codebase.
The TDD approach proved highly effective for systematic functionality recovery.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Remove outdated theme system refactor content from TODO.md since the layered
theme architecture work was already completed and released in v0.6.0. The
todofile is now clean and ready for new active development tasks.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Mark theme system refactor as completed
- Add context about new layered theme capabilities
- Document successful implementation of sophisticated theme combinations
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- 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>
Remove extensive documentation files to simplify repository structure
for v0.2.0 release. Core functionality is complete and tested.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Replace NEXT.md approach with standardized Keep a Todofile V0.0.1 format
for better task management and human-AI collaboration during coding sessions.
## Todofile System Setup:
- **TODO.md**: Main todofile following Keep a Todofile V0.0.1 format
- **TODOFILE_GUIDE.md**: Comprehensive system documentation and workflow
- **Integration**: Fully integrated with existing kaizen-agentic framework
- **Agent Support**: Uses agent-keepaTodofile for maintenance
## Content Migration:
- Migrated strategic priorities from NEXT.md to TODO.md [Unreleased] section
- Preserved session success criteria and development milestones
- Organized tasks by impact type (To Add, To Fix, To Refactor)
- Archived NEXT.md to history/NEXT_archived_20251025.md
## Documentation Updates:
- README.md: Updated "Next Actions" → "Current Tasks" link
- agent-project-management.md: Updated workflow to use TODO.md
- docs/README.md: Updated project management references
- Added comprehensive TODOFILE_GUIDE.md
## Benefits:
- **Standardized Format**: Industry-standard Keep a Todofile format
- **Better Organization**: Impact-based task categorization
- **AI-Ready**: Designed for human-AI collaboration workflows
- **Context Preservation**: Maintains coding flow across session interruptions
- **Integration Ready**: Works with existing agent and capability systems
Active tasks now in TODO.md [Unreleased] section focusing on strategic
issue resolution and capability management validation.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
