docs: point links at OpenIPC/vtesse instead of compot-dev/vtesse

CHANGELOG.md

@@ -1,7 +1,7 @@
 # Changelog
 
 The version lives in `include/vtesse/version.h`. Binaries are published only as the
-[`latest`](https://github.com/compot-dev/vtesse/releases/tag/latest) release, rebuilt
+[`latest`](https://github.com/OpenIPC/vtesse/releases/tag/latest) release, rebuilt
 from every push to `main`; this file is the change history.
 
 ## 1.12 — 2026-10-15

docs/architecture.md

@@ -50,7 +50,7 @@ the tunnel; there is no system network interface.
   big-endian MIPS.
 - **Small footprint:** `-Os`, strip; lwIP memory profiles (see below); optional
   modules `LWIP=0`, `SOCKS=0`, `UDP_RELAY=0`, `TAP=0`
-  ([#29](https://github.com/compot-dev/vtesse/issues/29), [usage](usage.md#building)).
+  ([#29](https://github.com/OpenIPC/vtesse/issues/29), [usage](usage.md#building)).
 - **Protocol-agnostic upper layers.** Everything above the transport talks to
   `tunnel_ops_t` only, so the stack, proxy and Android layers can later serve another
   tunnel protocol (e.g. [camex](https://github.com/openipc/camex)).
@@ -196,7 +196,7 @@ or its output buffer is full; frames from the tunnel are written non-blocking.
 
 ## Android
 
-Planned ([#13](https://github.com/compot-dev/vtesse/issues/13)): foreground service
+Planned ([#13](https://github.com/OpenIPC/vtesse/issues/13)): foreground service
 with a regular notification (not a VPN), no `VpnService`, no `BIND_VPN_SERVICE`.
 Android 14+ requires a `foregroundServiceType`; Doze and network changes are handled
 by reconnecting (`NetworkCallback`).

docs/protocol.md

@@ -55,7 +55,7 @@ in `<` `>`. Exactly 32 characters.
 
 The client cannot detect the variant in advance; the auth mode is a setting.
 VTesse implements XOR; Blowfish is planned
-([#16](https://github.com/compot-dev/vtesse/issues/16)).
+([#16](https://github.com/OpenIPC/vtesse/issues/16)).
 
 Reference vectors from the stock client are in
 [`bench/vectors/`](../bench/vectors/README.md).
@@ -152,7 +152,7 @@ address and port as the TCP socket and `connect()`s it to the client's TCP peer
 address plus the reported port; there is no `nat_hack`. Behind a NAT that does not
 preserve the source port (typical carrier-grade NAT) the client's datagrams are
 silently dropped. VTesse currently supports TCP only
-([#14](https://github.com/compot-dev/vtesse/issues/14)).
+([#14](https://github.com/OpenIPC/vtesse/issues/14)).
 
 ## Not provided by VTun
 

docs/security.md

@@ -17,7 +17,7 @@
   VTun's own encryption has no integrity protection anyway.
 - Use only over trusted networks or inside an external secure channel (TLS /
   stunnel, an operator VPN). A TLS wrapper for the TCP transport is planned
-  ([#15](https://github.com/compot-dev/vtesse/issues/15)).
+  ([#15](https://github.com/OpenIPC/vtesse/issues/15)).
 
 ## Sessions
 

docs/usage.md

@@ -59,7 +59,7 @@ Each target gives `vtesse-<target>` (lwIP + TAP) and `vtesse-tap-<target>` (TAP
 only); x86_64 also `vtund-3.0.2-x86_64`, the VTun server with our patches
 ([server/README.md](../server/README.md)). Use musl builds on devices: a static glibc binary cannot resolve host names
 without the NSS libraries of the same glibc. Prebuilt binaries are on the
-[releases page](https://github.com/compot-dev/vtesse/releases) (`latest` is rebuilt
+[releases page](https://github.com/OpenIPC/vtesse/releases) (`latest` is rebuilt
 from every push to `main`).
 
 ## vtesse-cli

server/README.md

@@ -20,7 +20,7 @@ challenge response), no LZO, no zlib. Requirements: a C compiler, `bison`, `flex
 ## Releases
 
 CI builds a static musl vtund for PCs and servers only (x86_64, `ci/build-musl.sh`)
-and attaches it to the [`latest`](https://github.com/compot-dev/vtesse/releases/tag/latest)
+and attaches it to the [`latest`](https://github.com/OpenIPC/vtesse/releases/tag/latest)
 release as `vtund-<VTun version>-x86_64`, e.g. `vtund-3.0.2-x86_64`. The name carries the
 original VTun version, not the VTesse version; the applied patches are listed below.
 The binary reports itself as upstream does (`VTun ver 3.X <build date>`),