kcode-k1-chat-thread-ktools 0.1.3

Synchronous Ktool dispatch for one K1 chat thread
Documentation
1
2
3
4
5
6
7
8
9
10
11
# K1 chat-thread Ktools 0.1.3

`ChatThreadKtools` is the synchronous per-thread dispatcher for `CurrentTime`, the five Kmap Ktools, the three read-only Social Ktools, and optionally `SetLaunchNode`. `new` preserves an Actions-only path; `new_with_social` adds one configured `SocialKtools` facade; `new_with_social_and_set_launch_node` adds independent Social and `SetLaunchNodeKtool` owners.

`bind_authorization` installs one exact `AccessContext`, `ProfileId`, and `AccessPolicy` triple. Rebinding the same triple is idempotent; a different active triple fails before changing either owner. `clear_authorization` clears the active triple and Actions authorization while preserving Actions session state.

`launch` delegates CurrentTime and Kmap behavior unchanged to Chat Thread Actions. `ListContacts`, `ListGroups`, and `GetGroup` require configured Social Ktools and active authorization. Missing Social composition returns `social Ktools are unavailable`; missing authorization returns `social authorization is not active`. Exact `SetLaunchNode` delegates to its configured owner and active authorization.

`ChatThreadKtoolExecutor` is the cloneable, mutex-serialized handle used when synchronous calls run outside the session actor. Its constructors preserve the same three compositions. `bind_authorization`, `clear_authorization`, `launch`, and `supports` lock only this dispatcher; callers do not need to retain actor or persistence locks while a call executes. `supports` reports only calls the concrete composition can execute.

KtoolDocs, SendMessage, WebSearch, registry gating, persistence, provider work, HTTP, retry, group authority, and migration are outside this package.