chore: rename quicproquo → quicprochat in docs, Docker, CI, and packaging

Rename all project references from quicproquo/qpq to quicprochat/qpc
across documentation, Docker configuration, CI workflows, packaging
scripts, operational configs, and build tooling.

- Docker: crate paths, binary names, user/group, data dirs, env vars
- CI: workflow crate references, binary names, artifact names
- Docs: all markdown files under docs/, SDK READMEs, book.toml
- Packaging: OpenWrt Makefile, init script, UCI config (file renames)
- Scripts: justfile, dev-shell, screenshot, cross-compile, ai_team
- Operations: Prometheus config, alert rules, Grafana dashboard
- Config: .env.example (QPQ_* → QPC_*), CODEOWNERS paths
- Top-level: README, CONTRIBUTING, ROADMAP, CLAUDE.md

sdks/typescript/README.md

@@ -1,13 +1,13 @@
-# @quicproquo/client
+# @quicprochat/client
 
-TypeScript SDK for [quicproquo](https://github.com/nicholasgasior/quicproquo) --
+TypeScript SDK for [quicprochat](https://github.com/nicholasgasior/quicprochat) --
 an E2E encrypted group messenger built on MLS (RFC 9420), hybrid post-quantum
 key exchange (X25519 + ML-KEM-768), and sealed sender envelopes.
 
 ## Features
 
 - **WASM-powered crypto** -- Ed25519 signatures, hybrid KEM, sealed sender,
-  message padding, safety numbers -- all compiled from the Rust `quicproquo-core`
+  message padding, safety numbers -- all compiled from the Rust `quicprochat-core`
   crate via `wasm-pack`.
 - **High-level client API** -- `QpqClient` wraps transport + crypto into a
   type-safe interface for resolving users, creating channels, and exchanging
@@ -20,7 +20,7 @@ key exchange (X25519 + ML-KEM-768), and sealed sender envelopes.
 ## Quick start
 
 ```typescript
-import { QpqClient } from "@quicproquo/client";
+import { QpqClient } from "@quicprochat/client";
 
 // Crypto-only (no server needed)
 const client = await QpqClient.offline();
@@ -37,7 +37,7 @@ console.log("Valid:", client.verify(alice.publicKey, msg, sig));
 
 ## Server connection
 
-The native qpq server speaks Cap'n Proto RPC over QUIC/TCP with Noise_XX.
+The native qpc server speaks Cap'n Proto RPC over QUIC/TCP with Noise_XX.
 Browsers cannot open raw TCP sockets, so a WebSocket bridge proxy is required
 for full server connectivity: