Repository navigation
feat: per-junction graceful fallback for priority requests - #61
Merged
Merged
Conversation
A rejected, timed-out or expired request now puts only its unpassed targets into STANDARD_FALLBACK; the run keeps going and other junctions keep requesting priority. Adds the seeded MIXED ITS scenario, crossing_strategy telemetry and fallback_intersection_ids on completion. Fixes the timeout event reusing a feedback sequence number the controller later emits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The mock transport now mirrors the backend: failed requests fall back per junction (resumable timeline), the seeded MIXED scenario uses the same hash, and ticks/completions carry crossing_strategy and fallback_intersection_ids. The dashboard warns without ending the run, marks fallback junctions, distinguishes priority green from ordinary signals, tags finished fallback runs and offers the Mixed scenario with a seed, in English and Polish. Also counts seconds held at a priority stop line in the mock's travel time and translates the next-signal copy, both previously missing. Adds ADR 0015. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.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
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
A rejected, timed-out or expired priority request no longer cancels the run. Only that request's unpassed junctions switch to
STANDARD_FALLBACK: they are crossed on ordinary signals. Other junctions keep requesting priority and the run mode never changes (ADR 0015).MIXEDITS scenario: each request's outcome is drawn from a validatedits_outcome_seed. The backend and the mock use the same hash.crossing_strategyon intersection telemetry,fallback_intersection_idson completion, andits_outcome_seedon start requests. TheITS_*cancel reasons are no longer emitted.Verification
test_real_data_smoke.pycome from stale local processed data and also occur onmain.Contract or safety impact
Additive;
schema_versionstays"1.0". Clients must acceptMIXED. Simulation only: no real signal actuation.Follow-ups