Consume the 6-digit code the founder received and start the research
pipeline.
**When:** after `create_application`, and ideally after the deck has
been uploaded over plain HTTP (see the `curl` printed by
`create_application`). Founder has read the code from their inbox.
**Before you call:**
- CONFIRM you have the right code from the founder (not guessing, not
stale). Once this succeeds, research starts and is irreversible.
- If deck parsing is still pending, that's fine — research auto-defers
and dispatches when the deck resolves. Don't wait, don't re-verify.
**Returns:** `status: researching` + whether research was dispatched now
or deferred on the deck.
**On error:**
- `wrong code` — response includes attempts-remaining. Ask the founder
to check their inbox again. If the error says the code is invalidated,
call `resend_verification` for a new one.
- `no active code` — they never received one, or it expired. Call
`resend_verification`.
- Already verified — idempotent success; returns current status.
Don't retry in a loop.
ConnectorNo auth