Changelog
All notable changes to the Lexigram Framework are documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
Section titled “[Unreleased]”ai-evaluationguide documenting the LLM evaluation and reproducibility subsystem — evaluators, harness, seed-stable experiment tracking, digest-verified checkpoints, ablations, and error analysis.
[0.1.3] — 2026-08-19
Section titled “[0.1.3] — 2026-08-19”- Admin live widgets:
activitynow pushes live updates over a single sharedEventSource; widgets declaringlive_resource_typesskip their poll trigger and re-render on matching SSE messages. - RBAC-gated widget stream at
/admin/_sse/widgets— filters byresource_typevia theresourcesquery parameter, checked againstPermissionService.can_list.
Changed
Section titled “Changed”/admin/_sse/eventsretired in favor of/admin/_sse/widgets(breaking for external clients polling the old path); live-widget dispatch reads nestedresource_typewith a fail-closed RBAC gate.SubjectAdminEventHubgained tenant scoping (subscribe(tenant_id=...)),drop_latestsubscriber overflow (publishing never blocks on a slow subscriber), andpublish_notification();ActionExecutor.event_hubis now typedSubjectAdminEventHub | Noneso@injectcan auto-resolve it.WidgetParamsandAdminEventcarry an optionaltenant_idfor tenant-scoped streams.
[0.1.2] — 2026-08-18
Section titled “[0.1.2] — 2026-08-18”- Settings sidebar categories now derive dynamically from each spec’s
package_source, replacing the fixed 3-category taxonomy; everyConfigSpeccan choose its own store, and readonly fields are enforced server-side. - Read-only
DeploymentInfoSpec(sourced fromEnvStore) and a System Info settings panel. - Per-request
tenant_idresolution: threaded throughConfigRegistry.get_values/saveandTenantConfigStorefor tenant-scoped settings. lexigram-ai-promptgained amax_variable_lengthconfig flag.- Structured management pages in
lexigram-contracts— the host renders all management page HTML.
Changed
Section titled “Changed”- Verified-only JWTs everywhere: the
allow_unverified_devoption is dropped. - Secrets are never rendered in settings form HTML; blank secret submissions leave the stored value unchanged.
- Dashboard content tables got consistent tabular visuals; the queue admin contributor now registers unnamed so admin boot resolves it.
- Migration status widget now wires to real migration data.
- Dead throttle decorator removed; idempotency is now dialect-aware.
Security
Section titled “Security”- Publish gate blocks sensitive wheel content;
required_audienceis now mandatory in strict environments. - 305 verified low-risk SAST findings remediated family-by-family; the security report tracks area status instead of individual specs.
- Structured error detail in blind-except log/query paths.
[0.1.1] — 2026-04-22
Section titled “[0.1.1] — 2026-04-22”- Initial framework release: 42 packages integrated and tested, DI/IoC container with provider pattern, and Result[T, E] error handling.
- Full audit framework with 8 audit types (tests, quality, security, protocols, etc.).
- Docker Compose infrastructure for integration testing (PostgreSQL, Redis, Kafka, MongoDB, Elasticsearch, MinIO, Qdrant, Neo4j).
- Import boundary enforcement with 6 architectural contracts.
- Multi-backend support for all data layers (no vendor lock-in).
- Version alignment across all packages.
Infrastructure
Section titled “Infrastructure”- PyPI-ready distribution for all 42 packages; root files reviewed.
Version History Template
Section titled “Version History Template”For Future Releases
Section titled “For Future Releases”Use this template when creating new releases:
## [X.Y.Z] — YYYY-MM-DD
### Added- Feature descriptions- New modules- API additions
### Changed- Behavior changes- API modifications- Documentation updates
### Fixed- Bug fixes- Issue resolutions
### Security- Security patches- Vulnerability fixes
### Deprecated- Features marked for removal
### Removed- Features removed- Modules deleted
### Migration Guide- Steps for upgrading- Breaking change details- Code examplesRelease Timeline
Section titled “Release Timeline”| Version | Date | Status | Notes |
|---|---|---|---|
| 0.1.3 | 2026-08-19 | ✅ Current | Admin live widgets, tenant-scoped streams |
| 0.1.2 | 2026-08-18 | ✅ Released | Settings taxonomy, verified-only JWTs, security hardening |
| 0.1.1 | 2026-04-22 | ✅ Released | Initial framework |
Upcoming
Section titled “Upcoming”Planned (No Specific Timeline)
Section titled “Planned (No Specific Timeline)”- Deloying Production grade applications
- Completing CLI
- Completing Admin
- Completing UI
Research Phase
Section titled “Research Phase”- Additional AI/ML capabilities
- Performance optimizations
Contributing Changes
Section titled “Contributing Changes”See CONTRIBUTING.md for guidelines on reporting bugs, requesting features, and submitting changes.
Security
Section titled “Security”For security issues, see SECURITY.md.
Last Updated: 2026-08-19
Current Version: 0.1.3
Python Support: 3.11+