docs: the numeric-coercion deviation is declared, not withheld

Leftover from the declare-and-fail change: the summary still opened with
'Withheld because of a defect' for a capability the same commit had
declared.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>

Author: aepfli

tests/test_provider_conformance.py

@@ -98,10 +98,9 @@ def new_provider() -> FlagsmithProvider:
         # initialize/shutdown lifecycle the suite can assert against. Declaring them would make
         # those scenarios pass without the provider having done anything, and a vacuous pass is
         # worse than a skip.
-        # DISABLED_FLAGS and NUMERIC_COERCION are declared and both fail. This provider attempts
+        # DISABLED_FLAGS and NUMERIC_COERCION are declared and both fail: this provider attempts
         # each and gets it wrong -- it raises GENERAL for a disabled flag, and type-checks a float
-        # that Flagsmith stores as a string -- so the scenarios run and the failures stay in the
-        # results rather than being withheld into skips.
+        # that Flagsmith stores as a string.
         capabilities={
             Capability.OBJECT,
             Capability.LARGE_INTEGERS,
@@ -130,7 +129,8 @@ def new_provider() -> FlagsmithProvider:
                 capability=Capability.NUMERIC_COERCION,
                 issue="",
                 summary=(
-                    "Withheld because of a defect rather than a design choice. Flagsmith has no "
+                    "Declared and failing rather than withheld, because the provider does have a float "
+                    "accessor and gets the answer wrong. Flagsmith has no "
                     "float type -- feature_state_value is natively boolean, integer or string -- "
                     "so every float is stored as a string, and _BASIC_FLAG_TYPE_MAPPINGS[FLOAT] "
                     "is a plain isinstance check against `float`. A Flagsmith float therefore "