@restoai/resto-datacli 0.1.10 → 0.1.11

package/.agents/skills/resto-datacli/SKILL.md

@@ -67,6 +67,12 @@ Always cite the evidence used in the final answer:
 
 If the answer uses a playbook, cite the playbook name/id and explain what was adapted.
 
+## Customer-Facing Field Labels
+
+For customer-facing answers, explain fields with Chinese display names from `displayText` or clear Chinese aliases; field codes are internal evidence for query plans, validation, debugging, and engineering handoff. Do not expose field codes by default in business-facing summaries, bullets, screenshots, or recommendations.
+
+When citing selected fields and filter fields, cite their Chinese names first. Include field codes only when the user asks for technical details, when showing an executable query plan, or when diagnosing mismatches between report metadata and report-api behavior.
+
 ## Practical Notes
 
 - Prefer narrow, auditable query plans over broad exploratory execution.

package/README.md

@@ -47,7 +47,6 @@ Token login still requires an explicit corporation id:
 ```bash
 resto auth login \
   --base-url https://bo.restosuite.cn \
-  --knowledge-base-url https://report-knowledge.restosuite.cn \
   --token <token> \
   --corporation-id 302
 ```
@@ -57,12 +56,11 @@ Password login follows the BO login step flow, encrypts the password with BO's R
 ```bash
 resto auth login \
   --base-url https://bo.restosuite.cn \
-  --knowledge-base-url https://report-knowledge.restosuite.cn \
   --username <account> \
   --password <password>
 ```
 
-`--base-url` is the BO login/report context host. `--knowledge-base-url` is the report-knowledge-service host used by `knowledge sync/check` and `query execute`; query execution goes through that service-side proxy so configured row limits and auth checks are enforced. `language-code` and `timezone` default to `zh_CN` and `Asia/Shanghai`. If the BO password flow requires an explicit tenant or flow step, pass `--corporation-id`, `--login-flow-code`, and optionally `--login-step-name`.
+`--base-url` is the BO gateway host used for login, knowledge manifest sync, and report query execution. `language-code` and `timezone` default to `zh_CN` and `Asia/Shanghai`. If the BO password flow requires an explicit tenant or flow step, pass `--corporation-id`, `--login-flow-code`, and optionally `--login-step-name`.
 For normal email/password login, `--login-flow-code` is not required; it is kept only as a troubleshooting escape hatch.
 
 ## Fixture Mode
@@ -86,6 +84,8 @@ resto query validate --plan docs/examples/dish-topn-plan.json
 
 Answers built with this CLI should cite the evidence used: report ID, selected fields, filter fields, explicit filter values and time range, currency when available, and the `resultId` returned by `resto query execute`. Snapshot transforms should also cite the source `resultId`, transform name, dimension, and metric. `topn` should cite its limit. `contribution` should cite its baseline `resultId`.
 
+Customer-facing summaries should use Chinese field display names or aliases first. Field codes are internal evidence for query plans, validation, debugging, and engineering handoff; do not expose them by default in business-facing answers unless the user asks for technical details.
+
 Playbooks are reference material, not automatic business conclusions. If a playbook is used, cite its name or ID and explain what was adapted.
 
 Agent workflow guidance is maintained in [`.agents/skills/resto-datacli/SKILL.md`](.agents/skills/resto-datacli/SKILL.md). Verification notes and backend caveats are tracked under [`docs/verification`](docs/verification), including [`docs/verification/phase1-mvp.md`](docs/verification/phase1-mvp.md).

package/dist/commands/auth.js

