docs(libmodule): finalize module ownership smoke

Author: ImperaZim

CHANGELOG.md

@@ -98,6 +98,10 @@
   commands extend `BaseModuleCommand`, services/capabilities are provided
   through `ModuleRuntime`, and EasyLibrary's legacy `ModuleManager` is no
   longer imported by the examples.
+- Added OP-68J smoke evidence for the final EasyLibrary module-core removal:
+  EasyLibrary without `LibModule` reports `provider=disabled`, package-backed
+  LibModule loads real fixtures with services/capabilities/reload/disable/enable
+  and standalone LibModule reports `Module provider switch: auto -> standalone`.
 - Validated OP-60 live loading against the local PMMP smoke server. LibModule
   loaded as `source=package-backed-virtual` from
   `plugin_data/EasyLibrary/packages/libmodule/1.0.0-dev` and as
@@ -106,7 +110,10 @@
 - Confirmed the portable runtime provider smoke with a real module fixture.
   `EasyModuleBasicExample` exercised `examples:hello` service/capability
   registration, resources, reload, disable-runtime, enable and refresh while
-  EasyLibrary kept the active PMMP host provider as `core`.
+  EasyLibrary still used the transitional host provider.
+- Confirmed the OP-68J fixture matrix with four example plugins:
+  `EasyModuleBasicExample`, `EasyModuleEconomyProviderExample`,
+  `EasyModuleFarmConsumerExample` and `EasyModuleDiagnosticsExample`.
 - Added focused tests for the copied status constants, health report statuses,
   summary schema, summary entry shape and doctor-compatible read model output.
 - Added focused tests proving the provider contract exposes metadata, summary
@@ -161,8 +168,13 @@
   repository pattern instead of leaving the remote metadata blank.
 - Reworked the example plugin docs as `LibModule` authoring references instead
   of EasyLibrary-backed module examples. The docs now explain that PMMP
-  discovery/resource registration remains a host-adapter responsibility until
-  OP-68I/OP-68J finish the migration.
+  discovery/resource registration remains a host-adapter responsibility while
+  `LibModule` owns module authoring and runtime behavior.
+- Fixed the example plugin source layout for PMMP's `src-namespace-prefix`
+  loader. Each example plugin main class now lives directly under
+  `examples/*/src/`, matching its configured namespace prefix.
+- Updated `ModuleRuntimeViewProvider` provider kinds to the current
+  `disabled`, `package-backed` and `standalone` vocabulary.
 - Updated `LibModuleInfo` and `package.yml` metadata to report
   contracts/read-model/provider-contract/provider-probe/dependency-resolver
   manifest/source, loader-boundary and registry/service readiness while still
@@ -189,64 +201,29 @@
   PHAR entries, package ZIP entries, checksums, EasyLibrary package contract and
   local Package Safety Gate install layout.
 
-### Not Yet Included
+### Still Not A Stable Promise
 
