[williamloo-scale]

Authoring tools for SDK sites, on main now that #445 (website.toml) is closed in favour of FD-4931 (#514): a site is declared by its folder's env.toml, and its card stays its contract.

• site-client.js (with .d.ts), shipped in the protocol package: api(), universeNow() from X-Universe-Now, followUniverseClock({path}), which re-reads it from a GET the site names so an idle page follows a stopped or faster clock, session(), signIn(), signOut(), errors as ApiError. Notes uses a copy, which a test keeps identical, and follows the clock through api/users.
• agent-env env website new NAME scaffolds a site like Notes: site.py (its own state behind a lock, the data plane's data/reset/data/add/data/get, a @ready_check the card's ready answers by), seed, a Vite web/ with the client, Dockerfile, README, and env.toml with type = "website", environment_name and backend_image = { dockerfile = "Dockerfile" }. --domain (repeatable) writes domains to env.toml; the card declares NAME.test. --from-mcp reads an MCP server's tools from its source (AST, without running it) and --from-tools-json from a tools/list answer; each tool becomes a stub route answering 501.
• agent-env env website dev runs a site locally without Docker: vite build --watch, uvicorn reload, and a local clock with the gateway's /clock routes. It first checks the folder's env.toml as a bundle reads it (a website, its domains valid). Each reload is synced to the clock and seeded, and conformance runs once.

A scaffolded image installs the protocol from PyPI, so it needs a protocol release with the client.

Test

Website CLI, config, bundle, env and protocol suites: 4,054 passed. Two test_disk_recipe tests fail, as they do on main on this machine (KVM). Generated sites pass the conformance check in the tests.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; the previous model-loading failure is fixed.

Summary

Adds a browser client, website scaffolding, and a local development command that rebuilds pages, reloads the server, and restores its clock and seed.

• Website pages can call their API and follow the universe clock.
• The CLI creates a website folder from a name or tool definitions.
• Website authors can run and reload a site locally with its clock and seed.

_{Reviews (19) · Last reviewed commit: "fix(website): a tool parameter named lik..." · Reviewed by Greptile}

[earakely-scale]

Closing this PR. We're taking over the website stack, and we've decided against a site-authoring CLI. Here's where each part stands:

• The website spec (website/spec, website.toml, the example specs) comes from feat(website): one spec declares a site, composes it and checks any server (FD-4683) #445, which was closed on Nov 6 in favour of env.toml (FD-4931).
• env website new and env website dev, their templates, and the TypeScript site client aren't planned.
• website/store.py, the default store of JSON collections, was taken out of the SDK when feat(website)!: WebsiteEnvironment serves a site on the website/v1 contract, and a conformance check tests any server (FD-4683) #428 merged. Sites write their own data hooks.
• @website(models=...) (website/database.py) isn't needed. On main, a website backend already gets a DATABASE_URL for its own schema in the env's service database, with changelog triggers, as an MCP server does, and keeps its state there through its own data hooks. A site whose pages share data with tools can be one env that is both a website and an MCP server (feat(website): a website env may be an MCP server too, its tools declared on its card (FD-4683) #508). Sharing tables across separate envs has no consumer yet.

The branch stays for reference, at head 7c67185.