dubbo: bound the Mutiny negative-path await wherever the test exists

The MutinyClientCallsTest stabilization (await().indefinitely() ->
atMost(10s)) was gated on MILESTONE_ID == M016.1 in both the compatibility
script and the test-compat Dockerfile, while the same test ships in other
checkpoints' trees (M003.3 END, M025 both states). An implementation that
drops the mocked failure then hangs the whole reactor at the unpatched
checkpoints until the evaluator's outer 3600s timeout, fail-closing the
entire cell (kimi-k3 M003.3/M025, 2026-07-18; three-way adjudication in
SWE-Milestone-data/reeval/dubbo_kimi_deepaudit_20260718/ADJUDICATION_CONSENSUS.md).

Gate on the runtime fact instead: patch whenever the test file exists in the
checked-out state. Golden semantics unchanged (correct implementations
observe the failure immediately); hanging implementations become one
deterministic failing test instead of a zeroed cell — identical to the
treatment M016.1 already had.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BXhU3BbzS4HgWvgvXeB1t1

apache_dubbo_dubbo-3.3.3_dubbo-3.3.6/dockerfiles/Dockerfile.test-compat

@@ -42,7 +42,7 @@ RUN set -euo pipefail; \
         compat_targets=( \
             dubbo-metrics/dubbo-tracing/src/test/java/org/apache/dubbo/tracing/utils/ObservationConventionUtils.java \
         ); \
-        if [[ "${MILESTONE_ID}" == "M016.1" ]]; then \
+        if [[ -f dubbo-plugin/dubbo-mutiny/src/test/java/org/apache/dubbo/mutiny/MutinyClientCallsTest.java ]]; then \
             compat_targets+=( \
                 dubbo-plugin/dubbo-mutiny/src/test/java/org/apache/dubbo/mutiny/MutinyClientCallsTest.java \
             ); \

apache_dubbo_dubbo-3.3.3_dubbo-3.3.6/dockerfiles/dubbo_test_compatibility.sh

@@ -64,20 +64,19 @@ fi
 
 echo ">>> Dubbo test compatibility patch applied successfully"
 
-# M016.1 owns a negative-path test that deliberately feeds an exception into
-# the candidate implementation.  An implementation that drops that exception
+# The Mutiny negative-path test deliberately feeds an exception into the
+# candidate implementation.  An implementation that drops that exception
 # leaves Mutiny's indefinite await blocked forever.  Surefire's fork timeout is
 # not a reliable assertion boundary: depending on fork shutdown timing it can
 # either omit this test report and continue, or hang the whole reactor until the
 # evaluator's outer timeout.  Bound the evaluator-owned await instead, so a
 # correct implementation still observes "boom" immediately while an incorrect
 # implementation becomes a deterministic failing test after ten seconds.
-if [[ "${MILESTONE_ID:-}" == "M016.1" ]]; then
-    if [[ ! -f "$mutiny_client_calls_test" ]]; then
-        echo "ERROR: Mutiny compatibility target is missing: $mutiny_client_calls_test" >&2
-        exit 49
-    fi
-
+# Applied to every checkpoint whose tree carries the test (not just M016.1):
+# the hazard travels with the test file, and gating on one milestone id left
+# identical hanging implementations measured at M016.1 but zeroing whole
+# cells at M003.3/M025 (kimi-k3 2026-07-18 incident).
+if [[ -f "$mutiny_client_calls_test" ]]; then
     mutiny_method=$(
         sed -n \
             '/void testOneToOneThrowsErrorWithMutinyAwait()/,/^[[:space:]]*@Test/p' \
@@ -105,5 +104,5 @@ if [[ "${MILESTONE_ID:-}" == "M016.1" ]]; then
         exit 51
     fi
 
-    echo ">>> Dubbo M016.1 Mutiny negative-path wait bounded successfully"
+    echo ">>> Dubbo Mutiny negative-path wait bounded successfully (${MILESTONE_ID:-unknown})"
 fi