Add Laravel Cloud branch deployment research

[peterjthomson]

Research findings on implementing one-click temporary deployments
based on Git branches using Laravel Cloud's Preview Environments
and API capabilities.

[kaurifund]

@peterjthomson what are you looking to do? Goals of this research

ab0t infra also has ephemeral sandboxes for coding agents

[peterjthomson]

@kaurifund Not sure yet. It's pretty exploratory. But for the Laravel Cloud part (if any) it would probably closer to traditional sandboxes with external URL availability for user acceptance testing. I've been mulling the overlaps (or divergences of):

1. Agent Sandboxes: Environments mainly for the coding agent, that have some light ability to execute application code.
   2: CI/CD Actions: Environments mainly for CI/CD testing, linting, can execute code but not much agent activity or compute.
2. Staging: Preview environments that humans can interact with the application code (no agent loaded).
   I think this is an incomplete mental model, but there's something important about actually executing / running / interacting with code beyond just tests.

[kaurifund]

@peterjthomson I think that staging one is interesting.

For example the biggest human factor (apart from guiding the agent) was manually downloading the repo to build it, and test it. As the remote server I was using was not big enough to handle to build step.

That would allow, browser based staging with a URL, that a playwrite, or browser agent could test. This was the main barrier for me as I didn't want to run playwrite locally, but needed a desktop to run it.

Also, github runners are a option for (1.)