Viking-UI 6.0 interlocks navigation across every DEML surface

Viking-UI 6.0 makes navigation a shared platform capability instead of a collection of surface-specific links. The Angular application, Astro marketing site, Django-rendered pages, and framework-neutral Web Components now consume the same auth-aware navbar, footer, call-to-action, and command-palette contracts. A sign-in or sign-out event can update each connected control without requiring every host application to implement its own session presentation logic.

The release also hardens how that state crosses application boundaries. DEML uses a persistent, origin-verified status bridge for live changes and a one-time session handoff when a signed-in user moves from the application to the marketing site. Protected destinations stay hidden from anonymous visitors, while authenticated links resolve to the dashboard, account, settings, and operational surfaces appropriate to the user.

For maintainers, packages/viking-ui/package.json is now the canonical version source for consumers and public documentation. Release automation synchronizes dependency ranges, lockfiles, pinned CDN examples, and generated marketing content, then rejects drift during local hooks and CI. That turns a version bump into one repeatable operation and prevents a stale consumer lockfile from blocking an otherwise healthy release.