v3.6.2
MemKraft 3.6.2
MemKraft 3.6.2 adds a provenance-aware artifact layer for completed content such as drafts, reports, and other authored turns that should remain directly recoverable after later summaries or context compaction.
Artifact capture and retrieval
- Persists completed content with optional structured platform, channel, thread, session, message, profile, and lineage provenance.
- Supports exact phrase retrieval and combined scope filters while keeping ordinary semantic search compatibility.
- Ranks direct source turns ahead of summaries and uses normalized offset-aware timestamps for deterministic oldest or newest ordering.
- Never fabricates timestamps, origins, or other runtime metadata that the caller did not provide.
- Publishes metadata through an atomic rename and removes content and temporary files when serialization fails.
Compatibility and migration
- The artifact API and Hermes metadata argument are additive and optional.
- Existing MemKraft stores require no migration or Markdown rewrite.
- Existing Hermes providers and callers that do not send metadata keep their previous behavior.
Verification
- Artifact and Hermes provider regression suite: 31 passed.
- Full MemKraft suite before the release metadata cut: 3,535 passed, 2 skipped.
- Packaging, release-lineage, build, fresh-wheel, and protected-main gates are required again on the exact 3.6.2 candidate before publication.
No 3.6.0 or 3.6.1 artifact or immutable tag is changed.