Each puzzle sorted by where it stands. Needs work: a big part (a clue list, the key, a page) is missing or broken in a way the proof page can't fix; the card says which part, the stage to restart it from, and the link that starts it. Ready for review: every part is there, or a gap is confirmed and labelled; doubts the proof page can settle are listed, and a missing title or byline is asked of the reviewer. Reviewed: a person said Ready or Not ready (only Ready puzzles are imported). Set aside: in scope, but a person decided it isn't a priority now (the card says why); it keeps what it was waiting on, and stays listed so what's missing is visible. Next on the proof page walks the list shown here.
Drawn from the records only: this puzzle's region boxes (what its parts were read from) and its key as assembly cut it; other puzzles in grey; the harvest's answer grids dashed. Hover a box for the milestone it came from.
Batch tools: the agent's pass, spend, the Notes rule, the Editor from the masthead, import
Notes rule
Which labelled lines (kept on the proof page) go in gxd's Notes, for the whole publication. Tick labels to see every line the rule would take, then save it.
Editor, from the masthead
Each issue's staff box, read by the page OCR (the masthead milestone). Tick the roles whose name is a puzzle's Editor, in order: the first one an issue's masthead lists is its puzzles' Editor, and the proof page shows it with this crop. An issue that lists none of them gets no Editor. Save the rule for the whole publication: this run's proof packets are made again with it (markup only, about half a minute), and later runs take it too.
Import
The puzzles that ship (your Ship or Ready; otherwise one reviewer's Ready and nobody's Not ready), as they would go into the publication repo's xd/, ids assigned last. Held ones say why.