Release summaries
authos-module-v0
Add the experimental AuthOS module and reusable deterministic UI preview surface.
maintainer
The AuthOS module adds fake-adapter preview flows and deterministic UI without taking ownership of production auth behavior.
integrator
Reuse the AuthOS module UI for preview and planning while keeping provider execution host/integration owned.
authos-uplift-w1-to-w5
AuthOS Uplift Waves 1–4 — 9 atoms, 10 molecules, 10 organisms, and 5 templates added additively. All pre-existing exports preserved. AuthOsTemplate retained as deprecated alias.
maintainer
Waves 1–4 of the AuthOS UI uplift land additively on top of the Track 1/2 baseline. Phase 0 expands AuthOsScreen to 12 values, adds AuthRoute + AuthFlowStep types, and locks bundle-adapter template prop signatures via a compile-time contract test. Phase 1 adds 9 new atoms (AuthCodeInput, PasswordStrengthMeter, IdentityChip, DeviceTrustBadge, RiskScoreMeter, EmailDomainBadge, RecoveryCodeChip, PolicySnippet, OrgRoleChip). Phase 2 adds 10 new molecules (PasswordField, EmailField, OtpField, EmailVerificationBanner, MagicLinkRequestPanel, DeviceCard, ConsentSummary, OrgMemberCard, InviteByEmailComposer, SignInProvidersStrip). Phase 3 adds 10 new organisms (SignUpForm, PasskeySetupForm, EmailVerificationFlow, MagicLinkRequestForm, MagicLinkConsumeFlow, ForgotPasswordForm, ResetPasswordForm, AuditLogTable, InvitationsTable, SsoLandingChooser). Phase 4 adds 5 templates (AuthCenteredTemplate, AuthSplitTemplate, AuthFullScreenTemplate, AuthStepperTemplate, AuthDashboardTemplate) with .web/.native pairs; AuthOsTemplate kept as deprecated alias. All exports added to src/ui/index.ts additively. Waves 5 (hooks) and 6–7 (screens refactor / pages / dual-app wiring) deferred.
integrator
Import new atoms, molecules, organisms, and templates from @lssm-tech/module.auth-os. All existing imports continue to work unchanged. To migrate away from the deprecated AuthOsTemplate, replace it with AuthCenteredTemplate (same prop surface).
g005-google-calendar-oauth-booking
Add the least-scope Google Calendar OAuth, availability, known-ID booking, recoverable lifecycle, and fenced protected app-notification integration edge.
integrator
Hosts can bind G015 booking saga ports to a least-scope Google edge while keeping OAuth material tenant-encrypted, replacement identities exact, and app notifications atomically claimed and deduplicated.
managed-companyos-google-calendar-oauth-journey
Complete the protected Google Workspace Calendar OAuth journey from planning setup through topology configuration.
customer
Authorized administrators can begin Google Workspace Calendar setup from CompanyOS and return to calendar topology configuration after consent.
integrator
Google OAuth exchange returns its vault-bound opaque connection key so the host can safely continue the user journey without provider identity.