docs(changelog): document init entity-detection overhaul in 3.3.3#1176
Merged
docs(changelog): document init entity-detection overhaul in 3.3.3#1176
Conversation
Adds entries to the 3.3.3 section for the work that landed via #1148, #1150, #1157, and #1175 (rescued from stacked feature branches into develop via #1175). Without these entries the 3.3.3 release notes on main would advertise only the hook/diary/search fixes that made it to develop through the first direct merge. Covers: - Manifest + git-author entity detection (#1148) - Regex detector accuracy improvements (#1148) - Optional --llm classification with Ollama / openai-compat / Anthropic provider abstraction and interactive UX (#1150) - Claude Code conversation scanner (#1150) - Init → miner registry wire-up so confirmed entities actually reach drawer metadata tagging (#1157) - Case-insensitive project dedup across all sources (#1175) - `mempalace mine` skips the generated entities.json artifact
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the v3.3.3 release notes to reflect the init entity-detection overhaul and related features that already landed (but weren’t documented) before the v3.3.3 tag is cut.
Changes:
- Adds a missing Bug Fix entry about
mempalace mineskipping generatedentities.json. - Documents major init/entity-detection improvements (manifest + git-author signal, regex accuracy, registry wire-up, case-insensitive dedup).
- Adds release-note entries for
mempalace init --llmand the Claude Code conversation scanner.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
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
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.
Context
The 3.3.3 section of
CHANGELOG.mdon develop was written before #1148, #1150, #1157, and #1175 landed (the last three were rescued from stacked feature branches via #1175 yesterday). Merging #1159 tomainwithout this update would advertise only the hook/diary/search fixes that made it to develop through the first direct merge — the entity-detection overhaul, the LLM refinement, the Claude Code convo scanner, and the miner wire-up would all ship silently.This PR adds the missing entries so the release notes reflect what actually shipped. Should merge into develop before #1159 cuts the tag.
Entries added
Bug Fixes
mempalace minenow skips the generatedentities.jsonfile so its contents aren't re-ingested as project contentImprovements
~/.mempalace/known_entities.json(feat(init): wire confirmed entities into the miner's known-entities registry #1157)Added
mempalace init --llmwith Ollama / openai-compat / Anthropic providers, interactive progress, Ctrl-C cancellation (feat(init): optional LLM-assisted entity refinement + Claude Code convo scanner (phase 2) #1150)Note on section date
The 3.3.3 section is dated
2026-04-23— from before the release. If the tag is cut2026-04-24, consider updating the section header to match. Not changed here; it's a judgement call on whether the date marks "intended release" or "actual tag cut."Test plan