Keep comparison files usable on LAN and distinguish build options - #2856
Open
Chris0Jeky wants to merge 7 commits into
Open
Keep comparison files usable on LAN and distinguish build options#2856Chris0Jeky wants to merge 7 commits into
Chris0Jeky wants to merge 7 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
… into codex/2808-comparison-compat
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.
Manual comparison recording and legacy-file import now work when randomUUID or SubtleCrypto is unavailable, using random bytes for IDs and a compatible local checksum solely for deduplication. Production attribution includes resolved Vite build options, so different deployment bases produce distinct frontend fingerprints.
Related to #2808; stacked on #2852. Preserves explicit local export/import with no telemetry or randomized assignment.
Validation: 6,287 frontend tests passed (3 existing skips); 16 targeted tests; two Node checks against platform SHA256 and fingerprint variants; typecheck, lint, production build, doc links and governance passed. Chromium passed the record/import/deduplicate/export/reload journey with the unavailable browser APIs simulated. Actual default and /Taskdeck/ production builds emitted distinct fingerprints. After integrating current main, 71 combined comparison/context tests, typecheck and production build passed. Independent Luna review and its bounded integration check found no blocking defects.
Not verified: physical LAN devices or hosted deployment. Hosted checks are pending. No backend runtime changes.