Project Sync — Deprecated Script Bridge

This skill is retained only as a migration note. The old flow was:

Agent skill -> project-sync -> sync.ts -> web API -> database

The new flow is:

Agent skill -> configured FeatBit experimentation MCP server -> FeatBit API -> database

Do not call sync.ts, do not set SYNC_API_URL, and do not require a per-experiment access token in the slash command.

MCP Contract

Use the configured FeatBit experimentation MCP server for all release-decision state. The MCP client configuration must provide normal FeatBit auth, including: