Repository navigation
Restore the prior identity integration for containment - #76
Merged
Merged
Conversation
Revert the identity integration introduced by #73 while preserving later template changes. Regenerate the canonical frame lock. No stored account, recovery-kit, project, or chat data is deleted.
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.
Scope
Temporarily restore the identity integration preceding #73. This is the exact inverse of that merge, plus canonical frame-lock regeneration. The later weight, service-worker and other template changes remain.
No account, recovery-kit, project or chat database is cleared or migrated. V4 session records are ignored by the restored loader, not deleted. Existing unexpired legacy sessions remain usable. This restores the complete frame, panels and assets rather than pointing at an unavailable old module.
Verified locally and independently
Full exact-head SDK and browser acceptance remain required. Deployment must verify the live pointer and full artifact. A pointer update does not recall already-open, offline-cached or explicitly pinned clients; there is no forced reload or data reset.