bug: config file doesn't exist after creation in some scenarios

[rkristelijn]

Bug Report

Description

User reports that even after writing the config file, the file doesn't exist in some scenarios.

Investigation Needed

• Test different operating systems (macOS, Linux, Windows)
• Test different Node.js versions
• Test different file system permissions
• Test with different home directory configurations
• Check if there are race conditions in file writing
• Verify path resolution works correctly in all environments

Current Status

✅ Working scenarios tested:

• Interactive mode on macOS with Node.js 22
• CI mode on macOS with Node.js 22
• File creation and reading works correctly
• Path resolution works correctly

Reproduction Steps

Need more details from user about:

1. Operating system and version
2. Node.js version
3. Exact command used
4. Any error messages
5. File system permissions
6. Home directory setup

Debugging Commands

# Check if config exists
node -e "import { configExists } from './src/config.mjs'; console.log('Config exists:', configExists());"\n\n# Check file permissions
ls -la ~/.lcodeconfig\n\n# Check home directory\necho $HOME\n\n# Test config creation\nnode index.mjs --init\n\n# Verify file exists after creation\nls -la ~/.lcodeconfig && cat ~/.lcodeconfig\n```