docs: the try-out page lists a row's fields, the posted review folds them into four; the README names the 350-character ask

docs/swarm/ui.md

@@ -115,9 +115,9 @@ doesn't parse, or it holds more than ten rules, the page shows the reason and
 leaves your classifications as they were.
 
 A run takes a minute or more, and up to half an hour for ten classifications.
-The page says it's running and shows how long it has been, then shows the review's table: for each classification the verdict,
-the model's certainty, the threshold, whether the verdict counted and the
-reason. A classification that couldn't run shows its error where the reason
+The page says it's running and shows how long it has been, then lists each classification with its verdict, the model's certainty, the
+threshold, whether the verdict counted and the reason; the posted review folds
+those fields into four columns ([`review-classifier.md`](review-classifier.md)). A classification that couldn't run shows its error where the reason
 would be. Under the table are the overall verdict, approve or request changes,
 and the head commit the run read. A failed run shows its error, for example when the swarm
 has no API key yet.

swarm-review-classifier/README.md

@@ -20,7 +20,7 @@ forge and holds no forge credential.
   (`--tools ""`), no MCP server, its own empty directory and
   `ANTHROPIC_API_KEY` in its environment only.
 - An answer is a JSON object with a verdict, a certainty and a reason; the
-  classifier truncates a reason over 500 characters to 499 plus `…`. A failed run, a
+  prompt asks for a reason under 350 characters, and the classifier truncates one over the 500 cap to 499 plus `…`. A failed run, a
   timeout or an answer that doesn't validate leaves that row without a verdict, and it doesn't count.
 - A run with no API key, or with no classification answered, fails as a
   whole: the caller sees an error, never a verdict.