Write auditing: record api.entry_written (who-changed-what) - #2
Merged
Merged
Conversation
Listens to core's api.entry_written (Slice 3) and records each create/update/ delete over the API — the acting token, the collection (resource) and the entry (target = slug) — so the audit log is a full who-changed-what trail, not just failures. - migration 002_audit_target adds a `target` column (the entry slug). - AuditRecorder maps a write payload (collection -> resource, slug -> target) as well as the failure shape; INSERT writes target. - AuditView gains a Target column, an "Entry written" label, and a writes count in the 24h summary. Tests: recorder maps a write; view renders a write with its target; boundary test asserts the entry_written listener + both migrations register. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Consumes core's
api.entry_written(Write API Slice 3) so the audit log records who changed what over the API — the acting token, the collection, and the entry (slug) — not just failures.002_audit_targetadds atargetcolumn (the entry slug).AuditRecordermaps write payloads (collection→resource,slug→target) alongside the failure shape.AuditViewgains a Target column, an Entry written label, and a writes count in the 24h summary.Tests: recorder maps a write; view renders one with its target; the boundary test asserts the
entry_writtenlistener + both migrations register. This makesapi-advanceda consumer of the write-audit event.🤖 Generated with Claude Code