fix: Support queue pause and resume in single-user mode

[Copilot]

Summary

The pause and resume session queue processor endpoints used AdminUser — which requires a valid Bearer token — causing 401s in single-user mode where no tokens exist. Changed both endpoints to use AdminUserOrDefault, consistent with other admin-only endpoints that already handle single-user mode correctly.

Changed in invokeai/app/api/routers/session_queue.py:

• PUT /{queue_id}/processor/resume: AdminUser → AdminUserOrDefault
• PUT /{queue_id}/processor/pause: AdminUser → AdminUserOrDefault

In single-user mode, AdminUserOrDefault falls back to a system admin identity. In multiuser mode, behavior is unchanged — an authenticated admin token is still required.

Related Issues / Discussions

QA Instructions

1. Run in single-user mode (default, multiuser=False)
2. Call PUT /api/v1/queue/{queue_id}/processor/pause and /resume without any Authorization header
3. Expect 200 responses instead of 401

Merge Plan

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[bug]: Support queue pause and resume in single-user mode</issue_title>
<issue_description>### Is there an existing issue for this problem?

• I have searched the existing issues

Install method

Invoke's Launcher

Operating system

Linux

GPU vendor

Nvidia (CUDA)

GPU model

No response

GPU VRAM

No response

Version number

feature/multiuser

Browser

No response

System Information

No response

What happened

The resume and pause queue endpoints use AdminUser which requires an authenticated token. In single-user mode (default deployment), no tokens exist, so these endpoints return 401. Other admin-only endpoints correctly use AdminUserOrDefault which falls back to a system admin in single-user mode.

What you expected to happen

I expect resume and pause endpoints to work correctly in single-user mode.

How to reproduce the problem

No response

Additional context

No response

Discord username

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [bug]: Support queue pause and resume in single-user mode #76

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[lstein]

Striaghtforward fix.