@aigne/doc-smith 0.8.11-beta.5 → 0.8.11-beta.7

package/.aigne/doc-smith/config.yaml

@@ -66,7 +66,9 @@ translateLanguages:
 docsDir: ./docs  # Directory to save generated documentation
 sourcesPath:  # Source code paths to analyze
   - ./
-lastGitHead: f3f14b93e6b2e6beb42b2f368c2560ab050dfd03
+lastGitHead: 6fc5d715e778663896ae179975ec72d9e5ff97ed
 # ⚠️ Warning: boardId is auto-generated by system, please do not edit manually
 boardId: "docsmith"
 appUrl: https://docsmith.aigne.io
+# Checkout ID for document deployment service
+checkoutId: ""

package/.aigne/doc-smith/output/structure-plan.json

@@ -66,7 +66,7 @@
       "agents/detail-regenerator.yaml",
       "agents/retranslate.yaml",
       "agents/team-publish-docs.yaml",
-      "agents/manage-prefs.mjs"
+      "agents/prefs/index.mjs"
     ]
   },
   {
@@ -97,7 +97,7 @@
     "parentId": "/configuration",
     "sourceIds": [
       "utils/preferences-utils.mjs",
-      "agents/manage-prefs.mjs",
+      "agents/prefs/index.mjs",
       "prompts/feedback-refiner.md"
     ]
   },

package/.aigne/doc-smith/preferences.yml

@@ -1,40 +1,43 @@
 rules:
-  - id: pref_0e628173a762f68f
-    active: true
-    scope: document
-    rule: When specifying Claude models, must use the format `anthropic:claude-3-5-sonnet`.
-    feedback: Claude models need to be specified like this anthropic:claude-3-5-sonnet
-    createdAt: 2025-09-07T02:27:18.528Z
   - id: pref_6e612d7ca8b7f3b6
     active: true
     scope: document
-    rule: When describing publishing options, should use plain text instead of custom components, and recommend users to run their own Discuss Kit instance while providing relevant links.
-    feedback: "Publishing options should not use custom components: recommend users to run their own Discuss Kit instance in the text, and add Discuss Kit related links"
+    rule: When describing publishing options, should use plain text instead of custom components, and recommend users to run
+      their own Discuss Kit instance while providing relevant links.
+    feedback: "Publishing options should not use custom components: recommend users to run their own Discuss Kit instance in
+      the text, and add Discuss Kit related links"
     createdAt: 2025-09-07T02:18:22.237Z
   - id: pref_039b58c47bdf95c9
     active: true
     scope: document
-    rule: In the "Prerequisites" section, should briefly introduce Node.js installation, specify using npm instead of pnpm, and guide users to the official website for detailed instructions.
-    feedback: "In the prerequisites section, provide a simple introduction on how to install Node.js, no need to install pnpm but use npm instead, guide users to the product official website for detailed installation instructions"
+    rule: In the "Prerequisites" section, should briefly introduce Node.js installation, specify using npm instead of pnpm,
+      and guide users to the official website for detailed instructions.
+    feedback: In the prerequisites section, provide a simple introduction on how to install Node.js, no need to install pnpm
+      but use npm instead, guide users to the product official website for detailed installation instructions
     createdAt: 2025-09-07T02:06:39.559Z
   - id: pref_03a45a593f645ce2
     active: true
     scope: document
-    rule: When describing Discuss Kit, must clearly state that it is a non-open-source service running on the official platform, not a self-hosted instance.
-    feedback: "In the core features description about document publishing, show the official platform link, run your own Discuss Kit instance, not self-hosted: Discuss Kit is not open source."
+    rule: When describing Discuss Kit, must clearly state that it is a non-open-source service running on the official
+      platform, not a self-hosted instance.
+    feedback: "In the core features description about document publishing, show the official platform link, run your own
+      Discuss Kit instance, not self-hosted: Discuss Kit is not open source."
     createdAt: 2025-09-07T01:59:12.876Z
   - id: pref_0c239f619329089f
     active: true
     scope: document
-    rule: "In the core features section, should use plain list format and add descriptions and links for AIGNE Hub and Discuss Kit."
-    feedback: Core features section should not use custom component lists, change to plain lists, add descriptions and links for AIGNE Hub and Discuss Kit to help users understand these two products
+    rule: In the core features section, should use plain list format and add descriptions and links for AIGNE Hub and
+      Discuss Kit.
+    feedback: Core features section should not use custom component lists, change to plain lists, add descriptions and links
+      for AIGNE Hub and Discuss Kit to help users understand these two products
     createdAt: 2025-09-07T01:53:22.969Z
     paths:
       - /overview
   - id: pref_4e8aa735b11d8484
     active: true
     scope: document
-    rule: "In the 'How It Works' document, only show DocSmith implementation details, should not include AIGNE Framework information."
+    rule: In the 'How It Works' document, only show DocSmith implementation details, should not include AIGNE Framework
+      information.
     feedback: How it works section does not need to show AIGNE Framework, only need to show DocSmith implementation
     createdAt: 2025-09-06T13:15:10.272Z
     paths:
@@ -42,14 +45,17 @@ rules:
   - id: pref_4ad26164f1f4fbf6
     active: true
     scope: document
-    rule: When describing multi-language support features, must clearly state support for 12 languages and list two to three mainstream languages as examples.
-    feedback: Multi-language support related features, clearly support 12 languages, no above statement, and give examples of two or three mainstream languages
+    rule: When describing multi-language support features, must clearly state support for 12 languages and list two to three
+      mainstream languages as examples.
+    feedback: Multi-language support related features, clearly support 12 languages, no above statement, and give examples
+      of two or three mainstream languages
     createdAt: 2025-09-06T12:55:42.678Z
   - id: pref_c84baec514ca5c60
     active: true
     scope: document
     rule: Core features list must describe product functionality characteristics, not promotional value or importance.
-    feedback: Core features list should describe DocSmith's functional characteristics, not describe product importance like a promotional brochure
+    feedback: Core features list should describe DocSmith's functional characteristics, not describe product importance like
+      a promotional brochure
     createdAt: 2025-09-06T12:47:46.583Z
   - id: pref_6da200d8e6fec09e
     active: true
@@ -72,6 +78,8 @@ rules:
   - id: pref_0112657e4103ba88
     active: true
     scope: structure
-    rule: Update documentation structure based on the latest source code, can add new documents and modify document dependencies on source code, but prohibit modifying any existing document paths.
-    feedback: Update documentation structure based on the latest source code, allow adding new documents and modifying document dependencies on source code, cannot modify existing document paths
+    rule: Update documentation structure based on the latest source code, can add new documents and modify document
+      dependencies on source code, but prohibit modifying any existing document paths.
+    feedback: Update documentation structure based on the latest source code, allow adding new documents and modifying
+      document dependencies on source code, cannot modify existing document paths
     createdAt: 2025-08-30T14:03:47.434Z