fix: prevent duplicate statusline when user/project settings are the same file

When the CLI is launched from ~ (home directory), user-level and
project-level settings.json resolve to the same file. This caused
resolveSettingsSources to merge the same content twice, resulting
in duplicate statusline segments and React non-unique key warnings.

Fix: detect same-file early in resolveCurrentSettings and pass null
for project settings when paths are identical.

Author: dengmik-commits

packages/core/src/settings.ts

@@ -654,9 +654,12 @@ export function writeModelConfigSelection(
 }
 
 export function resolveCurrentSettings(projectRoot: string = process.cwd()): ResolvedDeepcodingSettings {
+  const userPath = path.resolve(getUserSettingsPath());
+  const projectPath = path.resolve(getProjectSettingsPath(projectRoot));
+  const sameFile = userPath === projectPath;
   return resolveSettingsSources(
     readSettings(),
-    readProjectSettings(projectRoot),
+    sameFile ? null : readProjectSettings(projectRoot),
     {
       model: DEFAULT_MODEL,
       baseURL: DEFAULT_BASE_URL,