[0xcadams]

What

Report which required server component stopped before the process shuts down, keeping its original cause and any more specific failure classification. Stacked on #481.

Why

#481's binary manual-Compose CI failure lost its useful role-exit context: the database publisher failed before ready, and the standalone process later printed a generic startup failure. The component name existed only in the unrendered cause, so safe output did not identify what stopped.

The same manual-Compose case and the complete five-test binary group passed locally on unchanged adea3af9 in disposable Linux. Those passes do not establish the cause of the CI failure. This change preserves evidence for recurrence; it does not claim to fix that failure.

Changes

• Classify unclassified supervised exits as server.component_failed, retaining specific classifications and original cause identity.
• Report only the exit selected by process supervision, before shutdown, using the authored component name and existing safe fields such as SQLSTATE.
• Test classification, retry policy, no automatic restart, cause identity, safe output, and cancellation; retain the current supervision and join behavior.

[0xcadams]

the new failure is retained separately from carrier startup selection:

• fix: retain classified server component exit evidence #482 CI: QUIC TestIntegrationWorkloadTransportLifecycle failed at revoked HTTP (workload_transport_integration_test.go:156); binary passed. the original assertion did not identify the service or distinguish HTTP 200 from a redirect. original run: https://github.com/tnldotdev/tnl/actions/runs/40608618921/job/122554317800.
• signed/pushed test: retain exact workload HTTP denial evidence #484 at 76db6c52d6ef647695fcd240aafd789a3e0aa1a7 changes only evidence: exact fixture/service/status and a failure-only, one-second control snapshot containing observation/revocation/deadlines, with no credentials, keys, claims, bodies, or URLs.
• focused QUIC proof passed locally with the original serving source/assertions/budgets in 224.764s (223.12s subtest). routine Go/public API, daemon races, lint, formatting, and generation verification passed. this pass does not explain the CI failure.
• the disposable Linux reproduction is running against the same signed diagnostic source; no assertion, HTTP request, serving timeout, or admission retry was changed.
• test: reconcile runtime authority evidence on the native transport stack #485 carries that evidence and feat: integrate public ingress and native peer paths #470's previously missing 61033ba5 control-outage/certificate diagnostics on top of fix: activate only the selected native relay carrier #483. its combined control-restart/native-packet/workload qualification is running; no final-matrix success is claimed.
• test: reconcile runtime authority evidence on the native transport stack #485's initial routine Go run failed before full-duplex assertions: the unchanged QUIC contract fixture could not connect within five seconds (contract_test.go:87, no recent network activity). that log is retained separately; the later lint/format/generation targets in that command were not reached. no transport deadline is being increased to hide it.

all PRs remain unmerged drafts. no deployment, live infrastructure change, release, or deployed benchmark occurred; native production admission remains disabled.

[0xcadams]

superseded by the replacement cutover tracked in #499 (replacement stack #491). closing this original PR at the author's request so only the replacement review remains active. the original branch, commits, reviews and failure evidence are preserved; no branch is deleted. outstanding integration and validation remain tracked in the replacement, not waived by this closure.