Add working row actions

Admin actions must mutate the database and survive refresh.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Implement row actions on the table. Requirements: a detail view (drawer or page) showing the full record; edit with a validated form that persists changes; disable/enable or delete with a confirmation dialog; optimistic or refetch-based UI update after each action; visible success toast and error handling on failure. Every action must persist - verify by refreshing after each one.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

View, edit, and disable/delete actions that persist to the database.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Edits persist after a full refreshDelete/disable asks for confirmationFailures show a visible error, and the row is not silently wrong

Do not continue if…

! Stats cards showing hardcoded numbers
! Tables rendering static arrays instead of database queries
! Delete/disable that only removes the row from local state
! Admin routes reachable by any logged-in user

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Actions only update local state and vanish on refresh. Wire each action to a backend mutation endpoint, await the result, and refetch or reconcile the table.