From 0d54d07793648e3f200fa40a3c2df71d29233be2 Mon Sep 17 00:00:00 2001 From: Pavel Ivanov Date: Tue, 14 Jul 2026 22:08:14 -0700 Subject: [PATCH] conformance: ratchet DEV-1149-class experimental gaps as ticket-linked expected failures Executes the DEV-1149 decision (gaps stay visible as ratchets, never reclassified): every raw experimental fail/timeout from nightly run 29384698254 gets a missing_feature/bug entry pointing at DEV-1149 (missing batched events/track route) or DEV-1148 (hot-path Class 1). 22 new entries; scenarios already ratcheted untouched. Unlocks honest auto-promotion of these scenarios fleet-wide (a ratcheted expected_fail is promotion-acceptable; a raw fail is not). Co-Authored-By: Claude Fable 5 --- conformance/failures.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/conformance/failures.txt b/conformance/failures.txt index 50d05d1..823ed74 100644 --- a/conformance/failures.txt +++ b/conformance/failures.txt @@ -1,11 +1,33 @@ ai-fields-nested-not-toplevel@fault: missing_feature # SDK never POSTs events/track: track_ai ships via events/track_partial as a single-object body, not the ratified array batch (DEV-1149) +batching-close-drains-without-flush@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +batching-double-flush-no-duplicate@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +batching-flush-cycle-resets-queue@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +concurrency-batch-all-land@fault: missing_feature # requires the queued events/track complete-event buffer (batch drain/flush lifecycle) that the SDK lacks — ships single-object events/track_partial synchronously (DEV-1149; hot-path: DEV-1148) +concurrency-retry-preserves-all@fault: missing_feature # requires the queued events/track complete-event buffer (batch drain/flush lifecycle) that the SDK lacks — ships single-object events/track_partial synchronously (DEV-1149; hot-path: DEV-1148) +hang-request-deadline@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +hot-path-sustained-track-ai@fault: bug # Class 1 violation (CONTRACT 1.1): sustained track_ai posts synchronously on the caller's path; also no events/track batch route (DEV-1148; route gap: DEV-1149) hot-path-track-nonblocking@fault: bug # Class 1 violation (CONTRACT 1.1): TrackEvent posts synchronously (network I/O + retry sleep on the caller's goroutine); also ships via events/track_partial, never events/track (DEV-1148; route gap: DEV-1149) +negative-path-400-no-retry@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +negative-path-403-no-retry@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +negative-path-413-no-retry@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +negative-path-malformed-track-response@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +reconnect-identical-body@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) retry-401-no-retry@fault: missing_feature # SDK never POSTs events/track: TrackEvent ships via events/track_partial, so the 401-no-retry assertion records zero events/track attempts (DEV-1149) retry-429-hot-path@fault: bug # Class 1 violation (CONTRACT 1.1): TrackAI posts synchronously (network I/O + Retry-After sleep on the caller's goroutine); also ships via events/track_partial, never events/track (DEV-1148; route gap: DEV-1149) +retry-500-then-200@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +retry-after-cap@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +shutdown-drain-hang-deadline@fault: missing_feature # requires the queued events/track complete-event buffer (batch drain/flush lifecycle) that the SDK lacks — ships single-object events/track_partial synchronously (DEV-1149; hot-path: DEV-1148) +size-limit-deep-properties@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +size-limit-large-text-field@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +size-limit-oversized-attachment@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +size-limit-wide-properties@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) track-ai-custom-event@fault: missing_feature # SDK never POSTs events/track: track_ai ships via events/track_partial as a single-object body, not the ratified array batch (DEV-1149) track-attachments@fault: missing_feature # SDK never POSTs events/track: track_ai ships via events/track_partial as a single-object body, not the ratified array batch (DEV-1149) track-batch-array@fault: missing_feature # SDK never POSTs events/track and does no queue batching: each track posts one single-object events/track_partial request immediately (DEV-1149) track-nested-properties@fault: missing_feature # SDK never POSTs events/track: track ships via events/track_partial as a single-object body, not the ratified array batch (DEV-1149) track-plain-single@fault: missing_feature # SDK never POSTs events/track: track ships via events/track_partial as a single-object body, not the ratified array batch (DEV-1149) track-single@fault: missing_feature # SDK never POSTs events/track: track_ai ships via events/track_partial as a single-object body, not the ratified array batch (DEV-1149) +unicode-multibyte-fields@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +unicode-rtl-bidi@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) +unicode-surrogate-pairs@fault: missing_feature # SDK never POSTs events/track: the scenario's assertions target the ratified batched route, which the SDK lacks — behavior ships via single-object events/track_partial (DEV-1149) wrap-retry-429-partial-hot-path@fault: bug # Class 1 violation on the real route: TrackAI sleeps through Retry-After on the caller goroutine (step 1001ms vs max_ms 100) before the retry ships (DEV-1148)