ACT 0.7: sessions, three production bridges, and auth-via-args

The previous posts focused on what ACT is — sandboxed components, one binary per transport, capability ceilings. This one is about a thing that was missing: state . Most of the components on actpkg are pure request/response — crypto , encoding , random , time . They don't need a session because every call is independent. But the moment you reach for tools that do — a database connection, an OpenAPI client that has parsed a 5MB spec, an MCP bridge mid-handshake with an upstream server — there's n