Customer Record Audit Log (Changes & Deletions)

🔍 Problem Statement

As a publisher, there is no audit trail on customer records — when a record is changed or deleted, we cannot tell who did it, when, or from where. This makes dispute resolution, compliance auditing, and investigating discrepancies difficult.

💡 User Story

As a publisher, I want an audit log on the customer record covering both changes and deletions, so that I can trace every modification back to a collaborator and a timestamp.

🎯 Definition of Done (DoD)

• ✔ Given a customer record, when an admin views its audit log, then it shows a chronological list of changes — field changed, old value, new value, the collaborator (or system) responsible, and the timestamp.
• ✔ Given a customer record is deleted, when the deletion occurs, then it is recorded with the deleted customer, who performed it, the timestamp, and the method (manual/API) — plus a reason where available.
• ✔ At minimum, every Pelcro object a collaborator can create or modify exposes created_by, updated_by, and last_updated.
• ✔ Authorized users can view and search these events in the platform audit log, with retention aligned to the audit log policy.
• ✔ This change will impact UI / API — specifically the Customer detail page (Platform UI) and the audit-log resource (Core API).
• ✔ Limitations: history begins at rollout — changes made before the feature ships are not backfilled.