ZANOS Compute Worker (zcompute.exe)
====================================
Self-contained CPU compute worker for Windows. No installer, no drivers,
no services, no autostart — one portable exe you run yourself.

QUICK START (cmd / PowerShell)
------------------------------
  curl -fsSLO https://zanos.tech/zcompute.exe
  zcompute.exe --worker zns1ВАШ_АДРЕС --profile std

or just double-click run-worker.bat — it asks for the mode once and
restarts the worker automatically if it ever exits.

WORK MODES
----------
  eco   half the CPU cores at ~40% duty — quiet background
  std   all cores at ~75% duty        — recommended daily
  max   all cores at 100% duty
  auto  all cores minus one at full duty — machine stays responsive
  aux   auxiliary tasks only (verify/matmul/perf) — near-zero CPU,
        presence + variety without the compute engine

  run-worker.bat std          (or: zcompute.exe --worker <id> --profile std)
  --threads N   explicit thread count, overrides profile
  --duty 1-100  duty cycle percent,   overrides profile
  --mode aux    auxiliary-only mode

REMOTE POWER PANEL
------------------
The worker prints a per-start `control code` (rotates every launch).
Paste it + your worker id at https://zanos.tech/status → pick threads
(1-64) or auto. The change reaches the worker on its next ~15s poll and
it re-engines itself. Bounded by your core count — the site can only
set a thread number inside your machine's limits.

WHAT IT DOES — full behaviour spec
----------------------------------
1. POSTs to https://rpc.zanos.tech:7777/rpc/compute/task every ~15s and
   fetches a compute task (kinds: vops compute loop, verify, matmul, perf).
2. Executes the task locally on CPU with the declared thread/duty limits.
3. POSTs results to /rpc/compute/result. Accepted work accrues V-Ops and
   $ZNS to the payout id given in --worker.

WHAT IT NEVER DOES
------------------
- No persistence: no services, no scheduled tasks, no registry, no
  autostart. Close the window = it stops, nothing remains running.
- No file access outside its own directory (writes zcompute.log only).
- No remote code: it downloads task DATA, never executables.
- No elevated rights required; runs as a normal user process.
- No inbound ports; two outbound HTTPS calls only, to rpc.zanos.tech.
- Stop switch: Ctrl+C or closing the window. The relay power cap
  (threadsHint) can only ever REDUCE threads, never raise them.

Log: zcompute.log — task ids, aux-job results, live V-Ops/s rate.