[Bug] T3 Connect: Relay environment endpoint unavailable on CachyOS x86_64

Summary

T3 Code on CachyOS x86_64 fails to connect to remote environments with error:
'Failed to connect. Reconnecting... Reason: Relay environment endpoint is unavailable: endpoint_request_failed'

Trace ID: d24b28efla30909a7d1dbfd3444da762

Environment

• OS: CachyOS x86_64
• Tool: T3 Connect (remote app connection)
• Client: T3 Code mobile/desktop

Steps to Reproduce

1. Sign into T3 Connect on CachyOS x86_64
2. Try to connect to a remote environment
3. Error: 'Relay environment endpoint is unavailable: endpoint_request_failed'
4. Environment shows as discoverable but connection fails

Troubleshooting Already Attempted

• Signed out/in to T3 Connect via mobile app
• Cleared T3 Code IndexedDB cache
• Cleared T3 Code Local Storage cache
• Error persists after re-authentication

Additional Context

• User is on CachyOS (Arch-based Linux distribution)
• Issue appears related to T3 Connect relay state inconsistency
• Similar to issues reported in #6568 and #5712 on GitHub
• Environment may be linked to different cloud account state

Request

Investigate relay environment endpoint availability for CachyOS x86_64 platforms.
Consider platform-specific relay configuration or provide guidance on resolving inconsistent T3 Connect state after re-authentication.

--
This issue was filed from opencode session regarding T3 Connect relay endpoint failure on CachyOS.

No source file or test is named in the report. Start by reproducing the T3 Connect relay endpoint failure on CachyOS x86_64, then compare the behavior with issues #6568 and #5712 and inspect the reported authentication or relay-state context. Done means identifying the cause and documenting a verified fix or recovery path.