Skip to content

feat(kit): defer authenticated offline runtime - #92

Merged
rdlabo merged 2 commits into
mainfrom
feat/lazy-offline-remote-runtime
Aug 28, 2026
Merged

feat(kit): defer authenticated offline runtime#92
rdlabo merged 2 commits into
mainfrom
feat/lazy-offline-remote-runtime

Conversation

@rdlabo

@rdlabo rdlabo commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add an opt-in background resume mode for phased authenticated access
  • let route-scoped offline consumers initialize local storage first and start network/sync infrastructure after content readiness
  • preserve blocking initialization by default and keep deferred session preparation explicitly opt-in
  • redirect away from protected routes when a background resume receives an explicit 401/403

Compatibility

This is additive. Existing consumers retain blocking route activation and full runtime initialization. Package versions are intentionally unchanged. No migration is required.

Safety

Identity leases are rechecked across the readiness boundary. Stale background failures cannot clear or redirect a newer session. Classified transport failures keep verified access, while explicit authentication denial revokes access and redirects to the configured unauthorized route.

Verification

  • npm run lint
  • npx ng test kit --watch=false (53 files, 975 tests)
  • npm run prebuild:kit
  • consumer validation in SeatKeep: app/site lint, 118 app test files / 871 tests, site test, and CI production build
  • git diff --check

Performance scope

The change removes remote runtime discovery and synchronization from the opt-in authenticated route critical path. It does not claim a JavaScript bundle-size reduction.

@rdlabo
rdlabo merged commit ef4c596 into main Aug 28, 2026
13 checks passed
@rdlabo
rdlabo deleted the feat/lazy-offline-remote-runtime branch August 28, 2026 02:05
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