Exclude legacy sample jobs from public Find Work - #117
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Follow-up to #116. Public production readback correctly restored legitimate jobs #24–#27, but also surfaced six persisted legacy sample jobs because three historical seed-employer identities were absent from the consolidated
SEEDED_SAMPLE_EMAILSset.This hotfix:
reviewingstatus.TDD evidence
RED before implementation:
GREEN after implementation:
Independent exact-tree review
Reviewed tree:
d168348643b3658a0d2b670e50942156118c4d65d19be1b1bb7ca3891393236d2196f8594519e2d5231ffa96b28c68dc4b9cf8a9SEEDED_SAMPLE_EMAILSconsumers inspected; no stale parallel exclusion list found.open,reviewing,hired, invalid-status, detail, service, stats, and login behavior verified.Production verification plan
After deployment, read-only checks will require:
GET /jobsreturns exactly jobs feat: add autonomous AI QA service system #24–feat: add AI QA support and product content pages #27.reviewingand remain application-eligible.