feat: add manpages example demonstrating schema validation

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>

TODO.md

@@ -12,6 +12,8 @@ The structure organizes **future tasks** by their impact, just as a changelog or
 
 This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks.
 
+0. the file TODO.html is legacy i think and can be removed 
+
 ### Extract Capability-Capability from Issue-Facade
 
 **Context:** Issue-facade currently provides two capabilities:
@@ -81,4 +83,4 @@ The **capability-capability** includes:
 - ✅ Refactored to family-based directory structure (_issue-tracking/issue-facade)
 - ✅ Made feedback directory visible (feedback/ not .feedback/)
 - ✅ Renamed to explicit family declaration (CAPABILITY-issue-tracking.yaml)
-- ✅ Created CHANGELOG.md documenting v1.0.0
+- ✅ Created CHANGELOG.md documenting v1.0.0