fix(server): check out submodules in a new worktree - #7674

💭 Looking at the diff, the main change is in GitVcsDriverCore.ts adding submodule update logic, using Effect.catch since runGit's error channel is fully handled there, which fits the convention. I want to check the file's imports and surrounding context to confirm. Let me look at the changed region in context to see what surrounds it. The changes seem consistent with conventions overall. I want to verify that logging the full cause object doesn't violate the rule against copying raw command arguments or output into log payloads, so I need to check whether GitCommandError itself carries that sensitive data. This is a pre-existing legacy error type that the PR doesn't change, but the log annotation includes the whole error object whose detail might contain stderr output — that could be a new violation of the convention against copying command output into a parallel log payload. I want to check how other logWarning calls in this file handle causes to see if there's an established pattern to follow. This logging pattern matches existing conventions, and using Effect.catch here seems fine since the error channel is fully handled. The test file's use of finalizers and effect-based tests also looks consistent with conventions. Since this is a behavior change rather than a mechanical refactor, adding tests is justified. I should double-check the test imports to make sure they're pulling named exports correctly from "effect". Since there are no violations found, I'll keep the response as "All clear" while still satisfying the JSON schema requirement—using a plain title like "Effect Service Conventions: All clear" with summary "All clear".