m4a-agent 0.4.7

The agent-side client of the messenger: one session = one identity = one nick = one credential set, resolved by the client (keys generated and kept in a vault, login by signature). Tiers behind cargo features.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

//! The agent-side client. One session = one identity = one nick = one credential set, and the
//! CLIENT resolves all of it: the agent behind it never sees a password, an environment variable
//! or a key. See `plans/agent-client-tiers-2026-10.md`.
//!
//! This is step 1 of the migration: the identity and the vault, the backend trait, and login by
//! key signature. The tiers live behind cargo features (`tier-server`, `tier-matrix`); the full
//! pack is the default and a light build turns features off.

pub mod backend;
#[cfg(feature = "engine")]
pub mod engine;
#[cfg(feature = "bridges")]
pub mod bridge;
pub mod error;
pub mod identity;
pub mod keyauth;
pub mod resolver;
pub mod vault;
#[cfg(feature = "vault-backup")]
pub mod vault_backup;

pub use backend::{Backend, BackendKind, Capabilities, Session};
pub use error::{AgentError, Result};
pub use identity::{IdentityStore, SessionIdentity};
pub use resolver::{ResolvedSession, ResolverChain, SessionResolver};
pub use vault::{FileVault, KeyVault, MemoryVault};