@thinkingai/ae-cli 6.1.20 → 6.1.21

package/skills/ae-analysis/scripts/project-semantic-knowledge-wiki/company-kb.mjs

@@ -0,0 +1,112 @@
+#!/usr/bin/env node
+import fs from 'node:fs';
+import { spawnSync } from 'node:child_process';
+import { pathToFileURL } from 'node:url';
+
+const scoped = new Set(['+new', '+add', '+list-sources', '+schema', '+compile', '+status', '+import']);
+const requestScoped = new Set(['+import-status']);
+const directory = new Set(['+source-ls', '+source-read', '+source-put', '+source-rm']);
+const value = (args, key) => args[args.indexOf(key) + 1];
+
+// Project semantic KB operations must never fall back to a personal KB.
+export async function runCompanyKb(command, args, invoke) {
+  if (args.some((arg) => arg === '--custom-instructions' || arg.startsWith('--custom-instructions='))) {
+    throw new Error('Use --custom-instructions-file for custom compiler rules.');
+  }
+  if (command === '+import' && args.some((arg) => arg === '--model' || arg.startsWith('--model=') || arg === '--custom-instructions-file' || arg.startsWith('--custom-instructions-file='))) {
+    throw new Error('Snapshot import does not run the KB compiler; do not pass compiler model or custom rules.');
+  }
+  const preparedArgs = expandCustomInstructionsFile(args);
+  if (preparedArgs.some((arg) => ['--scope', '--source', '--sources', '--format', '--jq'].some(
+    (key) => arg === key || arg.startsWith(`${key}=`)))) {
+    throw new Error('Scope/output overrides are not allowed; use company JSON output.');
+  }
+  const call = async (cmd, flags) => {
+    const result = await invoke(['kb', cmd, ...flags]);
+    if (!result || result.ok !== true) {
+      throw new Error(`Company KB operation failed; stop without personal fallback: ${JSON.stringify(result?.error ?? result)}`);
+    }
+    return result;
+  };
+  if (command === '+list') {
+    const result = await call(command, preparedArgs);
+    if (!Array.isArray(result.data)) throw new Error('Unexpected KB list response.');
+    return { ...result, data: result.data.filter((kb) => kb.scope === 'company') };
+  }
+  if (requestScoped.has(command)) {
+    if (!args.includes('--request-id') || !value(args, '--request-id')) throw new Error('--request-id is required.');
+    const result = await call(command, preparedArgs);
+    if (result.data?.scope && result.data.scope !== 'company') throw new Error('Import status did not return a company KB; stop without personal fallback.');
+    return result;
+  }
+  if (!args.includes('--name') || !value(args, '--name')) throw new Error('--name is required.');
+  const name = value(args, '--name');
+  if (scoped.has(command)) {
+    const result = await call(command, [...preparedArgs, '--scope', 'company']);
+    if (command === '+new' && result.data?.scope !== 'company') throw new Error('Creation did not return a company KB; stop.');
+    if (command === '+import' && result.data?.scope && result.data.scope !== 'company') throw new Error('Snapshot import did not return a company KB; stop.');
+    if (command === '+add') {
+      const upload = result.data?.result;
+      if (!upload?.results?.length || upload.summary?.failed !== 0
+          || upload.results.some((item) => item.status !== 'created')) {
+        throw new Error(`Source upload was not completely successful; stop: ${JSON.stringify(upload)}`);
+      }
+    }
+    return result;
+  }
+  if (directory.has(command)) {
+    if (!args.includes('--id') || !value(args, '--id')) throw new Error('--id is required.');
+    const targetArgs = ['--name', name, '--scope', 'company'];
+    if (args.includes('--host')) targetArgs.push('--host', value(args, '--host'));
+    const sources = await call('+list-sources', targetArgs);
+    const source = sources.data?.items?.find((item) => item.id === value(args, '--id'));
+    if (!source || source.sourceType !== 'zip') throw new Error('ZIP source is not in the exact company KB; stop.');
+    // Directory endpoints currently resolve by name and source ID, without a scope flag.
+    // Verify ownership through the scope-aware source endpoint before every operation.
+    return call(command, preparedArgs);
+  }
+  if (['+index', '+grep', '+read'].includes(command)) {
+    const flags = [...preparedArgs];
+    flags.splice(flags.indexOf('--name'), 2);
+    const ref = { scope: 'company', name };
+    flags.push(command === '+read' ? '--source' : '--sources', JSON.stringify(command === '+read' ? ref : [ref]));
+    return call(command, flags);
+  }
+  throw new Error(`Unsupported project KB operation: ${command}`);
+}
+
+function expandCustomInstructionsFile(args) {
+  const fileIndex = args.indexOf('--custom-instructions-file');
+  if (fileIndex === -1) return args;
+  if (fileIndex + 1 >= args.length || args[fileIndex + 1].startsWith('--')) {
+    throw new Error('--custom-instructions-file requires a file path.');
+  }
+  if (args.includes('--custom-instructions')) {
+    throw new Error('Use either --custom-instructions or --custom-instructions-file, not both.');
+  }
+  const content = fs.readFileSync(args[fileIndex + 1], 'utf8');
+  if (!content.trim()) throw new Error('--custom-instructions-file is empty.');
+  if ([...content].length > 10000) throw new Error('--custom-instructions-file exceeds 10000 characters.');
+  return [
+    ...args.slice(0, fileIndex),
+    '--custom-instructions',
+    content,
+    ...args.slice(fileIndex + 2),
+  ];
+}
+
+if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
+  try {
+    const [command, ...args] = process.argv.slice(2);
+    const result = await runCompanyKb(command, args, (flags) => {
+      const child = spawnSync('ae-cli', flags, { encoding: 'utf8', stdio: ['inherit', 'pipe', 'pipe'] });
+      if (child.stderr) process.stderr.write(child.stderr);
+      if (child.error || child.status !== 0) throw new Error(child.error?.message || child.stderr || child.stdout || 'CLI failed.');
+      return JSON.parse(child.stdout);
+    });
+    console.log(JSON.stringify(result, null, 2));
+  } catch (error) {
+    console.error(error.message);
+    process.exitCode = 1;
+  }
+}

