Consolidate technical documentation and notes#50
Merged
calvingiles merged 2 commits intoNov 3, 2025
Merged
Conversation
…DSL validation Unify technical notes from docs/analysis/ and technical-notes/ into a single context/technical-notes/ directory with consistent DSL-validated format. Changes: - Register TechnicalNoteModule in BUILTIN_MODULES for DSL validation - Update location_pattern from specs/notes/ to context/technical-notes/ - Migrate and align 5 technical notes to consistent format: - TN-001: DSL Validator Expressiveness Analysis (from docs/analysis/) - TN-002: LLM Provider Selection (from technical-notes/) - TN-003: Type Definition Schema Design (from technical-notes/) - TN-004: Issue #42 Investigation (from technical-notes/) - TN-005: Specification DSL Design (from technical-notes/) - Standardize metadata: Type, Date, Author, Status, Related - Enforce required sections: Abstract, Background, Conclusion - Update .specallowlist and .specignore for new structure - Update test expectations for new location pattern - Remove old docs/analysis/ and technical-notes/ directories All technical notes now follow TN-XXX naming convention and validate against the TechnicalNoteModule schema with consistent structure and metadata. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Clean up stale references after consolidating technical notes to context/technical-notes/. Changes: - Update CHANGELOG.md: technical-notes/issue-42-investigation.md → TN-004.md - Update SPEC-004: technical-notes/specification-dsl-design.md → TN-005.md - Update TechnicalNoteModule docstring: specs/notes/ → context/technical-notes/ - Update test fixtures: specs/notes/ → context/technical-notes/ All references to old locations (docs/analysis/, technical-notes/, specs/notes/) have been updated to point to the new unified location. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…DSL validation
Unify technical notes from docs/analysis/ and technical-notes/ into a single context/technical-notes/ directory with consistent DSL-validated format.
Changes:
All technical notes now follow TN-XXX naming convention and validate against the TechnicalNoteModule schema with consistent structure and metadata.
🤖 Generated with Claude Code