Bugfix: Why were git operations still routing to AX42-U despite S260...

Documentation for Sessions

🐛 Bugfix: Why were git operations still routing to AX42-U despite S260...

Date: 2026-03-23
Time: 17:06:11 UTC
Session: gspace1-261.5
Agent: documentation
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

Why were git operations still routing to AX42-U despite S260 claiming they moved to AX102-U?

Task: S261: Fix git operations routing bug

🎯 Decision Made

Chosen:

Duplicate PLATFORM_GIT_SERVER_URL in .env.local. S260 added the correct entry at line 298 (ax102-01.gograb.space) but forgot to remove the old S246 entry at line 346 (sandbox.gograb.space). In dotenv, the LAST value wins within the file, so the old value was silently overriding the new one. Fixed by removing the duplicate at line 346 and leaving a comment pointing to the canonical entry.

Options Considered:

💭 Reasoning

This is a common dotenv pitfall: when adding a new value for an existing key, you MUST remove or comment out the old one. The file is 400+ lines, making duplicates easy to miss. Convention going forward: before adding any env var to .env.local, grep for existing definitions of the same key.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation