"Editor compiles the checked-out tree, not a git worktree branch"

A verification run (compile + test suite) against a worktree-only branch reports a green compile and passing tests, but the results are silently about main (or whatever branch is checked out in the editor's ProjectRoot). Branch-specific features are absent: new [ConVar] commands return Unknown Command, and branch-specific log markers never appear.

The editor compiles whatever is on disk at its ProjectRoot path. A git worktree creates a separate directory with its own checkout, but the editor has no awareness of worktrees. It reads the files at its configured root, which still has the original branch checked out. The compile and test results faithfully reflect that code, not the worktree branch.

1. Remove the worktree: git worktree remove <path> (confirm no other process or agent owns it first).
2. Check out the target branch in the editor's ProjectRoot: git checkout <branch>.
3. Re-verify. Hot reload picks up the checkout without an editor restart. New [ConVar] registrations appear within about a minute after the checkout completes (verified: the convar answered with its default value after a compile cycle of 0/0).

Evidence discipline: a suite pass without a log marker unique to the branch code is evidence of nothing. Before trusting any verification result, assert the presence of a branch-specific marker (a convar, a log line, a test label) that cannot exist on the base branch.

Once the branch is checked out directly in the ProjectRoot, the editor's file watcher detects the changed sources and triggers a recompile of the actual branch code. The worktree indirection is eliminated entirely.