PAGI 0.002002: Clarifying How Applications Are Loaded

Introduction PAGI 0.002002 is a specification release. It does not change the runtime shape of a PAGI application. A running application is still one asynchronous code reference: async sub app { my ($scope, $receive, $send) = @_; await $send->({ type => 'http.response.start', status => 200, headers => [[ 'content-type', 'text/plain; charset=utf-8' ]], }); await $send->({ type => 'http.response.body', body => 'Hello from PAGI!', more => 0, }); } What the release clarifies is how a general-purpose runner may reach that runtime boundary. The gap between Python callables and Perl objects PAGI's scope, receive, and send runtime shape was inspired by ASGI. ASGI describes an application as an asynchronous callable receiving those three values. In Python, that callable may be a function or an instantiated object implementing __call__; the distinction disappears at t