GPT-5 finding
Misleading comment: lifecycle failure marked as 'recoverable on next sweep tick' but worker marks review done and won’t retry lifecycle persistence
lowdocs-gaphigh
- apps/web/lib/review-worker.ts
After this catch, runReviewWorker proceeds and calls markReviewSucceeded, placing the row in a terminal 'done' state. The retry cron does not pick up 'done' rows, so this lifecycle persistence is not retried by the worker. The comment suggests recoverability by the next sweep, which conflicts with the actual state transition and the subsequent note that Sweeper cannot reconcile without lifecycle rows.
Recommendation
Clarify the comment to state that lifecycle persistence after comment post is not retried by the worker and is intentionally accepted as lost (no closure reconciliation). If recovery is desired, introduce a separate repair job to re-derive missing lifecycle rows for done reviews.