Thin the app's comments

The same pass the server had, on the Kotlin side: comments restating what
the code says are gone, and the ones recording a measurement, a constraint
or an incident are kept but cut to a few lines each. 6540 comment lines to
5674, and 920 lines off the app.

Two doc comments had drifted onto the item above the one they describe --
`contextAfter`'s onto `sessionWorking` in Events.kt, and `UsageMonitor`'s
equivalent on the server was fixed in the previous commit. Each is back on
its own item, which is the only non-comment line this diff moves.

The comments are reflowed to the column limit at their own indentation:
several were written wide, and ktfmt re-wrapped them into lines holding a
single orphan word. `/tmp` script, not kept -- ktfmt is idempotent over the
result, which is the check.

Left alone deliberately: this codebase's remaining comment density is high
because the comments carry things the code cannot say -- what a null means,
what a number was measured against, which bug a guard exists for. Of the
238 one-line doc comments in the app, five were pure restatement of the
name and were removed; the rest each say something the signature does not.

ktfmtFormat, compileDebugKotlin, lintDebug and testDebugUnitTest pass;
cargo test (127), clippy --all-targets and fmt still clean.

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

app/androidApp/src/main/kotlin/com/example/aiapp/Compaction.kt

@@ -7,12 +7,10 @@ import androidx.compose.ui.Modifier
  * The mark a compaction leaves in the transcript.
  *
  * A divider rather than something anybody said: everything above it is out of the session's context
- * now, and that is a fact about the conversation, not a turn in it. It has no collapsed form -- it
- * is already one line, and there is nothing behind it to open. Drawn by [TranscriptDivider], which
- * a clear also uses, so the two marks cannot drift apart.
+ * now, and that is a fact about the conversation, not a turn in it. Drawn by [TranscriptDivider],
+ * which a clear also uses, so the two marks cannot drift apart.
  *
- * Blue is [commandColor]: the session acting on itself rather than working on what was asked of it,
- * which is the same thing the status line says while the compaction runs.
+ * Blue is [commandColor]: the session acting on itself rather than working on what was asked of it.
  */
 @Composable
 fun CompactedRow(item: TranscriptItem.CompactedNote, modifier: Modifier = Modifier) {
@@ -23,9 +21,8 @@ fun CompactedRow(item: TranscriptItem.CompactedNote, modifier: Modifier = Modifi
  * What to say about a compaction: the two sizes, and nothing else.
  *
  * The counts are the whole point -- "a million tokens became ten thousand" is the reader's answer
- * to why the wait was worth it -- and they are all this says, because a divider is read in passing.
- * When they were not reported this says only that a compaction happened, rather than filling in a
- * plausible number or explaining at length what was missing.
+ * to why the wait was worth it. When they were not reported this says only that a compaction
+ * happened, rather than filling in a plausible number.
  */
 fun compactionSummary(item: TranscriptItem.CompactedNote): String {
     val pre = item.preTokens
@@ -41,8 +38,8 @@ fun compactionSummary(item: TranscriptItem.CompactedNote): String {
  * A token count as a reader reads one.
  *
  * Shared with the status row rather than formatted at each: the divider and the row report the same
- * quantity about the same moment, and one of them grouping its thousands while the other did not
- * read as two different measurements.
+ * quantity about the same moment, and one grouping its thousands while the other did not read as
+ * two different measurements.
  */
 fun tokens(count: Long): String = "%,d".format(count)
 
@@ -50,15 +47,12 @@ fun tokens(count: Long): String = "%,d".format(count)
  * What the working indicator says while a compaction is running.
  *
  * Elapsed time and nothing else, because elapsed time is all there is: the CLI announces that a
- * compaction has begun and then says nothing until it has finished, so any bar, percentage or
- * estimate here would be this screen's guess wearing a measurement's clothes. Knowing it has been
- * going forty seconds is what a reader actually wants -- it is the difference between waiting and
- * going to look at why.
+ * compaction has begun and then says nothing until it has finished, so any bar or estimate here
+ * would be this screen's guess wearing a measurement's clothes.
  *
  * [seconds] is null when this device did not see the compaction start, which is what opening a
- * session that is already compacting looks like. That case says only "compacting": no number is the
- * honest answer, and a number counted from the moment the screen opened would be wrong in the
- * direction that matters, since a compaction somebody is asking about is a long one.
+ * session that is already compacting looks like. That case says only "compacting": a number counted
+ * from the moment the screen opened would be wrong in the direction that matters.
  */
 fun compactingLabel(seconds: Long?): String =
     when {