maka-plugin-core

简体中文

Defines package declarations, contracts, compositions and the shared plugin lifecycle. plan checks selected entries and bindings; runtime manages registrations and retirement. Host and UI use this same kernel with different execution backends.

The kernel has no Agent policy or native layout vocabulary. A binding selects an export that satisfies an import; the receiving Host still checks permission when a call arrives.

Composition expansion, forwarding and dependency validation use iterative traversal with exact cycle checks. Repeated package templates remain valid when finite overrides terminate expansion; binding cardinality follows the declared import contract. Instance identities retain every nonzero source UUID.

Source · Cargo manifest