Add publishing audit and provenance for humans, API clients, and agents

[khoinguyenpham04]

This Roadmap discussion mirrors #1682: Add publishing audit and provenance for humans, API clients, and agents.

Use this discussion to upvote the roadmap item and discuss priority, use cases, and product feedback. Keep implementation tracking, reproduction details, and PR-specific feedback on the source issue.

• Source issue: #1682
• Status: Open
• Labels: None
• Original author: ascorbic

Original Issue

Goal

Publishing-sensitive actions should leave enough provenance to answer who changed content, what path they used, and when.

Scope

Track provenance for humans in the admin, API clients, and agent/MCP workflows. Include publish, unpublish, schedule, unschedule, discard, restore, trash, and permanent delete.

Acceptance criteria

• Publishing-sensitive actions record actor identity and access path.
• Agent/API actions are distinguishable from admin UI actions.
• The audit data is available to admins or documented for follow-up UI work.
• The design does not expose secrets or bearer tokens in audit records.