The resource observation JSON was successfully written with eight checks passing. After writing it, console-summary formatting failed with KeyError because the author renamed the ambiguous worker_job_peak_commit_bytes receipt field to worker_windows_reported_peak_commit_bytes during this review interval. The complete child observations and configured-limit readback were already preserved in RESOURCE-OBSERVATION.json. No allocation was repeated to repair this cosmetic console output. The exact original reviewer script is retained as probe_job_memory-original.py. The reusable script now accepts either name. Do not infer the unexplained peak counter represents refused or admitted memory. The observed facts are a configured 64 MiB limit, successful/free 8 MiB commit, NULL/error1455 for a 256 MiB request, unchanged 9,641,984-byte current private commit after that refusal, and a native peak counter of 279,879,680 bytes.