chore(deps): bump @dever-labs/ngx-mfe-broker from 0.1.4 to 0.2.0 in /angular-toolbar

[dependabot]

Bumps @dever-labs/ngx-mfe-broker from 0.1.4 to 0.2.0.

Release notes

Sourced from @​dever-labs/ngx-mfe-broker's releases.

v0.2.0

⚠️ Breaking Change

MfeStateService no longer falls back to in-memory defaults when a key is missing from localStorage.

Changed

• Fail-fast initialisation: if a key is missing from localStorage in a browser environment, an error is thrown immediately rather than silently using a default value
• Two-pass init: shell-provided initialState values are written to localStorage on first boot (if not already present), then signals are initialised exclusively from localStorage
• SSR / non-browser environments (no localStorage) still use the provided initialState value directly
• Removed unused internal defaults map from MfeStateService
• Updated docs to reflect fail-fast semantics and shell ownership of initial values

Why

The shell always loads first and owns all initial values. Any key missing from localStorage at init time indicates misconfiguration — surfacing it as an error is safer than returning a stale or wrong default.

Changelog

Sourced from @​dever-labs/ngx-mfe-broker's changelog.

[0.2.0] - 2026-07-16

Changed

• MfeStateService no longer falls back to in-memory defaults when a key is missing from localStorage. Instead it uses a two-pass init: first writes shell-provided initialState values to localStorage (if not already present), then reads from localStorage exclusively.
• If a key is missing from localStorage in a browser environment after the init write, an error is thrown immediately — misconfiguration fails loudly rather than silently.
• SSR/non-browser environments (no localStorage) still use the provided initialState value directly.
• Removed unused defaults map from MfeStateService.
• Updated docs to reflect fail-fast semantics and shell ownership of initial values.

Commits

• ec3cb49 feat!: fail-fast on missing localStorage keys, remove silent fallbacks (0.2.0)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)