Skip to content

fix: hide unassessed jobs and cache gate rejections - #23

Merged
sangowu merged 1 commit into
mainfrom
codex/fix-unassessed-job-visibility
Aug 11, 2026
Merged

sangowu merged 1 commit into
mainfrom
codex/fix-unassessed-job-visibility

Conversation

@sangowu

@sangowu sangowu commented Aug 11, 2026

Copy link
Copy Markdown
Owner

What changed

  • default Web job list now returns only real non-skipped matches for the latest CV
  • persist CV/JD/prompt-scoped relevance gate rejections
  • preserve no-CV behavior and invalidate rejections on CV, JD, language, or prompt changes
  • add cleanup coverage, regression tests, and documentation updates

Root cause

/api/jobs loaded the newest 200 raw cache rows and treated a missing match_score as visible. Relevance-gate rejection events were run-scoped only, so rejected cached jobs could reappear as unassessed and consume repeated model calls.

Impact

No fake zero scores and no bulk rescore. Existing unassessed historical rows are hidden by default; future gate rejections are reused only within their valid scope.

Validation

  • 255 passed
  • Ruff passed
  • Python compileall passed
  • frontend JavaScript syntax check passed
  • isolated SQLite smoke passed

@sangowu
sangowu merged commit 0aefac5 into main Aug 11, 2026
2 checks passed
@sangowu
sangowu deleted the codex/fix-unassessed-job-visibility branch August 11, 2026 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant