Why this matters now: Corrupts the audit/verification history that future analytics, disputes, and fraud investigations depend on.
Problem / What: When claimCompletionSlot reports the task is full, finalStatus flips to REJECTED but the stored Verification.verdict is still the original verdict ('approved' from result.verdict in verificationWorker.ts:94-101; parsed.data.verdict in proofController.ts:343-350; verdict in validatorService.ts:201-208). So proof.status = REJECTED while Verification.verdict = approved — a direct contradiction persisted to the DB.
Key Challenges: Capturing the effective verdict, not the intended one, and deciding whether to keep the auto-reject reason separate from the human/auto verdict. Needs a migration-safe write path since existing rows already disagree.
Acceptance Criteria:
- A
Verification row's verdict always matches the resulting Proof.status (or a new field effectiveVerdict is introduced and backfilled).
- New integration test asserts consistency for the capacity-rejected case across all three finalizers.
Relevant files/functions: src/workers/verificationWorker.ts:90-117, src/controllers/proofController.ts:322-367, src/services/validatorService.ts:161-245, prisma/schema.prisma (Verification model).
Out of scope: Changing the capacity-rejection behavior itself.
Labels: advanced, database, bug
Why this matters now: Corrupts the audit/verification history that future analytics, disputes, and fraud investigations depend on.
Problem / What: When
claimCompletionSlotreports the task is full,finalStatusflips toREJECTEDbut the storedVerification.verdictis still the original verdict ('approved'fromresult.verdictinverificationWorker.ts:94-101;parsed.data.verdictinproofController.ts:343-350;verdictinvalidatorService.ts:201-208). Soproof.status = REJECTEDwhileVerification.verdict = approved— a direct contradiction persisted to the DB.Key Challenges: Capturing the effective verdict, not the intended one, and deciding whether to keep the auto-reject reason separate from the human/auto verdict. Needs a migration-safe write path since existing rows already disagree.
Acceptance Criteria:
Verificationrow'sverdictalways matches the resultingProof.status(or a new fieldeffectiveVerdictis introduced and backfilled).Relevant files/functions:
src/workers/verificationWorker.ts:90-117,src/controllers/proofController.ts:322-367,src/services/validatorService.ts:161-245,prisma/schema.prisma(Verification model).Out of scope: Changing the capacity-rejection behavior itself.
Labels: advanced, database, bug