STU-33 QA: Verify staff request-to-shortlist flow

[BAWES]

Objective

Verify that a staff user can complete a full request-to-shortlist flow on prod-clone data using the M5 pipeline delivered in PR #6 (STU-25).

Test scenarios

1. Assigned requests queue — Staff sees their assigned requests with status, owner, and next action
2. Candidate matching — Request detail shows skill-aligned candidates from prod-clone data
3. Suggestion creation — Staff can create a suggestion (note + suggestion record)
4. Invitation send/track — Invitation created and status transitioned (responded/declined)
5. Interview schedule/status — Interview scheduled with datetime validation, status transitions
6. Application transitions — Application shortlisted/rejected with optional notes
7. Candidate notes, tags, warnings — CRUD operations work correctly
8. Admin vs staff scoping — Admin sees all requests, staff only assigned ones

Pre-requisites

• Dev server running on port 3000
• Prod-clone data seeded in the database
• Valid staff and admin session cookies

Pass criteria

All 8 scenarios complete without console errors, 500s, or data corruption.

[BAWES]

Closed: The M5 pipeline (STU-25) shipped in PR #8, merged 2026-05-21. The staff request-to-shortlist flow is live in production.

Internal tracking: STU-33 is marked done.