diagnostic(proxy): retain safe HTTP status on empty-provider errors

agents/poe/work/queue-330/BUILD.md

@@ -444,3 +444,10 @@ Status comes from the existing safe management receipt, not another request.
 No assertions, timeouts, retries, scheduling settings, product source or test
 fixtures changed. No module/test/binary/diagnostic executed. Wait for Sage's
 review and CLEAR after the288 processing diagnostic before one acceptance run.
+
+2026-10-25T06:49Z sage-4454 review addition: diagnostic error output now includes
+httpStatus from the same existing receipt written by ManagementClient finally,
+using the identical receipt-count guard as success. No new request or raw
+exception data; this distinguishes404 from5xx without names or values. Separate
+one-line diagnostic commit, no module/test/binary execution. Hold for CLEAR after
+Sage's288 processing pair; no independent load-based run decision.

agents/poe/work/queue-330/acceptance.mjs

@@ -94,6 +94,7 @@ try {
     }));
   } catch (error) {
     console.log('P4 empty-provider diagnostic ' + JSON.stringify({
+      httpStatus: receipts.length === receiptCount + 1 ? receipts.at(-1).status : null,
       code: clientErrorCodes.includes(error.code) ? error.code : 'proxy-client-error',
     }));
   }