[williamloo-scale]

Stacked on #443.

Website SDK follow-ups.

• Session cookie per site. agentenv_session_<name>, named on the card, so two sites under one gateway host don't overwrite each other's. The shared agentenv_session is still read for one release.
• /go?sid=. Each sid is a store of its own started from the seed, the CUA-Gym convention the website state verifier reads. A request runs in its ?sid=, else the one its browser last named (<cookie>_sid), else the default session, which is the data plane's state as before.
• Clock rate. /clock/time also answers virtual_seconds_per_real_second, which UniverseClock follows instead of inferring it.
• Conformance: required vs recommended. Only what website/v1 requires of any server fails a run: any host, health, no page at the reserved paths (new), the data-plane round trip. The card's details, X-Universe-Now, clock, forwarded headers and cookies warn; --strict fails on a warning.
• @website(models=...). An object with load/export/reset, or SQLAlchemy models. With models the site gets self.db on DATABASE_URL, and the data plane and /go read those tables, so the GUI and the MCP tools share rows.

Before merging

models= adds an optional db extra (sqlalchemy>=2.0), included in dev, and updates uv.lock. SQLAlchemy is imported only when a site uses models.

Test

Unit suite: 12,625 passed; the models= tests (6) also pass with SQLAlchemy installed.

🤖 Generated with Claude Code

Confidence Score: 4/5

Fix enum restores before merging; the conformance check can otherwise leave populated tables empty.

Findings

1.  Enum rows fail to restore ▶

Fix with agent prompt

### Issue 1
packages/agentenv-protocol/src/agentenv_protocol/website/database.py:176-180
`Tables.export()` turns Python enum members into their values, but `_row()` does not turn them back into members. SQLAlchemy's `Enum(State)` stores member names by default. For a member such as `OPEN = "open"`, the export contains `"open"` while PostgreSQL expects `"OPEN"`.

Restoring that export fails. The conformance check calls `data/reset` first, so it can leave the site's tables empty. Convert exported enum values back to the column's enum members before inserting.

---

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

Summary

Adds per-site login cookies, an explicit clock rate, required versus recommended conformance checks, and database-backed websites through models=.

• Website pages and tools can share rows in the environment database.
• Each named website uses its own browser session cookie.
• The conformance command separates required website checks from optional recommendations.
• Website clocks follow the rate reported by the gateway clock.

_{Reviews (13) · Last reviewed commit: "refactor(website): no /go?sid= sessions ..." · Reviewed by Greptile}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​psycopg@​3.3.7

View full report

[greptile-apps]

Enum rows fail to restore

Tables.export() turns Python enum members into their values, but _row() does not turn them back into members. SQLAlchemy's Enum(State) stores member names by default. For a member such as OPEN = "open", the export contains "open" while PostgreSQL expects "OPEN".

Restoring that export fails. The conformance check calls data/reset first, so it can leave the site's tables empty. Convert exported enum values back to the column's enum members before inserting.

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/agentenv-protocol/src/agentenv_protocol/website/database.py
Line: 176-180

Comment:
**Enum rows fail to restore**

`Tables.export()` turns Python enum members into their values, but `_row()` does not turn them back into members. SQLAlchemy's `Enum(State)` stores member names by default. For a member such as `OPEN = "open"`, the export contains `"open"` while PostgreSQL expects `"OPEN"`.

Restoring that export fails. The conformance check calls `data/reset` first, so it can leave the site's tables empty. Convert exported enum values back to the column's enum members before inserting.

---

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