reference creatortrack worktree npm install symlink break 20260715T182815

In the CreatorTrack warm-slot dev pool (worktrees under forge-suite-wt/warm-slot-N, see Worktree Dev Agents and warm slots), node_modules is normally a symlink shared across slots. Running npm install to add a new dependency inside one worktree (e.g. adding @huggingface/transformers for Task 15's embeddings work) silently converts that slot's symlink into a standalone real directory (observed: ~1.5GB), leaving other slots unaffected.

The already-running dev server in that slot then caches stale module-resolution state against the old symlink target, throwing errors like ENOENT ... node_modules/onnxruntime-node even though the package is actually installed.

Fix: kill the dev server and relaunch it using the warm pool's exact startup command from forge_creatortrack_agent_bootstrap.sh (a plain next dev restart in the wrong cwd/invocation won't pick up the new real directory correctly). Verify sibling slots (other ports) are still healthy afterward, since this is a per-slot mutation.

Why this matters: any worker task that adds an npm dependency inside a CreatorTrack worktree should expect this and restart via the bootstrap script rather than debugging the ENOENT as a code bug.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.72, mode staged]