Align driver routes with Ready execution lifecycle#129
Merged
Conversation
Constraint: Assignment must not advance a route beyond Ready. Rejected: Derive a fourth unfinished state from route date | It obscures the server lifecycle. Confidence: high Scope-risk: moderate Directive: Start and completion events remain the only driver lifecycle transitions. Tested: npm run check:workspace; npm run lint; npm run build; npm run check:native-release; git diff --check
5 tasks
Constraint: CI requires the current Expo-compatible patch versions. Rejected: Disable dependency alignment check | It would hide native compatibility drift. Confidence: high Scope-risk: narrow Directive: Use expo install when SDK compatibility expectations move. Tested: npx expo install --check; npm run check:workspace; npm run lint; npm run build; npm run check:native-release; git diff --check
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.
Summary
Traceability
Verification
Context
The service-context synchronization is tracked under change-control #225. Native preflight passed; Expo ownership, signing, and store approvals remain external release gates.