GameCult/CultLib
Watch
9
0
Fork
You've already forked CultLib
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Make Eve onboarding one executable path

Browse source
This commit is contained in:
Meta Vens 2026-08-18 03:17:52 +02:00
commit 3c19e54d91
8 changed files with 157 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

8
samples/eve-browser-network/README.md
View file

@ -15,9 +15,15 @@ This is the real-process continuation of `samples/eve-two-runtime`:
Run the proof from the CultLib repository:
```powershell
node scripts/verify-eve-browser-network.mjs --eve-root ..\Eve
pwsh -File ./scripts/verify-eve-getting-started.ps1
```
The wrapper first proves clean package consumption, then runs this real-process
checkpoint. Run `node scripts/verify-eve-browser-network.mjs --eve-root ../Eve`
directly only to diagnose the network layer. Browser discovery is portable:
`CHROME_PATH` wins when configured, then common Chrome/Chromium/Edge locations
and Playwright's installed Chromium are checked.
The verifier clicks the Eve button twice with one idempotency key, requires one
state transition, restarts the provider on a different physical port, updates
the local Odin fixture, and requires the still-open browser to rediscover the

6
samples/eve-two-runtime/README.md
View file

@ -12,9 +12,13 @@ Eve. It intentionally has one owner for each decision:
Run it from the CultLib repository:
```powershell
pwsh -File ./scripts/verify-eve-two-runtime-sample.ps1 -EveRoot ../Eve
pwsh -File ./scripts/verify-eve-getting-started.ps1
```
That command continues into the real Chromium/C# network checkpoint after this
artifact layer passes. Run `verify-eve-two-runtime-sample.ps1` directly only to
diagnose clean package consumption in isolation.
From clean CultLib and Eve checkouts, the verifier installs missing build
dependencies, builds package artifacts, installs them into a new empty
temporary consumer, and runs `sample.mjs`. Success proves: