Prepare CLEVER Driver 0.1.14 Play update - #60
Merged
Conversation
Constraint: Additive app contract only; server deployment and sequence persistence remain externally owned. Rejected: Local-only sequence caching | it can overwrite newer server dispatch order without a route version contract. Confidence: high Scope-risk: narrow Directive: Keep openTime informational until route optimization semantics are separately approved. Tested: 39 targeted tests; TypeScript typecheck; Expo lint; expo install --check; git diff --check. Not-tested: Native or Expo bundle builds, APK/AAB, device behavior, server persistence, and web round-trip.
Constraint: Use the versioned DSV route-order contract without APK, bundle, device, or deployment work. Rejected: Keep drag order only in component state | refresh and partial completion would restore the server sequence. Confidence: high Scope-risk: moderate Directive: Send the complete stop permutation, retain the command id across the one network retry, and adopt only the authoritative response version. Tested: npm run check:workspace (151 tests), npm run lint, npx expo install --check, git diff --check. Not-tested: Deployed server transaction, physical-device interaction, native build, APK, or production delivery flow.
Align the app-side acceptance boundary to the existing server authority while preserving legacy IDs and the conventional email path, and identify the next Play candidate as 0.1.14. Constraint: Build on candidate b443158 without modifying the deployed server or reusing the vc13 APK. Rejected: Broaden the server email contract | The deployed server remains the authentication authority. Confidence: high Scope-risk: narrow Directive: Keep EAS remote versioning authoritative and verify the production AAB resolves to versionCode 22 before any Play upload. Tested: 11 targeted tests; check:workspace 151 tests and typecheck; lint; Expo dependency check; Android and iOS exports; git diff check. Not-tested: Production EAS AAB, Play upload, Play-signed device update, and released app-server authentication E2E pending downstream release stages.
Contributor
Author
|
Final release-review evidence for
Version/link contract checked read-only on 2026-09-08:
PR #60 remains open and unmerged. No replacement EAS build, Play upload, review submission, rollout, server change, or device action was performed. The existing |
Lift the pending-save signal to the workspace so back, settings, logout, and tab actions cannot unmount the editor before the authoritative result is shown. Refresh the canonical order contract documentation and reserve the next Play version code because product bytes changed after review.\n\nConstraint: Preserve the existing versioned server-order contract and the already uploaded versionCode 22 artifact.\nRejected: Global mutation overlay | It adds unnecessary state machinery for one bounded editor lifecycle.\nConfidence: high\nScope-risk: narrow\nDirective: Do not allow workspace navigation to outlive or hide a pending manual-order save result.\nTested: 35 targeted tests; TypeScript typecheck and 153 tests; Expo lint; expo install --check; git diff --check.\nNot-tested: Replacement EAS AAB, Play upload, and Play-signed physical-device update pending downstream steps.
OziinG
force-pushed
the
cc-240-driver-0114-update
branch
from
September 8, 2026 08:39
af3bf83 to
66e0447
Compare
Keep foreground and push refreshes from closing the sequence editor during the pending server mutation, then apply the queued refresh once the save lifecycle ends. Remove the remaining stale order-unit descriptions from the design source of truth.\n\nConstraint: Finish only the review-reported save lifecycle defect and existing DESIGN.md corrections.\nRejected: Global refresh queue | The existing effect dependency can safely defer and replay the latest refresh key without a new state layer.\nConfidence: high\nScope-risk: narrow\nDirective: Route refreshes must not replace sequence-editor state while its save promise is pending.\nTested: 32 focused screen/back-navigation tests; TypeScript typecheck; git diff check; stale DESIGN wording scan.\nNot-tested: New EAS build, Play upload, physical-device update, merge, review submission, and rollout intentionally excluded.
OziinG
force-pushed
the
cc-240-driver-0114-update
branch
from
September 8, 2026 08:41
66e0447 to
a981cc0
Compare
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.
Connects EVNSolution/clever-change-control#240 and #1.
Release scope:
Verification completed locally:
Release boundary: