@vertesia/appgen-docs 1.5.0-dev.20260725.083715Z

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Vertesia
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,18 @@
+# @vertesia/appgen-docs
+
+Generated SDK declarations and focused development guidance used by Vertesia app agents.
+
+The package build reads the current composableai workspace outputs for `@vertesia/ui`,
+`@vertesia/client`, and `@vertesia/common`, then writes the published documentation under
+`lib/docs/` so the package entrypoint and documentation are restored together from build caches.
+The tool-server resource guide is copied from the plugin template's canonical
+`.agents/skills/vertesia-tool-server-resource/REFERENCE.md` during that build.
+
+Consumers can locate the installed documentation with:
+
+```ts
+import { appgenDocsRoot } from '@vertesia/appgen-docs';
+```
+
+The stable `frontend-imports.md` guidance intentionally does not contain a bundled CDN catalog.
+Consumers add the import specifiers exposed by their actual runtime UI deployment.

package/lib/docs/app-package-patterns.md

@@ -0,0 +1,62 @@
+# App Package Patterns
+
+Generated Vertesia apps expose portable capabilities from their service package. The build script writes:
+
+- `dist/app-package.json`: full package payload from the built server
+- `dist/app-package-summary.json`: compact runtime package inventory
+- `dist/app-quality-report.json`: source-level quality and artifact inventory
+
+Before publish, run the full service build:
+
+```sh
+pnpm run service:build
+```
+
+For package-only checks during authoring, run:
+
+```sh
+pnpm run service:build:server
+```
+
+The output must list the package artifacts. If an expected type, interaction, prompt, process, view, dashboard, template, widget, activity, tool, or seed script is missing from the summary, fix the exports before publishing.
+
+## ServerConfig Checklist
+
+`src/modules/app/resources/<kind>/index.ts` should export every user-owned collection or definition array. The generated `src/tool-server/app-server-modules.ts` aggregates active modules, and `src/tool-server/config.ts` consumes that generated wiring:
+
+```ts
+import type { ToolServerConfig } from '@vertesia/tools-sdk';
+import {
+  activities,
+  dashboards,
+  interactions,
+  processes,
+  skills,
+  templates,
+  tools,
+  types,
+  views,
+} from './app-server-modules.js';
+
+export const ServerConfig = {
+  prefix: '/api',
+  tools,
+  activities,
+  interactions,
+  types,
+  skills,
+  templates,
+  dashboards,
+  processes,
+  views,
+} satisfies ToolServerConfig;
+```
+
+If a capability is authored in source but absent from the package summary, check that:
+
+1. the capability collection exports from its own `index.ts`
+2. `src/modules/app/resources/<kind>/index.ts` includes that collection or definition
+3. `src/modules/app/resources/index.ts` re-exports the capability kind
+4. `pnpm run service:build:server` passes
+
+Prefer app-owned package artifacts over tenant-local Studio/Zeno DB configuration for product behavior. Runtime/test data belongs in Store objects that use app-owned type refs such as `app:my-app:case`.

package/lib/docs/frontend-imports.md

