[Feature] UI: Add archive action to CategoriesPage (admin-only)

[mpaulosky]

Summary

CategoriesPage.razor shows a grid with Edit actions but has no way to archive or delete a category. Once the API endpoint exists (see #120), this UI work adds the archive action — admin-only, with confirmation.

Context

The page uses RadzenDataGrid with inline edit. The action column currently has only an Edit button. Admin-only actions follow the pattern established in IssueDetailPage.razor (which uses ConfirmDialog for comment deletion).

Work Required

Archive Button

• Add an "Archive" button to the action column — visible only to admins (AuthorizeView Policy="Admin")
• Style consistently with existing buttons (Radzen ButtonStyle.Danger or an archive variant)
• Wire to a HandleArchive(string id) method

Confirmation Dialog

• Use the existing ConfirmDialog component (or equivalent) before submitting
• Text: "Archive '[CategoryName]'? It will no longer appear in issue forms."

API Call + Feedback

• Call CategoryApiClient.ArchiveAsync(id) (update the client to add this method)
• On success: remove the row from the grid without full reload (optimistic UI)
• On failure: show an error notification

Optional: Archived Filter Toggle

• Add a "Show archived" checkbox/toggle to the filter bar
• Pass to GetAllAsync to optionally include archived items (requires API param support)

Acceptance Criteria

• Archive button is visible to admin users only
• Confirmation dialog appears before archiving
• Confirmed archive calls DELETE API and removes item from grid
• Non-admin users cannot see or trigger the archive action
• Error state handled gracefully

Files

• src/Web/Components/Features/Categories/CategoriesPage.razor
• src/Web/Components/Features/Categories/CategoryApiClient.cs

Depends On

• [Feature] API: Add DeleteCategory handler and archive endpoint #120 (API: Add DeleteCategory handler and archive endpoint)

[github-actions]

🏗️ Squad Triage — Aragorn (Lead)

Issue: #124 — [Feature] UI: Add archive action to CategoriesPage (admin-only)
Assigned to: Legolas (Frontend Dev)
Reason: Issue relates to frontend/UI work

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

Team roster:

• Aragorn (Lead) → label: squad:aragorn
• Legolas (Frontend Dev) → label: squad:legolas
• Sam (Backend Dev) → label: squad:sam
• Gimli (Tester) → label: squad:gimli
• Boromir (DevOps) → label: squad:boromir
• Frodo (Tech Writer) → label: squad:frodo
• Gandalf (Security Officer) → label: squad:gandalf
• Ralph (Work Monitor) → label: squad:ralph
• @copilot (🤖 Coding Agent) → label: squad:@copilot
• @copilot (Coding Agent) → label: squad:copilot

To reassign, remove the current squad:* label and add the correct one.

[github-actions]

📋 Assigned to Legolas (Frontend Dev)

Issue: #124 — [Feature] UI: Add archive action to CategoriesPage (admin-only)

Legolas will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Legolas, work on issue #124

[github-actions]

📋 Marked as release:backlog — assign a release target when ready.