phpbotscout review status¶
Reports how many shadow answers have a verdict against the thirty that stand between shadow mode and posting, and how those verdicts went.
Every line is for one server: the one configured, or the one named with --server when there are
several. A stage server's reviewed answers count towards production's thirty while the two answer
alike, so judging production can mean adding two reports together (spec 0029 D4).
Usage¶
$ phpbotscout review status
Reviewed: 1 of 30 (answers 1, declines 0; posted 0, shadow 1)
Correct: 1 of 1
Citations apt: 1 of 1 judged
Excluded: 0
Waiting: 0
Feedback: 2 helpful, 1 not, on 2 answers
Reading the output¶
| Line | Meaning |
|---|---|
Reviewed |
Answers with a verdict, against the thirty. Split into answers (plain or hedged) and declines, and into posted and shadow. Excluded answers are not counted. |
Correct |
How many of the reviewed were judged correct. |
Citations apt |
How many had apt citations, out of those that had citations to judge. |
Excluded |
Replayed benchmark or calibration questions, taken out of the count. |
Waiting |
Answers ready for review and not yet judged. |
Feedback |
Readers' 👍 and 👎 on posted answers, and how many answers have any. Shown only as totals here, never beside an answer in review, so the votes cannot shape a verdict (spec 0027). |
It reports, it does not decide¶
status never says the gate is met, even at thirty. Whether the answers are worth posting is a
judgement about the verdicts, not the count, and lifting shadow mode is a code change made after
that judgement
(spec 0023
D7).
Flags¶
| Flag | Meaning |
|---|---|
--server <id> |
The server whose tally to report, by its discord.guilds[].space. Required when more than one server is configured, and implied when there is one. An unknown id is refused. |
Global flags are inherited from the root command.
See also¶
review: record the verdicts