onlyne-client 2.1.2

Onlyne client: role runtime, dispatch, intent, adapter socket
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

//! Tern backend: one block per onlyne session, one tab per role, one session
//! per cluster.
//!
//! Tern's tree is session → tab → block, and this backend maps one onlyne
//! cluster onto a Tern session, one role onto a tab of it, and one onlyne
//! session onto a block. The first spawn of a role launches its agent as the
//! role tab's first block; every later one splits beside a block of that tab.
//! A spawn creates only its own agent block — no shell is ever opened as a
//! place to split beside.
//!
//! Kept beside herdr's shape by operator decision. What differs is every host
//! operation: Tern takes a numeric block id rather than a `wF:p2` pane handle,
//! reports plain-text refusals with no JSON error code, and cannot rename a
//! block without renaming the tab that holds it — so this backend answers
//! `rename` unsupported rather than rename a role's whole tab.

mod cli;
mod policy;
mod resource;
mod session;

pub use session::TernBackend;

#[cfg(test)]
mod tests;