[Feature]: Replace Storefront static home dashboard with registered Dashboard component

[roncodes]

Summary

Replace the static dashboard content in Storefront's home.hbs with the shared <Dashboard /> component and register Storefront dashboard widgets through the widget service, following the pattern used by Ledger.

Problem / Use Case

Storefront currently hardcodes its home dashboard with specific widget components in addon/templates/home.hbs. This prevents the Storefront dashboard from using the shared dashboard system for default widgets, dashboard persistence, widget selection, and extension-scoped dashboard behavior.

Ledger already uses the intended pattern: it renders <Dashboard /> from its home template and registers a dedicated dashboard id plus widgets in addon/extension.js.

Proposed Solution

Update Storefront so the home route renders the shared dashboard component with a Storefront-specific dashboard id and name, for example:

<Dashboard @defaultDashboardId="storefront" @defaultDashboardName="Storefront Dashboard" @extension="storefront" ... />

Register a dedicated Storefront dashboard in addon/extension.js using the widget service, and register Storefront widgets against that dashboard namespace. Existing home widgets should become registered dashboard widgets instead of being statically rendered in home.hbs.

Affected Area

• addon/templates/home.hbs
• addon/extension.js
• Existing Storefront widget components under addon/components/widget/*
• Dashboard/widget registration behavior from @fleetbase/ember-core and @fleetbase/ember-ui

Acceptance Criteria

• Storefront home renders the shared <Dashboard /> component instead of hardcoded widget components.
• Storefront registers a dedicated storefront dashboard through the widget service.
• Storefront widgets shown on the current home page are available as registered widgets for the storefront dashboard.
• Default Storefront dashboard widgets load automatically for a first-time user.
• Existing Storefront widgets continue to fetch metrics, orders, and customers correctly.
• The global dashboard widget registration behavior is preserved or intentionally limited to the appropriate Storefront widget subset.
• Frontend lint and Ember tests/build are run, or skipped validation is explained.

Implementation Notes

Use Ledger as the reference implementation:

• packages/ledger/addon/templates/home.hbs
• packages/ledger/addon/extension.js

Expected implementation shape:

• Replace the static widget list in addon/templates/home.hbs with <Dashboard />.
• Move Storefront widget definitions into a registerWidgets(widgetService) helper in addon/extension.js, matching Ledger's structure.
• Register widgetService.registerDashboard('storefront').
• Register Storefront widgets with widgetService.registerWidgets('storefront', widgets).
• Mark the intended default widgets with default: true.
• Keep widget ids stable where possible, especially storefront-key-metrics-widget.

Documentation Impact

No public documentation update appears required unless the implementation changes user-facing dashboard configuration behavior beyond replacing the internal Storefront home dashboard rendering.

API Reference Impact

No API reference update appears required. This should be an Ember/dashboard registration change only, with no Storefront API request or response schema changes.

[github-actions]

Understanding: replace Storefront’s static home dashboard with the shared <Dashboard /> component and register Storefront widgets through the shared widget service under a Storefront-specific dashboard id.

Likely affected Storefront areas:

• addon/templates/home.hbs: currently hardcodes <Widget::StorefrontMetrics />, <Widget::Orders />, and <Widget::Customers />.
• addon/extension.js: currently registers only storefront-key-metrics-widget under the global dashboard namespace.
• addon/components/widget/*: existing metrics/orders/customers widgets already fetch Storefront data through storefront/int/v1.

Repository checks:

• @fleetbase/ember-ui Dashboard supports @defaultDashboardId, @defaultDashboardName, and @extension.
• @fleetbase/ember-core widget service supports registerDashboard(name) and registerWidgets(dashboardName, widgets), with default: true widgets becoming default dashboard widgets.

Safe for agent implementation: yes, with approval. This looks like a small Ember-only dashboard wiring change. It should not require backend, auth, payment, customer data handling, or API behavior changes. The implementing agent should keep the change scoped and preserve/clarify whether storefront-key-metrics-widget remains globally registered or moves only to the storefront dashboard namespace.

Documentation impact for fleetbase/fleetbase.io: likely none if this only changes internal dashboard composition. Add docs only if user-facing dashboard configuration behavior changes beyond enabling the shared dashboard behavior for Storefront.

API reference impact for fleetbase/postman: none expected. No endpoint, payload, validation, auth, or response schema change is implied.

Suggested validation:

• pnpm lint
• pnpm test:ember
• pnpm build
• If tests are too broad or environment-dependent, at minimum run targeted component/dashboard tests and explain skipped validation.

Blocking questions: none from triage. Implementation should explicitly decide whether the default Storefront dashboard includes the current home widgets only, or also keeps storefront-key-metrics-widget as a default/selectable widget because it is already registered today.

AGENT_STATUS: ready_for_approval