@gobi-starweaver/ws-cli 0.3.1

package/mcp/servers/ws-vision-ocr-server.js

@@ -0,0 +1,32 @@
+#!/usr/bin/env node
+import {
+  VISION_TOOL_DEFINITIONS,
+  WS_VISION_BRIDGE_TIMEOUT_MS,
+  WS_VISION_ENDPOINT_TIMEOUT_MS,
+  WS_VISION_OCR_NAMESPACED,
+  WS_VISION_OCR_TOOL,
+  WS_VISION_SERVER_NAME2 as WS_VISION_SERVER_NAME,
+  WS_VISION_TOOL_PREFIX,
+  WS_VISION_UPLOAD_NAMESPACED,
+  WS_VISION_UPLOAD_TOOL,
+  executeVisionTool,
+  releaseVisionImageRef,
+  resolveVisionGatewayTarget,
+  runWsVisionMcpServer
+} from "../../chunks/chunk-O2SA6W2I.js";
+import "../../chunks/chunk-BUBNMVFA.js";
+export {
+  VISION_TOOL_DEFINITIONS,
+  WS_VISION_BRIDGE_TIMEOUT_MS,
+  WS_VISION_ENDPOINT_TIMEOUT_MS,
+  WS_VISION_OCR_NAMESPACED,
+  WS_VISION_OCR_TOOL,
+  WS_VISION_SERVER_NAME,
+  WS_VISION_TOOL_PREFIX,
+  WS_VISION_UPLOAD_NAMESPACED,
+  WS_VISION_UPLOAD_TOOL,
+  executeVisionTool,
+  releaseVisionImageRef,
+  resolveVisionGatewayTarget,
+  runWsVisionMcpServer
+};

package/package.json

@@ -0,0 +1,26 @@
+{
+  "name": "@gobi-starweaver/ws-cli",
+  "version": "0.3.1",
+  "description": "北辰计划·望舒 Polaris·WS — 面向史学与人文研究的终端智能体（WS CLI）",
+  "license": "SEE LICENSE IN LICENSE",
+  "type": "module",
+  "main": "cli.js",
+  "bin": {
+    "ws": "cli.js"
+  },
+  "files": [
+    "cli.js",
+    "chunks/**",
+    "templates/**",
+    "bundled/**",
+    "assets/**",
+    "mcp/**",
+    "README.md",
+    "README-en.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
+  "dependencies": {}
+}

package/templates/prompts/init_command.md.ejs

@@ -0,0 +1,44 @@
+<% if (agentsMdFile == null) { %>
+Generate a file named ./AGENTS.md that serves as a contributor guide for this repository.
+<% } else { %>
+Update <%= agentsMdFile %> to align it with repository changes made after the last time <%= agentsMdFile %> was modified.
+<% } %>
+Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section.
+Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.
+
+Document Requirements
+
+- Title the document "Repository Guidelines".
+- Use Markdown headings (#, ##, etc.) for structure.
+- Keep the document concise. 200-400 words is optimal.
+- Keep explanations short, direct, and specific to this repository.
+- Provide examples where helpful (commands, directory paths, naming patterns).
+- Maintain a professional, instructional tone.
+
+Recommended Sections
+
+Project Structure & Module Organization
+
+- Outline the project structure, including where the source code, tests, and assets are located.
+
+Build, Test, and Development Commands
+
+- List key commands for building, testing, and running locally (e.g., npm test, make build).
+- Briefly explain what each command does.
+
+Coding Style & Naming Conventions
+
+- Specify indentation rules, language-specific style preferences, and naming patterns.
+- Include any formatting or linting tools used.
+
+Testing Guidelines
+
+- Identify testing frameworks and coverage requirements.
+- State test naming conventions and how to run tests.
+
+Commit & Pull Request Guidelines
+
+- Summarize commit message conventions found in the project’s Git history.
+- Outline pull request requirements (descriptions, linked issues, screenshots, etc.).
+
+(Optional) Add other sections if relevant, such as Security & Configuration Tips, Architecture Overview, or Agent-Specific Instructions.