Lazurio Folder project offers "Initialize Git", which puts .git into the Folder root and blocks every Machines apply #47

What happens

On a hosted Remote Environment, T3 Code's project for the Lazurio Folder (the Environment's Folder root, where every thread starts per decision 0189) shows Initialize Git in the Git actions control (GitActionsControl → vcs.init), because the Folder root is deliberately not a Git repository.

One click runs git init in the Folder root. T3 then stores its checkpoints there as refs/t3/checkpoints/<thread>/turn/<n>.

From that moment:

• the Folder boundary refuses the Environment: Platform requireFolderBoundary returns foreign-entry, and the Machines readback check lazurio-folder fails;
• the next Machines apply fails at that Environment and retains its lock;
• every later rollout of that Environment stays blocked until someone moves .git out of the Folder by hand.

Observed 2026-10-09: a Team Remote Environment, .git created by the button about eight hours before a planned apply, with no commits, no remote and nine checkpoint refs of one thread.

Proposal

Do not offer Initialize Git for the Lazurio Folder project, i.e. the project whose root is the Environment's Folder. Show a short line that the Folder is not a repository and that checkpoints work inside a module repository or a worktree.

This is option 2 of Lazurio/LazurioPlatform#256: remove the cause instead of tolerating .git in the Folder root. Other projects keep the button.

Acceptance

• In the Lazurio Folder project the control offers no git init.
• A test covers the Folder root project and a normal non-Git project.