Data pruning endpoint

[jekuaitk]

Adds a admin-only POST endpoint:

POST  /api/v1/prune/chats?days=N&dry_run=&limit=

Deletes chats that have not been updated for a given number of days. Requires an admin token
(JWT or API key) in the Authorization: Bearer header — non-admin callers get 401.

Parameter	Type	Required	Description
days	int ≥ 1	yes	Retention threshold: any chat whose updated_at is older than days days is a candidate for deletion.
dry_run	bool	no (default false)	When true, only counts the matching chats and deletes nothing.
limit	int ≥ 1	no (default unlimited)	Caps how many chats are processed in this call. Candidates are processed oldest-first, so repeated limited calls work through the backlog chronologically.

Pinned chats are always spared, regardless of age. Archived chats are pruned like any other.
Deleting a chat also removes its messages and shared-link copies, and tags that end up unused
by any of the affected user's remaining chats are cleaned up.

Examples

# Preview what a 180-day retention policy would delete
curl -X POST '.../api/v1/prune/chats?days=180&dry_run=true' -H "Authorization: Bearer $TOKEN"

# Prune at most 500 chats
curl -X POST '.../api/v1/prune/chats?days=180&limit=500' -H "Authorization: Bearer $TOKEN"

[cableman]

What about files user may have uploaded into chats? Do the project not have an "hook"/"function" to delete chats that purge all data involved. It exists in the front end as delete chat call?

UPDATE: Never mind

[cableman]

What is cutoff? magic number

[jekuaitk]

Added comment explaining!