[williamloo-scale]

Implements the website env item of M5 in CUA Env: Computer Envs and Computer App Envs (Websites in the computer, agreed Oct 26), extending the existing WebsiteEnv. A website env is one server image that serves the site's pages and API, so it no longer needs a separate frontend image. An env with one still deploys, put warns that it's deprecated, and a bundle may leave it out. The env declares the health path that answers once it's usable. Existing envs keep loading: the server image is written as server_docker_image_artifact beside backend_docker_image_artifact, which an older document holds and is read as the server image, and backend_image in an env.toml names it. Declared domains wait for the M5 site proxy that routes by them.

Validation: unit suite passes, with tests for one-image envs, health-path refusals, reading an older document, the frontend deprecation warning, and an optional image key in a bundle.

🤖 Generated with Claude Code

Confidence Score: 4/5

Fix the health-path fallback before merging so healthy sites without JSON cards can deploy.

Findings

1.  Healthy websites cannot deploy ▶

Fix with agent prompt

### Issue 1
src/agent_env/providers/env_providers/env_gateway_provider.py:1648
If a site returns its default HTML page for unknown paths, `_website_ready()` tries to parse the 200 response from `/.well-known/agent-env.json` as JSON. That raises `ValueError`, so every retry skips the declared `health_path` until deployment times out-even when that endpoint answers 200. Treat an unreadable card as absent and continue to the health check.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Makes WebsiteEnv deploy from one server image while preserving older two-image records.

• Website environments can use one server image for pages and APIs.
• The gateway routes one-image sites and waits for them to be ready.
• Browser routes cannot reach a site's framework data paths or card.
• Tasks can check values from a website's saved session state.
• The Notes example now includes its browser build dependencies.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[WebsiteEnv] --> B[Gateway deploy]
  B --> C[Start server image]
  C --> D[Fetch site card]
  D --> E{Readiness method advertised?}
  E -->|Yes| F[Poll ready method]
  E -->|No| G[Poll declared health path]
  D -->|HTML returned with 200| H[JSON parsing fails]
  H --> I[Retry until deploy fails]
  F --> J[Return deployed website]
  G --> J

Loading

_{Reviews (10) · Last reviewed commit: "feat(website): the gateway serves a one-..." · Reviewed by Greptile}