[maxmad64bis]

⚠️ base-red inherited: #14547

Summary

The proxy journal API already returns the received code, exit address, correlation id and served account, but the dashboard shows none of them: failures cannot be attributed to an exit at a glance. This displays the four fields (masked per the existing rules) and adds a traffic / connection-test filter, so an operator sees which exit failed with which upstream code and finds the request. The logs page also accepts ?correlationId= and prefills the journal filter, so the link from a log row finds the request.

Related Issues

No linked issue — display-only follow-up to the attribution columns already stored.

Validation

• Change type: UI
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

Tests Added Or Updated

• tests/unit/proxy-logger-observed-fields.test.tsx (vitest, 2 tests): four fields render masked, null never renders as 0, traffic/test partition including tests issued through a configured proxy, correlation link targets the correlation filter.
• tests/unit/ui/logs-page-correlation-prefill.test.tsx (vitest, 1 test): rendering the page with ?correlationId=abc sends the journal request with correlationId=abc.

Coverage Notes

• Covers src/shared/components/ProxyLogger.tsx and src/shared/components/ProxyLogDetail.tsx.
• New en.json keys translated across all 66 locales (check-new-key-coverage PASS).

Reviewer Notes

• No new route; client-side filter only, server fetch unchanged.
• null upstream status renders as "no response", never 0; no proxy identifiers are displayed.
• Prettier: the 4 touched UI/test files carry base-inherited style drift (base files fail prettier --check at the same spots); hunks-only --write would reformat half of RequestLoggerV2.tsx — left as-is, flagged here.