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:
2026-03-07 18:46:43 +01:00
parent a710037dde
commit 2e081ead8e
179 changed files with 1645 additions and 1645 deletions

View File

@@ -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:

View File

@@ -3,7 +3,7 @@
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>quicproquo -- E2E Encrypted Messenger Demo</title>
<title>quicprochat -- E2E Encrypted Messenger Demo</title>
<style>
:root {
--bg: #0d1117;
@@ -201,7 +201,7 @@
</head>
<body>
<h1>quicproquo</h1>
<h1>quicprochat</h1>
<p class="subtitle">E2E Encrypted Messenger -- Browser Demo</p>
<!-- Connection Bar -->
@@ -273,7 +273,7 @@
<!-- Sign & Verify -->
<div style="margin-top:0.75rem;">
<h2 style="font-size:1rem;">Sign &amp; Verify</h2>
<input type="text" id="sign-msg" placeholder="Message to sign (Alice's key)" value="Hello, quicproquo!">
<input type="text" id="sign-msg" placeholder="Message to sign (Alice's key)" value="Hello, quicprochat!">
<div class="row">
<button class="crypto-btn" id="btn-sign" disabled>Sign (Alice)</button>
<button class="crypto-btn" id="btn-verify" disabled>Verify (Alice pubkey)</button>

View File

@@ -1,11 +1,11 @@
{
"name": "@quicproquo/client",
"name": "@quicprochat/client",
"version": "0.1.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@quicproquo/client",
"name": "@quicprochat/client",
"version": "0.1.0",
"devDependencies": {
"typescript": "^5.0.0"

View File

@@ -1,5 +1,5 @@
{
"name": "@quicproquo/client",
"name": "@quicprochat/client",
"version": "0.1.0",
"type": "module",
"main": "dist/index.js",

View File

@@ -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.

View File

@@ -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)

View File

@@ -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

View File

@@ -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;

View File

@@ -429,12 +429,12 @@ name = "qpq-wasm-crypto"
version = "0.1.0"
dependencies = [
"js-sys",
"quicproquo-core",
"quicprochat-core",
"wasm-bindgen",
]
[[package]]
name = "quicproquo-core"
name = "quicprochat-core"
version = "0.1.0"
dependencies = [
"argon2",