igneum-labs e89a94570f Relay agent: the wait on a task is its own process with a cap, never -Wait (PC 2, 8 October 2026, 21:28 UK: a task that started Igneum Miner.exe held the agent for the app's whole life, because Start-Process -Wait waits for every descendant on the inherited console; the relay channel to PC 2 went silent for half an hour). Now WaitForExit(timeout_minutes, default 60) on the task's shell; a task past its cap is ended by its pid with a log line and exit 124, never by a name. Test known-failed first in relay/test/service.test.mjs ... Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-10-08 21:01:54 +00:00
..
auth.test.mjs	Relay: secrets compared in constant time (relay/lib/auth.mjs, unit test in CI), HSTS header, tools/relay.mjs prints /r/<token> in list and watch (round 4, X28 and X24 part)	2026-10-04 19:31:22 +00:00
clients.test.mjs	2.0.2: a manifest publish nudges every relay machine to check at once (the shipper's order, 8 October 2026: the engine's manifest check is hourly today, ten minutes from 2.0.2, and the mini took the 2.0.1 entry only when its api/update/check was called by hand). publish-manifest.sh --deploy ends by posting packaging/ota/update-check.ps1 as a relay run to every machine under ~/.config/igneum/relay-machines (--no-nudge skips it; an unreachable machine is one line, never a failure); the script asks the local engine through its own api/update/check with the token from app.url, waits 45 s and reads back what it staged (RESULT UPDATE-CHECK asked version=... manifest=... state=...); it installs, quits, pauses or resumes nothing (the engine's own path installs at its next safe moment and the MINING-ON relay run reads the apply). Also: publish-jobs.sh's edition read is safe under set -e (the pre-push publish-jobs check's sandboxed add had failed on it). Test known-failed first in relay/test/clients.test.mjs	2026-10-08 19:33:15 +00:00
ember.test.mjs	Ember 2: the climb's tests (a synthetic memory-bound card converges in five probes; a refused probe backs the knob off for good; each goal picks its point; the £/day formula) and the fleet prior carrying the memory clock (climb records aggregate)	2026-10-06 15:50:34 +00:00
guard.test.mjs	Relay: the X23 tree on master (the signed and tagged run, lib/handler.mjs, guard, the per-machine secret), the start-app kind, the v3 agent as the per-user logon task IgneumRelayService with install-agent.ps1 and the hidden loop, the per-install hostname on registration, the signing tools/relay.mjs so no lane posts an unsigned run (the live relay refuses one since the 7 October 2026 deploy), tools/console.mjs and build-job.mjs on the header tier (X24), the playbooks on RELAY_DL_BASE (X26) and wsl-setup's sudo for apt-get and dpkg only (X28), the new playbooks (start-app, agent-install, pc2-crash-collect, boot-check, freeze-check), and the deploy record with the rollback line (docs/plans/relay-deploy-2026-10-07.md: production igneum-relay-iabqarnby, previous bgy767z40)	2026-10-07 14:47:59 +00:00
handler.test.mjs	Relay: the X23 tree on master (the signed and tagged run, lib/handler.mjs, guard, the per-machine secret), the start-app kind, the v3 agent as the per-user logon task IgneumRelayService with install-agent.ps1 and the hidden loop, the per-install hostname on registration, the signing tools/relay.mjs so no lane posts an unsigned run (the live relay refuses one since the 7 October 2026 deploy), tools/console.mjs and build-job.mjs on the header tier (X24), the playbooks on RELAY_DL_BASE (X26) and wsl-setup's sudo for apt-get and dpkg only (X28), the new playbooks (start-app, agent-install, pc2-crash-collect, boot-check, freeze-check), and the deploy record with the rollback line (docs/plans/relay-deploy-2026-10-07.md: production igneum-relay-iabqarnby, previous bgy767z40)	2026-10-07 14:47:59 +00:00
parse.test.mjs	Merge pack-loop (36b7811) into release-0.3.10: a pack's seed words are its program attempt's words, not the bare seed's (the epoch 34 outage)	2026-10-05 19:23:59 +00:00
service.test.mjs	Relay agent: the wait on a task is its own process with a cap, never -Wait (PC 2, 8 October 2026, 21:28 UK: a task that started Igneum Miner.exe held the agent for the app's whole life, because Start-Process -Wait waits for every descendant on the inherited console; the relay channel to PC 2 went silent for half an hour). Now WaitForExit(timeout_minutes, default 60) on the task's shell; a task past its cap is ended by its pid with a log line and exit 124, never by a name. Test known-failed first in relay/test/service.test.mjs	2026-10-08 21:01:54 +00:00
wake.test.mjs	Console: the job-channel ping (MF-11, 7 October 2026). Every 0.3.21 app names itself on its wake long-poll (machine, version, last job); /wake records one row per machine in relay_wake_seen before it holds; the Machines tab reads "job channel polled N ago, last job X" and, after 15 minutes without a poll, "job channel silent since <time>, last job X" in red, whatever the uploads say (PC 2 lost power at 10:46Z and nothing said so until a person read the intake). Tests in relay/test/wake.test.mjs.	2026-10-07 14:10:59 +00:00