@@ -0,0 +1,75 @@
+# App Frontend Imports
+
+This file is generated by `@vertesia/appgen-docs`.
+Do not edit it by hand. Update the package generator or the UI package docs instead.
+
+Use this reference before adding imports or package dependencies in generated Vertesia apps.
+
+## Rules
+
+- Prefer the existing template dependencies and the CDN/import-map packages below.
+- Do not manually run `npm install` or `pnpm install` in the app workspace. `app_dev_server_start` owns install and typecheck.
+- Do not add `react-router-dom`; Vertesia apps use `@vertesia/ui/router`.
+- Do not import from bare `@vertesia/ui`; it has no package root export. Use subpath imports.
+- Use public subpath imports only. Never import from generated declaration/source paths such as
+  `@vertesia/ui/core/shadcn/*`, `@vertesia/ui/core/toast`, or any path shown in
+  `appgen/ui-interfaces.d.ts` section comments.
+- Do not add another UI framework to make guessed component code compile. If an API is uncertain, use `ui/llms.txt` and `appgen/ui-interfaces.d.ts`, or use plain JSX with Tailwind classes.
+- CDN availability only means a library can be imported/bundled. It does not mean it is the right default for generated apps.
+- If a component export is not confirmed, use plain HTML elements with Tailwind classes instead of guessing a shadcn/Radix import.
+- For generated app-level chrome, prefer plain JSX (`<aside>`, `<main>`, `<header>`, `<nav>`) with Tailwind classes over `@vertesia/ui/layout` shell components unless you have checked exact props in `appgen/ui-interfaces.d.ts`.
+
+## Vertesia Imports
+
+Use these subpaths:
+
+```ts
+import { useUserSession } from '@vertesia/ui/session';
+import { RouterProvider, NavLink, useNavigate, useLocation, useParams } from '@vertesia/ui/router';
+import { Button, Badge, Input, Textarea, Spinner, Modal, ModalTitle, ModalBody, ModalFooter } from '@vertesia/ui/core';
+import { Table, THead, TBody, TR, SelectBox, SelectList, useFetch, useToast } from '@vertesia/ui/core';
+import { GenericPageNavHeader, ModernAgentConversation } from '@vertesia/ui/features';
+import { MarkdownRenderer } from '@vertesia/ui/widgets';
+```
+
+Common pitfalls:
+
+- Toasts: `const toast = useToast(); toast({ title: 'Saved' });`. Do not import `toast`.
+- Textarea: `import { Textarea } from '@vertesia/ui/core'`. Do not import from `core/shadcn/textarea`.
+- Selects: use `SelectBox` or `SelectList`; there is no `SelectTrigger`/`SelectItem` export.
+- Tables: use `Table`, `THead`, `TBody`, `TR`; there are no `TableHeader`/`TableRow`/`TableCell` exports.
+- Store search: `client.objects.search(...)` returns `ObjectSearchResponse` with `results`.
+  Use `ContentObjectItem`, `ContentObject`, and `ObjectSearchResponse` from `@vertesia/common`;
+  do not import `SearchResult`, `DocumentSearchResult`, or `ContentObjectType` from `@vertesia/client`.
+  Generated app UI should use `client.objects.search({ query: { type, match }, limit })` for Store reads;
+  reserve `objects.find()` and `objects.list()` for platform/debug code, not normal customer app data loading.
+- Vertesia SDK methods must stay attached to their client topic. Do not assign/destructure methods like
+  `const search = client.objects.search; await search(...)`; call `await client.objects.search(...)` instead
+  so the SDK keeps its request context.
+- Charts: use Vega-based charting (`react-vega`, `vega-lite`, `vega-embed`) for core analytics,
+  dashboard pages, and data-exploration views because Vega specs can be wired cleanly to rows from
+  Store search, object aggregation, and Data Store queries. Recharts is acceptable only for simple
+  non-core visual summaries when the app explicitly includes it as a dependency.
+  For React-rendered Vega-Lite charts, use `import { VegaEmbed } from 'react-vega'`; do not import
+  `Vega`, `VegaLite`, or `VegaLiteChart` from `react-vega`.
+  Render with `<VegaEmbed spec={spec} options={{ actions: false }} />`; do not pass
+  `actions={false}` directly because React forwards that unknown prop to the DOM and the design
+  renderer treats the resulting console warning as a render failure.
+
+## Recommended App Defaults
+
+Start with:
+
+- `react`, `react-dom`
+- `@vertesia/ui`, `@vertesia/client`, `@vertesia/common`
+- `@vertesia/tools-sdk` and `hono` for service-target apps with package capabilities
+- `lucide-react` for icons
+- `react-vega`, `vega`, `vega-lite`, and `vega-embed` for analytics/dashboard charts backed by Store search or Data Store query rows
+- `react-markdown`, `remark-gfm`, and `rehype-katex` for markdown/document rendering
+- `papaparse`, `xlsx`, or `docx` only when the requested workflow needs file parsing or export
+
+## Runtime CDN Imports
+
+The documentation synchronizer replaces this section with the import specifiers exposed by the
+actual Vertesia UI deployment used by the app agent. If no catalog appears below, CDN discovery
+failed and package availability must be verified before adding a dependency.

package/lib/docs/handlebars-prompts.md

