Wetask's next update brings durable, fenced external workers, atomic batch settlement, and first-party Go, TypeScript, and Python clients. Wetask started with a simple goal: combine the pieces commonly assembled around a background job system into one Go-based runtime. That means a task queue, scheduler, cache, consensus, operational APIs, and observability without requiring a separate broker, result backend, and schedule service for every deployment. The next Wetask update takes tha...