package/skills/ae-analysis/scripts/project-semantic-knowledge-wiki/default-compile-rules.md

@@ -0,0 +1,30 @@
+# Project semantic knowledge base compile rules
+
+These rules guide Schema generation for project semantic knowledge bases built from source tree ZIP uploads.
+
+- Generate durable compile rules only. Do not copy platform working directory names, absolute filesystem paths, temporary extraction paths, source IDs, run IDs, or local machine paths into the generated rules.
+- Refer to the uploaded material as "the ZIP source tree" or "files under the source tree root". Use stable source-tree paths such as `sources/assets/reports/...` only when a rule must mention a category.
+- Treat `sources/README.md` and category `README.md` files as filing guides. They define where future material belongs; they are not business evidence.
+- CLI-managed asset facts live under `sources/assets/**`. Human project background, business rules, meetings, decisions, corrections, and references live outside `sources/assets/**`; asset refresh must not delete or override those human inputs.
+- Organize generated Wiki pages for knowledge consumption, not by mirroring every source file. Use project overview, business domains, reusable semantics, assets, decisions, and review pages.
+- Do not infer business meaning from titles alone. Preserve unknowns, conflicts, source scope, certification state, and provenance when evidence is incomplete.
+- Corrections and decisions override other material only when they state target, content, date, status, and applicable scope.
+
+
+## Navigation and page naming
+
+The generated top-level `index.md` must be a decision-oriented navigation page. It may contain only module navigation, common-entry guidance, and a compact category/count overview. Do not append a complete page list, sitemap, individual asset files, metadata property pages, numeric report IDs, numeric dashboard IDs, source container IDs, or raw source filenames to the top-level page. Top-level navigation should link to project overview, business domains, recall cards, asset category indexes, decisions, and review pages. List individual assets only inside the matching asset index page, domain page, dashboard page, source-container page, or search result context. If the compiler wants to expose a full sitemap, put it under `wiki/index.md` or category index pages, never in root `index.md`.
+
+When linking to an individual asset, use its business title as the visible link text and keep the numeric ID only as supporting identity beside the title, for example `近期客户成员聊天数量（report 13270719）`. Do not render bare numeric links such as `13270719` as navigation items.
+
+## Precompiled source contract
+
+CLI Agent has already performed the main semantic compilation for ALL assets: business meanings, SQL interpretation, calculation definitions, relationships, domains, recall boundaries, and conflict findings. These are editable source documents, not an imported final Wiki snapshot. Reuse their complete prose and calculation facts. Do not repeat project-wide extraction, SQL parsing, semantic planning, or per-field rewriting.
+
+Business-domain pages include an `Agent 使用摘要` for first-hop routing. Preserve it as the concise answer source for "what does this domain solve", "which events/metrics are mainly used", and "which dimensions should the agent drill down by". Do not replace it with a raw report list or regenerate it from every report page unless newer scoped evidence explicitly changes the summary.
+
+KB must compile and publish the final Wiki: preserve prepared asset sections, map source references to Wiki links, build concise titled navigation, and integrate project background, meetings, decisions and corrections. Batch independent page writes and link checks. Do not read each source repeatedly or regenerate unchanged pages.
+
+For SQL assets, preserve the complete Agent-authored purpose, parameters, output fields, grain, filters, limits, applicable/non-applicable questions and evidence locator in the report page's single `Agent 使用摘要`. Raw SQL/index JSON stays in the local evidence package; do not attempt to fetch it or infer omitted details. Missing facts remain unknown. Preserve certification, dependency-only status, conflicts and blocked recall; do not dismiss safety states as stale placeholders.
+
+During incremental compilation, inspect changed sources and their existing dependent pages. Update affected asset pages, indexes and cross-source conclusions; retain unrelated pages. Remove obsolete current assertions when a source changes or is removed. Integrate human evidence according to explicit scope, status and authority, never recency alone. Scope differences belong separately from same-scope contradictions. Preserve provenance to the actual uploaded source.