@vc-shell/vc-app-skill 2.0.1 → 2.0.3-pr222.ba0d3c5

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## [2.0.3](https://github.com/VirtoCommerce/vc-shell/compare/v2.0.2...v2.0.3) (2026-04-30)
+
+**Note:** Version bump only for package @vc-shell/vc-app-skill
+
+## [2.0.2](https://github.com/VirtoCommerce/vc-shell/compare/v2.0.1...v2.0.2) (2026-04-27)
+
+**Note:** Version bump only for package @vc-shell/vc-app-skill
+
 ## [2.0.1](https://github.com/VirtoCommerce/vc-shell/compare/v2.0.0...v2.0.1) (2026-04-24)
 
 ### Features

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vc-shell/vc-app-skill",
-  "version": "2.0.1",
+  "version": "2.0.3-pr222.ba0d3c5",
   "description": "AI coding skill for scaffolding and generating VirtoCommerce Shell applications. Works with Claude Code, OpenCode, Gemini, Codex, Cursor.",
   "bin": "./bin/install.cjs",
   "files": [

package/runtime/VERSION

@@ -1 +1 @@
-2.0.1
+2.0.3

package/runtime/knowledge/docs/_BUILD_HASH.md

@@ -1 +1 @@
-Synced from framework at commit 5f8005c08 on 2026-04-24T08:05:31.316Z
+Synced from framework at commit d658f5b4c on 2026-04-30T07:59:28.391Z

package/runtime/knowledge/docs/injection-keys.docs.md

@@ -19,22 +19,20 @@ This centralized approach has several advantages:
 
 ### Blade Navigation
 
-| Key                         | Type                                   | Description                                  |
-| --------------------------- | -------------------------------------- | -------------------------------------------- |
-| `NavigationViewLocationKey` | `BladeVNode`                           | Current blade VNode location in navigation   |
-| `BladeDescriptorKey`        | `ComputedRef<BladeDescriptor>`         | Current blade descriptor metadata            |
-| `BladeBackButtonKey`        | `Component \| undefined`               | Custom back button component for a blade     |
-| `BladeDataKey`              | _(from blade-navigation types)_        | Data passed between parent/child blades      |
-| `BladeContextKey`           | `ComputedRef<Record<string, unknown>>` | Blade-exposed context for widgets/extensions |
-| `BladeRoutesKey`            | `BladeRoutesRecord[]`                  | Registered blade routes                      |
-| `InternalRoutesKey`         | `BladeRoutesRecord[]`                  | Internal framework routes                    |
+| Key                  | Type                                   | Description                                  |
+| -------------------- | -------------------------------------- | -------------------------------------------- |
+| `BladeDescriptorKey` | `ComputedRef<BladeDescriptor>`         | Current blade descriptor metadata            |
+| `BladeBackButtonKey` | `Component \| undefined`               | Custom back button component for a blade     |
+| `BladeDataKey`       | _(from blade-navigation types)_        | Data passed between parent/child blades      |
+| `BladeContextKey`    | `ComputedRef<Record<string, unknown>>` | Blade-exposed context for widgets/extensions |
+| `BladeRoutesKey`     | `BladeRoutesRecord[]`                  | Registered blade routes                      |
+| `InternalRoutesKey`  | `BladeRoutesRecord[]`                  | Internal framework routes                    |
 
 ### Notifications
 
-| Key                        | Type                                | Description                                 |
-| -------------------------- | ----------------------------------- | ------------------------------------------- |
-| `NotificationTemplatesKey` | `NotificationTemplateConstructor[]` | Registered notification template components |
-| `NotificationStoreKey`     | `NotificationStore`                 | Shared notification store singleton         |
+| Key                    | Type                | Description                         |
+| ---------------------- | ------------------- | ----------------------------------- |
+| `NotificationStoreKey` | `NotificationStore` | Shared notification store singleton |
 
 ### Services
 
@@ -42,7 +40,6 @@ This centralized approach has several advantages:
 | ------------------------------- | ----------------------------- | ------------------------------ |
 | `WidgetServiceKey`              | `IWidgetService`              | Widget registration and lookup |
 | `DashboardServiceKey`           | `IDashboardService`           | Dashboard widget management    |
-| `GlobalSearchKey`               | `GlobalSearchState`           | Global search state            |
 | `MenuServiceKey`                | `MenuService`                 | Main navigation menu           |
 | `SettingsMenuServiceKey`        | `ISettingsMenuService`        | Settings sidebar menu          |
 | `AppBarWidgetServiceKey`        | `IAppBarWidgetService`        | App bar widget slots           |
@@ -81,14 +78,23 @@ This centralized approach has several advantages:
 
 ### Legacy Aliases (Deprecated)
 
-| Deprecated                    | Use Instead                 |
-| ----------------------------- | --------------------------- |
-| `navigationViewLocation`      | `NavigationViewLocationKey` |
-| `BladeDescriptor`             | `BladeDescriptorKey`        |
-| `NotificationTemplatesSymbol` | `NotificationTemplatesKey`  |
-| `BLADE_BACK_BUTTON`           | `BladeBackButtonKey`        |
-| `TOOLBAR_SERVICE`             | `ToolbarServiceKey`         |
-| `EMBEDDED_MODE`               | `EmbeddedModeKey`           |
+| Deprecated          | Use Instead          |
+| ------------------- | -------------------- |
+| `BladeDescriptor`   | `BladeDescriptorKey` |
+| `BLADE_BACK_BUTTON` | `BladeBackButtonKey` |
+| `TOOLBAR_SERVICE`   | `ToolbarServiceKey`  |
+| `EMBEDDED_MODE`     | `EmbeddedModeKey`    |
+
+### Removed Keys (No Replacement)
+
+These keys existed in v1.2.3 but have been removed from the framework entirely. There is no drop-in symbol replacement.
+
+| Removed                       | Notes                                                                          |
+| ----------------------------- | ------------------------------------------------------------------------------ |
+| `navigationViewLocation`      | Internal framework concern — no public replacement                             |
+| `BladeInstance`               | Use `useBlade()` composable, or `inject(BladeDescriptorKey)`                   |
+| `NotificationTemplatesSymbol` | Template system replaced by `NotificationStoreKey` + `useBladeNotifications()` |
+| `GlobalSearchKey`             | Internal concern now — no public replacement                                   |
 
 ## Usage Examples
 

package/runtime/knowledge/docs/shell/dashboard/draggable-dashboard/draggable-dashboard.docs.md

@@ -122,6 +122,8 @@ function resetLayout() {
 - **Widget registration**: Widgets must be registered via `useDashboard().registerWidget()` before the dashboard mounts. The component reads the widget registry and creates grid items for each.
 - **markRaw requirement**: Widget components must be wrapped in `markRaw()` when registering to prevent Vue from making them reactive (which would cause performance issues with the grid system).
 - **Responsive behavior**: On mobile viewports, widgets stack vertically in a single column. Drag-and-drop is disabled on touch devices for better usability.
+- **Module-ready gate**: When the host injects `ModulesReadyKey` (provided by `@vc-shell/mf-host`'s `registerRemoteModules`), the grid is held back until remote modules finish installing. This prevents widgets from mounting before their owning module's `defineAppModule.install` has merged its locales into vue-i18n — which would render translation keys instead of translated strings. Hosts without Module Federation (or tests/Storybook) inject nothing, and a fallback `ref(true)` keeps behavior unchanged.
+- **Loading skeletons**: While `ModulesReadyKey` is `false`, the dashboard renders a CSS-grid of pulsing placeholder cards instead of an empty container. Card sizes are restored from the last persisted layout in `localStorage` (so returning users see placeholders matching their real widgets); first-time visitors get a default layout of four 6×6 placeholders. Animations respect `prefers-reduced-motion`.
 
 ## Tips
 

package/runtime/knowledge/docs/ui/components/molecules/vc-field/vc-field.docs.md

@@ -196,6 +196,15 @@ For read-only display, `VcField` is lighter and cleaner than a disabled `VcInput
 
 The `type` prop affects rendering, not validation. Setting `type="email"` does not validate the email format -- it only renders the value as a `mailto:` link. For input validation, use VcInput with validation rules.
 
+## Horizontal Layout Without Label
+
+In `orientation="horizontal"` the component reserves the `aspectRatio[0]` track even when `label` is omitted. This keeps a column of `VcField`s aligned with their labeled siblings in a form grid. Use vertical orientation if you do not want this reservation.
+
+```vue
+<!-- Reserves the label column to align with sibling fields -->
+<VcField orientation="horizontal" :aspect-ratio="[1, 2]" model-value="No label" />
+```
+
 ## Related Components
 
 - [VcInput](../vc-input/) -- editable text field (use instead when user input is needed)

package/runtime/knowledge/docs/core/composables/usePlatformLocaleSync/usePlatformLocaleSync.docs.md

@@ -1,28 +0,0 @@
-# usePlatformLocaleSync
-
-One-way reactive bridge from the VirtoCommerce platform's locale storage key (`NG_TRANSLATE_LANG_KEY`, set by AngularJS + angular-translate) to the shell's language service.
-
-Call this composable only when the shell runs embedded inside the platform — `useShellBootstrap` invokes it automatically when `options.isEmbedded === true`. In standalone mode the shell owns its own locale via `VC_LANGUAGE_SETTINGS`, and this composable should not be used.
-
-## When to Use
-
-- Never call directly from feature code. This is a framework-internal sync primitive.
-- It is invoked once per `VcApp` mount from `useShellBootstrap`.
-
-## Behaviour
-
-- Reads `localStorage["NG_TRANSLATE_LANG_KEY"]` via VueUse's `useLocalStorage`, which subscribes to `storage` events for cross-tab reactivity.
-- On setup, if the value is non-empty, calls `LanguageService.setLocale(value)`. `setLocale` normalises the value (e.g. `en-US` → `en-us`), falls back to `en` for unsupported locales, updates `vue-i18n`, reconfigures `vee-validate`, and persists to `VC_LANGUAGE_SETTINGS`.
-- On subsequent changes of the platform key, re-applies the value.
-- Skips empty strings (platform clearing the key does not blank the shell locale).
-- Skips values equal to `currentLocale` to avoid redundant re-configuration.
-
-## How It Works
-
-`useLocalStorage("NG_TRANSLATE_LANG_KEY", "")` returns a `Ref<string>` that VueUse keeps in sync with `localStorage` and the DOM `storage` event (which fires in tabs other than the writer). The composable applies the current ref value once synchronously and then registers a `watch` on it; any cross-tab mutation flows through the ref into `setLocale`.
-
-The watcher is bound to the active effect scope (typically `VcApp`'s setup). When `VcApp` unmounts, the watcher stops; `useLocalStorage` cleans up its own `storage` listener.
-
-## Relationship to `VC_LANGUAGE_SETTINGS`
-
-The sync is strictly one-directional. `setLocale` writes to `VC_LANGUAGE_SETTINGS` as a side effect, but this composable never writes to `NG_TRANSLATE_LANG_KEY`. In embedded mode the in-shell `LanguageSelector` is unreachable (it lives inside `UserDropdownButton`, which is hidden when `isEmbedded` is `true`), so there is no competing writer from the shell side.