[ryanweiler92]

Summary

Adds a new system routine, Expense Review, to Collaboration Routines. When an email whose subject starts with Meeting Approval or Business Approval reaches the owner's inbox, the routine reads the request, checks it against the guideline documents the owner uploaded, and emails the owner a Deloitte-styled HTML memo with a suggested decision. It never replies to the requester; the owner still responds in MES.

Unlike the daily brief and weekly agendas, this routine runs off the mail import instead of a schedule, so WorkRoutine learns about unscheduled kinds.

What changed

New routine kind

• WorkExpenseRoutine (id expense-review, table WORK_EXPENSE_ROUTINE, automation expense-review.automation.json, result node review).
• Settings: only enabled and timezone. Subject prefixes are a constant (SUBJECTS). Matching is case-insensitive, skips leading gateway tags such as [EXT], and never matches RE:/FW: replies.
• Guideline documents live in a fixed user-asset folder, collaboration/routines/e8f3a1c2-5b6d-4a7e-9c0f-1d2e3b4a5f60, and are copied into the run room's documents/ folder before the agent starts (same path custom routines use). WorkRoutineDocuments.requireRoutine accepts that id besides stored custom routine ids.
• Reactors: WorkGetExpenseRoutine(), WorkSaveExpenseRoutine(settings=[{enabled, timezone}]), WorkRunExpenseRoutine(threadId=[...], messageKey=[...]).
• Automation: gather (Python, reads each request thread as clean text) -> review (Collaboration agent with collaborationRoutine, documents in the room) -> deliver (Python, Deloitte email shell, decision paragraph highlighted, Outlook link back to the request). Review order per request: Suggested decision, Before you respond, Guideline check table, Request table.

Trigger path

• BrainMailImport.Run.inbound records [messageKey, threadId, subject] of each newly imported message to the owner (from someone else, or a note the owner sent themselves; toMe now covers a self sender on To/Cc).
• BrainSync.run and BrainSync.importHeaders (webhook and pull paths) call WorkExpenseRoutine.onNewMail after the ingest lock. Matching mail from one import batch becomes one run. Only mail Brain has never seen triggers; mail that arrived while the routine was off is never reviewed.
• WorkRoutine.trigger(kind, owner, pixel, delay) fires the routine's durable Quartz job with a per-firing Pixel (JobDataMap override; RunPixelJobFromDB reads the merged map and SchedulerResource.executePixel runs the posted Pixel). It calls SchedulerDatabaseUtility.startScheduler first, because Quartz stands by after a restart until a schedule is saved.
• WorkExpenseRoutine.run settles a lost run first, claims with now=true, and when another review is still running schedules a one-shot retry two minutes later.

WorkRoutine engine

• Kind.scheduled() = the kind has a time default. Unscheduled kinds skip time/days validation, keep a never-firing cron (0 0 0 1 1 ? 2099) so save still creates the durable job and recipes row, report no nextRunAt, and get their own failed() wording.
• run(...) overload that merges trigger-supplied inputs (thread_ids, message_keys).
• Comment on the once-per-day guard shortcut: when restored, it must exclude unscheduled kinds.

Daily inbox brief

• WorkInboxRoutine.inputs passes skip_reply_subjects = WorkExpenseRoutine.SUBJECTS; the brief's gather skips reply drafts for those threads (new _request helper strips Re:/Fw:/bracket tags). The brief must not draft an approval of spend; the request still shows in priorities and action items. New start global in inbox-daily-brief.automation.json.

Plumbing

• CollaborationOwlCreator table loop and CollaborationDbUtils unique owner index include WORK_EXPENSE_ROUTINE.
• WorkRoutineRoom.open maps the new id (open a result as a chat).
• BrainResetUtils deletes the routine's runs.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.