Repository navigation
Report safe fields for rejected runtime identity - #613
Merged
Merged
Conversation
This was referenced Oct 13, 2026
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.
An archived runtime report rejected with runtime_target_mismatch currently provides no field-level diagnosis. Add fixed, allowlisted mismatched_fields to that skipped result and one safe JSON diagnostic line after the unchanged CLI first line.
Preserve the original comparison order, reject reason and exit 1; do not read later checkpoints after an earlier rejection. Report only the first failed comparison group, not a complete identity diff. Successful account-facts payloads and all original acceptance/rejection decisions remain unchanged. No expected/actual values, account or service mappings, report URI or credentials are logged.
Validation: 50 new field/type/order/CLI regressions (47 failed / 3 passed before implementation); 149 focused tests pass; required full suite 1419 passed / 5 existing skipped. Ruff, frozen lock and inert import checks pass. A finite synthetic baseline matrix made 320 project/publish comparisons across 160 cases with identical status/reason, first log line and successful POST payload; 144 safe diagnostics excluded private markers. Root reviewed the exact three-file diff; independent read-only review and final GitHub CI are tracked before merge.
Real per-slot report/configuration and deployment identity facts remain missing; this adds diagnosis for existing natural runs and does not establish their current cause or recovery. No workflows, private configuration, production pins, accounts, budgets, orders, notifications or strategy experiments are changed.
Refs QuantStrategyLab/QuantRuntimeSettings#632 and QuantStrategyLab/QuantRuntimeSettings#634.