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
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
/**
|
||||
* High-level quicproquo client.
|
||||
* High-level quicprochat client.
|
||||
*
|
||||
* Combines the WASM crypto layer with a WebSocket transport to provide
|
||||
* a type-safe API for interacting with a quicproquo server.
|
||||
* a type-safe API for interacting with a quicprochat server.
|
||||
*
|
||||
* The crypto helpers work standalone (no server connection required).
|
||||
* Server RPC methods require a WebSocket bridge proxy since the native
|
||||
@@ -30,7 +30,7 @@ export class QpqClient {
|
||||
}
|
||||
|
||||
/**
|
||||
* Connect to a quicproquo server via WebSocket bridge.
|
||||
* Connect to a quicprochat server via WebSocket bridge.
|
||||
*
|
||||
* NOTE: The server must expose a WebSocket-to-capnp bridge endpoint.
|
||||
* See the project documentation for bridge proxy setup.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
/**
|
||||
* @quicproquo/client -- TypeScript SDK for quicproquo E2E encrypted messenger.
|
||||
* @quicprochat/client -- TypeScript SDK for quicprochat E2E encrypted messenger.
|
||||
*
|
||||
* The SDK provides:
|
||||
* - WASM-powered crypto (Ed25519, hybrid X25519+ML-KEM-768, sealed sender)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
/**
|
||||
* Transport abstraction for communicating with a quicproquo server.
|
||||
* Transport abstraction for communicating with a quicprochat server.
|
||||
*
|
||||
* The native qpq server speaks Cap'n Proto RPC over QUIC/TCP + Noise_XX.
|
||||
* Browsers cannot open raw TCP sockets, so this SDK assumes a WebSocket
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
/** Options for connecting to a quicproquo server. */
|
||||
/** Options for connecting to a quicprochat server. */
|
||||
export interface ConnectOptions {
|
||||
/** WebSocket URL, e.g. ws://host:port or wss://host:port */
|
||||
addr: string;
|
||||
|
||||
Reference in New Issue
Block a user