@@ -0,0 +1,93 @@
+# Handlebars Prompts
+
+Use this when creating app-owned prompts and interactions in a Vertesia app package.
+
+## Rule
+
+New app-owned prompts should be Handlebars prompt files. Prefer `.hbs?prompt` files with YAML frontmatter for prompt metadata, then import those prompt definitions into the app's interaction collection.
+
+Do not create new JST prompts, plain-text prompt segments, or large inline TypeScript prompt strings unless a tiny dynamic wrapper is unavoidable.
+
+Every app-owned agent/system prompt should include current execution time near the top:
+
+```handlebars
+Today's date is {{_now}}.
+```
+
+## Helpers
+
+Registered Handlebars helpers:
+
+| Name | Description | Example |
+| --- | --- | --- |
+| `_now` | Current ISO timestamp at render time. | `Report generated at {{_now}}` |
+| `stringify` | Converts a value to JSON. Null/undefined become an empty string; strings are returned unchanged. | `Input: {{stringify data}}` |
+
+Standard Handlebars block helpers are available:
+
+| Name | Description | Example |
+| --- | --- | --- |
+| `if` / `unless` | Conditional rendering. | `{{#if flag}}Enabled{{else}}Disabled{{/if}}` |
+| `each` | Iterate arrays or objects. | `{{#each items}}- {{this.name}}{{/each}}` |
+| `with` | Change the current evaluation context. | `{{#with user}}{{name}}{{/with}}` |
+
+Execution variables:
+
+| Name | Description | Example |
+| --- | --- | --- |
+| `_model` | Model id when injected by the execution runner. It may be absent in preview/render contexts unless supplied as input. | `Model: {{_model}}` |
+
+No custom `default` helper is registered. Use an `if`/`else` block:
+
+```handlebars
+Priority: {{#if priority}}{{priority}}{{else}}standard{{/if}}
+```
+
+## Prompt File Pattern
+
+```handlebars
+---
+name: supplier-capa-risk-review
+title: Supplier CAPA Risk Review
+role: user
+content_type: handlebars
+schema:
+  type: object
+  properties:
+    capa_record:
+      type: object
+    focus:
+      type: string
+  required: [capa_record]
+---
+Review this supplier CAPA record.
+
+Today's date is {{_now}}.
+
+Record:
+{{stringify capa_record}}
+
+{{#if focus}}
+Focus: {{focus}}
+{{/if}}
+```
+
+Import the prompt definition in TypeScript and include it in the interaction collection:
+
+```ts
+import reviewPrompt from './prompts/supplier-capa-risk-review.hbs?prompt';
+
+export const interactions = new InteractionCollection({
+    name: 'supplier-capa',
+    interactions: [
+        {
+            name: 'risk-review',
+            title: 'Supplier CAPA Risk Review',
+            prompts: [reviewPrompt],
+            agent_runner_options: { is_agent: false },
+        },
+    ],
+});
+```
+
+For system prompts, keep the `{{_now}}` line in the system prompt itself. User prompts can include it when date-sensitive inputs matter, but system prompts are the default place.

package/lib/docs/package-dashboards.md

