long-running-job-monitor
Monitors long-running test suites, builds, installations, and deployments, including a run the agent starts itself with no user request, using timestamped logs, heartbeats, terminal markers, out-of-band probes, and WORKING/STALLED/DONE/FAILED classification. Survives control-channel drops; a restart starts a new readiness epoch. USE FOR: run the test suite, full suite, Pester run, Invoke-Pester, build.ps1, test.ps1, verification run, regression run, live test, live proof, proof run, integration test, deployment, installation, long-running job, is it stuck, still running, watch deployment, remote job, SSH, WinRM, keep me posted, answering while a job runs. DO NOT USE FOR: diagnosing why a build or test failed (use sampler-build-debug), writing test code (use pester-patterns), AutomatedLab Proxmox provisioning (use automatedlab-proxmox), WinRM connectivity diagnosis (use winrm-troubleshooting), short commands, skill authoring (use skill-creator), agent evals (use agent-evals).
Pinned to revision 7a186c5dfcf8, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/long-running-job-monitor/SKILL.md
- skills/long-running-job-monitor/notes-evals.md
- skills/long-running-job-monitor/references/heartbeat-protocol.md
- skills/long-running-job-monitor/references/out-of-band-verification.md
- skills/long-running-job-monitor/scripts/Start-DetachedPowerShell.ps1
- skills/long-running-job-monitor/scripts/Start-JobHeartbeat.ps1
- skills/long-running-job-monitor/scripts/Start-JobMonitor.ps1
Every link opens the file at its source, pinned to the revision this page describes.