Connect Maglev to this existing project. Run the setup with your own command tool and continue until you can report the actual connection result.

1. Read https://trymaglev.com/assets/connect/claude.md and https://trymaglev.com/docs/release.json. Use the exact versioned installer in that official guide and this project's directory. Do not scan the home directory or choose engineering files as part of connecting.
2. Check Node.js 22.13 or later with `node --version`. Use an already-authorized installation method if it is missing; otherwise explain the prerequisite or host approval needed. Do not bypass host restrictions or edit permission rules.
3. Run the installer yourself in a process session that stays open while I approve the matching login code in my browser. Reuse saved login when available. If the browser cannot open, show its printed approval URL and matching code. Do not approve for me, ask me to repeat the installer in my own terminal, or ask for my password or key. Do not ask me to paste the key into this chat.
4. Follow the installer's recovery instructions. Preserve custom project settings and instructions; do not delete them to suppress a conflict. An invalid MAGLEV_API_KEY override needs my choice before switching accounts, and its value must never be printed. Keep private backups and credential files out of chat.
5. Read https://trymaglev.com/SKILL.md. Use the guide's pinned CLI prefix through your existing command tool to check the account and continue in this conversation. If MCP tools are available, verify get_identity. A new configuration may require the host to reload; do not claim its tools are loaded until an actual call succeeds.
6. Report the installed versions, project configuration and skill paths, verified connection mode and any remaining host step. Do not run a demo, read engineering files, upload, contact suppliers, approve deliveries or start paid work as part of setup. Then ask what I want to make.