Fix remote name ordering in listRemoteNames to preserve longest-first for correct prefix disambiguation

Remove .toReversed() from listRemoteNames so it returns remotes in
longest-first order (as produced by parseRemoteNames). This ensures
parseUpstreamRefWithRemoteNames in resolveCurrentUpstream correctly
disambiguates prefix-overlapping remote names (e.g. 'my-org' vs
'my-org/upstream').

Author: cursoragent

apps/server/src/git/Layers/GitCore.ts

@@ -927,7 +927,7 @@ export const makeGitCore = Effect.fn("makeGitCore")(function* (options?: {
 
   const listRemoteNames = (cwd: string): Effect.Effect<ReadonlyArray<string>, GitCommandError> =>
     runGitStdout("GitCore.listRemoteNames", cwd, ["remote"]).pipe(
-      Effect.map((stdout) => parseRemoteNames(stdout).toReversed()),
+      Effect.map((stdout) => parseRemoteNames(stdout)),
     );
 
   const resolvePrimaryRemoteName = Effect.fn("resolvePrimaryRemoteName")(function* (cwd: string) {