{{ message }}
Repository navigation
refactor(hub): separate published improvement comments - #48
Merged
Copilot merged 1 commit intoOct 21, 2026
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot was unable to review this pull request because there is no eligible user to bill.
An enterprise owner can allow the organization to be billed for reviews like this by enabling Copilot code review for users without a license.
Contributor
Author
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.
Why
Private Pick & polish work should not add alternate behavior to ordinary review comments. This revises #39 with the agreed relational design and keeps unpublished improvements on the author's device, following the publication boundary in #37.
What changes
ImprovementCommentstores one request or agent response per record. Replies point to the original request, and a join table links responses to the requests they answer. Database constraints keep those links within the same creator's conversation. Hub reconstructs the existing thread payload from these records, retaining revision checks, immutable history, and deletion tombstones without changing ordinary review behavior.New uploads require a successful Build of the same Prototype and return its immutable
buildNumber. Later changes retain that Build. The canvas must verify that the captured local source matches the published Build before uploading; #49 supplies that gate and must land with this change. This intentionally replaces the development-only migrations rather than converting existing data.