docs(release): record LibModule dev asset smoke

Author: ImperaZim

CHANGELOG.md

@@ -21,6 +21,11 @@
   `docs/repository-presence.md`.
 - Added OP-68G release asset documentation through `docs/release-assets.md`,
   including the dev asset names, local validation checklist and publish gate.
+- Published and validated the OP-68G `v1.0.0-dev` prerelease assets. The
+  remote release contains the `.phar`, `.easylib.zip`, `package.yml` and
+  `checksums.txt` assets, and EasyLibrary's package manager smoke confirmed
+  `LibModule` active as `source=package-backed-virtual` with
+  `elprobe run libmodule functional=yes`.
 - Added release builders for `.phar` and `.easylib.zip` artifacts.
 - Added module-focused documentation for scaffold status, examples and the
   extraction boundary.

docs/release-assets.md

@@ -47,9 +47,11 @@ php .github/scripts/build-easylib-package.php
 Generated files are written to `dist/`. The directory is local-only and should
 not be committed.
 
-## OP-68G Local Validation
+## OP-68G Validation
 
-The current OP-68G local asset smoke validates:
+OP-68G validates both the local asset shape and the published GitHub release.
+
+Local asset checks:
 
 - the PHAR opens and contains the plugin manifest plus module runtime/command
   classes;
@@ -61,27 +63,36 @@ The current OP-68G local asset smoke validates:
 - a temp extracted install directory passes
   `PackageSafetyGate::evaluateState()` with the official catalog source.
 
-This is intentionally a pre-publish validation. A GitHub release must not be
-created from a stale commit. Publish the dev release only after the current
-LibModule and EasyLibrary catalog changes are committed and pushed.
-
-## Publish Gate
+Remote release checks:
 
-Before creating `v1.0.0-dev`:
+```text
+Release: https://github.com/ImperaZim/LibModule/releases/tag/v1.0.0-dev
+Assets: LibModule-1.0.0-dev.phar, LibModule-1.0.0-dev.easylib.zip, package.yml, checksums.txt
+Checksums: matched after download
+Release workflows: passed
+```
 
-1. Commit the current LibModule repository state.
-2. Commit the EasyLibrary catalog/changelog changes that recognize the package
-   metadata.
-3. Push both repositories to `development`.
-4. Create or dispatch the release workflow for `v1.0.0-dev`.
-5. Confirm the published release contains all four assets.
-6. Run a PMMP package-manager smoke using:
+PMMP smoke checks:
 
 ```text
 /easylibrary packages install libmodule development confirm
+restart
+/easylibrary packages status libmodule
 /easylibrary packages doctor
 elprobe libmodule
 elprobe run libmodule
+/easylibrary doctor
+```
+
+Confirmed result:
+
+```text
+Packages: 17 / installed: 17 / active: 17
+libmodule / LibModule v1.0.0-dev [active] type: runtime
+source=package-backed-virtual
+elprobe run libmodule functional=yes
+EasyLibrary doctor Problems: 0
+Smoke log: codex-smoke-op68g-libmodule-postfix-20260706-102748.log
 ```
 
 If the server has a standalone `LibModule` artifact, remove it before the