@@ -0,0 +1,110 @@
+# App Package Dashboards
+
+Use this when a Vertesia app contributes analytics dashboards through its service package.
+
+This covers how an **app package** registers dashboards. For Vega-Lite spec authoring (mark types, encodings, vconcat/hconcat layout, cross-panel selections), read `data-platform/dashboards.md` — do not duplicate spec details here.
+
+## Registering Dashboards
+
+App dashboards are `AppDashboardDefinition` objects on `ToolServerConfig.dashboards`. Each is exposed by the host as `app:<app-name>:<id>` and is read-only until a user clones it into a stored dashboard. They render over live Store/Data-Platform data, so there are no per-project dashboard records to seed.
+
+```ts
+import type { AppDashboardDefinition } from '@vertesia/common';
+import type { ToolServerConfig } from '@vertesia/tools-sdk';
+
+export const dashboards: AppDashboardDefinition[] = [
+  {
+    id: 'claims-by-status',
+    title: 'Claims by status',
+    description: 'Open vs. resolved claims over the last 30 days.',
+    tags: ['claims'],
+    // SQL shortcut for dashboards backed by a Data Platform data store.
+    query: `
+      SELECT status, COUNT(*) AS count
+      FROM claims
+      WHERE created_at >= {{since}}
+      GROUP BY status
+    `,
+    queryParameters: { since: '2026-05-01' },
+    queryLimit: 1000,
+    // Vega-Lite spec. The query result is injected as the default data source
+    // (data.values) — see data-platform/dashboards.md for spec authoring.
+    spec: {
+      $schema: 'https://vega.github.io/schema/vega-lite/v5.json',
+      mark: 'bar',
+      encoding: {
+        x: { field: 'status', type: 'nominal' },
+        y: { field: 'count', type: 'quantitative' },
+      },
+    },
+  },
+] satisfies AppDashboardDefinition[];
+
+export const ServerConfig = {
+  prefix: '/api',
+  dashboards,
+  // tools, interactions, types, processes, templates...
+} satisfies ToolServerConfig;
+```
+
+The app package endpoint serializes `ServerConfig.dashboards`:
+
+- `GET /api/package?scope=dashboards` returns `{ dashboards: [...] }`.
+- `GET /api/dashboards` lists registered dashboards.
+- `GET /api/dashboards/:id` retrieves by `id`, `name`, or `title`.
+
+## Data Sources
+
+A dashboard gets its rows from exactly one source. Pick the path that matches the backend:
+
+- **Data Platform SQL** — use the `query` shortcut (string) as above, or the explicit form `dataSource: { kind: 'data_sql', query, queryLimit?, queryParameters? }`. SQL is SELECT-only and supports `{{param}}` placeholders; defaults come from `queryParameters`.
+- **Store Elasticsearch DSL** — `dataSource: { kind: 'store_es_dsl', dsl, result? }`. The DSL runs through the secured Store query API (project/security filtering stays server-side). `result` maps the response into Vega rows: `{ type: 'hits' }` (default) or `{ type: 'aggregation_buckets', path, keyField?, countField? }`.
+
+```ts
+{
+  id: 'docs-by-type',
+  title: 'Documents by type',
+  dataSource: {
+    kind: 'store_es_dsl',
+    dsl: { aggs: { by_type: { terms: { field: 'type' } } }, size: 0 },
+    result: { type: 'aggregation_buckets', path: 'by_type', keyField: 'type', countField: 'count' },
+  },
+  spec: {
+    $schema: 'https://vega.github.io/schema/vega-lite/v5.json',
+    mark: 'arc',
+    encoding: {
+      theta: { field: 'count', type: 'quantitative' },
+      color: { field: 'type', type: 'nominal' },
+    },
+  },
+}
+```
+
+## Shape
+
+`AppDashboardDefinition`:
+
+```ts
+interface AppDashboardDefinition {
+  id: string;                 // local app dashboard id; exposed as app:<app-name>:<id>
+  name?: string;              // defaults to id
+  title?: string;             // defaults to name or id
+  description?: string;
+  tags?: string[];
+  dataSource?: DashboardDataSource;       // DashboardSqlDataSource | DashboardStoreElasticsearchDataSource
+  query?: string;             // SQL shortcut for data-store-backed dashboards
+  queryLimit?: number;
+  queryParameters?: Record<string, string>;
+  spec?: Record<string, unknown>;          // complete Vega-Lite spec
+  // Deprecated — do not use in new app packages:
+  queries?: DashboardQuery[];              // use a single query/dataSource instead
+  panels?: DashboardPanel[];               // use vconcat/hconcat in one spec
+  layout?: DashboardLayout;                // layout lives in the spec
+}
+```
+
+Prefer the modern single-source path (`query`/`dataSource` + one Vega-Lite `spec`). The legacy `queries`/`panels`/`layout` fields are deprecated because multiple data sources prevent cross-panel interactivity — express multi-panel layouts with `vconcat`/`hconcat` in a single spec.
+
+## App Manifest
+
+When publishing a service app that exposes dashboards, ensure the app manifest/capabilities include `dashboards` and publish with `target: "service"`. Studio normalizes app dashboard ids to `app:<app-name>:<id>` when listing installed app dashboards.