[williamloo-scale]

Stacked on #444.

A website spec: one TOML file declares a site, composes from parts, and checks any server against it. Design: docs/website-spec.md.

• agentenv_protocol.website.spec reads [site], [source], [data], [users], [roles], [routes.ops], [clock], [[uses]] and extends, with validation, overlays, composition, card params, from_card, from_environment, a JSON Schema and a CLI (validate, show, show --card).
• A name table for a multi env: synthetic over live over the allowlist, two sites of one kind on a name refused.
• @website(spec="website.toml"): the class is refused when its @api routes aren't the spec's, and its card is built from the spec. Notes now declares itself this way.
• env.toml takes spec = "website.toml" or an inline [spec]; the env takes its name, health path and domains from it.
• conformance --spec checks a server's card and routes against the spec; those checks are required.
• Examples in examples/website/specs/: a replayed Slack overlay, an intranet, and an SSO component.

Live and replay sources, served_by and models = "mcp:..." are modelled in the spec but not deployable from env.toml yet.

Test

Unit suite: 12,793 passed (one GitHub-clone test from main, which hangs on the local machine on main too, deselected).

🤖 Generated with Claude Code

Confidence Score: 5/5

No new blocking issue was confirmed in the reviewed changes.

Summary

Adds one website spec that describes a site, combines components, and checks a running server.

• Website specs describe sites and combine reusable parts.
• SDK site classes can take their routes and card details from a spec.
• Website environments can take their site details from a spec.
• Conformance checks compare a running site with its spec.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  TOML[Website spec] --> Resolve[Merge overlays and components]
  Resolve --> Validate[Check the combined spec]
  Validate --> SDK[WebsiteEnvironment and card]
  Validate --> Env[WebsiteEnv name, health and domains]
  Validate --> Check[Check a running server]
  SDK --> Check

Loading

_{Reviews (17) · Last reviewed commit: "fix(website): an overlay on a spec read ..." · Reviewed by Greptile}

[earakely-scale]

Closing in favour of FD-4931. Decided Nov 6: a website env is declared by its env.toml, as every bundle entry is, with no separate website.toml. env.toml holds the facts agentenv needs before a site runs (its domains first, stored on WebsiteEnv, with per-site overrides and put-time refusal of a name claimed twice), and the card a site serves stays its contract (routes, roles, sign-in, clock, tools). The spec's overlays, components, sources and name table are left out until something serves them; computer site routing keeps #448's site table.