Compose explicitly installed runtime services

Compose explicitly installed runtime services复制锚点链接

Host creation is asynchronous and prepares an explicit service list before Plugin admission. Service plans validate identity, properties, reserved Core members and dependencies before creating resources; preparation and shutdown preserve dependency order and clean partially prepared resources on failure. Core provides its own host composition entry, optional service type catalogs and synchronous token-based Context.require(), with stable missing-capability and access errors.

Persistence and Vault move to dedicated @pluxel/services entries. Encrypted Vault explicitly requires Persistence and flushes pending writes during Host cleanup; read-only deployment bindings need neither. Import Persistence helpers and Vault types from their service entries. The Runtime package is removed; servicesPreset() supplies the official default service composition.

Preserve identity through development and generated metadata复制锚点链接

Host development passes service declarations through the shared Host path. Service declaration changes replace the Host; failed asynchronous preparation creates a fresh compensation Host from the previous successful declaration. Native ESM and evaluated plugins share official service identity. Plugin/config metadata defaults to the Core toolchain, without requiring Runtime in independent service applications.

Unify plugin authoring and service ownership复制锚点链接

Plugin examples and official packages import the Core authoring model directly. Commands, Node modules and Workers are explicitly installed services; their tokens, declarations and types live at the service entries. Worker installations declare their Node module dependency. servicesPreset() combines these installations without introducing a second application or lifecycle model. The default Core author entry no longer forwards raw Context host construction helpers; service authors use @pluxel/core/host.

Host exposes generic configuration get/validate/patch/reset through its existing coordinator, preserving Core validation, storage confirmation and generation notification. Management delegates to these operations and retains browser report projection. Vault operations participate in owner and root admission: stop drains accepted work, rejects cached handles and flushes after pending storage IO.

Use standard tsdown application plugins复制锚点链接

Applications configure entry and output through tsdown and install pluxel() from @pluxel/rolldown in the ordinary plugins list. This replaces the application preset in the build subpath, retaining the same freezer, artifact assembly and deployment validation.

Separate business HTTP from management复制锚点链接

Install elysia() from @pluxel/services/elysia and use ctx.require(ElysiaApp) for the native generation-owned Elysia application. Independent Hosts expose business requests through createElysiaHandler(host), without management, Workbench or a listener. Official presets use the same installation and publication stages. Host services may bind fixed Core lifecycle stages before Plugin admission; no dynamic registration or secondary graph commit is introduced.

Persist and manage Host state directly复制锚点链接

Host owns configRecords and state.initial, optional borrowed document storage, read-only handling and flush failure reporting. Status snapshots and retained lifecycle diagnostics, startup intent, provider selection and fork operations share the same Host coordinator in standalone and default applications. Service removeNodeMetadata hooks run before durable fork removal; failure retains the stopped fork so cleanup can be retried.

Database moves from @pluxel/runtime/database to @pluxel/services/database. Install an explicit backend from @pluxel/services/database/pglite or /postgres. Driver dependencies are optional and only the chosen backend is imported. Missing installation reports the standard capability error. Database acquisition and cached handle operations participate in root and owner drain; closing waits for accepted transactions.

Share management, Workbench and development tooling复制锚点链接

The authenticated management endpoint/client, Workbench publication/browser code and logging backend move to independently selected packages. Vault administration is an ordinary explicitly installed Plugin. Host-dev owns the existing local console executor and typed script surface at @pluxel/host-dev/console; its Vite Host plugin accepts devConsole: true. Node and Workbench artifacts use ordinary Vite plugins and the shared Host candidate boundary. Canceled management work is rejected before queued execution starts; an admitted operation retains its existing completion and persistence semantics.

Share startup declarations and transport ownership复制锚点链接

Application startup and service test-host factories await the same createHost service preparation path. Official plugins import validation and RPC contracts from their owning packages, removing the Runtime peer where no runtime implementation is used. Services owns the Node HTTP/WebSocket carrier; Host-dev owns the development console, and queued management mutations honor cancellation before admission.

The root @pluxel/services entry contains only standardServices() and its base service types. Import the official servicesPreset() from @pluxel/services/preset; its Management and Logging configuration types remain owned by those packages and do not leak into independent base-service consumers. Generated hosts and current examples use the explicit preset entry.