AI Auto-Reject setting does nothing when enabled #94
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
ai_auto_rejectsetting is wired into the settings UI and stored, but enabling it has no effect. During a fetch,_classify_fetched_postsrecords anai_would_rejectrecommendation on each post, but that verdict is only surfaced as a badge + filters in the review UI — nothing ever rejects a post based on it.The AI auto-reject behaviour was deliberately deferred at launch ("the AI does not auto-reject at launch — it records a recommendation"), with
ai_auto_rejectadded as a placeholder flag. This issue is to implement the actual behaviour: when the setting is enabled, posts the AI would reject should be auto-rejected.Findings:
ai_auto_reject+get_ai_auto_reject_settingare defined but never consumed —check_reblog_filters/reject_blocked_postsonly apply the five deterministic filters. Classification (which setsai_would_reject) runs only in the scheduler's_fetch_stream_job, not the manualPOST /hashtags/{id}/fetch.Plan:
reject_ai_flagged_posts(db)inservices/export_eligibility.pymirroringreject_blocked_posts: whenai_auto_rejectis on, reject unreviewed posts whereai_would_reject is True, settingauto_reject_reasonfromtext_reason/vision_reasonand writing areview_feedbackrow._fetch_stream_jobright after_classify_fetched_posts.reject_ai_flagged_posts, then a scheduler integration test.Key files:
services/export_eligibility.py,services/scheduler.py,tests/test_reblog_controls.py.Branch:
feat/issue-94-wire-ai-auto-reject, PR intofeat/issue-80-collectwithRefs #94.Note: the manual fetch endpoint doesn't run AI classification today, so this auto-reject applies to scheduler fetches; wiring the manual Fetch button to also classify is a separate follow-up.