Order conversation artifact columns by their declared roles - #1141
Merged
Conversation
Puts the fields an examiner reads first at the front of every conversation artifact table: the event timestamp, any other date or time columns, then direction, sender, conversation label, message text and media. Remaining columns keep their existing relative order. The order is derived from the roles each artifact already declares in its data_views conversation block, so the table matches what LAVA renders. admin/scripts/check_conversation_column_order.py enforces it in the lint job and admin/docs/conversation_column_order.md records the convention. Row counts and values are unchanged; only column order moves. Co-Authored-By: Claude Opus 5 <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.
Orders the columns of every conversation artifact from the roles it already declares in its
data_viewsconversation block: the event timestamp, then any other date or time columns, then direction, sender, conversation label, message text and media. Everything else keeps its current relative order.admin/scripts/check_conversation_column_order.pyenforces the order and runs in the lint jobadmin/docs/conversation_column_order.mdwrites the convention downRow counts and values do not change, only column order. Artifacts whose headers are built at run time are reported as unchecked rather than passed.