docs: api comments say what the endpoints do, not how they came to be (#6277)

Rewrites the internal/api comment blocks to rule 32: task, milestone and
rule ids gone, the stories behind them restated as the constraint they
left, stale references corrected (the stream secret is wired from config,
the timezone handler already refreshes the scheduler, the Android app is
the native client, the design docs cited are not in the repo). Also
rewraps comment lines over 80 columns left by the earlier batches.

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

internal/server/requestlog_test.go

@@ -109,9 +109,10 @@ func TestRequestLog_AttributesPresent(t *testing.T) {
 	}
 }
 
-// Behind a proxy, the access log's `remote` must be the client rather than the proxy, and must agree with what the
-// Active-sessions surface records for the same request. Logs and UI
-// disagreeing about who connected is worse than either being wrong alone.
+// Behind a proxy, the access log's `remote` must be the client rather than the
+// proxy, and must agree with what the Active-sessions surface records for the
+// same request. Logs and UI disagreeing about who connected is worse than
+// either being wrong alone.
 func TestRequestLog_RemoteHonoursTrustedProxyDepth(t *testing.T) {
 	cases := []struct {
 		name       string