Game guide · source of truth
Ledger

M0-05B

Probe collectors and device probe runs

← Ledger

donestatus · M0
9✓ 2✗tests passed / failed
9.38Mtokens · 34 min
0evidence files

Evidence

From logs/evidence/M0-05B/. Click a thumbnail for the full image.

No evidence files in logs/evidence/M0-05B/.

Tests

pass EditMode compile + tests (CapabilityProbeTests) · 112.9 s · raw log$ node tools/unity-run.mjs editmode
pass data tests (device-probes incl. probe-contract) · 128.2 s · raw log$ pnpm data:test
fail probe.mjs usage without a target exits 2 · 0.7 s · raw log$ node tools/unity/probe.mjs
fail data tests · 201.0 s · raw log$ pnpm data:test
pass data tests · 138.2 s · raw log$ pnpm data:test
pass zoen-sim cargo tests + clippy · 78.2 s · raw log$ pnpm sim:test
pass Zoen.Core dotnet build + xunit · 102.2 s · raw log$ pnpm core:test
pass docs lint + index · 8.4 s · raw log$ pnpm docs:lint
pass wiki typecheck · 94.9 s · raw log$ pnpm --filter @zoen/wiki typecheck
pass wiki production build · 208.9 s · raw log$ pnpm wiki:build
pass wiki e2e (changed specs) · 15.1 s · raw log$ pnpm --filter @zoen/wiki exec playwright test --only-changed

Notes

2026-10-08 07:27 UTC · Split for context (150k meter). Done: Unity gatherer apps/client-unity/Assets/Zoen/Runtime/Diagnostics/CapabilityProbe.cs (SystemInfo/Screen facts, Android Build.SOC_MODEL API31 + PowerManager thermal status API29/headroom API30 via AndroidApplication.currentContext; logs ZOEN_PROBE {json} once AfterSceneLoad; never reads SystemInfo.deviceName), ZoenWebProbe in Plugins/WebGL/ZoenDevice.jslib (GLctx else probe canvas; WebGL/GLSL version, unmasked vendor/renderer when WEBGL_debug_renderer_info allowed, max texture/renderbuffer/samples, extensions, deviceMemory, cores, DPR, screen, UA; errors in 'error'), EditMode CapabilityProbeTests 3/3 (EditMode 65/65, contract via ProbeContract against reference-devices.json), tools/unity/probe.mjs (macos-app|mac-chrome|phone-chrome|android-apk|summary; host facts sysctl/sw_vers/system_profiler whitelisted keys/pmset, adb getprop whitelist/meminfo/thermalservice/battery/wm/display modes/Chrome version, userAgentData; no serials/UUIDs/adb serial; default --out logs/evidence/M0-05C, merged probe-summary.txt) + tools/unity/probe-contract.mjs (shared parser/contract check; data test 5/5 in device-probes.test.mjs). Mac Chrome probe runs headed by default (--headless optional: earlier smokes show headless also uses ANGLE Metal Apple M3). Test 03 (probe.mjs without target) is red only because the usage path exits 2 by design. verify --changed green on second run (first run read CONTINUE_HERE.md mid-edit at 8097 B). Phone NOT visible in adb devices at 14:54 and 15:10 (adb server was not running; started by my adb devices call). Remaining M0-05C: rebuild macOS (~14 min) then Web (~40 min), probe.mjs macos-app, mac-chrome, phone-chrome (needs phone), record ownerTestDevices[].probes (measured, dated, evidence path, validatesLowReference false) + data test cross-checking probe-<target>.json. M0-05D: Android rebuild + probe.mjs android-apk + record.