-- The production `imperazim\module` runtime is not extracted in this slice.
-- `ModuleManager`, lifecycle, commands, events and service registry are not
-  moved yet.
-- `ModuleRuntimeViewProvider` is read-only; it does not expose enable, disable,
-  reload, refresh or manager access.
-- `LibModuleRuntimeProvider` is a runtime wrapper only. It can expose a wrapped
-  `ModuleRuntime` read model, but it does not yet scan module folders, load PHP
-  files through PMMP plugin ownership or register PMMP commands/listeners/tasks
-  by itself. Pure PHP scanner/file-loader helpers exist, but host registration
-  remains an EasyLibrary adapter responsibility during OP-68.
-- `DependencyResolver` uses `ModuleDependencyNode`, not the full EasyLibrary
-  runtime `ModuleInterface`.
-- `ModuleManifest` models and validates arrays only. YAML/PMMP `Config` reading
-  and lifecycle ownership remain host-owned.
-- `ModuleManifestReader` is still a contract only. A concrete recursive
-  manifest path scanner exists, but the concrete YAML reader remains
-  host-owned.
-- `ModuleClassNameResolver` only calculates the expected class name. Fallback
-  PHP file loading and `ModuleInterface` validation now exist as separate
-  concrete helpers so hosts can choose when to load code.
-- `ModuleRegistry` stores portable dependency nodes, not live module instances
-  with PocketMine plugin owners.
-- `ModuleServiceRegistry` stores metadata descriptors, not live service
-  objects, and does not dispatch service events.
-- `ModuleCapabilityMap` models provider/preference decisions only; persistence
-  remains host-owned.
-- `ModuleLifecycleInventory` models resource ownership and cleanup order only.
-  It does not execute cleanup and does not store live PMMP objects, closures,
-  component handles or service objects.
-- `ModuleInterface` is a future host-neutral contract. EasyLibrary's current
-  production runtime still uses its core `ModuleManager`-centric contract until
-  the later runtime migration OPs are implemented.
-- The new `BaseModule` authoring core is host-neutral and the PMMP-facing
-  authoring helper classes exist in `LibModule`. Filesystem discovery, concrete
-  host registration and example migration are still pending before EasyLibrary
-  can delete its remaining module core.
-- Module commands are owned by `LibModule`, but command registration in a live
-  server is still host-owned. EasyLibrary uses a temporary adapter during
-  OP-68 while the old core runtime is removed.
-- `ModuleSettings` is a model only. Reading/writing YAML, migrating existing
-  EasyLibrary `modules.yml` and binding to PMMP data folders remain host adapter
-  responsibilities.
-- `ModuleRuntime` is portable only. It does not scan folders, read YAML, load
-  PHP files, validate `BaseModule` or register PMMP commands/listeners/tasks
+- No stable tag or stable release should be published from this dev baseline
+  alone.
+- PMMP-specific host policy remains explicit host integration work. LibModule
+  owns module API/runtime/commands/examples, while EasyLibrary currently owns
+  the official package-backed/standalone bridge that discovers plugin metadata,
+  reads host files and exposes diagnostics.
+- Copy-into-server examples are smoke-tested through EasyLibrary's bridge, but
+  final stable authoring docs still need the release-candidate pass.
+- Persistence of `ModuleSettings` remains host-owned: LibModule provides the
+  portable model, while EasyLibrary writes its current `modules.yml`.
+- `ModuleRuntime` remains intentionally portable. It can run modules and own
+  services/capabilities, but it does not pretend to replace PMMP plugin loading
   without a host adapter.
-- No stable tag or stable release should be published from this baseline alone.
 
 ### Why
 
-The repository needed the same foundation as the other official libs before the
-runtime can be moved safely. Splitting repository setup from runtime extraction
-keeps the next changes smaller, makes CI/release behavior visible early and
-avoids a half-migrated package that looks installable but cannot yet replace
-EasyLibrary's module core.
+The repository needed the same foundation as the other official libs before it
+could become the real module home. Splitting repository setup, release assets,
+API movement, command ownership, examples and smoke validation kept the
+migration inspectable instead of turning it into one huge opaque rewrite.
 
-OP-68F completes the public repository baseline before OP-68G starts publishing
-real dev release assets. That order keeps documentation, issue routing,
-security policy, quality checks and Discord notifications ready before the
-package manager is asked to download `LibModule` artifacts.
+OP-68F completed the public repository baseline before OP-68G published real
+dev release assets. OP-68H moved examples/docs here, and OP-68J proved the
+package-backed, standalone and no-LibModule runtime shapes in PMMP.

README.md

@@ -12,7 +12,8 @@ LibModule is the standalone home for the EasyLibrary module system.
 This repository is currently a **3.0-dev runtime extraction**: it provides the
 official standalone/package project shape, release automation, examples,
 documentation, portable read models, host-neutral runtime contracts, a portable
-runtime and package catalog metadata validated by the OP-60 smoke matrix.
+runtime, module commands, authoring examples and package catalog metadata
+validated by the OP-68J smoke matrix.
 
 ## Current Status
 
@@ -39,14 +40,15 @@ runtime and package catalog metadata validated by the OP-60 smoke matrix.
 | PMMP authoring helpers | Ready |
 | Module commands | Ready |
 | EasyLibrary runtime adapter | Smoke passed |
+| OP-68J package-backed/standalone/no-LibModule matrix | Smoke passed |
 | EasyLibrary package catalog entry | Smoke passed |
 | Stable release | Not published yet |
 
-The OP-60 smoke matrix passed for package-backed virtual loading, standalone
-loading and a real EasyLibrary module fixture. `LibModule` exposes the portable
-runtime, provider wrapper and catalog metadata that EasyLibrary needs to load it
-as a package-backed or standalone plugin while EasyLibrary keeps PMMP-specific
-host adapters in the core.
+The OP-68J smoke matrix passed for package-backed virtual loading, standalone
+loading, no-LibModule fallback and real module fixtures. `LibModule` now owns
+the public module API, portable runtime, provider wrapper, commands and
+examples; EasyLibrary keeps only the host bridge that discovers LibModule and
+reports the active provider.
 
 ## What This Library Will Own
 
@@ -116,17 +118,21 @@ The following pieces are already present:
   `ModuleRuntimeCommandAdapter`, `StructuralModuleCommandRuntimeProvider`,
   `ModuleCommandRunner`, `ModulesCommand` and `NativeModulesCommand`.
   `/easymodule`, `/emodule` and `/modules` are now command surfaces owned by
-  `LibModule`; EasyLibrary can temporarily adapt its legacy provider while
-  OP-68 finishes removing the old core runtime;
+  `LibModule`; EasyLibrary adapts the active LibModule provider through its
+  host bridge;
 - OP-60 live smoke evidence: `elprobe run libmodule` reports
   `functional=yes` for both package-backed virtual and standalone loading;
+- OP-68J live smoke evidence: EasyLibrary without LibModule reports
+  `provider=disabled`; package-backed LibModule loads real fixtures with
+  services/capabilities/reload/disable/enable; standalone LibModule reports
+  `Module provider switch: auto -> standalone`;
 - examples showing the `LibModule` authoring API with `BaseModule`,
   `ModuleContext`, `BaseModuleCommand`, services, capabilities and diagnostics;
 - docs describing the extraction boundary and current scaffold status.
 
-PMMP host adapters such as YAML reading through `pocketmine\utils\Config`,
-listener/task registration and copy-into-server example smoke are still being
-extracted from EasyLibrary 3.0-dev after OP-68H.
+PMMP host integration is intentionally split: LibModule owns the module API and
+runtime, while EasyLibrary owns the package/plugin bridge that discovers loaded
+plugins, reads host metadata and exposes diagnostics.
 
 ## Installation
 
@@ -149,10 +155,10 @@ use imperazim\module\BaseModule;
 use imperazim\module\ModuleContext;
 ```
 
-Do not publish a stable copy-into-server module authoring promise from this dev
-baseline alone. The portable `LibModule` runtime is active/catalog-ready and
-the public authoring classes/examples exist here, but EasyLibrary still owns
-part of the PMMP host adapter until the rest of OP-68 is complete.
+Do not treat this dev baseline as a stable 1.0 release yet. The portable
+`LibModule` runtime is active/catalog-ready and the public authoring
+classes/examples exist here, but the 3.0-dev line still needs the final release
+candidate pass before stable publication.
 
 ## Examples
 
@@ -255,6 +261,9 @@ notification workflow documentation and remote About/topics metadata.
 OP-68H moved the authoring examples and usage docs out of EasyLibrary's legacy
 core tree and into this repository. The examples now use `ModuleContext` and
 the `LibModule` public helpers instead of EasyLibrary's legacy `ModuleManager`.
+OP-68J validated those examples in PMMP through EasyLibrary's LibModule bridge:
+package-backed fixtures discovered modules, services, capabilities, resources,
+doctor/failure output, reload, disable and enable successfully.
 
 ## License
 

docs/examples.md

@@ -15,20 +15,22 @@ These examples are intentionally no longer written against EasyLibrary's legacy
 
 ## Current Host Status
 
-OP-68H moves the authoring examples and docs into `LibModule`. The examples are
-authoring references for the new API, not a stable copy-into-server promise yet.
+OP-68H moved the authoring examples and docs into `LibModule`. OP-68J then
+loaded these examples in a real PMMP package-backed smoke through EasyLibrary's
+LibModule bridge.
 
-During the rest of OP-68, EasyLibrary still owns part of the PMMP host adapter:
+EasyLibrary still owns the host bridge that discovers plugin metadata and
+connects loaded plugins to the active LibModule runtime:
 
 - plugin/module source discovery;
 - YAML reading through the PocketMine environment;
-- PMMP command, listener and task registration;
-- compatibility with old `ModuleManager`-centric modules.
+- PMMP command, listener and task registration policy;
+- package-backed or standalone provider selection.
 
 That means a host must explicitly wire these examples into a `ModuleRuntime`
 session and register any PMMP resources it wants to expose. The files under
-`examples/` show the module shape and the runtime contracts that the host will
-load once OP-68I removes the remaining EasyLibrary legacy runtime.
+`examples/` show the module shape and the runtime contracts that EasyLibrary's
+bridge can now load from package-backed LibModule.
 
 ## Included Examples
 

docs/provider-contract-slice.md

@@ -16,7 +16,7 @@ of EasyLibrary.
 
 - provider id;
 - provider name;
-- provider kind: `core`, `package-backed` or `standalone`;
+- provider kind: `disabled`, `package-backed` or `standalone`;
 - provider plugin name and version;
 - whether the provider is external to the host core;
 - `summary(): ModuleRuntimeSummary`;
@@ -33,8 +33,9 @@ of EasyLibrary.
 - PMMP command registration;
 - PMMP plugin ownership rules.
 
-Those operations still belong to EasyLibrary's current core provider until a
-later runtime extraction step proves the host adapter.
+Those operations are intentionally outside the read-only view. In the current
+3.0-dev line, LibModule owns the runtime implementation and EasyLibrary calls
+the richer host-facing adapter when command/lifecycle mutation is required.
 
 ## Why This Exists
 
@@ -45,16 +46,16 @@ is trusted to own command/lifecycle mutation.
 
 ## Current Status
 
-`LibModule` can define and test a read-only provider contract.
-
-EasyLibrary still owns the active provider implementation:
+`LibModule` defines and tests a read-only provider contract, and the later
+OP-68J smoke matrix validated it in all active provider modes:
 
 ```text
