This is part of Thecore framework.

Per ADR 0001 (host app), any ApplicationRecord subclass that does not define its own RailsAdmin::ModelName concern still gets a sensible navigation_label and a real default icon (fa fa-table) in the RailsAdmin sidebar, instead of falling back to RailsAdmin's own unconfigured default (no group / no icon).

This is provided by ThecoreUiRailsAdminDefaultNavigationConcern (config/initializers/concern_default_navigation.rb), registered into ThecoreBackendCommons::DefaultModuleRegistry so it is included automatically into every model at class-definition time — no generated concern file required.

The default navigation_label reuses the exact same i18n key (I18n.t('admin.registries.label')) that the Thecore VS Code extension's addModel command already hardcodes into every freshly generated RailsAdmin::ModelName concern, so a model relying on this default reads identically, to an end user, to one whose generated-and-never-customized concern was kept around.

Field-level configuration is never defaulted — hide, sticky, configure :field, custom list/edit blocks, etc. stay exclusively in hand-written RailsAdmin::ModelName concerns. A model that already has its own concern is unaffected: its own navigation_label/navigation_icon (if set) and all field-level config still win over/apply alongside the default.

Temporary dependency note: this feature requires ThecoreBackendCommons::DefaultModuleRegistry, merged into thecore_backend_commons's release/3 branch but not yet published to RubyGems. The Gemfile pins a git source for this (github: "gabrieletassoni/thecore_backend_commons", branch: "release/3") until a real release ships — remove it once thecore_backend_commons cuts a version satisfying the gemspec's >= 3.4 constraint.

A built-in admin UI for sending Web Push test notifications. It lets you pick one or more active subscribers and fire a real notification immediately — useful for verifying the end-to-end VAPID setup without writing any code.

1. rails db:seed has run (VAPID keys generated in ThecoreSettings).
2. At least one browser has registered a push subscription (via the React client's subscribeToPush() — see the model_driven_api README).
3. The current RailsAdmin user can manage :push_message (or manage :all).

In RailsAdmin, click Push Notification Test in the top navigation bar (root actions area).

Click Send Test to dispatch. The backend creates one PushMessage per selected subscriber and calls PushNotificationService.dispatch for each. A flash notice reports how many notifications were sent.

The same flow available in the UI can be triggered from anywhere in the backend:

subscriber = PushSubscriber.active.find(42)
message = subscriber.push_messages.create!(
  title: "Hello",
  body:  "This is a test notification",
  url:   "https://yourapp.com/tasks/1",
  icon:  "https://yourapp.com/icon-192.png"
)
ThecoreBackendCommons::PushNotificationService.dispatch(subscriber, message)

Or via the REST API from a privileged client (see send_push in the model_driven_api README).