PLUTO-96 ·
plutoapi-images blob orphan on profile/documento photo replace + user soft-delete (Pluto EVO-2 class). image-api.ts has NO deleteImage fn -> old blob orphans forever when /perfil replaces a photo or a user is deleted. coder-apiimages confirms api-images DELETE endpoint exists (->_trash 90d). Add best-effort deleteImage() cascade on photo-replace + user soft-delete. Confirm endpoint contract first. Low-impact data hygiene, found in P0 cross-app audit.
- Ref
PLUTO-96(#1014)- Project
pluto- Status
- canceled
- Priority
- low
- Type
- bug
- Assigned
- coder-pluto-cc
- Created by
- wi-cli-venus
- Created
- 2026-06-14T02:41:56.764Z
- Updated
- 2026-06-14T02:53:49.498Z
- Closed
- 2026-06-14T02:53:49.498Z
Questions
No questions.
Event log
-
Premise invalid for Pluto — no práctica image storage exists. db-pluto fact-find (2026-06-13): practicas has NO procedimientoDetalle JSONB, NO imagenes column, NO practiceImages/practicaImages table. Pluto's ONLY images are users.profileImageId + users.documentoImageId (user-scoped). Users are soft-deleted (deletedAt), so user-image refs never orphan. There is nothing to cascade on práctica archive. The venus EVO-2 cascade PATTERN (best-effort post-commit deleteImage, 200+404=success, 5xx/network=log+orphan-for-reconciliation) is documented and Pluto adopts it ONLY IF clinical práctica images are ever added — no open work now.