XWorkmate Bridge Migration

Summary

The ACP Bridge Server implementation was migrated out of xworkmate-app into the standalone sibling repository xworkmate-bridge.

This migration separates the embedded Go bridge/server from the Flutter application repository. The app now depends on the sibling xworkmate-bridge repo for the helper/runtime contract instead of carrying an in-repo Go bridge copy.

New Repository

Repository path: /Users/shenlan/workspaces/cloud-neutral-toolkit/xworkmate-bridge
Go module: xworkmate-bridge
Helper binary output name: xworkmate-go-core

What Moved

The previous xworkmate-app/go/go_core implementation was migrated to xworkmate-bridge, including:

ACP Bridge HTTP/WebSocket server
ACP stdio entrypoint
internal routing, dispatch, mounts, shared RPC helpers, gateway runtime support, memory, skills, and toolbridge packages
Go tests for ACP routing/contracts and bridge helper behavior
legacy static token auth helper code previously stored under xworkmate-app/go_service

What Stayed In xworkmate-app

The following app-side concerns remain in xworkmate-app:

Flutter UI and settings pages
ACP Bridge client-side configuration and secure-storage handling
Dart runtime launch/locator logic for the helper binary

Build Contract

xworkmate-app expects the helper artifact named xworkmate-go-core.

This is the current cross-repo runtime contract for local development flows, not a legacy compatibility shim. The helper is built from xworkmate-bridge and consumed by xworkmate-app outside the shipped app bundle.

App Repository Changes

In xworkmate-app:

go/go_core was removed
scripts/build-go-core.sh now resolves and builds from sibling repo xworkmate-bridge
the script supports both normal workspace layout and worktree layout
release notes references were updated to point at the new repository

Validation

Validated during migration:

cd xworkmate-bridge && go test ./...
cd xworkmate-bridge && bash scripts/build-helper.sh
cd xworkmate-app && bash scripts/build-go-core.sh

Operational Note

For local development and packaging, xworkmate-bridge must exist as a sibling repository next to xworkmate-app, unless XWORKMATE_BRIDGE_DIR is set explicitly.

At runtime, the app treats bridge-related discovery, provider sync, connection metadata, and ACP conversation forwarding as bridge-owned concerns. Account sync only updates bridge-linked configuration attributes and secure secret references; it does not auto-connect the bridge.

2.5 KiB Raw Blame History