Networking Migration Readiness Checklist (T0-08..T0-24)

Status: draft Owner: transport docs + protocol stack alignment

This checklist translates protocol rewrite gates into a deterministic promotion plan.

Execution mapping:

• Ticket-level gate states are recorded in docs/waves/WORK_ITEMS.md (T0-08 through T0-24) in the Migration gates fields.

Gate policy

Promotion from bridge-first to stronger protocol layers requires:

1. ticket owner signoff,
2. fixture coverage marked in docs/waves/SPEC_TEST_COVERAGE.md,
3. explicit profile gate annotation in docs/waves/WORK_ITEMS.md,
4. no contract drift in browser/contracts/transport.ts and engine-wasm/contracts/wml-engine.ts.

Ticket-level done-done gates

T0-08 (Owner: transport-rust)

• Done-1: replay-window/TID policy tables are implemented and deterministic under both duplicate/no-cache assumptions.
• Done-2: out-of-order invoke and timeout transitions are logged with deterministic terminal state.
• Done-3: fixtures in transport-rust/tests/fixtures/transport/ cover at least one each of table-6/7/8-like decisions.

T0-09 (Owner: transport-rust)

• Done-1: WSP mode is machine-enforced as CO-only/CL-only/both profile artifact.
• Done-2: connectionless matrix fixture rejects invalid req/ind primitive transitions.
• Done-3: profile test matrix updates gate any unsupported primitive behavior in CI-like check.

T0-10 (Owner: transport-rust)

• Done-1: assigned-number registry fixture set includes PDU types, headers, and abort reasons.
• Done-2: unknown/unassigned token handling path is explicit and tested for both encode/decode.
• Done-3: regression fixture proves stable profile-dependent behavior.

T0-11 (Owner: transport-rust)

• Done-1: negotiation-capability merge/intersection implemented as deterministic min-policy.
• Done-2: negotiated limit violations emit deterministic abort/error and are fixture-asserted.
• Done-3: cap-overrun fixture proves blocked request paths and trace tags.

T0-12 (Owner: transport-rust, docs)

• Done-1: RQ-TRX-009 posture is declared with a fixed implemented/delegated/deferred split.
• Done-2: compatibility-check artifact is versioned in docs and does not conflict with T0-14 profile rules.
• Done-3: no uncoded TCP-optimization requirement enters transport implementation silently.

T0-13 (Owner: transport-rust, docs)

• Done-1: one explicit decision is made (in-scope or deferred) for WAP-159.
• Done-2: if deferred, scope-guardrails are written into transport-adjacent docs with no code requirement.
• Done-3: if in-scope, data_sm mapping and WCMP payload validation fixtures exist.

T0-14 (Owner: transport-rust, browser)

• Done-1: profile contract now includes near-term and target-state transport modes.
• Done-2: hard gate rules for profile promotion are linked to ticket IDs and fixture coverage.
• Done-3: migration lane order is mirrored in docs/waves/networking-implementation-checklist.md and WORK_ITEMS.md.

T0-15 (Owner: transport-rust, browser)

• Done-1: cache policy includes shared request-policy path and deterministic override precedence.
• Done-2: fixture lane proves hit/miss/reload/invalidation behavior under cache-control.
• Done-3: profile transition tests show cache policy parity between profiles.

T0-16 (Owner: spec-processing)

• Done-1: one canonical WAP-259 variant exists in spec-processing/source-material.
• Done-2: finalize-new-source-material.fish --dry-run returns zero unresolved transport conflicts.
• Done-3: review ledger includes one current row per transport/security canonical ID.

T0-17 (Owner: docs + transport)

• Done-1: non-core transport adjacencies (WAP-204*, WAP-213*) remain explicitly deferred; WAP-120 stays outside transport ownership but active under the WAE compliance lane.
• Done-2: TRANSPORT_ADJACENT_SPEC_TRACEABILITY.md and OUT_OF_SCOPE... are aligned on transport-adjacent deferrals.
• Done-3: migration profile promotion criteria references T0-17 as scope-lock check.

T0-18 (Owner: transport-rust, docs)

• Done-1: retransmission timer/counter behavior is explicit and fixture-backed.
• Done-2: duplicate invoke/result handling includes deterministic cache-retention policy.
• Done-3: NACK delay and retransmission hold-off policy is explicitly profile-gated for SAR lanes.

T0-19 (Owner: transport-rust)

• Done-1: WDP datagram trait is the protocol-native ingress to connectionless WSP in wap-net-core and to WTP only in a separately activated connection-oriented extension.
• Done-2: UDP mapping for 9200..9203 is deterministic and fixture-covered.
• Done-3: SAR behavior is documented and profile-gated (off default unless explicitly enabled).

T0-20 (Owner: transport-rust, docs)

• Done-1: WSP assigned-number/header registry coverage is table-driven and versioned.
• Done-2: unknown token/code-page behavior is explicit and tested for active profiles.
• Done-3: code-page shift, unsupported encoding paths, and method request/result classification over minimal Get/Post/Reply PDUs have deterministic outcomes.

T0-21 (Owner: transport-rust, docs)

• Done-1: WTLS phase boundary is explicit (no-op vs active minimal) and default-safe.
• Done-2: active-mode record parsing and handshake retransmission/duplicate behavior is fixture-covered.
• Done-3: security path cannot activate without profile-gate enablement artifacts.

T0-22 (Owner: transport-rust, docs)

• Done-1: replay harness baseline exists and CONNECT / GET / REPLY protocol paths are runnable from transport-rust/tests/interop_replay.rs.
• Done-2: retransmission and duplicate-TID replay paths are runnable in the same corpus.
• Done-3: migration profile gates can now reference replay results as mandatory promotion evidence.

T0-24 (Owner: transport-rust, docs)

• Done-1: schema-versioned seed corpus exists with committed metadata, provenance, and legal-reuse posture for Connect, Get/Reply, retransmission, and duplicate-TID flows.
• Done-2: replay harness validates both deterministic event order and transaction-level outcomes from those seed fixtures.
• Done-3: T0-22 references the seed corpus as required replay baseline input rather than ad hoc replay JSON.

Cross-tile closure rule

T0-17 had to stay true before promotion in T0-14, and T0-18..T0-24 had to be green before moving from gateway-bridged to wap-net-core. That promotion baseline is now satisfied; future gates apply to wap-net-ext or rollback decisions.