yoi/crates/client
2026-06-26 00:25:03 +09:00
..
src fix: align worker rename followups 2026-06-26 00:25:03 +09:00
Cargo.toml feat: add ticket role pod launcher 2026-06-06 04:18:36 +09:00
README.md refactor: rename pod crate to worker 2026-06-26 00:05:57 +09:00

client

Role

client contains reusable socket-client and runtime-command mechanics for talking to Pods from CLI/TUI code.

Boundaries

Owns:

  • one-shot Worker socket client behavior
  • request/reply delivery mechanics
  • runtime command construction below the product façade
  • shared attach/status probing helpers used by higher layers

Does not own:

  • product command names (yoi)
  • Worker state authority (worker, pod-store, session-store)
  • UI rendering (tui)
  • Engine turn semantics (llm-engine)

Design notes

The client boundary lets tui and yoi share Worker communication without making library crates depend on the product binary. Socket clients should drain connect-time snapshot/alert traffic before sending a method or deciding status.

See also