Repository navigation
fix: clarify ITS feedback and skip unneeded mock recovery - #60
Merged
Merged
Conversation
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.
Summary
Verification
tests/dataset/test_real_data_smoke.py::test_committed_curated_files_match_the_processed_report. The processed ETL report lacks curated-input hashes; dataset artifacts are unchanged.Contract or safety impact
No API, generated-contract, dependency, backend controller behavior, routing-policy, or real signal actuation changes. All ITS responses and signal states remain simulated. Backend timing settings remain configurable; the selector describes the application defaults.
Follow-ups
Regenerate the local processed ETL report to restore curated-input hashes and clear the unrelated dataset check. Rebuild/restart the application after integration to load the corrections.