libchat/Cargo.toml


[workspace]
resolver = "3"

members = [
    "core/sqlite",
    "core/conversations",
    "core/crypto",
    "core/double-ratchets",
    "core/storage",
    "crates/client",
    "crates/client-ffi",
    "bin/chat-cli", "extensions/delivery",
]

# default-members = [ "core/*", "crates/*"]
default-members = [ "core/*"]

[workspace.dependencies]
blake2 = "0.10"
libchat = { path = "core/conversations" }
storage = { path = "core/storage" }

# Panicking across FFI boundaries is UB; abort is the correct strategy for a
# C FFI library.
[profile.release]
panic = "abort"
Add Project scaffolding (#1) 2025-12-22 09:40:46 -08:00
			`[workspace]`
			`resolver = "3"`
Implement double ratchet (#9) 2026-01-15 08:47:02 +08:00
Add Project scaffolding (#1) 2025-12-22 09:40:46 -08:00			`members = [`
feat: storage implementation and trait abstraction (#79) * feat: storage for conversations * fix: db types conversion * feat: run migrations from sql files * feat: persist identity * fix: revert double ratchet storage refactor * fix: clean * refactor: use result wrapper for ffi * refactor: uniform storage error into chat error * fix: zeroize identity record * fix: zeroize for secret keys in db operations * fix: transactional sql migration * fix: remove destroy_string * feat: db storage for inbox ephermeral keys * chore: remove in memory hashmap for ephemeral keys * feat: persist conversation store * feat: wire with the double ratchet storage * feat: remove conversation store * chore: fix conversation type not used * feat: mock chat store implementation * chore: sqlite module * feat: sqlite crate * chore: sqlite rename * chore: more refactor * extract ratchet store trait * chore: clear error conversion * chore: remove customized db conn * chore: fix clippy * chore: refactor to use generics and enum * chore: further clean for review comments 2026-04-03 08:25:26 +08:00			`"core/sqlite",`
Flatten Repos (#70) * move to “crates” style folder * Update workspace * clear crate names * Rename crate folders based on feedback * Use workspace dependencies instead of paths * Move updated files from core 2026-03-24 18:21:00 -07:00			`"core/conversations",`
			`"core/crypto",`
			`"core/double-ratchets",`
			`"core/storage",`
			`"crates/client",`
feat: implement Client crate and C FFI bindings (#73) Implement a `client` crate that wraps the `libchat` context behind a simple `ChatClient<D>` API. The delivery strategy is pluggable via a `DeliveryService` trait, with two implementations provided: - `InProcessDelivery` — shared `MessageBus` for single-process tests - `CDelivery` — C function-pointer callback for the FFI layer Add a `client-ffi` crate that exposes the client as a C API via `safer-ffi`. A `generate-headers` binary produces the companion C header. Include two runnable examples: - `examples/in-process` — Alice/Bob exchange using in-process delivery - `examples/c-ffi` — same exchange written entirely in C; smoketested under valgrind (to catch memory leaks) in CI iterates: #71 2026-04-08 23:15:48 +02:00			`"crates/client-ffi",`
Add GroupV1 2026-04-23 18:04:45 -07:00			`"bin/chat-cli", "extensions/delivery",`
Add Project scaffolding (#1) 2025-12-22 09:40:46 -08:00			`]`
PrivateV1 Convo Initialization via Inbox (#13) * Load orginal protofiles * Change package name * Add prost generation * Remove placeholders * Add generated files + imports * replace with chat-proto * Add XK0 * auto formatting * Initial implementation of PrivateV1 initialization * Add ConvoFactory trait * Hook up indentity placeholder * Remove RemoteInbox until it’s needed * Simplify Identity ownership * Clean up x3handshake * Move inbox encryption * Simplify inbox encryption * Cleanup warnings * Add todos * Update chat-proto crate * Publickey Handling * Reorg Inbox handshake * Update Inbox convoId * Remove file structure headers * Update ConvoID * Add Domain Separator trait * Remove Convo trait functions * Rename Context * Add SecretKey * Add workspace dependency * update KE name * Update comments for clarity * Remove Xk0 references * Bump chat_proto version and relock 2026-01-22 06:39:09 +07:00
Add GroupV1 2026-04-23 18:04:45 -07:00			`# default-members = [ "core/", "crates/"]`
			`default-members = [ "core/*"]`

PrivateV1 Convo Initialization via Inbox (#13) * Load orginal protofiles * Change package name * Add prost generation * Remove placeholders * Add generated files + imports * replace with chat-proto * Add XK0 * auto formatting * Initial implementation of PrivateV1 initialization * Add ConvoFactory trait * Hook up indentity placeholder * Remove RemoteInbox until it’s needed * Simplify Identity ownership * Clean up x3handshake * Move inbox encryption * Simplify inbox encryption * Cleanup warnings * Add todos * Update chat-proto crate * Publickey Handling * Reorg Inbox handshake * Update Inbox convoId * Remove file structure headers * Update ConvoID * Add Domain Separator trait * Remove Convo trait functions * Rename Context * Add SecretKey * Add workspace dependency * update KE name * Update comments for clarity * Remove Xk0 references * Bump chat_proto version and relock 2026-01-22 06:39:09 +07:00			`[workspace.dependencies]`
			`blake2 = "0.10"`
Flatten Repos (#70) * move to “crates” style folder * Update workspace * clear crate names * Rename crate folders based on feedback * Use workspace dependencies instead of paths * Move updated files from core 2026-03-24 18:21:00 -07:00			`libchat = { path = "core/conversations" }`
			`storage = { path = "core/storage" }`
fix(nim-bindings): add all-endpoints test and fix installation_name ABI (#66) Add nim-bindings/tests/test_all_endpoints.nim which imports bindings directly and calls every FFI proc, forcing the linker to include all symbols. This catches link-time and runtime issues that the pingpong example missed because unused symbols were optimised out. Running the new test revealed an ABI mismatch in installation_name: the Rust function used an explicit out-parameter but ReprCString has only flat fields, so Nim emits it as a C return value. CI now runs nimble test next to nimble pingpong. 2026-02-28 21:03:55 +01:00
			`# Panicking across FFI boundaries is UB; abort is the correct strategy for a`
			`# C FFI library.`
			`[profile.release]`
			`panic = "abort"`