v3.11.9 - The Bridge Learns Which Files to Carry

The Bridge Learns Which Files to Carry

v3.11.9 fixes a bridge staging regression found during live sync verification. The bridge export surface now stages generated artifacts without force-adding ignored large telemetry files, while still force-adding the small shared.js file:// compatibility wrapper that the bridge repo intentionally ignores in local checkouts.

Changed

• bridge_push now stages normal generated paths with regular git add.
• shared.js is force-added separately so ignored local checkout rules do not block sync.
• Ignored large files under extended_memory/, such as memory_events.json, are no longer force-added by the generated-artifact stage path.
• bridge_sync_worker now follows the same staging behavior as the MCP bridge server.
• Package metadata is bumped to 3.11.9.

Verification

• python3 -m py_compile bridge_server.py bridge_sync_worker.py db_utils.py
• ruff check .
• git diff --check
• pytest -q tests/test_bridge_server.py tests/test_bridge_sync_worker.py tests/test_surface_contract.py -> 51 passed
• pytest -q -> 840 passed
• Live bridge verification: local_tasks=897, remote_tasks=897, HEAD...origin/main = 0 0.

Not changed

• No schema migration.
• No bridge/agent process restart required.
• No manual release assets added; source archives remain the current release pattern.