"New Manuscripts" (status 47) and "Manuscripts Returned to Editor-in-Chief" (status 48) above are this Section Editor's own, per-assignee view — narrowed to manuscripts where a ju_manuscript_reviewer row has assign_status = 14, reviewer = <this Section Editor>, review_locked = 0. Editor-in-Chief's own "Manuscripts Assigned to Section Editor" / "Manuscripts Returned Back from Section Editor" queues (documented in apps/legacy/spec/Editor-In-Chief/editor-in-chief-manuscripts-assigned-to-section-editor.md and its sibling) show the same statuses journal-wide, unnarrowed. Same underlying manuscripts, two different portals/scopes — not a duplicate page.

sec_editor.php's _action switch also defines jexp, config, in_house, print, galley_proof/glp_resp, tech_editor/tech_editor_p, page_designer/page_designer_p, payment/py_c, accept_sc, archived, the preprint/jpm/preprint_ready/preprint_returned family, invite/save_invite/invited, edb_report, withdraw, and final_reject cases. None of them is linked from __seceditor_qmenu(), __seceditor_pmenu() (both in template/rules.php), or the live (uncommented) part of the Classic default view — most sit inside a literal /* ... */ comment block in view/index.sec_editor.view.php (lines 265–338, 347–352) preserved from before Production Manager / Language Editor / Page Designer existed as their own modules, and the rest split two ways: jexp and edb_report are copy-paste leftovers from editor.php's own dispatch that are genuinely live there instead (editor.php:460 and editor.php:729 have real, working render-switch cases, byte-identical to the dead copies here; edb_report is additionally live in jexpert.php:588). config and in_house, by contrast, are dead everywhere: each exists only as a page-title-switch case (sec_editor.php:76/212, editor.php:103/260, jexpert.php:196 — jexpert.php has no config case at all) with no matching case in any of these three files' render switch, so visiting ?_action=config or ?_action=in_house on any of them just re-renders that file's own default dashboard. _action=pending_revise is additionally excluded because its query is byte-identical to revise above (same params, same output) — a duplicate title on an identical screen, not a materially different one.

(_action=track) has a page title and a working renderer (EditorManager::showManuscriptTracking) but no live link anywhere in this module — the one reference in view/manu.view.php is commented out and hardcoded to editor.php, not sec_editor.php. Kept as its own row (generic, shared-across-roles utility rather than a screen claimed by a sibling module) but flagged here as reachable only by a hand-typed URL; the equivalent content is otherwise surfaced inline as the "Submission History" AJAX tab inside Manuscript Detail.

has no sec_editor.php?_action= of its own — clicking a manuscript ID in any list above fires prepareToAccept() (inc/js/editor.js), an AJAX POST to request/editor.ajax.php that renders inline via the shared view/manu.view.php detail tabs and decision panel. Counted as its own row per the row-identification method's "distinct tab/ sub-view within an action" clause, since it is a materially different, role-gated screen (Section Editor's "Return Back Manuscript to Editor-in-Chief" decision plus reviewer assignment) — matching the same treatment given to the equivalent screen in the Editor-in-Chief / Executive Director / Production Manager modules.