ai-ops-templates/context/CHANGELOG.md
DMleadgen 2598e55a54 Add sync protocol for portable context management
- ai-sync-protocol.md: Session start and post-change sync rules
- _sync section in schema for auto-sync configuration
- Updated client skill template with Forgejo fetch patterns
- Client projects now self-sufficient via central repo fetch

Version 1.1.0

Made-with: Cursor
2026-03-06 16:24:57 -07:00

70 lines
1.7 KiB
Markdown

# AI Context Changelog
This file tracks all changes to the ai-ops-templates repository. Updates are logged automatically when context files are modified.
---
## Format
```
## [YYYY-MM-DD] - Version X.X.X
### Added
- New features or files
### Changed
- Modifications to existing files
### Fixed
- Bug fixes or corrections
### Context Updates
- Changes triggered by project work
```
---
## [2026-03-06] - Version 1.1.0
### Added
- `ai-sync-protocol.md` - Session start and post-change sync protocol
- `_sync` section in `ai-context.schema.json` for auto-sync configuration
- Forgejo fetch patterns in client skill template
### Changed
- Updated `client-skill.template.md` with central repository fetch instructions
- Session now starts with sync check from Forgejo
### Architecture
- Central management from Abundance project
- Single source of truth: Forgejo repo
- Client projects self-sufficient via fetch from Forgejo
---
## [2026-03-06] - Version 1.0.0
### Added
- Initial repository structure
- templates/ - Schema.org JSON-LD templates (product, event, local-business, faq)
- rules/ - Brand, UI, SEO, and decision guide rules
- snippets/ - Reusable code components and utilities
- schemas/ - JSON schemas for configuration validation
- presets/ - Client brand presets (slc-bride, default)
- context/ - Changelog and sync tracking
- skill-templates/ - Client SKILL.md template
### Architecture
- Self-update protocol implemented
- Meta sections in all JSON files for version tracking
- Decision guide for AI tool/pattern selection
---
<!--
To add new entries:
1. Add new section with date and version
2. List changes in appropriate category
3. Update last-sync.json timestamp
4. Commit changes
-->