[0xcadams]

What

Retain the exact HTTP response and service when the real workload revocation/expiry proof fails. Stacked on #482, independently of #483's native carrier-selection change.

Why

#482's QUIC workload CI failed at the revoked-HTTP check, but its assertion conflates HTTP 200 with a redirect and omits the service. That does not establish whether a target accepted the request or the browser path redirected it. The binary group passed in that run; this is a separate unresolved qualification failure, not evidence that component-exit reporting changed authorization.

The existing local pass history does not explain this failure. Keep the response evidence and control's corresponding revocation/deadline state before changing behavior or the proof's limits.

Changes

• Record the fixture session label, exact saved-service name, and observed HTTP status on a forbidden success/redirect.
• On that failure only, read a bounded, non-secret control snapshot containing observation time, revocation state, lease deadline, and fixed deadline. Do not print credentials, keys, claims, response bodies, or URLs.
• Keep the original revocation/expiry assertions, HTTP requests, test selectors, and deadlines unchanged; add no retry and make no serving change.

[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]

disposable Linux reproduction completed on signed #484 source 76db6c52d6ef647695fcd240aafd789a3e0aa1a7:

task go:test:integration RUN='^TestIntegrationWorkloadTransportLifecycle/quic$' passed in 223.298s (222.20s QUIC subtest), crossing revocation, the unrenewed lease, renewed continuity, and fixed expiry with the original assertions and serving deadlines. the local macOS proof also passed in 224.764s.

the #482 CI revoked-HTTP failure remains unexplained. neither pass identifies the original response status/service, so the exact-response/control-deadline diagnostics remain in #484 and the combined #485 stack. no admission retry, timeout increase, serving change, production operation, or claim of final qualification was introduced.

the integrated #485 routine run separately hit a five-second QUIC fixture connection timeout before full-duplex assertions. its focused unchanged TestSessionContract race proof passed in 1.439s; the first failure is retained and routine validation is being repeated after the Linux workload completed.