[BUG]: DELETE /api/checklists/{uuid} returns "List not found" despite checklist existing

[alienos]

Describe the bug

Description:
When using the API key authentication (x-api-key header), the DELETE endpoint for checklists always returns {"error":"List not found"} regardless of whether the checklist exists and belongs to the authenticated user.

Steps to reproduce:

1. Create a new checklist via POST /api/checklists (works fine)
2. Verify the checklist exists via GET /api/checklists (returns the checklist with valid UUID)
3. Attempt to delete via DELETE /api/checklists/{uuid} (fails with "List not found")
4. Adding items to the checklist via POST /api/checklists/{uuid}/items works fine

Expected behavior:
DELETE should remove the checklist or return appropriate error if user lacks permission.

Actual behavior:
DELETE /api/checklists/{uuid} returns {"error":"List not found"} even for freshly created checklists owned by the authenticated user.

Environment:

• Jotty version: 1.21.1 (docker self-hosted)
• Authentication: API key (x-api-key header)

Notes:

• GET /api/checklists works correctly
• POST /api/checklists creates checklists successfully
• DELETE /api/notes/{uuid} for notes works fine
• Only the checklists DELETE endpoint appears broken

Steps to Reproduce

Steps to reproduce:

1. Create a new checklist via POST /api/checklists (works fine)
2. Verify the checklist exists via GET /api/checklists (returns the checklist with valid UUID)
3. Attempt to delete via DELETE /api/checklists/{uuid} (fails with "List not found")
4. Adding items to the checklist via POST /api/checklists/{uuid}/items works fine

Expected behavior:
DELETE should remove the checklist or return appropriate error if user lacks permission.

How do you run Jotty?

Docker

Jotty Version

1.21.1

Checklist

• I have searched across other issues to make sure this bug has not been already reported.

[fccview]

Oh no.
This is so frustrating, sorry about that, I knew about this and thought I fixed it and absolutely moved on from it 🤦

yes, it has been an issue for ages, out of curiosity for now, would you be able to try giving it a checklist slug rather than uuid? (e.g. /api/checklists/checklist-name-here)

if it works you can at least continue developing what you are until I officially fix this and then you can change it to the uuid. If it doesn't you may need to be a little patient until I sort it all out

[fccview]

So, this will be fixed once I fully move away from id+category, may take a little bit.. hang in there 😆