Skip to content

feat(website): sync the clock of, snapshot, and configure a multi env's websites as its MCP servers (FD-4683) - #427

Draft
williamloo-scale wants to merge 1 commit into
wloo/web-apps-verifierfrom
wloo/website-harness-gaps
Draft

williamloo-scale wants to merge 1 commit into
wloo/web-apps-verifierfrom
wloo/website-harness-gaps

Conversation

@williamloo-scale

Copy link
Copy Markdown
Contributor

Stacked on #392.

A website env, and a multi env's websites, now get the same harness treatment as MCP servers:

  • sync_env_clock syncs a website env's site and a multi env's websites; a site that doesn't follow the clock is tolerated.
  • snapshot_env exports each website child through its data plane; one without a data plane is skipped with a warning, and the step fails only if nothing is exported.
  • A config broadcast (apply_server_config with "*") reaches websites, and skips one without a card or the extension, even in strict mode, so a multi env with an older site behaves as before.

legacy_protocol.backing_servers(env) lists MCP servers then websites; on a name clash the MCP server wins.

Test

tst/unit/task_step, tst/unit/env, tst/unit/providers: 5303 passed (one timing test in child_sessions_test.py, untouched here, flaked once and passes on rerun).

🤖 Generated with Claude Code

…'s websites as its MCP servers (FD-4683)

sync_env_clock reaches a website env's site, and a multi env's websites beside its MCP servers; a site that doesn't
follow the clock is tolerated. snapshot_env exports each website child through its data plane and skips, with a
warning, one that has none. A config broadcast to every service reaches websites too, and skips one without a card or
the extension, so a multi env with an older site behaves as before.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant