Set up /inspect to just be summary statistics so you keep double-blind review, and use file manipulation commands on the shell command line if you need to.
@prnk28 HAVE YOU NOTICED HOW FAR AHEAD OF SCHEDULE THE REFACTORING GOT US? :D
The only thing we need to pick back up off of the redesign floor is tokens for reviewers so you can run reputation scores on them. Maybe if GET /inspect is given an optional argument like /inspect[?has=string] then it can search for files which contain those strings to make a 7x6 statistics table? Then you can just use the category names for strings and not have to list them all in your code!
@prnk28 ...the point being, that the ratio of reviewer identification token strings occurring in file sets with -e instead of -o (and something mumble mumble about -t we will figure out) is the same as the reviewer's agreement score, and, well, you probably need more statistics to figure out the reputation score as we originally designed it from that, but I'm pretty sure that can be part of GET /inspect?has=RevewByWikiGnome543 somehow.