Second pass with the avoid-ai-writing detector

The skill's detector scored the README, PARITY.md and the extracted
comment prose. Fixed what it flagged: hollow intensifiers, "in order
to", "additionally", "the whole point", bold sentences in docs, and
bold that had wrapped across comment lines. Comment prose scores a
maximum of 4 out of 100 across the repo.

One sweep rule mangled four comments ("which is the entire point of X"
lost its clause); repaired, and the rule now keeps the clause.

Comments and strings only. 1208 tests pass, counted from the XML.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

engine/src/test/kotlin/io/flamenet/e2e/SecureBytesTest.kt

@@ -10,8 +10,8 @@ import kotlin.test.assertTrue
 /**
  * Zeroing key material once it has been used (ios#39, Android half).
  *
- * **The claim being tested is narrow, and the tests are shaped to keep it
- * narrow.** What this buys is that a derived key is not left sitting in the
+ * The claim being tested is narrow, and the tests are shaped to keep it
+ * narrow. What this buys is that a derived key is not left sitting in the
  * heap after the one moment it was needed. It is not "the key is gone", a
  * compacting collector can have moved the array, Android has compressed swap,
  * and there is no `memset_s` on the JVM. `SecureBytes` says all of that in