carlos / platform Public

Half of discussion #6: the activator's wake now reports its own duration, split into the app's boot and everything else, on the wake event carlos logs already carries.

instance woke in 1.4s (spawn 1.2s) (version 7507a33)

spawn is Backend.Start alone — exec to the socket accepting, the app's own boot — so an app can finally tell "our boot is slow" from "the wake path is slow", which #6 says it cannot do at all today. Unmeasured stays unmeasured: a wake with no timings reads exactly as the line did before.

The other half — a Server-Timing header from the edge — is deliberately not here, and the reason is this repo's own hard-won rule: the wrappers in internal/edge share ONE header map from handler to connection, and maybeStore caches rec.Header().Clone(). A timing header set the obvious way would be cached and served to later visitors as though it described THEIR request. Where it goes in the wrapper order, and which responses may carry it, is a design question rather than a patch.