@@ -131,8 +131,7 @@ function extractPasswordLoginProfile(payload, fallbackCorporationId) {
 }
 function withReportContext(profile, options) {
     const reportContext = buildReportContext(profile, options);
-    const baseProfile = options.knowledgeBaseUrl ? { ...profile, knowledgeBaseUrl: options.knowledgeBaseUrl } : profile;
-    return reportContext ? { ...baseProfile, reportContext } : baseProfile;
+    return reportContext ? { ...profile, reportContext } : profile;
 }
 async function fetchProfileReportContext(profile, fetchImpl) {
     const response = await fetchImpl(`${trimTrailingSlash(profile.baseUrl)}${PROFILE_INFO_PATH}`, {
@@ -594,7 +593,6 @@ export function createAuthCommand(options = {}) {
         .description("Save local authentication profile")
         .option("--interactive", "Prompt for authentication details")
         .option("--base-url <url>", "Resto BO base URL")
-        .option("--knowledge-base-url <url>", "Report knowledge service base URL")
         .option("--token <token>", "API token")
         .option("--corporation-id <id>", "Corporation ID")
         .option("--username <username>", "BO username/account for password login")
@@ -627,7 +625,6 @@ export function createAuthCommand(options = {}) {
         printJson(write, {
             authenticated: true,
             baseUrl: profile.baseUrl,
-            ...(profile.knowledgeBaseUrl ? { knowledgeBaseUrl: profile.knowledgeBaseUrl } : {}),
             corporationId: profile.corporationId,
             languageCode: profile.languageCode,
             timezone: profile.timezone,

package/dist/commands/knowledge.js

@@ -11,20 +11,20 @@ function parseSchemaVersion(write, value) {
     }
     return parsed;
 }
-function createDefaultSyncService(localRoot, profile, knowledgeBaseUrl, factory) {
+function createDefaultSyncService(localRoot, profile, baseUrl, factory) {
     if (factory) {
-        return factory({ localRoot, profile, knowledgeBaseUrl });
+        return factory({ localRoot, profile, baseUrl });
     }
     return new KnowledgeSyncService({
         localRoot,
         manifestClient: new ManifestClient({
-            knowledgeBaseUrl,
+            baseUrl,
             profile
         })
     });
 }
-function resolveKnowledgeBaseUrl(profile, override) {
-    return override ?? profile.knowledgeBaseUrl ?? profile.baseUrl;
+function resolveManifestBaseUrl(profile) {
+    return profile.baseUrl;
 }
 export function createKnowledgeCommand(options = {}) {
     const write = options.write ?? ((message) => process.stdout.write(message));
@@ -45,7 +45,6 @@ export function createKnowledgeCommand(options = {}) {
         .option("--env <env>", "Knowledge environment", "test")
         .option("--schema-version <version>", "Knowledge schema version", "1")
         .option("--fixture", "Sync bundled local fixture knowledge without remote services or auth")
-        .option("--knowledge-base-url <url>", "Knowledge service base URL")
         .allowExcessArguments(false)
         .action(async (rawOptions) => {
         const schemaVersion = parseSchemaVersion(write, rawOptions.schemaVersion);
@@ -58,7 +57,7 @@ export function createKnowledgeCommand(options = {}) {
                 if (!profile) {
                     failJson(write, "AUTH_NOT_CONFIGURED", "Authentication profile is not configured. Run resto auth login first.");
                 }
-                return createDefaultSyncService(options.localRoot, profile, resolveKnowledgeBaseUrl(profile, rawOptions.knowledgeBaseUrl), options.createKnowledgeSyncService);
+                return createDefaultSyncService(options.localRoot, profile, resolveManifestBaseUrl(profile), options.createKnowledgeSyncService);
             })();
         printJson(write, await service.sync({
             env: rawOptions.env,
@@ -71,7 +70,6 @@ export function createKnowledgeCommand(options = {}) {
         .option("--env <env>", "Knowledge environment", "test")
         .option("--schema-version <version>", "Knowledge schema version", "1")
         .option("--fixture", "Check bundled local fixture knowledge without remote services or auth")
-        .option("--knowledge-base-url <url>", "Knowledge service base URL")
         .allowExcessArguments(false)
         .action(async (rawOptions) => {
         const schemaVersion = parseSchemaVersion(write, rawOptions.schemaVersion);
@@ -84,7 +82,7 @@ export function createKnowledgeCommand(options = {}) {
                 if (!profile) {
                     failJson(write, "AUTH_NOT_CONFIGURED", "Authentication profile is not configured. Run resto auth login first.");
                 }
-                return createDefaultSyncService(options.localRoot, profile, resolveKnowledgeBaseUrl(profile, rawOptions.knowledgeBaseUrl), options.createKnowledgeSyncService);
+                return createDefaultSyncService(options.localRoot, profile, resolveManifestBaseUrl(profile), options.createKnowledgeSyncService);
             })();
         printJson(write, await service.check({
             env: rawOptions.env,

package/dist/config/profile.js

@@ -1,7 +1,6 @@
 import { z } from "zod";
 const authProfileSchema = z.object({
     baseUrl: z.string().min(1),
-    knowledgeBaseUrl: z.string().min(1).optional(),
     token: z.string().min(1),
     corporationId: z.string().min(1),
     languageCode: z.string().min(1),

package/dist/knowledge/manifest-client.js

@@ -7,16 +7,16 @@ function unwrapManifestPayload(payload) {
     return payload;
 }
 export class ManifestClient {
-    knowledgeBaseUrl;
+    baseUrl;
     profile;
     fetchImpl;
     constructor(options) {
-        this.knowledgeBaseUrl = options.knowledgeBaseUrl.replace(/\/+$/, "");
+        this.baseUrl = options.baseUrl.replace(/\/+$/, "");
         this.profile = options.profile;
         this.fetchImpl = options.fetchImpl ?? fetch;
     }
     async fetchManifest(request) {
-        const response = await this.fetchImpl(`${this.knowledgeBaseUrl}/api/knowledge/manifest`, {
+        const response = await this.fetchImpl(`${this.baseUrl}/api/knowledge/manifest`, {
             method: "POST",
             headers: {
                 "corporation-id": this.profile.corporationId,

package/docs/installation.md

@@ -117,7 +117,6 @@ resto auth login --interactive
 ```shell
 resto auth login \
   --base-url https://bo.restosuite.cn \
-  --knowledge-base-url https://report-knowledge.restosuite.cn \
   --corporation-id <集团ID> \
   --token <BO登录token>
 ```
@@ -127,13 +126,12 @@ resto auth login \
 ```shell
 resto auth login \
   --base-url https://bo.restosuite.cn \
-  --knowledge-base-url https://report-knowledge.restosuite.cn \
   --corporation-id <集团ID> \
   --username <账号> \
   --password <密码>
 ```
 
-`--base-url` 是 BO 登录和上下文接口地址；`--knowledge-base-url` 是 `report-knowledge-service` 地址。知识包同步和 `resto query execute` 都走 `report-knowledge-service`，由服务端代理统一做鉴权和 `pageSize` 上限控制。
+`--base-url` 是 BO 网关地址。登录、知识包同步和 `resto query execute` 都通过该 BO 网关访问；不需要单独配置 `report-knowledge-service` 域名。
 
 中国区上线阶段，`language-code` 和 `timezone` 默认使用：
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@restoai/resto-datacli",
-  "version": "0.1.10",
+  "version": "0.1.11",
   "type": "module",
   "bin": {
     "resto": "dist/cli.js"