@fias/create-fias-plugin 1.8.0 → 1.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fias/create-fias-plugin",
3
- "version": "1.8.0",
3
+ "version": "1.9.1",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
@@ -1,4 +1,4 @@
1
- <!-- fias-sdk-guide-version: 2.16.0 -->
1
+ <!-- fias-sdk-guide-version: 2.17.0 -->
2
2
 
3
3
  # FIAS Plugin Development Guide
4
4
 
@@ -784,7 +784,7 @@ There are two declaration lanes, one shape:
784
784
  ```tsx
785
785
  import { useFiasAIActions } from '@fias/arche-sdk';
786
786
 
787
- useFiasAIActions({
787
+ const { openAssistant } = useFiasAIActions({
788
788
  description: 'Once a document is open, the assistant can rotate its pages.',
789
789
  actions: [
790
790
  {
@@ -815,6 +815,7 @@ Rules that matter:
815
815
  - `requiresConfirmation: true` makes the assistant ask the user before dispatching. It escalates only — nothing can skip a confirmation the platform requires.
816
816
  - Manifest actions win id collisions with runtime ones; the merged list is capped at 50.
817
817
  - The assistant is not present in the builder preview or the dev harness — declarations are accepted but nothing dispatches until the published plugin runs with the Fias AI window.
818
+ - **`openAssistant()`** (the hook's return) asks the HOST to open the Fias AI panel — use it for a contextual affordance (an empty-state "Ask Fias AI to get started" button). The host already shows its own "Works with Fias AI" chip, debounces your requests, and ignores them for a while after the user closes the panel — never call it in a loop or on mount. There is deliberately no way to pass text along: the assistant's input belongs to the user.
818
819
 
819
820
  ### `useArcheAssets()` — Contributor-published asset library
820
821
 
@@ -1,4 +1,4 @@
1
- <!-- fias-sdk-guide-version: 2.16.0 -->
1
+ <!-- fias-sdk-guide-version: 2.17.0 -->
2
2
 
3
3
  # FIAS Plugin Development Guide
4
4
 
@@ -784,7 +784,7 @@ There are two declaration lanes, one shape:
784
784
  ```tsx
785
785
  import { useFiasAIActions } from '@fias/arche-sdk';
786
786
 
787
- useFiasAIActions({
787
+ const { openAssistant } = useFiasAIActions({
788
788
  description: 'Once a document is open, the assistant can rotate its pages.',
789
789
  actions: [
790
790
  {
@@ -815,6 +815,7 @@ Rules that matter:
815
815
  - `requiresConfirmation: true` makes the assistant ask the user before dispatching. It escalates only — nothing can skip a confirmation the platform requires.
816
816
  - Manifest actions win id collisions with runtime ones; the merged list is capped at 50.
817
817
  - The assistant is not present in the builder preview or the dev harness — declarations are accepted but nothing dispatches until the published plugin runs with the Fias AI window.
818
+ - **`openAssistant()`** (the hook's return) asks the HOST to open the Fias AI panel — use it for a contextual affordance (an empty-state "Ask Fias AI to get started" button). The host already shows its own "Works with Fias AI" chip, debounces your requests, and ignores them for a while after the user closes the panel — never call it in a loop or on mount. There is deliberately no way to pass text along: the assistant's input belongs to the user.
818
819
 
819
820
  ### `useArcheAssets()` — Contributor-published asset library
820
821