Adopt clone-isolation for solo-venus-cc (post-VENUS-4) per pluto topology ref pm-pluto-cc-mr4gqnpgg218: own sibling FULL CLONE at evolutiva-pensanta-com/venus-solo/ (worktree ruled out - refuses 2nd checkout of main), origin=same repo so push triggers same Vercel; .env.local copied+gitignored, node_modules pnpm-hardlinked, .solo-verdicts gitignored; LLMMSG_AGENT from .llmmsg-env overlay so gate solo-scope still fires cwd-independent; solo LAUNCHED from agents/solo-venus/ but cd's to clone for all edit+push, git -C pull --rebase origin main before each WI; GitHub is the sync point. Kills the git-add-all cross-agent WIP fold hazard (single-head, no partner-freeze). ALSO reconsider venus memory-lint-in-gate: pluto's gate never lints memory (only git diff HEAD of app tree); may supersede/pair-with VENUS-116