@aigne/doc-smith 0.8.10-beta.1 → 0.8.10-beta.3

package/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.8.10-beta.1"
+  ".": "0.8.10-beta.3"
 }

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## [0.8.10-beta.3](https://github.com/AIGNE-io/aigne-doc-smith/compare/v0.8.10-beta.2...v0.8.10-beta.3) (2025-09-19)
+
+
+### Bug Fixes
+
+* **cli:** add enterprise deployment related links ([#125](https://github.com/AIGNE-io/aigne-doc-smith/issues/125)) ([f115309](https://github.com/AIGNE-io/aigne-doc-smith/commit/f11530967fef0bf2ead7f307a5513a1f3d6513f5))
+* polish review prompt copywriting ([#124](https://github.com/AIGNE-io/aigne-doc-smith/issues/124)) ([ea3c6a8](https://github.com/AIGNE-io/aigne-doc-smith/commit/ea3c6a837a32b0135e75faf85406049406055931))
+
+## [0.8.10-beta.2](https://github.com/AIGNE-io/aigne-doc-smith/compare/v0.8.10-beta.1...v0.8.10-beta.2) (2025-09-18)
+
+
+### Bug Fixes
+
+* polish code test ([#122](https://github.com/AIGNE-io/aigne-doc-smith/issues/122)) ([0629705](https://github.com/AIGNE-io/aigne-doc-smith/commit/0629705ebd271282411d507421c1ba5dd01473b9))
+* update document structure review prompts and display ([#119](https://github.com/AIGNE-io/aigne-doc-smith/issues/119)) ([e2d99db](https://github.com/AIGNE-io/aigne-doc-smith/commit/e2d99db83ff3a6266b32dd450a79b6e000aff09e))
+* update usage rules for field elements ([#120](https://github.com/AIGNE-io/aigne-doc-smith/issues/120)) ([434f161](https://github.com/AIGNE-io/aigne-doc-smith/commit/434f161ab7dd989d57ca670f36d0828c09abe38a))
+
 ## [0.8.10-beta.1](https://github.com/AIGNE-io/aigne-doc-smith/compare/v0.8.10-beta...v0.8.10-beta.1) (2025-09-18)
 
 

package/agents/generate/check-need-generate-structure.mjs

@@ -21,11 +21,11 @@ export default async function checkNeedGenerateStructure(
         "Your project configuration is complete. Would you like to generate the document structure now?",
       choices: [
         {
-          name: "Generate now - Start building the document structure",
+          name: "Generate now - Start generating the document structure",
           value: "generate",
         },
         {
-          name: "Review configuration first - Modify settings before generating",
+          name: "Review configuration first - Edit configuration before generating",
           value: "later",
         },
       ],
@@ -34,7 +34,7 @@ export default async function checkNeedGenerateStructure(
     if (choice === "later") {
       console.log(`\nConfiguration file: ${chalk.cyan("./.aigne/doc-smith/config.yaml")}`);
       console.log(
-        "Review and modify your configuration as needed, then run 'aigne doc generate' to continue.",
+        "Review and edit your configuration as needed, then run 'aigne doc generate' to continue.",
       );
 
       // In test environment, return a special result instead of exiting
@@ -81,12 +81,12 @@ export default async function checkNeedGenerateStructure(
     if (shouldRegenerate) {
       finalFeedback = `
       ${finalFeedback || ""}
-      
-      根据最新的 DataSources 更新结构规划：
-        1. 对于新增的内容，可以根据需要新增节点，或补充到原有节点展示
-        2. 谨慎删除节点，除非节点关联 sourceIds 都被删除了
-        3. 不能修改原有节点的 path
-        4. 根据最新的 Data Sources 可以按需要更新节点的 sourceIds。
+
+      Update document structure based on the latest DataSources:
+        1. For new content, add new sections as needed or supplement existing section displays
+        2. Be cautious when deleting sections, unless all associated sourceIds have been removed
+        3. Do not modify the path of existing sections
+        4. Update section sourceIds as needed based on the latest Data Sources
       `;
     }
   }
@@ -97,7 +97,7 @@ export default async function checkNeedGenerateStructure(
     finalFeedback = `
     ${finalFeedback || ""}
 
-    用户请求强制重新生成结构规划，请根据最新的 Data Sources 和用户要求重生生成，**允许任何修改**。
+    User requested forced regeneration of document structure. Please regenerate based on the latest Data Sources and user requirements, **allowing any modifications**.
     `;
   }
 
@@ -167,7 +167,7 @@ export default async function checkNeedGenerateStructure(
         }
 
         if (hasUpdated) {
-          message = `\n### Project Information Updated\n\nSaved to \`.aigne/doc-smith/config.yaml\`:\n\n${message}\n\n`;
+          message = `\n## Project Information Updated\n\nSaved to \`.aigne/doc-smith/config.yaml\`:\n\n${message}\n\n`;
         }
       }
     } catch (error) {

package/agents/generate/index.yaml

@@ -10,6 +10,12 @@ skills:
       skipIfExists: true
   - ../utils/load-sources.mjs
   - ./check-need-generate-structure.mjs
+  - url: ../utils/save-output.mjs
+    default_input:
+      saveKey: documentStructure
+      savePath:
+        $get: outputDir
+      fileName: structure-plan.json
   - ./user-review-document-structure.mjs
   - url: ../utils/save-output.mjs
     default_input:

package/agents/generate/user-review-document-structure.mjs

@@ -29,8 +29,8 @@ function formatDocumentStructure(structure) {
 
   function printNode(node, depth = 0) {
     const INDENT_SPACES = "  ";
-    const FOLDER_ICON = "📁";
-    const FILE_ICON = "📄";
+    const FOLDER_ICON = "  📁";
+    const FILE_ICON = "  📄";
     const indent = INDENT_SPACES.repeat(depth);
     const prefix = depth === 0 ? FOLDER_ICON : FILE_ICON;
 
@@ -46,6 +46,21 @@ function formatDocumentStructure(structure) {
   return { rootNodes, printNode };
 }
 
+function printDocumentStructure(structure) {
+  console.log(`\n  ${"-".repeat(50)}`);
+  console.log("  Current Document Structure");
+  console.log(`  ${"-".repeat(50)}`);
+
+  const { rootNodes, printNode } = formatDocumentStructure(structure);
+
+  if (rootNodes.length === 0) {
+    console.log("  No document structure found.");
+  } else {
+    rootNodes.forEach((node) => printNode(node));
+  }
+  console.log();
+}
+
 export default async function userReviewDocumentStructure({ documentStructure, ...rest }, options) {
   // Check if document structure exists
   if (!documentStructure || !Array.isArray(documentStructure) || documentStructure.length === 0) {
@@ -53,17 +68,20 @@ export default async function userReviewDocumentStructure({ documentStructure, .
     return { documentStructure };
   }
 
+  // Print current document structure in a user-friendly format
+  printDocumentStructure(documentStructure);
+
   // Ask user if they want to review the document structure
   const needReview = await options.prompts.select({
     message:
-      "Would you like to review the document structure?\n  You can modify titles, reorganize sections, or refine content outlines.",
+      "Would you like to optimize the document structure?\n  You can edit titles, reorganize sections.",
     choices: [
       {
         name: "Looks good - proceed with current structure",
         value: "no",
       },
       {
-        name: "Review and provide feedback",
+        name: "Yes, optimize the structure",
         value: "yes",
       },
     ],
@@ -80,27 +98,11 @@ export default async function userReviewDocumentStructure({ documentStructure, .
   while (iterationCount < MAX_ITERATIONS) {
     iterationCount++;
 
-    // Print current document structure in a user-friendly format
-    console.log(`\n${"=".repeat(50)}`);
-    console.log("Current Document Structure");
-    console.log("=".repeat(50));
-
-    const { rootNodes, printNode } = formatDocumentStructure(currentStructure);
-
-    if (rootNodes.length === 0) {
-      console.log("No document structure found.");
-    } else {
-      rootNodes.forEach((node) => printNode(node));
-    }
-
-    console.log(`${"=".repeat(50)}\n`);
-
     // Ask for feedback
     const feedback = await options.prompts.input({
       message:
         "How would you like to improve the structure?\n" +
-        "  • Rename, reorganize, add, or remove sections\n" +
-        "  • Adjust content outlines for clarity\n\n" +
+        "  • Rename, reorganize, add, or remove sections\n\n" +
         "  Press Enter to finish reviewing:",
     });
 
@@ -152,6 +154,9 @@ export default async function userReviewDocumentStructure({ documentStructure, .
           console.warn("Your feedback was applied but not saved as a preference.");
         }
       }
+
+      // Print current document structure in a user-friendly format
+      printDocumentStructure(currentStructure);
     } catch (error) {
       console.error("Error processing your feedback:");
       console.error(`Type: ${error.name}`);

package/agents/init/index.mjs

@@ -393,17 +393,11 @@ export function generateYAML(input) {
   let yaml = "# Project information for documentation publishing\n";
 
   // Serialize the project info section safely with string quoting
-  const projectSection = yamlStringify(
-    {
-      projectName: config.projectName,
-      projectDesc: config.projectDesc,
-      projectLogo: config.projectLogo,
-    },
-    {
-      quotingType: '"',
-      defaultStringType: "QUOTE_DOUBLE",
-    },
-  ).trim();
+  const projectSection = yamlStringify({
+    projectName: config.projectName,
+    projectDesc: config.projectDesc,
+    projectLogo: config.projectLogo,
+  }).trim();
 
   yaml += `${projectSection}\n\n`;
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aigne/doc-smith",
-  "version": "0.8.10-beta.1",
+  "version": "0.8.10-beta.3",
   "description": "AI-driven documentation generation tool built on the AIGNE Framework",
   "publishConfig": {
     "access": "public"
@@ -12,13 +12,13 @@
   "author": "Arcblock <blocklet@arcblock.io> https://github.com/blocklet",
   "license": "Elastic-2.0",
   "dependencies": {
-    "@aigne/aigne-hub": "^0.9.3",
-    "@aigne/anthropic": "^0.13.3",
-    "@aigne/cli": "^1.46.2",
-    "@aigne/core": "^1.60.2",
-    "@aigne/gemini": "^0.13.3",
-    "@aigne/openai": "^0.15.3",
-    "@aigne/publish-docs": "^0.10.0",
+    "@aigne/aigne-hub": "^0.9.5",
+    "@aigne/anthropic": "^0.13.4",
+    "@aigne/cli": "^1.48.1",
+    "@aigne/core": "^1.60.3",
+    "@aigne/gemini": "^0.13.4",
+    "@aigne/openai": "^0.15.4",
+    "@aigne/publish-docs": "^0.11.0",
     "@terrastruct/d2": "^0.1.33",
     "chalk": "^5.5.0",
     "debug": "^4.4.1",

package/prompts/detail/custom/custom-code-block.md

@@ -3,7 +3,7 @@
 
 When generating Markdown, you can add enhanced attributes to code blocks to provide richer functionality and better display effects. These attributes allow you to specify **titles**, **icons**, and more for code blocks.
 
-** Please use these enhanced attributes as much as possible to improve display effects **
+**Please use these enhanced attributes as much as possible to improve display effects**
 
 ### Attribute Definition
 
@@ -76,8 +76,8 @@ class ShoppingCart {
 **Example 1**
 
 There are two errors in this example:
-- Language name should not include suffixes, like ',no_run' in the example
-- Title does not need a key specified, just configure the value directly
+- Language name should not include suffixes like ',no_run' in the example
+- Title does not need a key specified; just configure the value directly
 
 ```rust,no_run title="main.rs" icon=logos:rust
 use tokio::runtime::Runtime;

package/prompts/detail/custom/custom-components.md

@@ -37,12 +37,38 @@ Attribute Rules:
 
 Suitable for displaying API parameters, return values, context data, and any structured data with metadata in a clean, organized format. Supports nested structures for complex data types.
 
+### 2.1. `<x-field-group>` Field Group Component
+
+Used to group multiple related `<x-field>` elements at the top level, indicating they belong to the same object or context. This provides better organization and visual grouping for related parameters.
+
+Syntax:
+
+```
+<x-field-group>
+  <x-field data-name="field1" data-type="string" data-desc="First field description"></x-field>
+  <x-field data-name="field2" data-type="number" data-desc="Second field description"></x-field>
+  <x-field data-name="field3" data-type="boolean" data-desc="Third field description"></x-field>
+</x-field-group>
+```
+
+Attribute Rules:
+
+- No attributes required
+- Must contain multiple `<x-field>` elements
+- Only `<x-field>` elements are allowed as children
+- Cannot be nested inside other `<x-field>` or `<x-field-group>` elements
+- Used only at the top level for grouping related fields
+
+### 2.2. `<x-field>` Individual Field Component
+
 Syntax:
 
 ```
 <x-field data-name="field_name" data-type="string" data-default="default_value" data-required="true" data-deprecated="false" data-desc="Field description">
   <!-- For complex types, children can only be other x-field elements -->
   <x-field data-name="nested_field" data-type="string" data-desc="Nested field description"></x-field>
+  <!-- Optional: Use x-field-desc for rich text descriptions with inline markdown -->
+  <x-field-desc markdown>This field supports **bold text**, `inline code`, and other inline markdown formatting.</x-field-desc>
 </x-field>
 ```
 
@@ -53,48 +79,117 @@ Attribute Rules:
 - `data-default` (optional): Default value for the field
 - `data-required` (optional): Whether the field is required ("true" or "false")
 - `data-deprecated` (optional): Whether the field is deprecated ("true" or "false")
-- `data-desc` (optional): Description of the field (replaces previous body content)
-- Children: For complex types (object, array), children can only be other `<x-field>` elements. For simple types, children can be empty.
+- `data-desc` (optional): Simple description of the field (plain text only)
+- Children: For complex types (object, array), children can contain multiple `<x-field>` elements and optionally one `<x-field-desc>` element. For simple types, children can be empty or contain one `<x-field-desc>` element.
+
+Child Elements:
+
+- `<x-field-desc>` (optional): Rich text description supporting inline markdown formatting
+  - `markdown` (required): **MUST** be set to "markdown" - this attribute is mandatory and cannot be omitted
+  - Supports **bold text**, `inline code`, *italic text*, and other inline markdown
+  - Cannot contain block-level elements (no code blocks, headers, lists)
+  - **Mutually exclusive with `data-desc`**: Use either `data-desc` attribute OR `<x-field-desc>` element, not both
+  - Only one `<x-field-desc>` element per `<x-field>` is allowed
+  - **Validation**: `<x-field-desc>` without `markdown` attribute will be rejected
 
 Nesting Rules:
 
 - Maximum nesting depth: 5 levels (to avoid overly complex structures)
-- Children elements must only be `<x-field>` components
-- Use `data-desc` attribute for field descriptions instead of body content
-- **Always use opening/closing tags format**: `<x-field ...></x-field>` for all types
-- For simple types (string, number, boolean), children can be empty: `<x-field ...></x-field>`
-- For complex types (object, array), children contain nested `<x-field>` elements
+- **Top-level organization**: Use `<x-field-group>` to group related `<x-field>` elements at the top level
+- **Field component children**: Children elements must only be `<x-field>` and `<x-field-desc>` components
+- **Group component children**: `<x-field-group>` can only contain `<x-field>` elements
+- **Mutually exclusive descriptions**: Use either `data-desc` attribute OR `<x-field-desc>` element, not both
+- **Child element limits**: 
+  - For simple types: children can be empty or contain exactly one `<x-field-desc>` element
+  - For complex types: children can contain multiple `<x-field>` elements and optionally one `<x-field-desc>` element
+- **Always use opening/closing tags format**: `<x-field ...></x-field>` and `<x-field-group>...</x-field-group>` for all types
+- **Mandatory markdown attribute**: Every `<x-field-desc>` element **MUST** include `markdown` attribute - elements without this attribute will be rejected
+- **Grouping rules**:
+  - `<x-field-group>` can only be used at the top level
+  - Cannot be nested inside `<x-field>` or other `<x-field-group>` elements
+  - Must contain multiple `<x-field>` elements
+- For simple types (string, number, boolean), children can be empty or contain one `<x-field-desc>`: `<x-field ...></x-field>` or `<x-field ...><x-field-desc markdown>...</x-field-desc></x-field>`
+- For complex types (object, array), children contain nested `<x-field>` elements and optionally one `<x-field-desc>` element
 
 **Usage Rules:**
 
 - **Context types must use `<x-field>` instead of tables** for consistent formatting
+- **Mandatory markdown attribute**: Every `<x-field-desc>` element must include `markdown` attribute
+
+**Error Examples:**
+
+❌ **INCORRECT** - Missing `markdown` attribute:
+```
+<x-field data-name="api_key" data-type="string" data-required="true">
+  <x-field-desc>Your **API key** for authentication.</x-field-desc>
+</x-field>
+```
+
+✅ **CORRECT** - With required `markdown` attribute:
+```
+<x-field data-name="api_key" data-type="string" data-required="true">
+  <x-field-desc markdown>Your **API key** for authentication.</x-field-desc>
+</x-field>
+```
 
 Example:
 
 ```
-<!-- Single field -->
+<!-- Single field with simple description (using data-desc) -->
 <x-field data-name="user_id" data-type="string" data-default="u0911" data-required="true" data-deprecated="true" data-desc="Unique identifier for the user. Must be a valid UUID v4 format."></x-field>
 
-<!-- Multiple related fields (Props, Parameters, Returns, Context) -->
-<x-field data-name="name" data-type="string" data-required="true" data-desc="The name of the product."></x-field>
-<x-field data-name="description" data-type="string" data-required="false" data-desc="An optional description for the product."></x-field>
-<x-field data-name="type" data-type="string" data-required="false" data-desc="The type of product (e.g., 'service', 'good')."></x-field>
+<!-- Single field with rich text description (using x-field-desc) -->
+<x-field data-name="api_key" data-type="string" data-required="true">
+  <x-field-desc markdown>Your **API key** for authentication. Generate one from the `Settings > API Keys` section. Keep it secure and never expose it in client-side code.</x-field-desc>
+</x-field>
 
-<!-- Complex nested object -->
-<x-field data-name="session" data-type="object" data-required="true" data-desc="User session information containing authentication and permission data">
+<!-- Multiple related fields grouped together (Props, Parameters, Returns, Context) -->
+<x-field-group>
+  <x-field data-name="name" data-type="string" data-required="true" data-desc="The name of the product."></x-field>
+  <x-field data-name="description" data-type="string" data-required="false" data-desc="An optional description for the product."></x-field>
+  <x-field data-name="type" data-type="string" data-required="false" data-desc="The type of product (e.g., 'service', 'good')."></x-field>
+  <x-field data-name="price" data-type="number" data-required="true" data-default="0">
+    <x-field-desc markdown>Product price in **USD**. Must be a positive number with up to 2 decimal places.</x-field-desc>
+  </x-field>
+</x-field-group>
+
+<!-- Multiple field groups for different contexts -->
+<x-field-group>
+  <x-field data-name="username" data-type="string" data-required="true" data-desc="User login name"></x-field>
+  <x-field data-name="email" data-type="string" data-required="true" data-desc="User email address"></x-field>
+  <x-field data-name="password" data-type="string" data-required="true" data-desc="User password"></x-field>
+</x-field-group>
+
+<x-field-group>
+  <x-field data-name="host" data-type="string" data-required="true" data-default="localhost" data-desc="Database host address"></x-field>
+  <x-field data-name="port" data-type="number" data-required="true" data-default="5432" data-desc="Database port number"></x-field>
+  <x-field data-name="ssl" data-type="boolean" data-required="false" data-default="false" data-desc="Enable SSL connection"></x-field>
+</x-field-group>
+
+<!-- Complex nested object with rich descriptions -->
+<x-field data-name="session" data-type="object" data-required="true">
+    <x-field-desc markdown>Contains all **authentication** and **authorization** data for the current user session. This object is automatically populated after successful login.</x-field-desc>
     <x-field data-name="auth" data-type="object" data-required="true" data-desc="User authentication information">
         <x-field data-name="token" data-type="object" data-required="true" data-desc="Access token information">
-            <x-field data-name="access_token" data-type="string" data-required="true" data-default="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." data-desc="JWT access token for API authentication"></x-field>
-            <x-field data-name="refresh_token" data-type="string" data-required="false" data-default="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." data-desc="Refresh token for obtaining new access tokens"></x-field>
+            <x-field data-name="access_token" data-type="string" data-required="true" data-default="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...">
+                <x-field-desc markdown>**JWT token** containing user identity and permissions. Expires in `24 hours` by default. Use the `refresh_token` to obtain a new one.</x-field-desc>
+            </x-field>
+            <x-field data-name="refresh_token" data-type="string" data-required="false" data-default="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...">
+                <x-field-desc markdown>Used to obtain new `access_token` when the current one expires. Valid for **30 days**.</x-field-desc>
+            </x-field>
             <x-field data-name="expires_at" data-type="number" data-required="true" data-default="1704067200" data-desc="Token expiration timestamp (Unix timestamp)"></x-field>
         </x-field>
         <x-field data-name="user" data-type="object" data-required="true" data-desc="User basic information">
             <x-field data-name="profile" data-type="object" data-required="true" data-desc="User profile information">
                 <x-field data-name="name" data-type="string" data-required="true" data-default="John Doe" data-desc="User name"></x-field>
-                <x-field data-name="email" data-type="string" data-required="true" data-default="john.doe@example.com" data-desc="User email address"></x-field>
+                <x-field data-name="email" data-type="string" data-required="true" data-default="john.doe@example.com">
+                    <x-field-desc markdown>Primary email address used for **login** and **notifications**. Must be a valid email format.</x-field-desc>
+                </x-field>
                 <x-field data-name="avatar" data-type="string" data-required="false" data-default="https://example.com/avatars/john-doe.jpg" data-desc="User avatar URL"></x-field>
             </x-field>
-            <x-field data-name="permissions" data-type="array" data-required="true" data-default='["read", "write", "admin"]' data-desc="User permissions list"></x-field>
+            <x-field data-name="permissions" data-type="array" data-required="true" data-default='["read", "write", "admin"]'>
+                <x-field-desc markdown>Array of **permission strings** that determine what actions the user can perform. Common values: `"read"`, `"write"`, `"admin"`, `"delete"`.</x-field-desc>
+            </x-field>
         </x-field>
     </x-field>
 </x-field>
@@ -118,7 +213,7 @@ Attribute Rules:
 -	data-columns (optional): Number of columns, integer (e.g., 2, 3). Default is 2.
 -	Must contain multiple <x-card> elements internally.
 -	Consistency requirement: All <x-card> elements within the same <x-cards> must maintain visual consistency:
-    -	Recommended to always provide data-icon for each card.
+    -	It's recommended to always provide data-icon for each card.
     -	Or all cards should have data-image.
     -	Avoid mixing (some with icons, some with only images).
 

package/prompts/detail/d2-chart/official-examples.md

@@ -1,4 +1,6 @@
-以下是 d2 官方提供的一些示例，拥有比较好的展示效果，在实际生成图表的时候，可以参考官方示例的使用方式，来提升图表的表现力
+<d2_official_example>
+Here are examples from the official D2 documentation with good visual effects.
+When generating charts in practice, you can refer to these official examples to enhance the expressiveness of your charts.
 
 - Bank Securities
   ```d2
@@ -706,3 +708,5 @@
     ```
   | {near: bottom-center}
   ```
+
+</d2_official_example>

package/prompts/detail/d2-chart/rules.md

@@ -1,8 +1,9 @@
+<d2_generate_constraints>
 # D2 Diagram Generation Expert Guide
 
 ## Preamble: LLM Role and Core Objective
 
-You are an expert Software Architect and a master of the D2 (Declarative Diagramming) language. Your primary function is to translate abstract descriptions of software systems, components, and processes into precise, readable, and visually effective D2 diagram code.
+You are an expert software architect and a master of the D2 (Declarative Diagramming) language. Your primary function is to translate abstract descriptions of software systems, components, and processes into precise, readable, and visually effective D2 diagram code.
 
 Your core directive is to produce D2 code that is not only syntactically correct but also semantically meaningful and adheres to the highest standards of technical diagramming. The generated output must follow all instructions, constraints, and best practices detailed in this document. You will operate in a zero-tolerance mode for syntactical errors, especially concerning predefined keyword values. The fundamental principle is the separation of concerns: the logical structure of the diagram must be defined independently of its visual styling. The following chapters are structured to enforce this principle.
 
@@ -1090,3 +1091,5 @@ Session.t2 -> Lua: "Trigger OnPlayerTurn"
 User.t2 <- Session.t2
 ```
 
+
+</d2_generate_constraints>