@microsoft/rayfin-guide 1.35.0-alpha.1286 → 1.35.0-alpha.1315

package/assets/docs/cli/connectors/add.md

@@ -0,0 +1,78 @@
+---
+sidebar_position: 2
+---
+
+# connector add
+
+```bash
+npx rayfin connector add --type <type> --workspace-id <ws-id> --item-id <item-id> [--name <name>] [--operations <ops>]
+```
+
+`connector add` declares a connector in `rayfin/rayfin.yml` and scaffolds its supporting files.
+
+The CLI verifies the Fabric item, derives a connector `name` from the item's display name (override with `--name`), writes the entry to `rayfin.yml`, scaffolds `rayfin/connectors/<name>/schema.ts`, and runs schema discovery. `rayfin/connectors/<name>/metadata.json` is written so a subset of entities can be generated later.
+
+If you do not already know the workspace and item IDs, run [`connector search`](./search.md) first — its `--json` output includes a ready-to-run `addCommand` for each result.
+
+## Options
+
+| Flag                  | Required     | Purpose                                                                                                                                                                                                                 |
+| --------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--type <type>`       | yes          | The connector type, for example `fabric-sqlanalytics`, `fabric-warehouse`, `fabric-sqldatabase`, `kusto`, or `fabric-semanticmodel`.                                                                                    |
+| `--workspace-id <id>` | yes (Fabric) | Fabric workspace ID. Must be a literal — `${VAR}` placeholders are rejected.                                                                                                                                            |
+| `--item-id <id>`      | yes (Fabric) | Fabric item or artifact ID. Must be a literal.                                                                                                                                                                          |
+| `--name <name>`       | no           | Connector name. Derived from the item display name when omitted.                                                                                                                                                        |
+| `--operations <ops>`  | no           | Comma-separated subset of the type's allowed operations, for example `read,update`. Narrows the emitted `operations:` at add time. Omit for all allowed operations. Each value must be in the type's catalog allowlist. |
+| `-y, --yes`           | no           | Auto-accept overwrite and confirmation prompts (non-interactive).                                                                                                                                                       |
+| `-v, --verbose`       | no           | Verbose diagnostics.                                                                                                                                                                                                    |
+
+## Scoping operations
+
+Without `--operations`, `connector add` writes **every** operation the catalog allows for the type. Prefer scoping at add time over hand-editing YAML afterwards:
+
+```bash
+npx rayfin connector add --type fabric-warehouse --workspace-id <ws> --item-id <item> --operations read,update
+```
+
+The resulting `rayfin.yml` entry lists operations as objects, not bare strings:
+
+```yaml
+connectors:
+  - name: inventory
+    type: fabric-warehouse
+    config:
+      workspaceId: ${WS_ID}
+      itemId: ${ITEM_ID}
+    auth:
+      type: delegated
+    operations:
+      - name: read
+      - name: update
+```
+
+Rules:
+
+- You can narrow below the catalog default; you cannot widen above it.
+- There is no `all` meta-operation — list every action explicitly.
+- The host validator rejects unknown or duplicate operation names at `rayfin up` time.
+
+## Category B connectors
+
+For `kusto` and `fabric-semanticmodel`, `connector add` writes the `rayfin.yml` entry but there are no GraphQL entities to discover, so no entity files are generated and no row-level security applies:
+
+- `executeQuery` is the only allowed operation.
+- `auth.type` must be `delegated`.
+- The connector is pinned to an adapter version.
+- There is no `metadata.json` entity list to generate from.
+
+After adding, exercise the connector with [`connector invoke`](./invoke.md) rather than writing entity code.
+
+## Related commands
+
+```bash
+npx rayfin connector list [--verbose] [--json]
+
+# Removes the rayfin.yml entry AND the rayfin/connectors/<name>/ directory.
+# Re-add after remove to refresh metadata, then regenerate entity files yourself.
+npx rayfin connector remove <name> [--yes]
+```

package/assets/docs/cli/connectors/index.md

@@ -0,0 +1,58 @@
+---
+sidebar_position: 6
+---
+
+# Connectors
+
+Connectors let a Rayfin app read from — and, for some types, write to — Microsoft Fabric data sources: warehouses, SQL databases, Lakehouse SQL analytics endpoints, semantic models, and KQL databases.
+
+## Prerequisite — the `connector` command group is feature-flagged
+
+`rayfin connector ...` is only registered when the `RAYFIN_FEATURE_FLAGS` environment variable contains `connectors`. Without it the commands do not exist and the CLI reports an unknown command.
+
+```bash
+RAYFIN_FEATURE_FLAGS=connectors npx rayfin connector search --help
+```
+
+Each command has its own reference page:
+
+- [`connector search`](./search.md) — discover Fabric sources the signed-in identity can add.
+- [`connector add`](./add.md) — declare a connector in `rayfin.yml` and scaffold its files.
+- [`connector inspect`](./inspect.md) — run a single read-only sample query against a source.
+- [`connector invoke`](./invoke.md) — run one named operation against a configured connector.
+
+A typical loop is search → add → inspect (Category A) or search → add → invoke (Category B).
+
+## Two categories of connector
+
+The commands available to a connector, and the code you write against it, depend on its category.
+
+|                                       | Category A — GraphQL entity connectors                          | Category B — function-bridge connectors                |
+| ------------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------ |
+| **Types**                             | `fabric-sqlanalytics`, `fabric-warehouse`, `fabric-sqldatabase` | `kusto`, `fabric-semanticmodel`                        |
+| **App surface**                       | Generated entity files with typed CRUD through the data client  | A single `executeQuery` operation carrying a raw query |
+| **Operations**                        | `read` only for `fabric-sqlanalytics` (Lakehouse SQL endpoints are read-only); `read`, `create`, `update`, `delete` for `fabric-warehouse` and `fabric-sqldatabase` (narrowable) | `executeQuery` only                                    |
+| **Auth**                              | `delegated` or configured per project                           | Must be `delegated`                                    |
+| **Entity files and `@role` policies** | Yes                                                             | No                                                     |
+| **`metadata.json` entities**          | Yes                                                             | No                                                     |
+| **`connector inspect`**               | Supported                                                       | `fabric-semanticmodel` only — `kusto` is not supported |
+| **`connector invoke`**                | Rarely needed                                                   | The main way to exercise the connector                 |
+
+Category B connectors are pinned to an adapter version and expose no GraphQL entities, so there is nothing to generate and no row-level security to author.
+
+## Where connector state lives
+
+- `rayfin/rayfin.yml` — the `connectors:` block: each connector's `name`, `type`, `config` (workspace and item IDs), `auth`, and `operations`.
+- `rayfin/connectors/<name>/metadata.json` — discovered schema for Category A connectors; the source for generating entity files.
+- `rayfin/connectors/<name>/schema.ts` — placeholder scaffold written by `connector add`.
+
+`npx rayfin connector list` prints the configured connectors; `npx rayfin connector remove <name>` deletes both the `rayfin.yml` entry and the `rayfin/connectors/<name>/` directory.
+
+## Deploying connectors
+
+```bash
+npx rayfin up                                     # deploy connectors to the cloud
+npx rayfin up connector apply [--name <name>]     # re-apply DAB config only
+```
+
+Most connector commands work before deployment. The exception is [`connector invoke`](./invoke.md) for every type except `fabric-semanticmodel`, which posts to the deployed item and therefore requires a prior `rayfin up`.

package/assets/docs/cli/connectors/inspect.md

@@ -0,0 +1,78 @@
+---
+sidebar_position: 3
+---
+
+# connector inspect
+
+```bash
+npx rayfin connector inspect (--name <name> | <direct-selector-flags>) (--entity <name> | --query <path>) [--rows <n>] [--verbose] [--json]
+```
+
+`connector inspect` takes no positional arguments — every selector and query mode is a flag.
+
+`connector inspect` runs a single read-only sample query against a connector's underlying source, before you have written any app code. Use it to check a table's real data and shape ahead of entity generation, or to debug a row-level-security or query issue on an already-wired connector. It is a development aid — never use it to power app functionality.
+
+Supported types: the three Category A SQL types (`fabric-sqlanalytics`, `fabric-warehouse`, `fabric-sqldatabase`) and `fabric-semanticmodel` (DAX). `kusto` is **not** supported today — the command errors with `Unsupported connector type: kusto`.
+
+## Pick exactly one selector and one query mode
+
+Two independent choices, each a mutually exclusive pair. Passing zero or both options in a pair fails validation before any network call.
+
+| Choice                                          | Option A                                                                                                                      | Option B                                                                                                                                                                                       |
+| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Selector** — which connector or item to query | `--name <name>` — a connector already declared in `rayfin.yml`                                                                | Direct mode — `--workspace-id`/`--workspace <name>` plus `--item-id`/`--item <name>` plus `--type <type>`, or `--url <portal-url>` for a semantic model (auto-extracts workspace and item IDs) |
+| **Query mode**                                  | `--entity <name>` — structured: builds `SELECT TOP (n) * FROM <entity>` (SQL) or `EVALUATE TOPN(n, '<entity>')` (DAX) for you | `--query <path>` — raw: runs the literal `.sql` or `.dax` file verbatim, still capped and validated                                                                                            |
+
+All four combinations of `{--name, direct} × {--entity, --query}` are valid.
+
+`--workspace` and `--item` accept display names and are resolved to IDs the same way [`connector add`](./add.md) fuzzy matching works; `--workspace-id` and `--item-id` take literal IDs directly.
+
+## Entity resolution
+
+Applies to `--entity` mode only.
+
+- **`--name` plus `--entity` with an unqualified name (no `.`)** — first checked against the connector's local `rayfin/connectors/<name>/metadata.json`, with no network call. Zero matches falls through to live resolution; exactly one match auto-qualifies to `schema.table`; more than one match fails immediately asking you to disambiguate with a schema-qualified name. It does **not** fall through to live resolution in the ambiguous case.
+- **Any other combination** — direct mode, or `--query` mode — never consults `metadata.json`. For SQL types, an unqualified `--entity` is resolved live via `SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE LOWER(TABLE_NAME) = LOWER('<entity>')`: zero matches passes the name through unqualified, one match auto-qualifies, more than one match throws asking you to disambiguate with `--entity <schema>.<table>`.
+- A schema-qualified `--entity <schema>.<table>` skips resolution entirely, in both cases.
+
+## Validation
+
+Applies to both query modes.
+
+- **SQL** — must start with `SELECT` or `WITH`; must be a single statement (a trailing `;` is fine, an embedded one is not); rejects `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `CREATE`, `ALTER`, `DROP`, `TRUNCATE`, `EXEC`/`EXECUTE`, and `INTO` anywhere outside a string literal.
+- **DAX** — must start with `EVALUATE`.
+- `--query <path>` must resolve to a `.sql` or `.dax` file inside the project root; paths outside it are rejected. The project root is the directory containing `rayfin/rayfin.yml` when one is found. Direct mode (no `--name`) falls back to the current working directory if no `rayfin.yml` exists, so `--query` never requires a Rayfin project.
+- `--rows <n>` caps the sample size — default 10, maximum 100. The result reports `truncated: true` when the source had more rows than the cap.
+
+## Examples
+
+```bash
+# --name selector + structured entity mode
+npx rayfin connector inspect --name inventory --entity Order
+
+# --name selector + raw query file
+npx rayfin connector inspect --name inventory --query rayfin/queries/order.sql
+
+# Direct selector (literal IDs) + structured entity mode
+npx rayfin connector inspect --workspace-id <ws-id> --item-id <item-id> --type fabric-warehouse --entity Order
+
+# Direct selector (fuzzy display names) + raw query file
+npx rayfin connector inspect --workspace "Sales Analytics" --item "Inventory Warehouse" --type fabric-warehouse --query rayfin/queries/order.sql
+
+# Semantic model (DAX), resolved from a Fabric portal URL
+npx rayfin connector inspect --url <fabric-portal-semantic-model-url> --query rayfin/queries/model.dax
+```
+
+Combine `--workspace-id`, `--item-id`, and `--type` with either `--entity` or `--query` freely — none of the four combinations require `--name` or a `rayfin.yml` entry to exist.
+
+## Errors
+
+SQL errors are categorized before being shown:
+
+| Condition                                                      | Surfaced as                                                                            |
+| -------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
+| SQL Server error `229`, `230`, `262`, `297`, `300`             | "Permission denied", with a permissions recovery hint.                                 |
+| SQL Server error `18456`, `4060`, or `ELOGIN`                  | "Authentication failed", with a `rayfin login` recovery hint.                          |
+| Anything else, including invalid object name / table not found | The underlying message, with a generic "verify the entity/table name and access" hint. |
+
+Semantic model HTTP errors map `401` to re-login, `403` to permissions, and everything else to the generic hint.

package/assets/docs/cli/connectors/invoke.md

@@ -0,0 +1,76 @@
+---
+sidebar_position: 4
+---
+
+# connector invoke
+
+```bash
+npx rayfin connector invoke <connector-name> <operation> (--input '<json>' | --file <path>) [--verbose] [--json]
+```
+
+`connector invoke` runs a single named operation against a configured connector and prints the result. It is the loop for exercising [Category B connectors](./index.md#two-categories-of-connector) — `executeQuery` over DAX or KQL — without writing any app code.
+
+Both positionals also have flag forms, `--name <name>` and `--operation <operation>`, which win over the positionals when both are given.
+
+Run it from inside a Rayfin project: it resolves `rayfin/rayfin.yml`, and fails with a recovery hint if there is no project root or the `connectors:` block is empty.
+
+## Payload input
+
+Exactly one of these is required — passing both, or neither, fails:
+
+- `--input '<json>'` — inline JSON payload for the operation input.
+- `--file <path>` — path to a JSON file. The path is resolved against the project root, and **the resolved path must stay inside it**; a `../` escape is rejected before the file is read. An absolute path is accepted as long as it resolves inside the project root.
+
+## Operation resolution
+
+The requested operation is matched **case-insensitively** against the connector's `operations:` list in `rayfin.yml`. If that entry has no `operations:`, the connector type's full catalog allowlist is used instead. A miss fails with the allowed set listed.
+
+## Transports
+
+Two transports, chosen by connector type:
+
+- **`fabric-semanticmodel`** — the CLI calls Fabric/Power BI **directly under the developer's own identity**, so this works whether or not `npx rayfin up` has been run. It requires `workspaceId` **and** `itemId` under the connector's `config:` block; without both, it fails up front rather than falling through to the deployed transport. The Power BI scope and audience are derived from the configured Fabric API base URL, so an INT ring mints an INT-audience token.
+- **Every other type, including `kusto`** — POSTs to the deployed item at `<remote-endpoint>/__private/connectors/<name>/invoke`, so it requires a prior `npx rayfin up`.
+
+## Token handling (semantic model path)
+
+`npx rayfin login` only consents to the Fabric scope, not the Power BI scope this path needs. Consequences:
+
+- Interactively (no `--json`), the CLI prompts to complete Power BI consent.
+- With `--json`, token acquisition is **silent-only** so prompts cannot corrupt the single-JSON-object contract. If consent is still needed the command fails and tells you to drop `--json` or set `RAYFIN_TOKEN`.
+- `RAYFIN_TOKEN`, when set, is passed through **unchanged** regardless of the scopes requested. Its audience is decoded and checked locally, so a wrong-audience or undecodable token fails with a clear message instead of surfacing later as a phantom workspace-permission error.
+
+## Output
+
+`--verbose` cannot be combined with `--json` — narration would break the single-object contract.
+
+Success emits `{status: 'ok', connector, operation, output}`. In non-JSON modes it prints `✅ Invoked <name>.<operation>` followed by the output.
+
+What `output` holds depends on the connector. `fabric-semanticmodel` normalises inside its `invoke` middleware, so `output` is already a discriminated result rather than the raw service envelope: `{status: 'success', table, requestId}`, where `table.columns` are `{name, dataType}` and `table.rows` are column-aligned arrays. No caller-side conversion is needed, and the same shape comes back whether the operation ran locally or through the deployed item.
+
+A resolved call is **not** automatically a success, and the failure signal depends on the same distinction. A connector that normalises reports Power BI failures — expired token, missing Build permission, throttling — as `{status: 'error', error, requestId}`, where `error` carries `category`, `message`, and optional `code` and `details`. A connector that returns the raw envelope reports failure as `status: 'Failed'` instead. The CLI reads both, converts either into a non-zero exit, and surfaces the service-supplied request id for tracing.
+
+## Examples
+
+```bash
+# Inline payload, positional args
+npx rayfin connector invoke mymodel executeQuery --input '{"query":"EVALUATE TOPN(10, Sales)"}'
+
+# Same thing with flag forms and a payload file
+npx rayfin connector invoke --name mymodel --operation executeQuery --file ./payload.json
+
+# Machine-readable (no --verbose allowed alongside)
+npx rayfin connector invoke mymodel executeQuery --input '{"query":"EVALUATE TOPN(1, Sales)"}' --json
+```
+
+## Errors
+
+| Message                                                          | Fix                                                                                   |
+| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| `Missing required connector invoke arguments`                    | Supply both the connector name and the operation.                                     |
+| `Choose exactly one payload source` / `Missing payload input`    | Pass exactly one of `--input` or `--file`.                                            |
+| `Input file must be inside the project`                          | Use a relative path under the project root.                                           |
+| `Operation "<op>" is not allowed for connector "<name>"`         | Check the connector's `operations:` in `rayfin.yml`, or the type's allowlist.         |
+| `missing workspaceId/itemId in rayfin.yml`                       | Add both under `config:`, or re-run [`connector add`](./add.md).                      |
+| `Access token has the wrong audience for the Power BI query API` | Unset or replace `RAYFIN_TOKEN`, or re-run without `--json` to consent interactively. |
+| `No remote endpoint configured`                                  | The non-semantic-model transport needs a deployed item — run `npx rayfin up` first.   |

package/assets/docs/cli/connectors/search.md

@@ -0,0 +1,66 @@
+---
+sidebar_position: 1
+---
+
+# connector search
+
+```bash
+npx rayfin connector search [query] [--workspace-id <id> --type <types> | --all-workspaces --type <types>] [--limit <n>] [--json]
+```
+
+`connector search` finds Fabric data sources — warehouses, SQL databases, Lakehouses, semantic models, and KQL databases — that the signed-in identity can add as connectors, before you know exact workspace or item IDs.
+
+Use it to find candidates for [`connector add`](./add.md). It never touches app data itself.
+
+## Scope resolution
+
+The search scope is resolved in priority order:
+
+1. `--workspace-id <id>` — search exactly one workspace. **Requires** `--type`: without it, every discoverable item type would be fetched with a separate request to that workspace.
+2. `--all-workspaces` — tenant-wide scan across every workspace the identity can access. **Requires** `--type` (the only server-side filter) to keep the scan bounded.
+3. No scope flag, run inside a Rayfin project with deployments — defaults to the union of every workspace recorded in the project's deployments registry (dev, prod, and so on), without switching the active deployment. This is the only scope that does **not** require `--type`.
+
+Only one of `--workspace-id` and `--all-workspaces` may be given. Outside a Rayfin project with zero deployments, one of them is required; omitting both fails with `workspace scope is required`.
+
+## Filtering
+
+| Flag                                       | Purpose                                                                                                                                              |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `[query]` (positional) or `--query <text>` | Case-insensitive name filter. Omit to list every connectable source in scope. `--query` wins if both are given.                                      |
+| `--type <types>`                           | Comma-separated subset of connector types, for example `fabric-warehouse,fabric-sqldatabase`. Required with `--workspace-id` and with `--all-workspaces`.                      |
+| `--limit <n>`                              | Caps the rows shown. Ignored in interactive mode, where the picker paginates the full result set instead; applies only to plain and `--json` output. |
+
+## Output modes
+
+- **Interactive** (default on a TTY) — a paginated picker. Page size comes from `RAYFIN_CONNECTOR_SEARCH_PAGE_SIZE`, default 30. Picking a source runs a pre-flight access check (SQL endpoint, Kusto endpoint, or semantic model probe, depending on type) before handing off to [`connector add`](./add.md); a failed check re-shows the picker instead of aborting. `--yes` and `--verbose` are forwarded to the `connector add` it runs.
+- **Plain** (non-TTY) — prints the list and exits, with no prompt.
+- **`--json`** — a machine-readable envelope on stdout: `{status, query, scope, count, sources}`. Each row carries `workspaceId`, `itemId`, and `connectorType`, plus `suggestedName` (the sanitized display name to use as the connector name) and `addCommand` (the exact `rayfin connector add …` string to run). Skips both the picker and the access-check pre-flight.
+
+Duplicate-looking entries — for example a SQL Database and its SQL-analytics-endpoint twin sharing a workspace and display name — are grouped visually next to each other in interactive and plain output only. They are never deduplicated, and `--json` always returns the canonical, ungrouped order.
+
+The SQL-endpoint-permissions note ("Schema discovery for SQL-based connectors requires SQL endpoint permissions") only prints when at least one result is a SQL-dialect connector type — never for a semantic-model-only or Kusto-only result set.
+
+## Examples
+
+```bash
+# Query text as a positional argument, scoped to one workspace (--type is required with --workspace-id)
+npx rayfin connector search "sales" --workspace-id <ws-id> --type fabric-warehouse
+
+# Tenant-wide scan, narrowed to one or more types (--type is required with --all-workspaces)
+npx rayfin connector search --all-workspaces --type fabric-warehouse,fabric-sqldatabase
+
+# No scope flag inside a deployed project — searches every deployment workspace, no --type needed
+npx rayfin connector search
+
+# Machine-readable output, capped to 5 rows, skips the interactive picker
+npx rayfin connector search --workspace-id <ws-id> --type fabric-warehouse --json --limit 5
+```
+
+## Errors
+
+| Message                                              | Fix                                                                                                               |
+| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `Command incomplete: workspace scope is required`    | No `--workspace-id` or `--all-workspaces` and no deployments found. Pass one of those flags.                      |
+| `--type is required with --all-workspaces`           | Add a `--type` filter to bound the tenant-wide scan.                                                              |
+| `--type is required with --workspace-id`             | Add a `--type` filter so a single request is made instead of one per discoverable item type.                      |
+| `You don't have the required permission on <source>` | The pre-flight access check failed during the interactive add handoff. Pick a different source or request access. |

package/assets/docs/cli/index.md

@@ -55,6 +55,20 @@ For the full walkthrough, see the [CLI Quickstart](./quickstart.md) or the [Buil
 | `npx rayfin up secrets apply` | Read secrets from `rayfin/.env` file (prefixed with `RAYFIN_SECRET_`) and securely apply them to the remote Rayfin item workload. Validates that secrets are persisted. Use `--env-file <path>` to specify a custom .env file location. |
 | `npx rayfin up staticapp deploy` | Build, package, and deploy static content to the remote Rayfin item. Add `--skip-build` to deploy existing build output without rebuilding. |
 
+### Connectors
+
+Connectors let a Rayfin app read from existing Fabric sources. The `connector` command group is only registered when `RAYFIN_FEATURE_FLAGS` contains `connectors`. See [Connectors](./connectors/index.md) for the full guide.
+
+| Command | Description |
+| --- | --- |
+| `npx rayfin connector search [query]` | Discover Fabric sources you can connect to. See [Searching for sources](./connectors/search.md). |
+| `npx rayfin connector add` | Declare a connector in `rayfin.yml` and run schema discovery. See [Adding a connector](./connectors/add.md). |
+| `npx rayfin connector list` | List the connectors declared in the current project. |
+| `npx rayfin connector remove <name>` | Remove a connector's `rayfin.yml` entry and its `rayfin/connectors/<name>/` directory. |
+| `npx rayfin connector inspect` | Run a read-only sample query against a connector's source. See [Inspecting a source](./connectors/inspect.md). |
+| `npx rayfin connector invoke <name> <operation>` | Run one named operation against a configured connector. See [Invoking an operation](./connectors/invoke.md). |
+| `npx rayfin up connector apply` | Re-apply connector configuration to the remote Rayfin item. |
+
 ## Update the CLI
 
 To get the latest version of the Rayfin CLI and its dependencies:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@microsoft/rayfin-guide",
-  "version": "1.35.0-alpha.1286",
+  "version": "1.35.0-alpha.1315",
   "description": "Cross-cutting Builder guides for the Rayfin platform — discovered by `@microsoft/rayfin-docs` via the `rayfinDocs` package.json field convention.",
   "type": "module",
   "files": [