Package dev.shamoo.runtime.core
package dev.shamoo.runtime.core
-
ClassDescriptionResource that can notify an ownership registry after it closes naturally.Generated binding identity required before a platform operation can be invoked.Version-filtering event bus whose subscriptions follow plugin generation ownership.Core-owned service directory with generation-aware providers and stable consumer proxies.Stable reason that prevents a plugin from loading.Immutable dependency graph and deterministic lifecycle ordering.Consumer behavior when a service provider generation is transactionally replaced.A synchronous host suitable for command-line tools and deterministic tests.Optional engine-neutral contract for transferring opaque state between runtime generations.Raised when a caller requests a transition outside the central transition table.Indicates that a valid manifest cannot run in the current runtime environment.Immutable discovered plugin installation; it does not imply activation.Atomic invocation admission and drain accounting for one plugin.Idempotent active-invocation lease.Runtime-facing invocation admission boundary.Raised when a plugin is no longer admitting invocations.Immutable invocation admission counters.Structured base error emitted by lifecycle coordination.Measured lifecycle coordination counters.Structured timeout from a lifecycle hook or invocation drain.Immutable audit entry for an atomic lifecycle state transition.Runtime-core admission boundary for parsing and compatibility validation.Optional correlated request transport over an allowlisted raw plugin-message sender.Explicit distinction between an absent carrier/proxy, a canonical response frame, and a local transport error.Immutable allowlist of narrow platform operations; platform service objects are never exposed.A platform operation result with an optional generation-owned resource.Structured lifecycle rejection caused by dependency state or compatibility.Resolves semantic dependencies and ordering hints with stable lexical tie-breaking.Recursively observes plugin directories and emits one candidate path after a quiet window.Structured disable hook failure.Secure, deterministic discovery of directory-based plugin installations.Structured rejection produced while inventorying the runtime plugins directory.Complete discovery outcome; one bad installation does not hide valid siblings.Structured drain hook or active-invocation wait failure.Structured enable hook failure.Engine-neutral subscriber for a compatible versioned event payload.Generation-scoped cross-plugin versioned event surface.Validated stable identity of a script plugin.One immutable administrative view assembled under coordinator serialization.Serializes plugin lifecycle operations and enforces dependency, drain, timeout, and cleanup rules.Structured hook failure with a phase-specific code.Thread-safe state machine backed by the single authoritative transition table.Stable administrative states for one installed plugin candidate.Structured load hook failure.Structured rejection of operations on a quarantined plugin.Structured ready hook failure.Engine-neutral lifecycle hooks for one plugin runtime.Core-owned services supplied to a runtime implementation.Composition-root interface used to create an engine runtime for an admitted candidate.Engine-neutral implementation of one explicitly versioned plugin service.Stable consumer handle that resolves its provider generation for every invocation.Generation-scoped cross-plugin service registration and lookup surface.Prepares an installation candidate without replacing the currently installed candidate.Structured unload hook failure.Explicit policy for moving repeated failures or resource leaks into quarantine.Thread-safe first/last registration ownership for shared native resources.Categories exposed in plugin resource ownership reports.Structured unload failure caused by plugin-owned resources.Result of a reverse-order resource cleanup pass.Immutable view of a live plugin-owned resource.Thread-safe typed ownership registry that closes resources in reverse registration order.Platform services available to a runtime without exposing server-specific types.Indicates that a runtime could not acquire its engine resources.Truly measured per-runtime counters.Canonical immutable runtime permissions derived from a manifest Node policy.Observable lifecycle state of a per-plugin runtime.Opaque allowlisted JS callback; platform adapters may pass only copied data values.A lifecycle-bound script engine.Correlated data-boundary failure for one cross-runtime service operation.Raised by a stable service proxy when no active compatible provider can admit the call.Deterministic registry of exact generated-to-original source positions.One-based source location.