You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Minors from the order lens on #384 (#384 (comment)). Neither is a regression; both were there before #384.
No test guard for dropping the runtime-service lines. If a sync drops both the ForkLayers.layerRuntimeServices and ForkLayers.layerRoutes lines from apps/server/src/server.ts (together with the two /mcp reads in forkLayers.ts:39-46), the server still boots and holdWork.boot.test.ts stays green. The usage pacing gate and the slot gate are then silently off, and automatic updates are gone. The seam check only notes dropped lines during a sync. Fix: add a boot or layer test asserting that UsagePacer and the slot gate are present in the built runtime (for example, resolve them in the boot test), so dropping the lines goes red.
holdWork.boot.test.ts reads the machine's managed policy file. On a machine whose policy turns T3 Connect off, the held phase waits forever. Fix: point the spawned server at an empty or temporary policy path, as other Connect tests do. The test also clears the environment, which on some machines drops a library path node needs: keep the variables node needs to start.
Activity
boot test: guard the fork layer lines; pass on node's start variables (…
boot test: guard the fork layer lines; pass on node's start variables (…