feat(feedback): include post status in similar-posts (possible duplicates)#103
Merged
Conversation
findSimilarPosts now joins status_template and returns each candidate's status (displayName + color), exposed as SimilarPost.status via the signal ingestion plugin. Lets the composer show whether a possible-duplicate match is already completed/closed rather than still open to duplicate. Regenerates the committed executable schema (baked into the Docker build; graphql:generate does not run on deploy).
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Task link: N/A
Adds the candidate post's current status to the
similarPosts("possible duplicates") results so the composer can show whether a match is already completed/closed rather than still open to duplicate.findSimilarPostsnowLEFT JOINsstatus_templateand returnsstatus: { displayName, color } | nullper candidate.SimilarPostStatustype andSimilarPost.statusfield.schema.executable.ts+schema.graphql). This is required: the server boots from and the Docker build bundles the committed executable schema, andgraphql:generatedoes not run on deploy.Pairs with backfeed-app PR "show status on possible-duplicate suggestions". Merge this first so the live API serves
SimilarPost.statusbefore the app selects it.Test Steps
bun graphql:generateis already reflected;bun run checkis clean.bun test --env-file .env.local src/lib/feedback/brain.integration.test.ts -t findSimilarPostspasses (2/2), including the new assertion thatstatusis present.similarPosts(projectId, content) { id title score status { displayName color } }and confirmstatusresolves (null for posts with no status template).