fix(prompts): restore soft-deleted prompts on upsert match instead of skipping

[byteclimber]

Problem

upsertPrompts (src/support/prompts-storage.js) built its existence lookup without a status filter, so it matched soft-deleted rows — then dropped any soft-deleted match entirely:

if (match && match.status !== 'active') {
  continue; // no insert, no update, no restore
}

Re-importing an identical prompt silently no-oped while the API still returned 201 with created:0 / skipped:N. A brand left with only soft-deleted prompts could never re-create identical prompts — the import dedup matched the deleted ghosts and skipped.

Observed in production

Brand 019e92a2-…40 (ZEE): GET /prompts → total:0, GET /prompts?status=deleted → total:817. Every re-import returned 201 but wrote nothing. (The 817 rows were restored out-of-band; this PR fixes the cause.)

Fix

Replace skip-on-deleted-match with restore-on-match: a matched row now flows into the update path, which sets status back to 'active' (via row.status, default 'active') and refreshes its fields. Genuinely new prompts still insert. This makes re-import idempotent and self-healing for soft-deleted rows.

Tests

• Flipped the two unit tests that previously asserted the silent-skip behavior to assert restore-on-match (update back to active, targeting the existing row by uuid, no insert).
• Full prompts-storage suite passes (124 tests).

Risk

Low. Behavior change is confined to the deleted-match branch; the active-match and new-insert paths are unchanged. Restoring updates existing rows rather than inserting, so it cannot create duplicates.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!