Skip to content

Restore the prior identity integration for containment - #76

Merged
afflom merged 1 commit into
mainfrom
fix/contain-identity-v4
Nov 14, 2026
Merged

afflom merged 1 commit into
mainfrom
fix/contain-identity-v4

Conversation

@afflom

@afflom afflom commented Nov 14, 2026

Copy link
Copy Markdown
Member

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

  • All 20 reverted files exactly match Prism id on stitch alone: each app keeps its own device, nothing to deploy #73's first parent, 3587f34.
  • Canonical frame-sync check: 18/18 hashes.
  • Legacy identity verifier: 13/13 controls.
  • Exact session-loader fixtures: legacy accepted, v4 and expired ignored, zero storage writes.
  • Locked npm dependencies and frame publisher reproduce the previous frame hash d38b00b7f913db49dd5a5b5ff778a62a525405714bceb83ca676f3768b06b852 and panels hash 04106bff9d8f5ddf56d469f90d1ca09c8ca778d407a2ec97a967bf227a595104.

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.

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.
@afflom
afflom marked this pull request as ready for review November 14, 2026 02:37
@afflom
afflom merged commit e686941 into main Nov 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant