fix(audit): align workflow run Phase 3E contract - #69
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Description
This change aligns the workflow-run audit contract with the Phase 3E ownership and retention model used by the latest workflow stack.
The previous contract still referenced obsolete grouping indexes, transitional rollback naming, and outdated runtime compatibility floors. That created a mismatch between what the audit tooling validated and what newer workflow services actually write and depend on.
This update brings the adapter and index inspection logic in sync with the current workflow-run schema by:
useridAs a result, audit output now reflects the real operational contract for workflow runs, reducing false positives during migrations and ensuring retention, cleanup, and project-scoped status queries are validated consistently across services.