[immakermatty]

Status: ready for review

Why

When a Lazurio Environment refuses a project or a chat outside its Lazurio Folder (#58), a person reads the refusal. Those texts used internal words: "retarget", "provides the Lazurio project at its Folder root", "T3 worktree", "must not become a repository itself". The wording pass in the comments of #58 suggested plain replacements. They were not applied before the merge, and the Admin asked for them. They should ride the stable 0.0.45-lazurio.8, which ships #58.

What changes

Where	Before	After
managedFolder.ts, chat outside the Folder	This Environment starts agents in its Lazurio Folder; existing conversations remain available as history.	Agents in this Environment work in its Lazurio Folder; your earlier chats stay here as history.
managedFolder.ts, another project root	This Environment provides the Lazurio project at its Folder root.	In this Environment, the Lazurio project is the Lazurio Folder itself.
managedFolder.ts, rename	The managed project is named Lazurio.	This project keeps the name Lazurio.
managedFolder.ts, another folder	A managed Environment does not retarget projects. Use the Lazurio project.	In this Environment a project cannot point to another folder. Use the Lazurio project.
managedFolder.ts, removal	The Lazurio project is provided by this Environment and cannot be removed.	The Lazurio project belongs to this Environment and cannot be removed.
managedFolder.ts, worktree	Chats in this Environment start at the Lazurio Folder root, without a T3 worktree.	Chats in this Environment start in the Lazurio Folder, without a separate worktree.
ProviderCommandReactor.ts	This Environment starts agents in its Lazurio Folder. Start a new chat in the Lazurio project.	Agents in this Environment work in its Lazurio Folder. Start a new chat in the Lazurio project.
VcsProvisioningService.ts	The Lazurio Folder contains separate repositories and must not become a repository itself.	The Lazurio Folder holds separate repositories, so it cannot become a repository itself.

OrchestrationEngine.test.ts pinned "retarget"; it now pins "cannot point to another folder".

What does not change

Behaviour, the refusals' conditions, the CLI (t3 lazurio capabilities, t3 lazurio model) and every other text. The managed Folder's behaviour fix and seam cleanup are the separate phase A task.

Verification

• vp test run src/orchestration/Layers/OrchestrationEngine.test.ts src/orchestration/Layers/ProviderCommandReactor.test.ts src/vcs in apps/server: 316 passed (one failure before the test update, the pinned "retarget").
• vp fmt --check on the four files: clean, and the pre-commit formatter ran.
• Lint could not run locally: the filtered install lacks the lint plugin's dependency. CI runs it.

🤖 Generated with Claude Code

[agentrozjedemeai]

@immakermatty Approved for exact head bc0d1b3. The eight user-facing replacements match the requested wording on #58 and the PR before/after table. Diff inspection confirms only those eight string literals and the matching engine assertion changed; refusal conditions are untouched. Isolated checkout git diff --check and a nine-substitution/string-boundary check passed. Lazurio Fork CI run 38363167256 is successful on this head (format, server/web typecheck, managed Folder tests, builds and archive smoke). The reported 316 focused tests were not rerun locally: this temporary clone has no dependencies and the 8 GB host is under memory pressure. No unresolved review threads.