starknet_transaction_prover: log resolved config at startup (secrets redacted)

[avi-starkware]

No description provided.

[avi-starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• starknet_transaction_prover: log resolved config at startup (secrets redacted) #14684 👈 (View in Graphite)
• starknet_transaction_prover: origin-level breadcrumbs for validation errors #14172
• starknet_transaction_prover: /health returns 503 when service is saturated #14171
• starknet_transaction_prover: track saturation and queue depth on the request path #15027
• starknet_transaction_prover: bump prover_panics_total on panic hook fire #14170
• starknet_transaction_prover: HTTP request count + latency + in-flight metrics #14169
• starknet_transaction_prover: proving-job duration + outcome metrics #14168
• starknet_transaction_prover: Prometheus /metrics endpoint with build_info #14167
• starknet_transaction_prover: extract the TLS accept loop and test its drain #15049
• starknet_transaction_prover: graceful shutdown on SIGTERM/SIGINT #15026
• starknet_transaction_prover: global panic hook with structured log #14166
• starknet_transaction_prover: document existing logging, request ids and health probe in README #14203
• main-v0.14.4

This stack of pull requests is managed by Graphite. Learn more about stacking.

[reviewable-StarkWare]

This change is 

[cursor]

PR Summary

Low Risk
Observability-only change with explicit URL redaction and a regression test; no request-handling or auth behavior changes.

Overview
Startup configuration logging moves from an inline banner in main to ServiceConfig::log_startup_summary(), which emits a structured event="config_resolved" line after file/env/CLI merge and before the server binds.

That log records build identity plus the resolved service and prover settings operators care about (listen address, transport, queue/connection limits, CORS, OHTTP, chain/RPC/blocking-check options, etc.), while RPC and blocking-check URLs stay host-only and TLS cert/key paths are omitted. The post-bind “server is running” log is unchanged; the README now documents the two startup lines and updates redaction wording.

A traced_test asserts URL userinfo and path secrets never appear in the startup summary output.

^{Reviewed by Cursor Bugbot for commit adbd7ea. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8ccf362. Configure here.}

[cursor]

Weak startup redaction test isolation

Low Severity

startup_summary_logs_hosts_and_redacts_url_credentials calls from_args before log_startup_summary, and from_args already emits redacted CLI-override lines that include the same hosts. The positive logs_contain host checks can therefore pass even if log_startup_summary stops logging hosts. Secret-absence checks still cover the summary path, but host logging on the config_resolved line is not actually pinned.

 

^{Reviewed by Cursor Bugbot for commit 8ccf362. Configure here.}