GABRIEL — HP LAPTOP PARTICIPANT TEST

1. Install Node.js 24 or later from https://nodejs.org if needed.
2. Extract this ZIP. Open the gabriel-hp-live folder in PowerShell.
3. Run: node monitor.mjs
4. Open the http://127.0.0.1:... address printed in the terminal.
5. Keep the terminal open; Ctrl+C or Stop monitoring stops the session.

Counters refresh every five seconds. The connector stores up to 60 CPU,
memory, optional disk and Windows battery observations in memory only.
Failed collection retries automatically; stale readings are not shown as live.

To test a website lookup: enter your submitted signal UUID and the exact
hostname (example: gabrieleffect.com), then Start this scoped test. Leave the
optional correction checkbox OFF for the first observation. Check hostname
now performs a bounded lookup; later checks run once per minute.

OPTIONAL CORRECTION: If you tick the local consent checkbox, two failed Windows
system lookups plus a successful direct resolver query permit ONE Windows
DNS cache reset per connector run. It clears the ENTIRE local DNS cache,
including entries used by other applications. No cache snapshot is restored;
Windows rebuilds entries through subsequent lookups. This can help certain
lookup-path issues; it is not a general fix for slow applications or memory
pressure. A follow-up lookup records success or failure without proving cause.
The command may fail for permissions; Gabriel does not elevate privileges.

No application is closed, file read, DNS server changed, reboot performed,
or data uploaded. Physical voltage/temperature/vibration sensors and hosted
case upload are not connected. Other repairs are not implemented. The signal
UUID is a participant assertion, not authenticated access to a hosted case.
Keep the local dashboard private; do not expose it to a network. Stop blocks
new actions; an already issued cache command cannot restore prior entries.
