no-mistakes(document): Fix stale scope-conformance port-support claims

Author: dmealing

docs/features/metadata-sources.md

@@ -713,8 +713,8 @@ Design rationale and the full phase plan:
 
 - [`fixtures/scope-conformance/`](../../fixtures/scope-conformance/) — 10 cases
   pinning `*` / `**`, include-union, exclude-after-include, literal metacharacters,
-  and case sensitivity. TypeScript runs it today; the other four ports have no runner
-  yet, because `scope` itself stays Node-CLI-only (see "Port support" above). See
+  and case sensitivity. All five ports run it (Kotlin inherits Java's); only the Node CLI
+  reads `scope` from the config (see "Port support" above). See
   [`CONFORMANCE.md`](../CONFORMANCE.md).
 
 **TypeScript gates**

fixtures/source-resolution-conformance/README.md

@@ -4,7 +4,7 @@ Pins how a consumer's `sources` set in `.metaobjects/config.json` resolves to a
 set of metadata files. Every port's CLI must resolve the SAME FILES from the
 same declaration — that is the cross-port promise this corpus exists to keep.
 
-Companion to `scope-conformance/`, which pins the (currently TypeScript-only)
+Companion to `scope-conformance/`, which pins the
 `scope` pattern grammar. The two are independent: `sources` decides which files
 are read, `scope` filters what is emitted from them.