Authentication is a long-running Workflow

This post details how KERNEL models long-running authentication connections as durable Workflows, incorporating human intervention and external approvals as explicit states within the Workflow lifecycle. It highlights the use of child Workflows for individual login attempts and the separation of concerns between Go for durability and TypeScript for agent execution. The post also discusses strategies for maintaining authenticated sessions, including recurring health checks, automatic reauthentication, and circuit breakers for repeated failures.