P-TRANSPORT: canonical ingress convergence

[pcvantol]

P-TRANSPORT — technical closure status

Current exact head: 833c81033bff09b908b02bea28bfda9629cded0f
Source of truth: docs/engineering/P_TRANSPORT_AUDIT_CLOSURE_REGISTER.md

Delivered and qualified

• AC-01–AC-07: Console lifecycle guardrails, Server-owned File Inbox, canonical component/log authority, and Dashboard-wrapper retirement.
• AC-04: installed Dependabot multi-project binding; transient CENTRAL startup-lock retry is bounded to one second (382cecf).
• AC-09: immutable, installation-bound receipt-to-run provenance.
• AC-12: installed positive and negative Server Relay restart canaries.
• Coverage baseline: rebuilt candidate ran 1163 Python tests; all 107 production modules satisfy the >=80.20% branch-coverage contract.

Exact-head installed UI review package

• Fresh 833c810 wheel installed into the real EP Server runtime; loopback Console is healthy on 127.0.0.1:8765 and relay is restored on the Tailnet listener.
• Normal-state desktop, component-detail, logging, Server-settings, narrow/mobile, and bounded relay-degradation screenshots captured from that installed candidate.
• HTTP/API details use status_code / detail_code; raw dashboard.health and normal-user CENTRAL terminology are absent.
• Browser regression and five-locale localization contract pass.
• Hosted validate, browser shards, CodeQL, security and delivery checks pass on this exact head.
• Human UI review: operator approval required.

Governance — no authorization implied

P-TRANSPORT AWAITING_HUMAN_UI_REVIEW
TECHNICAL_CLOSURE = BLOCKED
HUMAN_UI_REVIEW = NOT_READY
OWNER_AUTHORIZATION = NOT_REQUESTED
MERGE = PROHIBITED

The Owner Authorization check is intentionally not requested and must not be interpreted as a technical test failure.