Repository navigation
Expose current conversation names through concept retrieval - #698
Merged
Merged
Conversation
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.
Named conversation concepts could resolve to a generic label even though chat history held a title. Project the current canonical title through conversation and general concept-name retrieval, batching owner/session reads and requiring the authenticated source owner. Titles remain source-owned and renames require no copied Vontology name.
The browser compact-reference metadata now uses the conversation list's per-viewer naming preference, with the canonical title and name source exposed separately. Shared reference access continues through existing invitation checks.
Validation: 46 targeted backend tests passed across conversation concepts, compact-reference Flask/MCP routes, concept name resolution and summary rendering;
git diff --checkpassed. Covers rename, unnamed fallback, 53-concept batching, unauthenticated/other-owner denial and viewer preference versus canonical title. No live-browser or public deployment claim.Native task:
#V#task_agent_d6078d36e9cd8e9b357d0354ea19161e. Source screenshot#V#computer_file_copy_452eec80e55d4e14bcc83b6340c9da9binspected and retained in the controller evidence directory; SHA-256e9352df3cb9b6d42eeb89fccf4e31a5714da8e4f1a09ba13dc7d74771dfb37bb. No private screenshot bytes committed.Merge decision: ready on bounded service/route evidence. No deployment requested.