Archived jobs can auto-claim after restore and should require explicit reopen

[hammerdirt-analyst]

• Problem
  • A locally restored archived/finalized job can implicitly regain
    assignment on the server and submit again without an explicit server-
    side reopen step.
• Current behavior
  • The server assignment/auth path allows auto-claim of an existing
    unassigned job during normal access.
  • For archived jobs, this is too permissive.
  • In practice, a restored local archived job can submit again and the
    server treats it as correction-mode finalization.
• Why this is a problem
  • Archived jobs should be closed by default.
  • Reopening archived work should require an explicit operator/admin
    action.
  • Silent auto-claim weakens lifecycle control and makes restore behavior
    ambiguous.
• Expected behavior
  • Assignment enforcement should not auto-claim jobs whose authoritative
    status is ARCHIVED.
  • Reopen/reassign should be explicit.
• Acceptance criteria
  • A finalized/unassigned archived job does not regain assignment
    implicitly from a restored local copy.
  • Active jobs still work normally.
  • Correction/reopen remains possible only through an explicit server-side
    action.

3. Admin auth model is operator-only for beta; long-term admin identity/auth
   still needs to be defined