gmail-triagelisted

# Gmail Triage Interactive GTD-inspired state machine for Gmail. Gaia analyzes threads, proposes transitions. User decides. Gaia executes. This is the PROCESS layer; it depends on `gmail-policy` for every rule -- label definitions, security tiers, the interpretation of a review trigger (Intent Classification), and the Autonomous Action Boundary that decides what may run without approval. That dependency holds in every mode, headless included: a security rule cannot live only in the process that obeys it. ## State Labels Five `_gaia/*` labels (defined in `gmail-policy`) — three durable active states, plus staging and soft-delete: - `_gaia/action` — user must act - `_gaia/waiting` — user acted, awaiting reply - `_gaia/someday` — interesting, no urgency - `_gaia/pending` — staging (triage backlog) - `_gaia/trash` — soft delete; never truly deleted No `_gaia/*` label = processed/done. ## Thread-Awareness Rule Before presenting ANY labeled email, check the thread: message count, who sent last, when. This determines framing: - "necesitas responder" (user is last) - "esperando desde [date]" (user replied, waiting on them) - "sin actividad hace 2 semanas — ¿hacer seguimiento?" (stale waiting) These two sections are the state-machine expression of the **Autonomous Action Boundary** in `gmail-policy` — the boundary is the rule, these are its transitions. ## Automatic Transitions (no confirmation needed) - User replies to an `action` thread → move to `waiting` - New message arr