Merge pull request #8 from Microck/docs/remove-fake-roadmap-info

Docs: remove non-Windows roadmap/plans

Author: Microck

docs/architecture/overview.mdx

@@ -453,14 +453,11 @@ Server handles:
 - Single-server architecture (no clustering)
 - 64MB recovery buffer (bounded memory)
 - Windows-only (ConPTY dependency)
-- No SSH agent forwarding
 
-### Planned Improvements
+### Roadmap
 
-- [ ] SSH config parsing (ProxyJump, LocalForward)
-- [ ] Server cleanup on pipe disconnect
-- [ ] Cross-platform terminal component (Linux/macOS)
-- [ ] AEAD encryption (authenticated encryption)
+There is no published roadmap. If you want to propose changes or new features, please open an issue:
+https://github.com/Microck/UndyingTerminal/issues
 
 ## Next Steps
 

docs/concepts/encryption.mdx

@@ -234,7 +234,7 @@ The terminal displays the passkey on startup. Save it for client connections.
 <Steps>
   <Step title="Generate new passkey">
     ```powershell
-    # Linux/macOS:
+    # OpenSSL (any OS):
     openssl rand -hex 16
     
     # Windows (PowerShell):

docs/config/server-config.mdx

@@ -131,7 +131,7 @@ $hexKey = -join ($bytes | ForEach-Object { $_.ToString("x2") })
 Write-Output "shared_key_hex=$hexKey"
 ```
 
-```bash Linux/MSYS2
+```bash OpenSSL (MSYS2/Git Bash)
 # Generate random 32-byte hex key
 openssl rand -hex 32
 ```

docs/installation.mdx

@@ -147,17 +147,12 @@ ConPTY support requires Windows 10 Build 17763 (October 2018 Update) or later.
     </Note>
   </Tab>
 
-  <Tab title="Package Manager (Future)">
+  <Tab title="Package Manager">
     ### Package Manager Installation
 
     <Warning>
-    Not yet available. Track progress on the [GitHub issues page](https://github.com/Microck/UndyingTerminal/issues).
+    Not available.
     </Warning>
-    
-    Future support planned for:
-    - Chocolatey: `choco install undying-terminal`
-    - Scoop: `scoop install undying-terminal`
-    - WinGet: `winget install UndyingTerminal`
   </Tab>
 </Tabs>
 

docs/introduction.mdx

@@ -130,11 +130,9 @@ Undying Terminal consists of three components:
 |----------|--------|-------|
 | Windows 10+ | Fully Supported | Primary target platform |
 | Windows Server 2019+ | Fully Supported | Service mode available |
-| Linux | Planned | Server/terminal components |
-| macOS | Planned | Future support |
 
 <Note>
-Currently Windows-only, but architecture is designed for cross-platform expansion.
+Undying Terminal is Windows-only.
 </Note>
 
 ## Performance Characteristics

docs/troubleshooting/common-issues.mdx

@@ -226,7 +226,7 @@ Test-NetConnection <HOST> -Port 2022
 
     **If large** (>10MB):
     - Wait for catchup to complete
-    - Future: Reduce keepalive frequency (recompile needed)
+    - To reduce keepalive frequency: requires a recompile
   </Step>
 
   <Step title="Check Server Load">

docs/troubleshooting/faq.mdx

@@ -48,24 +48,15 @@ Unlike traditional SSH, it implements:
 - Optional encryption (XSalsa20)
 
 **Known Limitations**:
--  Windows-only (Linux/macOS planned)
-
-See [Roadmap](#roadmap) for planned features.
+-  Windows-only
 
 ### Can I use this on Linux or macOS?
 
-**Not yet**. Currently Windows-only due to ConPTY dependency.
-
-**Planned**:
-- Linux: Server + terminal components (TBD)
-- macOS: Server + terminal components (TBD)
+No. Undying Terminal binaries are Windows executables.
 
-**Current Workaround**:
-- Run server on Windows
-- Connect from Linux/macOS using SSH bootstrap:
-  ```bash
-  ssh user@windows-server "cd /path && ./undying-terminal-terminal.exe"
-  ```
+If you need to use it from a non-Windows machine, the practical options are:
+- Use RDP/Remote Desktop into a Windows machine and run the client there
+- Run a Windows VM and run the client there
 
 ### What does "undying" mean?
 
@@ -485,7 +476,7 @@ constexpr auto kKeepaliveInterval = std::chrono::seconds(5);
 // Change to desired interval
 ```
 
-**Future**: Config file option planned.
+There is no config file option for this currently.
 
 ### How does the recovery buffer work?
 
@@ -504,34 +495,12 @@ Each connection maintains:
 
 ### Can I run the client on Linux?
 
-**Via SSH bootstrap**: Yes
-
-```bash
-# Linux client connecting to Windows server
-ssh user@windows-server "cd /path && ./undying-terminal-terminal.exe"
-```
-
-**Native Linux client**: Not yet (planned)
+No. The client is Windows-only.
 
 ## Roadmap
 
-### What's planned for future releases?
-
-**v1.0.1 (Released)**:
-- SSH config parsing (`~/.ssh/config` support)
-- SSH agent forwarding (`-A`/`--ssh-agent`)
-- Server cleanup on pipe disconnect
-- ProxyJump and LocalForward from config
-
-**v1.2 (Planned)**:
-- Linux server + terminal support
-- Compression (optional)
-- Configurable keepalive interval
-
-**v2.0 (Planned)**:
-- macOS support
-- AEAD encryption (authenticated)
-- Multi-server clustering
+There is no published roadmap. If you want to propose changes or new features, please open an issue:
+https://github.com/Microck/UndyingTerminal/issues
 
 **Community requests**: [GitHub Issues](https://github.com/Microck/UndyingTerminal/issues)
 
@@ -550,7 +519,7 @@ See [Contributing Guide](/development/contributing).
 
 ### Where can I get support?
 
-**Documentation**: https://undyingterminal.dev  
+**Documentation**: https://undyingterminal.mintlify.app/  
 **GitHub Issues**: https://github.com/Microck/UndyingTerminal/issues  
 
 **Before asking**: