The tools/call pipeline — policy, approvals, limits, idempotency, dry run, taint, audit

Shipped

September 27, 2026 at 8:00 AM UTC

Author

Kamo

Commit

9088730

A stored idempotency entry is answered before the planner reads again (SP05-T11-order); an approved call in a tainted run still answers to the capability and charter checks (SP05-T11-taint); nothing after a successful handler turns it into OUTCOME_UNKNOWN, and untrusted content is withheld while the run cannot be marked (SP05-T11-after); the session's TimezoneType name is the member's zone for daily limits (SP05-T11-zone).