Repository navigation
feat(activity): graph changes in each entity's, namespace's and recording's activity history - #134
Merged
Merged
Conversation
…ding's activity history Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DCB28xsaiCpiDKKk2JjRpe
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
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.
Requested by Adeel · project thread
Description
Before: a resource's activity history showed API requests, model calls, runs and audit log entries. Changes to the entity graph (#119) only showed in Routines › History.
After:
GET /api/v1/activityalso lists the graph changes that touched the resource.entity:<id>: every change to that entity.space:<id>: the namespace's curation (analysis results left out, since they would flood it).recording:<id>: what analysing that recording changed.Each row is a
changewith actiongraph.<op>, who made it, anddetailholding the version, how it was made (web, token, assistant, …) and why. Anyone who can read an entity's namespace can now readentity:<id>activity (before, only admins could). The activity panel labels these rows "Graph · Renamed · v12 · why", so the recording History tab and the namespace admin panel show them.Motivation and Context
This finishes the last item of the graph history plan in DEVLOG.md: graph events in the activity ledger from #114. No new tables or writes. The rows are read from
graph_eventand merged with the ledger at read time.Types of changes
Checklist:
tests/api/test_graph_history.py::test_graph_changes_in_activity_history. Full backend suite: 614 passed, 1 failed (the known LibreOffice conversion test). Frontend jest 679, tsc and lint pass.🤖 Generated with Claude Code
https://claude.ai/code/session_01DCB28xsaiCpiDKKk2JjRpe
Generated by Claude Code