feat(research): add shared history workspace#59
Draft
hubab1 wants to merge 1 commit into
Draft
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
1 participant
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.
Summary\n\n- add a read-only shared search-history workspace with master/detail browsing\n- scope history models to exact project and keyword generations\n- paginate with the stable shared-history cursor and retry failed continuations without discarding loaded pages\n- distinguish reported result counts from retained result rows and explain that positions belong to returned apps, not the research project\n- improve loading, empty, error, selection, and accessibility states\n\n## Validation\n\n- 3 focused presentation tests passed\n- full suite passed: 456 tests in 43 suites\n- signed macOS build succeeded\n- deep strict code-signature verification passed\n- independent logic and UI reviews found no actionable P1/P2 issues\n- no live persistent-store launch was performed\n\n## Stack\n\nDepends on #58. This persistence-backed UI stack remains a draft for manual review.