Android comments describe the code to a stranger (#6223)

Milestone 546 "Bring the repo to the comment standard (rule 32) and
compose defaults (rule 198)", step #6223 "Comment standard sweep:
Android client".

KDoc, comments, manifest and resource notes, Gradle and TOML comments
and the ffi crate's docs now state what the code does and the
non-obvious why in the present tense. Issue, Scribe-note, milestone
(M13, M304, M315, M12) and family-idea references are gone, as are
comparisons to Minstrel and the narration of what used to be: the
capture sheet the editor replaced, the per-note colour story, the
operator's device-pass feedback, the bindgen-as-[[bin]] failure, the
0.60 edge alpha before it was re-solved, and the checker bugs behind
check-strings/check-symbols. Hazards stay as facts: the signing key that
can't be rotated, the alias that keeps the earlier name, PKCS12's single
password, unwind over abort, the UTC date-picker read, the
DerivedTint/colors.ts mirror.

One stale claim is gone: DerivedTint said the web had no test runner,
but notes/grammar.test.ts runs the same tint cases. detekt.yml said
"these two places" over a list of five.

49 files, comments only: a comment-stripping diff of every changed file
against HEAD is identical.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

android/tools/check-strings.py

@@ -44,8 +44,7 @@ def supplied_args(rest):
     """Count top-level commas in an argument tail.
 
     Kotlin permits a TRAILING comma before the closing paren, which is not an
-    argument — counting it inflated every multi-line call by one the first time
-    this was written, and made three correct call sites look broken. Braces count
+    argument; counting it would inflate every multi-line call by one. Braces count
     toward depth as well as parens, or a comma inside a lambda would be read as
     another argument.
     """