It defines PMAdmin, used only by the old duplicate app trees under main/pm.php and mainn/pm.php (each a self-contained legacy snapshot that renders its screens inline in the same PHP file rather than via the view/*.view.php dispatch pattern — main/pm.php:9 and mainn/pm.php:8 both require_once '../class/pm.class.php', the same shared top-level class/pm.class.php file documented above, not a class/ or view/ directory of their own — out of this segment's scope per the taxonomy's "16 role-entry PHP files" source). The live, currently-routed apps/legacy/js/pm.php documented here instead instantiates EditorManager (class/editor.class.php, which extends ManuManager from class/manu.class.php) — the same class hierarchy editor.php uses, gated to ju_contact_role._role = 11.

has no ?_action= of its own — it is the editorManuActions action panel (available "make a decision" options, keyed off edt_r=11 in class/editor.class.php) plus the shared getManuscriptDetails manuscript-info panel (view/manu.view.php), both loaded into the modal defined in view/index.pm.view.php ($FUNCTION == 'modal') via request/editor.ajax.php's prepareToAccept task, opened by clicking a manuscript ID inside any of the queues above (every queue's list row shares the same javascript:prepareToAccept(<manu_code>) link, view/editor.view.php:4489). Counted as its own row per the row-identification method's "distinct tab/sub-view within an action" clause — it renders a materially different screen (decision form + full manuscript info) than the list rows it is launched from. But decision controls rarely render in practice: editorManuActions() has an unconditional early return (class/editor.class.php:73-76), before the edt_r switch runs, whenever getPMStatus() is 1 — i.e. the journal is listed in the preprint_ju setting and so delegates production to a Production Manager, the normal case for using pm.php at all (see apps/legacy/spec/Editor-In-Chief/editor-in-chief-in-publishing-menu-group.md) — and manu_status is one of 6,19,20,21,27,28,29,60,61,66,67. That blocked set covers every value in the edt_r==11 branch's own manu_status whitelist (6,19,20,21,27,28,29,33,60,61, class/editor.class.php:168-180) except 33, and 34 (Returned to Editor-in-Chief) was never in that whitelist either. So for a Production-Manager journal, only the New Manuscripts queue (manu_status=33) reliably surfaces the decision form through this modal — the other 9 queues above open it with only the manuscript-info panel.

pm.php's page-title switch has a case "guide" (setting the title to "Guide for Editor") and template/rules.php's __pm_qmenu() has a commented-out "Product Manager Guide" quick-menu link, but the module's actual render switch has no matching case "guide" — requesting pm.php?_action=guide falls through to the default branch and silently renders the Dashboard (just with a different page title). Unlike the Language Editor's and Technical Editor's genuine Guide pages, this never renders a distinct screen, so it is not counted as a row.

and Returned from Author After Editing Fixes are absent from the Modern-theme sidebar menu (__pm_pmenu()) and only appear on the Classic-theme Dashboard when their respective manuscript counts are greater than zero — but both remain directly reachable via _action=tech_au / _action=au_tech regardless of theme or count, per the row-identification method's "secondary/hidden actions count" clause. The same manu_status pair (60/61) is also exposed by the Language Editor module (tech_editor.php).

The root pm.php loads the shared inc/js/editor.js (same file editor.php uses), so its manuscript-detail panel can open journal/rev_questions.php, journal/rev_subject.php, and journal/sug_op.php the same way — documented in full at Editor-in-Chief. The mainn-hosted mirror (mainn/pm.php) instead loads its own mainn/inc/js/pm.js, whose showRevNote(ID) loads a host-local copy, mainn/rev_questions.php, at line 399 — both fold into the manuscript rows above rather than getting their own rows (route-file checklist gap, resolved 2026-07-02).