docs(testing): state the enforcement status of both new rules

The sibling mandatory conventions all end by naming the test that enforces
them. These two do not have one, so say so explicitly rather than let the
'(mandatory)' heading imply CI coverage: the CLI-customized-command rule has
a lint tracked in #1402, and the list-ordering rule stays judgment-based by
design (a lint cannot decide whether a given list is order-significant).

Author: go-to-k

.claude/rules/testing.md

@@ -206,6 +206,12 @@ existing fixtures do not set it and are fine, because the hang only bites the
 customized commands. `tests/integration/emr-instance-configs/verify.sh` is the
 reference.
 
+NOT mechanically enforced yet — a lint over `tests/integration/*/verify.sh` is
+tracked in issue
+[#1402](https://github.com/go-to-k/cdkd/issues/1402), so until then this is a
+read-it-and-follow-it rule. User-facing writeup in
+[docs/testing.md](../../docs/testing.md).
+
 ### `verify.sh` list readbacks must be order-insensitive (mandatory)
 
 AWS does not preserve the submitted order of list-valued members on readback.
@@ -232,6 +238,11 @@ order-significant (DNS resolver lists, preference orders — see
 `getDriftUnorderedPaths`) must stay unsorted, because sorting it would HIDE a
 real regression.
 
+NOT mechanically enforced — whether a given list is order-significant is a
+judgment call a lint cannot make, so this one stays a read-it-and-follow-it
+rule by design. User-facing writeup in
+[docs/testing.md](../../docs/testing.md).
+
 ### Fixture stateful L2s need an explicit removalPolicy (mandatory)
 
 Stateful CDK L2 constructs (`kinesis.Stream`, `dynamodb.Table`/`TableV2`,