give ExMCP consumer a writable dependency path #275
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ex-mcp-consumer-cache-20260913"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The isolated ExMCP consumer writes its lock, build, and dependency trees under EX_MCP_CONSUMER_SCRATCH. Give it a worker-owned mounted parent and create a unique directory there. This removes the remaining EACCES after the Hex home mount was corrected.
Validation: the new mount guard fails before the recipe change and passes after it; scripts/check passes.