@xano/xanoscript-language-server 12.20.1 → 12.22.0

package/README.md

@@ -1,28 +1,18 @@
-> [!IMPORTANT]
-> **This repository has moved to [xano-inc/xanoscript-language-server](https://github.com/xano-inc/xanoscript-language-server).**
-> This copy is no longer maintained. Open new issues and pull requests there.
+# XanoScript Language Server
 
-```
-██╗  ██╗███████╗    ██╗      █████╗ ███╗   ██╗ ██████╗ ██╗   ██╗ █████╗  ██████╗ ███████╗
-╚██╗██╔╝██╔════╝    ██║     ██╔══██╗████╗  ██║██╔════╝ ██║   ██║██╔══██╗██╔════╝ ██╔════╝
- ╚███╔╝ ███████╗    ██║     ███████║██╔██╗ ██║██║  ███╗██║   ██║███████║██║  ███╗█████╗
- ██╔██╗ ╚════██║    ██║     ██╔══██║██║╚██╗██║██║   ██║██║   ██║██╔══██║██║   ██║██╔══╝
-██╔╝ ██╗███████║    ███████╗██║  ██║██║ ╚████║╚██████╔╝╚██████╔╝██║  ██║╚██████╔╝███████╗
-╚═╝  ╚═╝╚══════╝    ╚══════╝╚═╝  ╚═╝╚═╝  ╚═══╝ ╚═════╝  ╚═════╝ ╚═╝  ╚═╝ ╚═════╝ ╚══════╝
-
-███████╗███████╗██████╗ ██╗   ██╗███████╗██████╗
-██╔════╝██╔════╝██╔══██╗██║   ██║██╔════╝██╔══██╗
-███████╗█████╗  ██████╔╝██║   ██║█████╗  ██████╔╝
-╚════██║██╔══╝  ██╔══██╗╚██╗ ██╔╝██╔══╝  ██╔══██╗
-███████║███████╗██║  ██║ ╚████╔╝ ███████╗██║  ██║
-╚══════╝╚══════╝╚═╝  ╚═╝  ╚═══╝  ╚══════╝╚═╝  ╚═╝
-```
+The [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) implementation for XanoScript, the language that describes a [Xano](https://www.xano.com) backend: its APIs, functions, tables, tasks, agents, MCP servers and policies.
 
-# XanoScript Language Server
+Xano is one platform to build, run and govern AI-built software. This server brings the platform's rules into the editor, so you and your coding agent see the problems a push would refuse while you write the code.
 
-A Language Server Protocol (LSP) implementation for [XanoScript](https://xano.com), built on [Chevrotain](https://chevrotain.io/).
+Built on [Chevrotain](https://chevrotain.io/) and maintained by the Xano team.
 
-Maintained by the [Xano](https://xano.com) team.
+## Features
+
+- **Diagnostics** - Errors and warnings as you type, including cross-file references, variable usage and workspace policy checks
+- **Completion** - Context-aware suggestions, triggered by `.`, `:`, `$` and `|`
+- **Hover** - Documentation for statements, filters, input variables and policy checks
+- **Go to definition** - Jump to a referenced function, task, query or table, or to where a variable is set
+- **Semantic highlighting** - Token-based highlighting for every XanoScript construct
 
 ## Installation
 
@@ -30,155 +20,100 @@ Maintained by the [Xano](https://xano.com) team.
 npm install @xano/xanoscript-language-server
 ```
 
-**Requirements:** Node.js 20+
+Requires Node.js 20 or later.
 
-## Features
+## Usage
 
-The language server provides full LSP support including:
+The package ships two entry points:
 
-- **Code Completion** - Context-aware suggestions triggered by `.`, `:`, `$`, and `|`
-- **Syntax Highlighting** - Semantic token-based highlighting for XanoScript constructs
-- **Hover Information** - Documentation and type information on hover
-- **Diagnostics** - Real-time error detection and reporting
+| Entry point | Runtime | Transport |
+|---|---|---|
+| `server.js` | Node.js | stdio / IPC, via `vscode-languageserver/node` |
+| `language-server-worker.js` | Browser (Web Worker) | `postMessage`, via `vscode-languageserver/browser` |
 
-## Supported Object Types
+Point any LSP client at `server.js` for `.xs` files. For example, with VS Code's `vscode-languageclient`:
 
-The parser supports the following XanoScript constructs:
+```js
+const serverModule = require.resolve("@xano/xanoscript-language-server/server.js");
+
+const client = new LanguageClient(
+  "xanoscript",
+  "XanoScript",
+  {
+    run: { module: serverModule, transport: TransportKind.ipc },
+    debug: { module: serverModule, transport: TransportKind.ipc },
+  },
+  { documentSelector: [{ scheme: "file", language: "xanoscript" }] }
+);
+```
+
+### Policy checks
+
+XanoScript `policy` files are checked against Xano's policy check catalogue. The server ships a snapshot of it (`parser/policy/catalogueSnapshot.js`), so what it reports is a warning: your instance may be newer than the snapshot. A host that can fetch the live catalogue can load it with `setPolicyCatalogue()` from `parser/policy/catalogue.js`.
+
+## Supported object types
 
 | Type | Description |
 |------|-------------|
-| `query` | API endpoints with HTTP verbs, input validation, and responses |
-| `function` | Reusable logic blocks with testing capabilities |
-| `task` | Scheduled operations with cron-like triggers |
+| `query` | API endpoints with HTTP verbs, input validation and responses |
 | `api_group` | Collections of related API endpoints |
+| `function` | Reusable logic blocks with tests |
+| `task` | Scheduled operations with cron-like triggers |
 | `table` | Database schema definitions with column types |
-| `table_trigger` | Database table trigger definitions |
-| `workflow_test` | Test definitions for workflows |
-| `addon` | Add-on definitions |
-| `agent` | AI agent definitions |
-| `agent_trigger` | Agent trigger handlers |
-| `branch` | Branch logic |
-| `mcp_server` | MCP server definitions |
-| `mcp_server_trigger` | MCP server trigger handlers |
+| `table_trigger` | Database table triggers |
+| `workflow_test` | Workflow test definitions |
 | `middleware` | Middleware definitions |
-| `realtime_channel` | Realtime v1 channel definitions |
-| `realtime_trigger` | Realtime v1 trigger handlers |
-| `realtime_server` | Realtime v2 server definitions (the container that owns channels) |
-| `channel` | Realtime v2 channel definitions (path templates) |
+| `addon` | Add-on definitions |
+| `branch` | Branch definitions |
+| `workspace` / `workspace_trigger` | Workspace definitions and triggers |
+| `error_trigger` | Error trigger handlers |
+| `agent` / `agent_trigger` | AI agent definitions and triggers |
+| `tool` | Tool definitions, including MCP tool metadata |
+| `mcp_server` / `mcp_server_trigger` | MCP server definitions and connection triggers |
+| `prompt` / `resource` | MCP prompts and resources |
+| `policy` | Workspace policies and their rules |
+| `microservice` | Container and Helm microservice deployments |
+| `realtime_channel` / `realtime_trigger` | Realtime v1 channels and triggers |
+| `realtime_server` / `realtime_server_trigger` | Realtime v2 servers and connection triggers |
+| `channel` / `channel_trigger` | Realtime v2 channels and join/leave triggers |
 | `message` | Realtime v2 channel message handlers |
-| `channel_trigger` | Realtime v2 channel triggers (join/leave lifecycle, deliver per-recipient) |
-| `realtime_server_trigger` | Realtime v2 connection lifecycle triggers (connect/disconnect) |
-| `tool` | Tool definitions |
-| `workspace` | Workspace definitions |
-| `workspace_trigger` | Workspace trigger handlers |
-
-## Built-in Function Domains
-
-XanoScript includes functions organized by domain:
-
-- **ai** - AI and machine learning operations
-- **api** - External API calls and HTTP requests
-- **array** - Array manipulation and iteration
-- **cloud** - Cloud service integrations
-- **controls** - Flow control (conditionals, loops, etc.)
-- **db** - Database queries and operations
-- **debug** - Debugging and logging utilities
-- **expect** - Testing assertions
-- **math** - Mathematical operations
-- **object** - Object manipulation
-- **redis** - Redis cache operations
-- **schema** - Schema operations
-- **security** - Authentication and security functions
-- **storage** - File storage operations
-- **stream** - Streaming data operations
-- **text** - String manipulation
-- **util** - General utilities
-- **var** - Variable operations
-- **zip** - Compression utilities
-
-## Project Structure
-
-```
-├── server.js              # LSP server entry point
-├── lexer/                 # Lexical analysis
-│   ├── lexer.js           # Chevrotain lexer implementation
-│   ├── tokens.js          # Main token registry
-│   └── [domain].js        # Domain-specific tokens (api, db, cloud, etc.)
-├── parser/                # Syntax parsing
-│   ├── base_parser.js     # Core XanoBaseParser
-│   ├── [type]_parser.js   # Object type parsers
-│   ├── attributes/        # Field attributes (description, disabled, sensitive)
-│   ├── clauses/           # Language blocks (stack, input, response, etc.)
-│   ├── definitions/       # Type and column definitions
-│   ├── functions/         # Built-in functions by domain
-│   └── generic/           # Reusable parsing components
-├── onCompletion/          # Code completion logic
-├── onDidChangeContent/    # Diagnostics and error reporting
-├── onHover/               # Hover documentation
-└── onSemanticCheck/       # Semantic token highlighting
-```
-
-## Development
-
-```sh
-# Install dependencies
-npm install
+| `run` | Run job and service definitions |
 
-# Run all tests (~1800 tests)
-npm test
+## Built-in function domains
 
-# Run specific test
-npm test -- -g "test name"
+`ai`, `api`, `array`, `cloud`, `controls`, `datadog`, `db`, `debug`, `expect`, `math`, `mcp`, `object`, `realtime`, `redis`, `schema`, `security`, `storage`, `stream`, `text`, `util`, `var`, `zip`
 
-# Lint code
-npm run lint
+## Project structure
 
-# Fix lint issues
-npm run lint:fix
-
-# Generate TextMate language definition
-npm run tm
+```
+├── server.js                  # Node LSP entry point
+├── language-server-worker.js  # Browser (Web Worker) entry point
+├── lexer/                     # Token definitions
+├── parser/                    # Grammar rules
+│   ├── base_parser.js         # Core XanoBaseParser
+│   ├── [type]_parser.js       # One parser per object type
+│   ├── attributes/            # Field attributes (description, disabled, sensitive)
+│   ├── clauses/               # Blocks (stack, input, response, ...)
+│   ├── definitions/           # Type and column definitions
+│   ├── functions/             # Built-in statements by domain
+│   ├── generic/               # Shared parsing components
+│   └── policy/                # Policy check catalogue
+├── onCompletion/              # Completion
+├── onDefinition/              # Go to definition
+├── onDidChangeContent/        # Diagnostics
+├── onHover/                   # Hover documentation
+├── onSemanticCheck/           # Semantic tokens
+└── workspace/                 # Cross-file index and validation
 ```
 
-## Adding New Features
-
-### New Object Type
-
-1. Create a new parser in `parser/` (e.g., `my_object_parser.js`)
-2. Follow existing parser patterns (see `query_parser.js`, `function_parser.js`)
-3. Register it in `server.js`
-
-### New Keyword/Function
-
-We have a hierarchy for the different statements XanoScript uses:
-
-1. **Parser** - Top level (Query parser, Function parser, etc.)
-2. **Clause** - Main blocks in a given object type (stack, response, input, etc.)
-3. **Functions** - Statements like `debug.log` or `db.query`
-4. **Attributes/Definitions** - Components used to define functions
-5. **Generic** - Shared language toolset
-
-To add a new function:
-
-1. Add token definition in appropriate `lexer/` file
-2. Create function implementation in `parser/functions/[domain]/`
-3. Register in parent clause or parser
-4. Add comprehensive tests in corresponding `.spec.js` file
-
-## Testing
-
-The language server is heavily tested and should remain that way. Tests should be:
-
-- Easy to copy, paste, and extend
-- Straightforward and easy to read
-- Avoid dynamic generation (no loops)
+## Contributing
 
-Test files use `.spec.js` naming convention and mirror the source structure.
+This repository receives one commit per release. Development happens elsewhere, so pull requests are turned off here. Found a bug? [Open an issue](https://github.com/xano-inc/xanoscript-language-server/issues/new?template=bug_report.yml). [CONTRIBUTING.md](CONTRIBUTING.md) says what makes a report quick to fix.
 
-## CI/CD
+## Security
 
-On commit, pre-commit hooks run linting via Husky. The CI pipeline runs all tests and linting checks. Configuration is in `.github/workflows/ci.yml`.
+To report a vulnerability, see [SECURITY.md](SECURITY.md). Please don't open a public issue.
 
 ## License
 
-MIT License - see [LICENSE](LICENSE) for details.
+[MIT](LICENSE)

package/embedded/README.md

@@ -81,7 +81,7 @@ This works in any context (not just `api.lambda`), making it flexible for future
 ## Client-Side vs Server-Side
 
 - **Server-side** (this folder): JavaScript implementation used by language server
-- **Client-side** (`src/tooling/js_embedding.ts`): TypeScript implementation used by VS Code extension
+- **Client-side**: the editor extension creates the virtual documents with the same extraction logic
 - Both implement the same extraction logic but in their respective environments
 
 ## Testing
@@ -89,7 +89,6 @@ This works in any context (not just `api.lambda`), making it flexible for future
 All modules are ES6 modules and can be tested independently:
 
 ```bash
-cd language-server
 node -e "import('./embedded/embeddedContent.js').then(m => console.log(m.extractEmbeddedJS('code = \"\"\"\\nconsole.log()\\n\"\"\"')))"
 ```
 

package/lexer/db.js

@@ -145,6 +145,12 @@ export const OracleToken = createTokenByName("oracle", {
   categories: [Identifier],
 });
 
+// db.external.snowflake
+export const SnowflakeToken = createTokenByName("snowflake", {
+  longer_alt: Identifier,
+  categories: [Identifier],
+});
+
 export const DbTokens = [
   DbToken,
   QueryToken,
@@ -169,6 +175,7 @@ export const DbTokens = [
   MysqlToken,
   PostgresToken,
   OracleToken,
+  SnowflakeToken,
   WhereToken,
 ];
 
@@ -183,6 +190,7 @@ export function mapTokenToType(token) {
     case MysqlToken.name:
     case PostgresToken.name:
     case OracleToken.name:
+    case SnowflakeToken.name:
     case QueryToken.name:
     case GetToken.name:
     case AddToken.name:

package/lexer/mcp.js

@@ -4,9 +4,8 @@ import { createTokenByName } from "./utils.js";
 // MCP 2026-07-28 authoring keywords: the `prompt` and `resource` object kinds,
 // the tool/prompt/resource metadata keys, and the `mcp.elicit` / `mcp.progress`
 // statements, plus the per-server `oauth` block and the `mcp.oauth.complete` /
-// `mcp.oauth.request` / `mcp.oauth.revoke` statements. Grounded against cloud-client's schema DSL
-// (`script/kind/schema/core/{prompt,resource,tool,mcp_server}.yaml` and
-// `script/kind/schema/statement/mcp.{elicit,progress}.yaml`).
+// `mcp.oauth.request` / `mcp.oauth.revoke` statements. Grounded against the Xano
+// backend's XanoScript schema.
 //
 // Ordering note: a keyword with `longer_alt: Identifier` loses to an EARLIER
 // shorter token, so `prompts` must precede `prompt`, and `resource` is lexed

package/lexer/realtime.js

@@ -19,10 +19,17 @@ export const PublishToken = createTokenByName("publish", {
   categories: [Identifier],
 });
 
+// kick
+export const KickToken = createTokenByName("kick", {
+  longer_alt: Identifier,
+  categories: [Identifier],
+});
+
 export const RealtimeStatementTokens = [
   RealtimeToken,
   GetSessionToken,
   PublishToken,
+  KickToken,
 ];
 
 export function mapTokenToType(token) {
@@ -30,6 +37,7 @@ export function mapTokenToType(token) {
     case RealtimeToken.name:
     case GetSessionToken.name:
     case PublishToken.name:
+    case KickToken.name:
       return "function";
     default:
       return null;

package/lexer/realtime_server_trigger.js

@@ -14,7 +14,7 @@ export const RealtimeServerTriggerToken = createTokenByName(
 // longer_alt lists the trigger token so `realtime_server_trigger` wins over the
 // shorter `realtime_server` prefix, AND Identifier so a name that merely EXTENDS
 // the keyword (e.g. `realtime_server_0`, the default scaffold name) tokenizes as
-// one identifier instead of keyword + leftover `_0` (DEV-7582). longer_alt is not
+// one identifier instead of keyword + leftover `_0`. longer_alt is not
 // transitive, so Identifier must be listed here directly — matching the
 // [ServerDetailsToken, Identifier] precedent in channel.js.
 export const RealtimeServerToken = createTokenByName("realtime_server", {

package/onHover/functions.md

@@ -460,6 +460,18 @@ trigger.call "onNewOrder" {
 
 - `trigger.call` can call any trigger defined within your workspace, table, realtime, agentic or API triggers.
 
+# workflow_test.call
+
+```xs
+workflow_test.call "sign up" {
+  datasource = "test"
+} as $signup
+```
+
+**Note:** `workflow_test.call` is only available within `workflow_test`.
+
+Runs another workflow test as a step of this one, so a chain of tests can build on each other. `datasource` optionally picks the datasource the called test runs against.
+
 # tool.call
 
 ```xs
@@ -1167,6 +1179,19 @@ db.external.postgres.direct_query {
 
 Performs a SQL query directly on an external PostgreSQL database. The `response_type` indicates if the result is a `list` or a `single` record. The `connection_string` establishes the database connection, and `arg` provides values for placeholders. The results are stored in the `as` variable, here `$recent_customers`.
 
+# db.external.snowflake.direct_query
+
+```xs
+db.external.snowflake.direct_query {
+  sql = "SELECT * FROM customers WHERE customers.last_purchase > ?"
+  response_type = "list"
+  connection_string = $env.SNOWFLAKE_CONNECTION_STRING
+  arg = $input.date_threshold
+} as $recent_customers
+```
+
+Performs a SQL query directly on an external Snowflake database. The `response_type` indicates if the result is a `list` or a `single` record. The `connection_string` establishes the database connection, and `arg` provides values for placeholders. The results are stored in the `as` variable, here `$recent_customers`.
+
 # debug.stop
 
 ```xs
@@ -1985,10 +2010,13 @@ Removes characters (default is whitespace, or as specified by `value`) from both
 throw {
   name = "ValidationError"
   value = "Invalid user input provided"
+  status = 400
 }
 ```
 
-Throws an error and halts the script’s execution immediately. The `name` parameter specifies the error type (e.g., `"ValidationError"`), and `value` provides a custom error message to describe the issue.
+Throws an error and halts the script’s execution immediately. The `name` parameter specifies the error type (e.g., `"ValidationError"`), and `value` provides a custom error message to describe the issue. A `try_catch` can catch it.
+
+`status` (optional, a whole number from 100 to 599) is the HTTP status the request answers with when nothing catches the throw, including a throw inside a function run with `function.run`. Without it, an uncaught throw answers 200. A caught throw never changes the status.
 
 # try_catch
 

package/package.json

@@ -1,7 +1,14 @@
 {
   "name": "@xano/xanoscript-language-server",
-  "version": "12.20.1",
-  "description": "Language Server Protocol implementation for XanoScript",
+  "version": "12.22.0",
+  "description": "Language Server Protocol implementation for XanoScript, the language of Xano backends",
+  "keywords": [
+    "xano",
+    "xanoscript",
+    "language-server",
+    "lsp",
+    "chevrotain"
+  ],
   "type": "module",
   "main": "server.js",
   "files": [
@@ -31,14 +38,17 @@
   ],
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/xano-labs/xs-language-server.git"
+    "url": "git+https://github.com/xano-inc/xanoscript-language-server.git"
   },
   "author": "Xano <support@xano.com>",
   "license": "MIT",
+  "engines": {
+    "node": ">=20"
+  },
   "bugs": {
-    "url": "https://github.com/xano-labs/xs-language-server/issues"
+    "url": "https://github.com/xano-inc/xanoscript-language-server/issues"
   },
-  "homepage": "https://github.com/xano-labs/xs-language-server#readme",
+  "homepage": "https://github.com/xano-inc/xanoscript-language-server#readme",
   "scripts": {
     "test-one": "mocha",
     "test": "mocha \"**/*.spec.js\"",

package/parser/agent_parser.js

@@ -206,7 +206,9 @@ export function agentDeclaration($) {
                   "api_version?": "[string]",
                   "baseURL?": "[string]",
                   "compatibility?": ["strict", "compatible", ""],
-                  "dynamic_retrival?": ["enabled", "disabled", ""],
+                  // Free-form JSON text in the Studio form, written back
+                  // verbatim, so any string is valid.
+                  "dynamic_retrival?": "[string]",
                   "headers?": "[string]",
                   "include_thoughts?": "[boolean]",
                   "model?": "[string]",

package/parser/attributes/descriptionFieldAttribute.js

@@ -1,5 +1,8 @@
 import { EqualToken } from "../../lexer/control.js";
-import { StringLiteral } from "../../lexer/literal.js";
+import {
+  SingleQuotedStringLiteral,
+  StringLiteral,
+} from "../../lexer/literal.js";
 import { MultiLineStringToken } from "../../lexer/multiline.js";
 import { DescriptionToken } from "../../lexer/tokens.js";
 
@@ -15,6 +18,10 @@ export function descriptionFieldAttribute($) {
       {
         ALT: () => $.CONSUME(StringLiteral), // e.g., "A description of the field"
       },
+      {
+        // the platform writes a value holding a double quote as '...'
+        ALT: () => $.CONSUME(SingleQuotedStringLiteral),
+      },
       {
         ALT: () => $.CONSUME(MultiLineStringToken), // e.g., "fieldDescription"
       },

package/parser/attributes/docsFieldAttribute.js

@@ -1,5 +1,8 @@
 import { EqualToken } from "../../lexer/control.js";
-import { StringLiteral } from "../../lexer/literal.js";
+import {
+  SingleQuotedStringLiteral,
+  StringLiteral,
+} from "../../lexer/literal.js";
 import { MultiLineStringToken } from "../../lexer/multiline.js";
 import { DocsToken } from "../../lexer/tokens.js";
 
@@ -15,6 +18,10 @@ export function docsFieldAttribute($) {
       {
         ALT: () => $.CONSUME(StringLiteral), // e.g., "A docs of the field"
       },
+      {
+        // the platform writes a value holding a double quote as '...'
+        ALT: () => $.CONSUME(SingleQuotedStringLiteral),
+      },
       {
         ALT: () => $.CONSUME(MultiLineStringToken), // e.g., "fieldDocs"
       },

package/parser/branch_parser.js

@@ -15,30 +15,46 @@ export function branchDeclaration($) {
     ]);
     $.validateDeclarationName(nameToken, "branch");
 
+    // Mirrors the branch document the platform writes on pull. A middleware
+    // entry carries `active: false` when the middleware is disabled.
+    const middlewareEntry = { name: "[string]", "active?": "[boolean]" };
     const middlewareSchema = {
-      pre: [{ name: "[string]" }],
-      post: [{ name: "[string]" }],
+      pre: [middlewareEntry],
+      post: [middlewareEntry],
     };
 
+    // `0` is a valid limit, and the backend writes `task: 0` (not `false`)
+    // for a disabled task history.
+    const historyValues = [false, 0, 10, 100, 1000, 10000, "all"];
+
     $.SUBRULE($.schemaParseAttributeFn, {
       ARGS: [
         parent,
         {
-          color: "[string]",
           "description?": "[string]",
+          // Omitted by the backend when the branch has no color.
+          "color?": "[string]",
           middleware: {
             function: middlewareSchema,
             query: middlewareSchema,
             task: middlewareSchema,
             tool: middlewareSchema,
+            // Always written by the platform.
+            "message?": middlewareSchema,
+            // Written only when the branch has some.
+            "prompt?": middlewareSchema,
+            "resource?": middlewareSchema,
           },
           history: {
-            function: [false, 10, 100, 1000, 10000, "all"],
-            query: [false, 10, 100, 1000, 10000, "all"],
-            task: [false, 10, 100, 1000, 10000, "all"],
-            tool: [false, 10, 100, 1000, 10000, "all"],
-            trigger: [false, 10, 100, 1000, 10000, "all"],
-            middleware: [false, 10, 100, 1000, 10000, "all"],
+            function: historyValues,
+            query: historyValues,
+            task: historyValues,
+            tool: historyValues,
+            trigger: historyValues,
+            middleware: historyValues,
+            // Written only when they differ from the default.
+            "prompt?": historyValues,
+            "resource?": historyValues,
           },
         },
       ],

package/parser/channel_parser.js

@@ -22,6 +22,7 @@ export function channelDeclaration($) {
     let hasMiddleware = false;
     let hasInput = false;
     let hasDescription = false;
+    let hasDocs = false;
     let hasGuid = false;
     let hasTags = false;
     let hasActive = false;
@@ -156,6 +157,14 @@ export function channelDeclaration($) {
             $.SUBRULE($.inputClause);
           },
         },
+        {
+          // written by the platform when the channel has docs
+          GATE: () => !hasDocs,
+          ALT: () => {
+            hasDocs = true;
+            $.SUBRULE($.docsFieldAttribute);
+          },
+        },
         {
           GATE: () => !hasDescription,
           ALT: () => {

package/parser/clauses/flexibleStringClause.js

@@ -1,5 +1,8 @@
 import { EqualToken } from "../../lexer/control.js";
-import { StringLiteral } from "../../lexer/literal.js";
+import {
+  SingleQuotedStringLiteral,
+  StringLiteral,
+} from "../../lexer/literal.js";
 import { MultiLineStringToken } from "../../lexer/multiline.js";
 import { InstructionsToken } from "../../lexer/tool.js";
 
@@ -26,6 +29,10 @@ export function flexibleStringClause($) {
       {
         ALT: () => $.CONSUME(StringLiteral), // e.g., "A instructions of the field"
       },
+      {
+        // the platform writes a value holding a double quote as '...'
+        ALT: () => $.CONSUME(SingleQuotedStringLiteral),
+      },
       {
         ALT: () => $.CONSUME(MultiLineStringToken), // e.g., "fieldinstructions"
       },

package/parser/clauses/historyClause.js

@@ -5,8 +5,7 @@ import { HistoryToken } from "../../lexer/tokens.js";
 /**
  * Parses the history clause.
  *
- * `history` mirrors the backend serializer (cloud-client
- * helper/script/transform via `Transform::onSchemaRequestHistory`): the value is
+ * `history` mirrors the backend serializer: the value is
  * `false` (disabled), `"inherit"` (hand-authored sentinel), `"all"` (unbounded),
  * or ANY non-negative integer message limit — not a fixed set of magic numbers.
  * It is split across two OR branches because `schemaParseEnumFn` refuses an enum