Weaver OA Audit Manager

Problem

Weaver E-Cology OA approvals are spread across portal pages, form fields, related contracts, and audit logs. Manual inspection or prompting a model to infer page content can omit fields, summarize required tables, or accidentally trigger approval actions. This skill maps those operations to explicit CLI commands and an Agent routing table.

Core workflow

• Login and session: use oa-audit-cli login for QR-code sign-in, store the session in .oa/cookies.json, and verify it with session --probe.
• Lists and details: workflow-doing, workflow-done, workflow-my, and workflow-cc retrieve current todos, done items, my requests, and CC items; workflow-todo-detail, workflow-done-detail, and workflow-cc-detail return Markdown or page details.
• Flow context: workflow-detail presents form fields, the 8-column audit trail, attachments, and contract links; workflow-invoices extracts invoice data, while workflow-attachments downloads main-form files.
• Gated writes: workflow-operate and workflow-forward-operate are disabled by default, require a single explicitly specified process ID, and remain constrained by OA_APPROVAL_ENABLED and a whitelist.

Boundaries

The OA base URL and a valid session are required. It targets Weaver OA workflow forms, not non-OA forms such as ehr; do not force workflow-detail on empty or negative request IDs. Approval writes remain disabled by default, and batch or Agent-selected approval operations are not allowed.