Adam Moussa f3a28ecb8b Add deterministic template parser for WO emails ... The workorder-email-processor sends every one of ~22.9k emails/month to an LLM, but ~93.6% are the plain-text "AMAZON UPDATE WO DETAILS" comment template and ~6.4% the HTML "AMAZON assign Work Order" template. Parse those two shapes deterministically, offline, so the AI call is reserved for the long tail. The module is pure (no boto3, no network). try_deterministic_parse classifies by subject, extracts the shared contract fields, and returns a result ONLY when it passes a strict fail-closed validation gate: exact contract-key set, subject/id agreement, the literal "Work Order: <id>" double space, per-type required fields, site-code shape, and a label-bleed guard so a value that over-ran into the next field fails. Any miss, drift, or extractor exception yields None so the caller falls back to the AI extractor -- data is never corrupted, only the fallback rate rises. Refs: #23		2026-07-15 20:09:29 -04:00
..
po	Update boto3 requirement in /lambdas/po/email_processor (#94)	2026-07-14 13:13:03 +00:00
wo	Add deterministic template parser for WO emails	2026-07-15 20:09:29 -04:00