The Editor-in-Chief manuscript detail view (opened by clicking any manuscript ID from any queue above) is not a separate _action= route in legacy: it loads via AJAX (request/editor.ajax.php, task=showManusriptDetails → EditorManager::preAssignReviewers → view/editor.view.php → ManuManager::getManuscriptDetails → view/manu.view.php) into the current queue page, keyed by manu_code. The editor.php?_action=manuscript&tab=… Legacy Ref/Route pattern used for the nine "Manuscript Detail" rows below is a normalized representation (per the approved template) of that tabbed panel, not a literal query string found in the code.

Three more manuscript-detail popups fold in here rather than getting their own rows (route-file checklist gap, resolved 2026-07-02): Reviewer's Note/Questionnaire (journal/rev_questions.php, opened by showRevNote(ID) loading ./journal/rev_questions?edt=1&revNote=...), Assign-by-Subject picker (journal/rev_subject.php, opened by showEdSubs(st) loading ./journal/rev_subject?rev=...&edt_r=...), and Suggest Opponent Reviewer (journal/sug_op.php, opened by showSugOpRev(ID, lbl) loading ./journal/sug_op?edt=...) — all three are raw filename targets fetched by inc/js/editor.js into the manuscript-detail modal, never an editor.php _action= branch, which is why they weren't traced by this design's row-identification method on the first pass. editor.js is shared code: it is also loaded by sec_editor.php (Section Editor), pm.php (Production Manager), jexpert.php (Executive Director), and sp_editor.php (Specialist Editor), so the same three popups are reachable from those modules' manuscript-detail panels too — documented once here rather than duplicated on every sibling page. The Reviewer's Note/Questionnaire popup is additionally shared by reviewer.js (Reviewer role, own showRevNote), te.editor.js (Technical Editor), and edb.review.js (Editorial Board, which also reuses the Assign-by-Subject picker) — see the one-line cross-references on those modules' own pages.

Rows intentionally omitted as non-rows (per the row-identification method): _action=config (has a page-title case but no case in the content switch — falls through to the default dashboard, no distinct render), _action=in_house (same — title-only, dead), _action=withdraw and _action=final_reject (both exist in editor.php's switch but are unreachable from any Editor-in-Chief menu/link — withdraw is only ever linked from author.php; both are subset views already covered by "Deleted / Withdrawn Manuscripts" and "Rejected Manuscripts"), and _action=pending_revise (identical query and view to "Manuscripts Need Revision" — same status set, no menu link, not a materially different screen). imps (impersonate, reached from the "Users List" icon row) is a redirect handler with no rendered screen of its own (ContactAdmin::impersonateAsUser() ends in __redirect("./contacts?_action=profile")) and is likewise excluded. _action=portal_login (the "Login Customer Portal (CRM)" quick-menu entry — __editor_qmenu, template/rules.php:429-433) is likewise a redirect handler with no rendered screen of its own — CrmManager::PortalLogin() (class/crm.class.php:586-609) only calls header("Location: ...") to an external CRM portal (portal.sinaweb.net / portal.ejournalplus.com), with no HTML output — and is excluded for the same reason (the Manager module excludes this identical action for the same cause; see publishing-workflow/manager.html). resetpass, by contrast, is a GET link with no redirect that renders a distinct confirmation panel (user name/username/new password) — see the "Reset User Password (confirmation panel)" row below.

"Invite Manuscript" / "Invited Manuscripts" render real, distinct screens (inviteManuscriptForm() / getInvitedManuscripts()) but their menu links are commented out in the Classic-theme navigation (view/index.editor.view.php) and absent from the Modern-theme menu builder (__editor_pmenu) — included here as dormant-but-functional routes, per the "secondary/hidden actions count if they render a distinct screen" rule.

"Manuscripts Sent to Production Manager (delegated / preprint variant)" (_action=preprint) is properly linked in the Classic theme when production is delegated (Mode A), but in the Modern/admin theme's menu builder (__editor_pmenu in template/rules.php) its menu slot is immediately overwritten by "Ready to Send to Production Manager", making it unreachable from that theme's menu — a documented legacy inconsistency (see editor-in-chief-menu-visibility-rules.md, "A duplicated ‘Sent to Production Manager’ variant is dead code"). The route itself still renders a distinct screen (a different manuscript-status set than the consolidated "jpm" queue), so it is listed as its own row.

"Manuscripts Sent to Author for Editing Problems" / "…Returned by Author After Fixing Editing Problems" (_action=tech_au / _action=au_tech, statuses 60/61) are not documented in the Editor-in-Chief menu-overview/menu-visibility spec files, but are confirmed present and linked in the Classic-theme navigation (view/index.editor.view.php), immediately after the Language Editor queues.

Per spec (editor-in-chief-menu-visibility-rules.md, "Inconsistency States"), "Manuscripts with Technical Editor's Decision" has an inverted (likely defective) visibility condition — it is shown only when its count is zero and hides as soon as any manuscript reaches that status, the opposite of every other count-gated queue. The row is listed here because the underlying route still renders the list; the menu-visibility defect is a Phase D/E concern, not a reason to omit the page.

"Incomplete Submissions" is not part of the documented menu-group map; per spec it "renders at the very bottom of the EIC primary navigation, immediately after ‘Deleted Manuscripts’" — it is placed directly after "Deleted / Withdrawn Manuscripts" here for that reason, ahead of "Archived Manuscripts" and "Manuscripts with Comment" (which the spec groups under the same "Rejected/Deleted" heading but does not place the incomplete-submissions item inside).

'Incident Repair Email — Authors' / 'Incident Repair Email — Reviewers' (_action=incident_repair / _action=incident_repair&rvv) render real, distinct screens (ReparManuFiles::eicReparirEmailForm() / reviewrRepairForm()) but, like Invite/Invited above, have no live UI entry point — their only link is commented out in the Classic-theme toolbar (view/index.editor.view.php:103-105) and the action is absent from the Modern-theme's quick menu (__editor_qmenu, template/rules.php:392-449) — included here as dormant-but-functional routes under the same rule.