Retain K1 connection between scans and admit the next named acquisition

This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 21:13:17 +03:00
parent ed9a77ba73
commit c6693d6f44
17 changed files with 586 additions and 274 deletions
@@ -367,6 +367,17 @@ def test_canonical_session_owns_start_active_scan_stop_and_save_boundary() -> No
assert response_evidence[0]["operation_key"] == "bootstrap:1:DeviceInfoRequest"
assert response_evidence[-1]["operation_key"] == "modeling:stop"
assert all("payload" not in item for item in response_evidence)
before_batches = list(transport.batches)
standby_pumps = len(transport.maintain_calls)
transport.pre_start_ready = lambda _binding: True
executor.maintain_standby_until_next_acquisition(
lambda: len(transport.maintain_calls) >= standby_pumps + 3,
)
assert transport.batches == before_batches
assert len(transport.maintain_calls) == standby_pumps + 3
# A next dialogue must use a fresh transport, not reset one-shot guards.
with pytest.raises(ApplicationAcceptanceError):
executor.run_connection_stage(orchestrator)
assert APPLICATION_KEY not in str(executor.snapshot())
assert VENDOR_DEVICE_ID not in str(executor.snapshot())
TypeAdapter(JsonValue).validate_python(executor.snapshot())