Create dashboard run on register_run - #41
Merged
Merged
Conversation
Admin list/detail read the runs table; registration alone must surface the run without a separate create_run. Bumps to 0.1.3. Co-authored-by: Cursor <cursoragent@cursor.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.
Summary
register_runnow upserts a dashboardrunsrow so Admin list/detail show the run without a separatecreate_run.__run_total__spend overlayscost_microson get/list; halt/clear keep the dashboard row in sync.__version__) so this can ship via the Release workflow after merge.Test plan
pytest tests/test_store.py::test_register_run_creates_dashboard_rowpassesregister_run(or run a client that only registers), confirm the run appears on Admin Dashboard without an explicitcreate_runmain(empty tag →v0.1.3) and confirm PyPIagent-tokenops==0.1.3Made with Cursor