docs: standardize on yymmdd- timestamp prefix format
Some checks failed
Test Suite / performance-tests (push) Has been cancelled
Test Suite / code-quality (push) Has been cancelled
Test Suite / security-scan (push) Has been cancelled
Test Suite / unit-tests (3.11) (push) Has been cancelled
Test Suite / unit-tests (3.12) (push) Has been cancelled
Test Suite / integration-tests (push) Has been cancelled
Test Suite / e2e-tests (push) Has been cancelled
Test Suite / test-summary (push) Has been cancelled
Some checks failed
Test Suite / performance-tests (push) Has been cancelled
Test Suite / code-quality (push) Has been cancelled
Test Suite / security-scan (push) Has been cancelled
Test Suite / unit-tests (3.11) (push) Has been cancelled
Test Suite / unit-tests (3.12) (push) Has been cancelled
Test Suite / integration-tests (push) Has been cancelled
Test Suite / e2e-tests (push) Has been cancelled
Test Suite / test-summary (push) Has been cancelled
Naming Convention Updates: - Renamed history/2026-01-06-semantic-document-validation → history/260106-semantic-document-validation - Documented yymmdd- format convention in history/README.md and roadmap/README.md - Updated all date references in WORKPLAN.md and DONE.md - Fixed SCHEMA_MANAGEMENT_GUIDE.md references to use yymmdd- format Convention Details: - Format: yymmdd-topic-name (e.g., 260106-semantic-document-validation) - Benefits: Concise while maintaining chronological sorting - Examples documented in both README files - Applies to both roadmap/ and history/ directories This establishes a consistent timestamp prefix convention that Claude and its agents should follow. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -534,10 +534,10 @@ Planned features:
|
|||||||
|
|
||||||
## Related Documentation
|
## Related Documentation
|
||||||
|
|
||||||
- [Schema Naming Specification](../history/2026-01-05-schema-of-schemas/SCHEMA_NAMING_SPEC.md)
|
- [Schema Naming Specification](../history/260105-schema-of-schemas/SCHEMA_NAMING_SPEC.md)
|
||||||
- [Schema Loader Guide](../history/2026-01-05-schema-of-schemas/SCHEMA_LOADER_GUIDE.md)
|
- [Schema Loader Guide](../history/260105-schema-of-schemas/SCHEMA_LOADER_GUIDE.md)
|
||||||
- [Metaschema Reference](../markitect/schemas/schema-schema-v1.0.md)
|
- [Metaschema Reference](../markitect/schemas/schema-schema-v1.0.md)
|
||||||
- [Implementation Workplan](../history/2026-01-05-schema-of-schemas/WORKPLAN.md) (archived)
|
- [Implementation Workplan](../history/260105-schema-of-schemas/WORKPLAN.md) (archived)
|
||||||
|
|
||||||
## Support
|
## Support
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Completed: Semantic Document Validation
|
# Completed: Semantic Document Validation
|
||||||
|
|
||||||
**Date Completed**: 2026-01-06
|
**Date Completed**: 260106 (2026-01-06)
|
||||||
**Topic**: Semantic Document Validation for x-markitect Schema Extensions
|
**Topic**: Semantic Document Validation for x-markitect Schema Extensions
|
||||||
|
|
||||||
---
|
---
|
||||||
@@ -154,4 +154,4 @@
|
|||||||
---
|
---
|
||||||
|
|
||||||
**Topic Status**: COMPLETED AND ARCHIVED
|
**Topic Status**: COMPLETED AND ARCHIVED
|
||||||
**Archive Location**: `history/2026-01-06-semantic-document-validation/`
|
**Archive Location**: `history/260106-semantic-document-validation/`
|
||||||
@@ -576,7 +576,7 @@ watch -n 2 'markitect validate draft.md --schema api-documentation-schema-v1.0.m
|
|||||||
|
|
||||||
## ✅ COMPLETION SUMMARY
|
## ✅ COMPLETION SUMMARY
|
||||||
|
|
||||||
**Date Completed**: 2026-01-06
|
**Date Completed**: 260106 (2026-01-06)
|
||||||
**Status**: All 6 phases completed successfully
|
**Status**: All 6 phases completed successfully
|
||||||
|
|
||||||
### Implementation Results
|
### Implementation Results
|
||||||
@@ -660,4 +660,4 @@ watch -n 2 'markitect validate draft.md --schema api-documentation-schema-v1.0.m
|
|||||||
✅ >90% test coverage for validator modules
|
✅ >90% test coverage for validator modules
|
||||||
✅ Complete documentation with examples for each schema type
|
✅ Complete documentation with examples for each schema type
|
||||||
|
|
||||||
**Topic Status**: CLOSED - Moved to history on 2026-01-06
|
**Topic Status**: CLOSED - Moved to history on 260106 (2026-01-06)
|
||||||
@@ -5,6 +5,16 @@ This history directory contains old planning directories for roadmap topics.
|
|||||||
- See ../roadmap for current and future topics
|
- See ../roadmap for current and future topics
|
||||||
- 2025 has not been using using topic directories but various files
|
- 2025 has not been using using topic directories but various files
|
||||||
|
|
||||||
|
## 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-of-schemas`
|
||||||
|
|
||||||
|
This convention keeps names concise while maintaining chronological sorting.
|
||||||
|
|
||||||
## Purpose
|
## Purpose
|
||||||
|
|
||||||
This historical documentation serves multiple purposes:
|
This historical documentation serves multiple purposes:
|
||||||
|
|||||||
@@ -6,6 +6,16 @@ This roadmap directory contains planning directories for roadmap topics.
|
|||||||
- Keep current state of what's next to implement in TODO.md
|
- Keep current state of what's next to implement in TODO.md
|
||||||
- See ../history directory for closed topics
|
- 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
|
## Purpose
|
||||||
|
|
||||||
This planning documentation serves multiple purposes:
|
This planning documentation serves multiple purposes:
|
||||||
|
|||||||
Reference in New Issue
Block a user