Replay retained logs on remote enrollment - #1034
Open
platypii wants to merge 1 commit into
Open
Conversation
platypii
force-pushed
the
fix-local-to-remote-history-sync
branch
from
August 31, 2026 06:09
8d3230e to
6ff8e1f
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
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
This completes the client side of the local-first upgrade path: a user can capture locally for days or weeks, then run
hyp remote login,hyp join, or choose remote sync in setup and have retained eligible history sent on the first released sync. Progress remains isolated if the user later enrolls with another server or organization.Server prerequisite
Requires hyparam/hypaware-server#387, which adds the stable organization identifier to bootstrap and refresh responses. That PR is merged, deployed, and validated against production. Production refresh returned
org: "hyperparam", with stable origin and organization across refresh. Validation used an empty temporaryHYP_HOME, so it uploaded no logs and did not touch the real local cache or configuration.Compatibility and privacy
Existing unscoped progress is adopted once for the current destination so already-acknowledged rows do not replay after upgrade. This relies on the confirmed field state that no existing users have changed organizations. New destinations receive separate state and replay retained eligible history.
The shared usage-policy seam is unchanged. Local-only rows, opted-out client rows, and privacy-ineligible datasets remain withheld.
Validation
npm teston currentmasterplus this commit: 5,302 passed, 1 skipped, 1 unrelated failure intest/core/cache-inplace-compaction.test.jsnpm run typecheckon currentmasterplus this commit: blocked by an unrelated existing error insrc/core/cache/maintenance.js:1345This branch does not modify either failing cache file. Before
origin/masteradvanced to v1.27.0, the full suite passed with 5,220 tests and typecheck passed.