Debugging Playground issues can be cumbersome. Having a timed debug log of events would make it easier, something like:

[2026-01-14 14:58:12.32415] `playground.writeFile()` called by external caller
[2026-01-14 14:58:13.22415] Blueprint execution started ({ "steps": [ ... ] })
[2026-01-14 14:58:14.92415] Blueprint step 1 "writeFile" started
[2026-01-14 14:58:15.12415] Blueprint step 1 "writeFile" finished
[2026-01-14 14:58:16.82415] User requested `/wp-admin/`

Other events that might be useful:

• PHP boot options
• Query parameters and their change
• php.run() called + the exit code and error details if it failed
• Anytime a new PHP instance is spawned (only in some kind of a "very verbose debug" mode)
• ... what else? ...

It would also be nice to have a way of preserving that log across page reloads (or at least accessing the last, say, 10 log files)

Note this is not about debugging each WordPress site. It's a debugging tool for Playground developers and integrators. It would be a great addition to Playground devtools suite and perhaps to some kind of "integrator mode" on playground.wordpress.net.