Detailed validation

Build validation

• Built packages/preload with pnpm build.
  • Result: passed.
  • Vite emitted the existing runtime asset warning for /lol-game-data/assets/v1/profile-icons/4216.jpg, but the preload bundle built successfully.
• Built Windows Release x64 native core with MSBuild:
  • core/core.vcxproj
  • Result: passed with 0 warnings and 0 errors.

GitHub Actions validation

The first test build failed during artifact staging because app-hub now emits the native core at:

core/bin/core.dll

but the workflow tried to copy:

bin/core.dll

This PR fixes that staging path.

Local runtime setup

Installed the rebuilt app-hub core.dll into the old installed loader for runtime testing, per Nomi's suggestion.

The app-hub core uses the new machine-wide data root:

C:\ProgramData\.pengu

Plugins were copied/tested from:

C:\ProgramData\.pengu\plugins

Elaina theme live validation

Tested live in LCUX through Chrome DevTools Protocol against Pengu's debug port.

Confirmed:

• elaina-theme\index.js loads.
• Background-Customizer\index.js loads.
• Pengu.plugins is populated from C:\ProgramData\.pengu\plugins.
• ElainaData exists.
• ElainaData storage mode is fs.
• PluginFS helpers are available:
  • read
  • write
  • ls
  • stat
• ElainaData.json exists.
• marker writes persisted to disk.
• start-time matched in memory and file.
• No ElainaData.get(...) called before ElainaData.init() pre-init warning was observed.

Known unrelated console item still present from Elaina media handling:

DOMException: Failed to load because no supported source was found.

Async/coalesced DataStore validation

Tested live against the app-hub datastore path:

C:\ProgramData\.pengu\datastore

The CDP test performed 250 rapid DataStore.set/remove cycles twice.

Confirmed both times:

• DataStore.set() kept returning synchronous true.
• DataStore.remove() kept returning synchronous true.
• in-memory final value was the newest write, index: 249.
• after async flush, decoded datastore file on disk also had index: 249.
• removed keys were absent on disk.
• delayed repeat did not show stale queued saves rolling the file back.

Plugin load timeout validation

The app-hub preload timeout warning previously logged after 15 seconds even when plugins loaded successfully, because the timeout was never cancelled after allLoaded won the Promise.race.

Added cancellation for that timer.

Validated with a 20-second CDP watch:

• Background Customizer loaded.
• Elaina loaded.
• Pengu.plugins stayed populated.
• document.readyState was complete.
• timeoutWarningsSeen: 0.

Extra PluginFS lab plugins

Created local folder plugins under C:\ProgramData\.pengu\plugins to exercise PluginFS and bus behavior in more detail:

pluginfs-lab
plugin-bus-listener
@pengu-lab/scoped-plugin

Validated live:

• all lab plugins loaded
• top-level folder plugin received context.fs
• namespaced folder plugin received context.fs
• context.meta.name was correct for scoped plugin: @pengu-lab/scoped-plugin
• context.bus existed
• fs.mkdir worked
• fs.write worked
• fs.write(..., { append: true }) worked
• fs.read matched written content
• fs.stat returned expected file metadata
• fs.ls returned expected entries
• traversal read was denied
• absolute path read was denied
• Windows reserved filename write was denied
• scoped plugin wrote/read Unicode JSON successfully
• bus listener received pluginfs-lab:ready
• lab plugin received listener ack
• DataStore burst write final value was newest index, 99

PluginFS lab log showed:

{
  "traversalDenied": true,
  "absoluteDenied": true,
  "reservedWriteDenied": true
}

Scoped plugin log wrote Unicode successfully:

{
  "plugin": "@pengu-lab/scoped-plugin",
  "unicode": "scoped ✓"
}

macOS note

This app-hub workflow currently only has a Windows job. The old main workflow had a Windows/macOS matrix, but feat/app-hub has been rewritten to build-windows only. macOS app-hub support/build validation is therefore not covered by this PR's current workflow.

Merge note: this has been validated locally on Windows with live LCUX testing, but we should still wait for at least one additional tester to try this branch/build before merging.