-CoreModuleRuntimeProvider -> ModuleRuntimeProvider -> ModuleRuntimeViewProvider
+disabled
+package-backed
+standalone
 ```
 
-`LibModule` is still not an official package catalog runtime.
-
-OP-44 builds on this contract with
-[`provider-probe-slice.md`](provider-probe-slice.md), adding a concrete
-`LibModuleRuntimeProvider` probe while keeping `runtime-ready=false`.
+OP-44 built on this contract with
+[`provider-probe-slice.md`](provider-probe-slice.md). OP-55/OP-58 then attached
+the portable runtime to `LibModuleRuntimeProvider`, and OP-68J validated
+package-backed and standalone ownership in PMMP.

docs/scaffold-status.md

@@ -2,10 +2,10 @@
 
 `LibModule` is intentionally in 3.0-dev extraction mode.
 
-The repository can now be validated, built and released as a dev artifact, but
-the PMMP host adapter is still being completed. The portable runtime, command
-surface, authoring API and examples now live here; EasyLibrary still owns the
-transitional host bridge until OP-68I/OP-68J prove parity.
+The repository can now be validated, built and released as a dev artifact. The
+portable runtime, command surface, authoring API and examples now live here;
+OP-68J proved parity through EasyLibrary's package-backed, standalone and
+no-LibModule smoke matrix.
 
 ## Ready
 
@@ -18,19 +18,18 @@ transitional host bridge until OP-68I/OP-68J prove parity.
 - Portable module constants and read models.
 - Read-only module provider contract.
 - Authoring examples updated for the `LibModule` public API.
+- Package-backed and standalone PMMP smoke through EasyLibrary.
+- Disabled-provider fallback when LibModule is not installed.
 
 ## Not Ready
 
-- Full PMMP host adapter ownership.
 - Copy-into-server example smoke as the only supported module workflow.
-- Official EasyLibrary package catalog entry.
 - Stable release.
-- Standalone production usage without EasyLibrary host integration.
+- Standalone production guidance outside EasyLibrary host integration.
 
 ## Guardrails
 
 - Keep `imperazim\module` owned by `LibModule`; EasyLibrary transitional code
-  must stay under `imperazim\library\module`.
-- Do not remove the remaining EasyLibrary host bridge until external provider
-  tests prove parity.
+  must stay outside that namespace.
+- Keep EasyLibrary host bridge code under `imperazim\library\libmodule`.
 - Do not publish a stable release from scaffold-only code.

…aryexamples/basic/BasicExamplePlugin.php …-basic-plugin/src/BasicExamplePlugin.phpexamples/01-basic-plugin/src/easylibraryexamples/basic/BasicExamplePlugin.php renamed to examples/01-basic-plugin/src/BasicExamplePlugin.php examples/01-basic-plugin/src/easylibraryexamples/basic/BasicExamplePlugin.php renamed to examples/01-basic-plugin/src/BasicExamplePlugin.php

@@ -16,7 +16,7 @@
  * @experimental 3.0-dev provider contract for the future LibModule split.
  */
 interface ModuleRuntimeViewProvider {
-    public const KIND_CORE = 'core';
+    public const KIND_DISABLED = 'disabled';
     public const KIND_PACKAGE_BACKED = 'package-backed';
     public const KIND_STANDALONE = 'standalone';