Summary for 2026-07: This month focused on strengthening the reliability and correctness of the Node Browser via robust error handling in the Node-proxied browser. Key feature delivered: preserve HTTP status codes in error messages from the node browser proxy to ensure the gateway's retry logic can determine the appropriate action. This change prevents loss of status information when errors cross the RPC boundary, enabling correct stale-target retries. The update involved minimal formatting changes in the >=400 error path and was validated by the extensions/browser invoke-browser test suite, which passed 14/14. The work aligns with business goals of higher uptime, fewer failed requests on retries, and improved observability around browser tool failures. Co-authored notes and changelog updates were included as part of the release. Overall, this enhances reliability with modest code changes and clear test coverage.