fix: list one authorized document per project across turns - #998
Open
time-attack wants to merge 1 commit into
Open
fix: list one authorized document per project across turns#998time-attack wants to merge 1 commit into
time-attack wants to merge 1 commit into
Conversation
Group the viewer-visible owned and shared file set before cursor pagination. Prefer an owned copy, then the earliest artifact, while retaining the raw per-turn ledger and exact handle lookups. Keep context resources exhaustive and file search on raw authorized artifact identities. Co-authored-by: Ian Chou <ertiach@gmail.com>
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.
Fixes #601. Reported by @ianTPE from a multi-user QM deployment.
A project's Files view was displaying the artifact ledger: each upload or agent reattachment created another row for the same document. Keep that ledger, but return one authorized document per scope/content hash in the viewer's file list.
Change
Validation
Local behavior check
Booted the real core with a synthetic four-document dataset and exercised
GET /v1/scope-resourcesbefore and after:No production data, credentials, or LLM calls were used for this check.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.