Summary

Wires ST1's IMAP poll listener through to a real `EmailInboundHandler` mirroring `SlackDMHandler`'s 5-step filter precedence. Adds JSONL inbound log, chain-event emit on identified Joshua mail, and opt-in AUTO_REPLY via reasoning engine + existing PurelymailClient outbound.

Bucket spec: `17_cc_bucket_prompts/KR-FEAT-EMAIL-INBOUND-IMAP_active.md`

Filter precedence (5 steps, ordered per spec)

`HandlerResult.should_mark_seen` drives the listener's `mark_seen()` call. Terminal-success statuses get SEEN (we explicitly chose to not re-process a filter-dropped UID); handler errors stay UNSEEN so transient failures get a retry.

Chain event `[kora.email_inbound.received]` emitted ONLY on identified Joshua mail.

JSONL schema (`${KORA_HOME}/email_inbound_log.jsonl`)

```json
{
"received_at": "...", "message_id": "...", "from": "...",
"to": [...], "subject": "...",
"body_text_truncated_2k": "..." (max 2048 chars),
"has_html": false, "attachments_count": 0,
"handled_status": "received|filtered_*|handler_error",
"spoofing_check_skipped": true, "imap_uid": 42,
"in_reply_to": null,
"extra": {...} (optional, per-filter diagnostic),
"error": "..." (optional, handler_error path only)
}
```

Body truncated to 2KB per spec — operator pulls full body from Purelymail webmail.

AUTO_REPLY (`KORA_EMAIL_AUTO_REPLY`, default OFF)

When env in {true, 1, yes, on} AND `handled_status == received`:

1. Build `IncomingMessage(text=body_text, source="email", metadata={from, subject, message_id, in_reply_to})`
2. Load `ConversationContext` via new `load_email_context()` — reads BOTH `email_inbound_log.jsonl` + `email_outbound_log.jsonl`, applies transitive chain-anchor closure over (message_id ↔ in_reply_to) pairs, returns up to N most-recent turns chronologically
3. `current_reasoning_engine().respond(message, context)`
4. Send via `current_purelymail_client().send_email(...)` with `from_addr=KORA_EMAIL_KORA_ADDRESS`, `to=[parsed.from_address]`, `subject="Re: " + parsed.subject` (idempotent), `in_reply_to=parsed.message_id`

Failure modes → canned fallback text `"Kora is currently unable to respond by email; operator notified."`:

• Engine unavailable
• `engine.respond()` raises
• `result.error` set (e.g. cost-halted)
• Empty response text

Send failures DON'T change inbound status — outbound JSONL records the SendResult separately; inbound stays SEEN.

Surface

Security carry-forward

• IMAP / SMTP passwords + bot tokens NEVER in JSONL (test pins absence across diverse-failure modes — env-read raise, log-write failure, handler exception)
• Body text logged truncated to 2KB; full payload only in Purelymail's webmail
• Spoofing-check absence is a recorded flag (`spoofing_check_skipped: true`), never a silent bypass

Test plan

• 63 new tests pass (28 handler + 16 listener wire-in + 19 context loader)
• 477/477 cross-bucket regression (clients/ + test_listeners/ + handlers/ + reasoning/)
• Ruff clean
• Verified AUTO_REPLY env truthy variants {true, 1, yes, on}; default + falsy values keep reply disabled
• Verified subject idempotency: `Re: existing thread` → `Re: existing thread` (no doubling)

Cascade

ST3: Operator runbook addendum — extend `purelymail_outbound_runbook.md` with inbound section (Doppler secrets, smoke test, troubleshooting). After ST3 merges Feature 3 closes fully.

🤖 Generated with Claude Code