kushi-agents 3.13.0 → 3.15.0

package/bin/cli.mjs

@@ -25,6 +25,8 @@ if (args.includes('--help') || args.includes('-h')) {
   Options:
     --dest <path>       Override destination (relative for vscode, absolute for clawpilot)
     --force             Overwrite existing destination without asking
+    --yes, -y           Accept the default destination and skip the project-root
+                        check (useful for scripted or agent-driven installs)
     --no-settings       Skip .vscode/settings.json update (vscode target only)
     --no-instructions   Skip .github/copilot-instructions.md merge (vscode target only)
     --help, -h          Show this help
@@ -55,6 +57,7 @@ if (args.includes('--clawpilot')) {
 const options = {
   dest: getFlag('--dest'),
   force: args.includes('--force'),
+  yes: args.includes('--yes') || args.includes('-y'),
   noSettings: args.includes('--no-settings'),
   noInstructions: args.includes('--no-instructions'),
   target,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kushi-agents",
-  "version": "3.13.0",
+  "version": "3.15.0",
   "description": "Install Kushi — multi-source project evidence agent with snapshot+stream capture across Email, Teams, OneNote, SharePoint, Meetings, CRM, ADO. WorkIQ-only for M365 sources (Graph / m365_* FORBIDDEN as fallbacks; user-paste is first-class). Host-agnostic.",
   "type": "module",
   "bin": {

package/plugin/instructions/crm-internal-vs-confirmed.instructions.md

@@ -8,7 +8,7 @@ applyTo: "**"
 
 **A CRM field value is NEVER automatically a confirmed fact.** A Dataverse field update records an internal decision; it does not prove the decision has been (a) communicated to the customer, (b) approved by deal desk / finance / legal, or (c) confirmed in a customer-facing transcript, note, email, or meeting artifact.
 
-Adapted into kushi from Nova doctrine (see `fde-grounding.instructions.md > CRITICAL: CRM Field Values vs. Confirmed Facts`).
+Adapted into kushi from prior doctrine (see `fde-grounding.instructions.md > CRITICAL: CRM Field Values vs. Confirmed Facts`).
 
 ## Three states every CRM-sourced assertion must be classified into
 

package/plugin/instructions/engagement-root-resolution.instructions.md

@@ -12,7 +12,7 @@ The **engagement-root** is the parent folder that contains all of the user's eng
 Resolve `<engagement-root>` in this order — first match wins:
 
 1. **`<USER_HOME>/.copilot/project-evidence.yml`** — read `engagement_root:` field (preferred).
-2. **`customer_workspace/FDEDocs/`** — if the user's workspace has this symlink, follow it. Common in NOVA-style installs.
+2. **`customer_workspace/FDEDocs/`** — if the user's workspace has this symlink, follow it. Common in FDE-style installs.
 3. **Ask the user** once and persist the answer to `<USER_HOME>/.copilot/project-evidence.yml engagement_root`.
 
 ## Live config location

package/plugin/learnings/crm.md

@@ -14,7 +14,7 @@ A live Dataverse REST probe afternoon of 2026-05-18 — `GET /new_frontierengine
 ### Why this was a defect
 The pull-crm SKILL `Resolution order` section already documented the 4-step sequence (title → account → recent-slice → ask) — but bootstrap was not actually executing it. It appears bootstrap relied on a WorkIQ-only / metadata-only probe that didn't reach Dataverse, then silently wrote `disabled: true`. That is the worst possible disposition: it pretends there is no CRM record, hides the failure from future refreshes, and the project loses CRM evidence entirely.
 
-Adjacent observation: Nova (sibling tool) does this resolution sequence in its bootstrap and would not have missed FE-2026-001791. The doctrine was present in kushi but the execution path was weak.
+Adjacent observation: equivalent sibling tooling performs this resolution sequence in its bootstrap and would not have missed FE-2026-001791. The doctrine was present in kushi but the execution path was weak.
 
 ### Fix
 - New HARD-rule instruction `plugin/instructions/crm-bootstrap-discovery.instructions.md` — `disabled: true` is ONLY allowed after the FULL 4-step REST sequence returns 0 AND the user is presented with top candidates. Auth/reachability failures must leave the boundary EMPTY (with `reason: 'crm-auth-unavailable-<date>'`) so the next refresh retries — NEVER write `disabled: true`.

package/plugin/learnings/onenote.md

@@ -98,7 +98,7 @@ The first eight `pull-onenote` versions used prose phrasing (`"sectionFileId <id
 
 1. WorkIQ does NOT honor `wdsectionfileid = <id>` as filter syntax — it routes to summary mode AND returns "OneNote internal properties not exposed as searchable fields" refusal text.
 2. The wdpartid GUIDs we observed in earlier runs were **URL fragments inside SharePoint Doc.aspx hyperlinks** that WorkIQ rendered as response footnotes — not search-index extractor outputs.
-3. The Nova-pattern (natural-language query naming the section + notebook by display name and the page by quoted title) is the actual working pattern. It returned a real verbatim body for the HCA `4/3 - HCA with Jay and Martin` page.
+3. The natural-language WorkIQ pattern (query naming the section + notebook by display name and the page by quoted title) is the actual working pattern. It returned a real verbatim body for the HCA `4/3 - HCA with Jay and Martin` page.
 4. **Body retrieval is non-deterministic** — the same 4/3 page returned a verbatim body at 19:42 PDT and `BODY-NOT-EXPOSED` at 19:48 PDT, same query, no edits. The M365 search index's exposure of OneNote bodies oscillates over time.
 5. **The blocker for months was the WorkIQ EULA.** Without `workiq accept-eula`, every OneNote query silently returns nothing useful. This is a one-time setup step, not a per-call gate.
 
@@ -112,7 +112,7 @@ The first eight `pull-onenote` versions used prose phrasing (`"sectionFileId <id
 
 **HCA result (2026-05-14):** 18 pages enumerated. 1 captured verbatim (4/3). 15 pending retry (BODY-NOT-EXPOSED). 2 enumeration-only (will be probed in Step B on next refresh).
 
-**Key lesson:** when a doctrine is grounded in pattern-matching against tool responses (e.g. "field names route to extractor"), validate it empirically against the live tool BEFORE shipping. The v3.7.8 doctrine was internally consistent and self-citing but never actually tested end-to-end — the 4/3 success that motivated v3.7.9 happened only after honestly retracting v3.7.8 and replicating the Nova workflow step-by-step.
+**Key lesson:** when a doctrine is grounded in pattern-matching against tool responses (e.g. "field names route to extractor"), validate it empirically against the live tool BEFORE shipping. The v3.7.8 doctrine was internally consistent and self-citing but never actually tested end-to-end — the 4/3 success that motivated v3.7.9 happened only after honestly retracting v3.7.8 and replicating the natural-language WorkIQ workflow step-by-step.
 
 
 ## 2026-05-14 — v3.7.9 retraction + v3.8.0 architectural pivot

package/plugin/skills/pull-onenote/SKILL.md

@@ -342,7 +342,7 @@ Used ONLY when:
 - The previous run hit auth-required and retry-cooldown has not elapsed (24h), OR
 - The user explicitly requests WorkIQ-only for diagnostic comparison.
 
-Canonical WorkIQ Step B query (the Nova-pattern):
+Canonical WorkIQ Step B query (natural-language pattern):
 
 > Return the FULL readable content verbatim of the page titled `<title>` in my OneNote section `<one_sectionName>` in notebook `<one_notebookName>`. Do not summarize. Do not paraphrase. If the body is not exposed, say so explicitly with the literal phrase `BODY-NOT-EXPOSED` on its own line.
 

package/src/constants.mjs

@@ -40,6 +40,46 @@ export const PROJECT_GITHUB_EXCLUDED_FILES = [
   'config/m365-mutable.json'
 ];
 
+/**
+ * Files / directories that indicate the cwd is a sane install target.
+ *
+ * Two flavors:
+ *   - 'code'       — a software project root (any common ecosystem).
+ *   - 'engagement' — a Kushi engagement folder (Evidence/State/integrations live here,
+ *                    or this dir already has a prior Kushi install / reference pack).
+ *
+ * Either flavor suppresses the "this directory does not look like a project root"
+ * warning. If neither is present and the directory is non-empty, the installer
+ * shows an actionable warning. If the directory is empty, it shows a friendly
+ * INFO message instead — empty dirs are the normal "starting fresh" case.
+ */
+export const PROJECT_MARKERS = [
+  // ── code project roots ──────────────────────────────────────────────────
+  { name: 'package.json',      kind: 'code', type: 'file' },
+  { name: '.git',              kind: 'code', type: 'dir'  },
+  { name: 'pyproject.toml',    kind: 'code', type: 'file' },
+  { name: 'requirements.txt',  kind: 'code', type: 'file' },
+  { name: 'Cargo.toml',        kind: 'code', type: 'file' },
+  { name: 'go.mod',            kind: 'code', type: 'file' },
+  { name: 'pom.xml',           kind: 'code', type: 'file' },
+  { name: 'build.gradle',      kind: 'code', type: 'file' },
+  { name: 'build.gradle.kts',  kind: 'code', type: 'file' },
+  { name: 'composer.json',     kind: 'code', type: 'file' },
+  { name: 'Gemfile',           kind: 'code', type: 'file' },
+  { name: 'mix.exs',           kind: 'code', type: 'file' },
+  // ── .NET (glob, not literal name) ───────────────────────────────────────
+  { glob: /\.csproj$/i,        kind: 'code', type: 'file' },
+  { glob: /\.fsproj$/i,        kind: 'code', type: 'file' },
+  { glob: /\.sln$/i,           kind: 'code', type: 'file' },
+  // ── Kushi engagement folders ────────────────────────────────────────────
+  { name: 'Evidence',          kind: 'engagement', type: 'dir'  },
+  { name: 'State',             kind: 'engagement', type: 'dir'  },
+  { name: 'integrations.yml',  kind: 'engagement', type: 'file' },
+  { name: 'integrations.yaml', kind: 'engagement', type: 'file' },
+  { name: '.kushi',            kind: 'engagement', type: 'dir'  },
+  { name: '.kushi-reference',  kind: 'engagement', type: 'dir'  },
+];
+
 /** VS Code settings keys → the .kushi subdirectory they point at. */
 export const SETTINGS_MAP = {
   'chat.agentFilesLocations':        'agents',

package/src/main.mjs

@@ -10,6 +10,7 @@ import {
   CLAWPILOT_AGENT_SOURCE,
   CLAWPILOT_SKILL_DEST,
   PLUGIN_SOURCE_DIR,
+  PROJECT_MARKERS,
 } from './constants.mjs';
 import { promptForDestination } from './prompt.mjs';
 import { copyAssets, copyProjectFiles } from './copy-assets.mjs';
@@ -82,14 +83,8 @@ export async function main(options = {}) {
  */
 async function installVscode(options, resolved, version) {
   const projectRoot = process.cwd();
-  const hasProjectMarker =
-    fs.existsSync(path.join(projectRoot, 'package.json')) ||
-    fs.existsSync(path.join(projectRoot, '.git'));
-
-  if (!hasProjectMarker) {
-    console.warn(
-      '  WARN: This directory does not look like a project root (no package.json or .git found). Proceeding anyway.\n',
-    );
+  if (!options.yes) {
+    warnIfNotProjectRoot(projectRoot);
   }
 
   let dest;
@@ -112,6 +107,8 @@ async function installVscode(options, resolved, version) {
       console.error('\n  Destination must be within the current project.\n');
       process.exit(1);
     }
+  } else if (options.yes) {
+    dest = DEFAULT_DEST;
   } else {
     dest = await promptForDestination(DEFAULT_DEST);
   }
@@ -276,4 +273,90 @@ async function confirmOverwriteIfExists(fullDest, displayDest, force) {
     console.log('\n  Cancelled.\n');
     process.exit(0);
   }
+}
+
+/**
+ * Detect whether the cwd looks like a sane install target and, if not, print
+ * an actionable message. Three cases:
+ *
+ *   1. A code marker (package.json, .git, pyproject.toml, *.csproj, ...) or an
+ *      engagement marker (Evidence/, State/, integrations.yml, .kushi/, ...)
+ *      is present → silent, proceed.
+ *   2. The directory is empty → friendly INFO ("starting fresh — Kushi will
+ *      create a new install here"). Empty dirs are the normal first-run case
+ *      and should not produce a WARN.
+ *   3. The directory has files but no recognized marker → WARN with the
+ *      actual fix (run `git init`, cd to an engagement folder, or pass --yes
+ *      to skip this check in scripted use).
+ *
+ * @param {string} projectRoot
+ */
+function warnIfNotProjectRoot(projectRoot) {
+  const marker = findProjectMarker(projectRoot);
+  if (marker) return;
+
+  let entries;
+  try {
+    entries = fs
+      .readdirSync(projectRoot)
+      .filter((n) => n !== '.DS_Store' && n !== 'Thumbs.db');
+  } catch {
+    entries = [];
+  }
+
+  if (entries.length === 0) {
+    console.log(
+      '  INFO: Empty directory detected — Kushi will create a fresh install here.\n',
+    );
+    return;
+  }
+
+  console.warn(
+    '  WARN: This directory has files but no recognized project marker',
+  );
+  console.warn(
+    '        (e.g. package.json, .git, pyproject.toml, *.csproj, or a Kushi',
+  );
+  console.warn(
+    '        engagement folder containing Evidence/, State/, or integrations.yml).',
+  );
+  console.warn('');
+  console.warn('  If this is intentional, press Enter to accept the default path.');
+  console.warn('  Otherwise, Ctrl+C and either:');
+  console.warn('    • run `git init` first (for a new code project), or');
+  console.warn('    • cd into your engagement folder (where Evidence/ lives), or');
+  console.warn('    • re-run with `--yes` to suppress this check in scripted use.\n');
+}
+
+/**
+ * Return the first matching project/engagement marker in `dir`, or null.
+ * @param {string} dir
+ * @returns {{ name: string, kind: 'code'|'engagement', type: 'file'|'dir' } | null}
+ */
+function findProjectMarker(dir) {
+  let entries;
+  try {
+    entries = fs.readdirSync(dir, { withFileTypes: true });
+  } catch {
+    return null;
+  }
+
+  for (const marker of PROJECT_MARKERS) {
+    if (marker.glob) {
+      const hit = entries.find(
+        (e) => e.isFile() && marker.glob.test(e.name),
+      );
+      if (hit) return { name: hit.name, kind: marker.kind, type: 'file' };
+      continue;
+    }
+    const hit = entries.find((e) => e.name === marker.name);
+    if (!hit) continue;
+    if (marker.type === 'dir' && hit.isDirectory()) {
+      return { name: marker.name, kind: marker.kind, type: 'dir' };
+    }
+    if (marker.type === 'file' && hit.isFile()) {
+      return { name: marker.name, kind: marker.kind, type: 'file' };
+    }
+  }
+  return null;
 }

package/src/settings.mjs

@@ -4,12 +4,12 @@ import { modify, applyEdits, parse, printParseErrorCode } from 'jsonc-parser';
 import { SETTINGS_MAP } from './constants.mjs';
 
 /**
- * Merge Nova settings into .vscode/settings.json (JSONC-safe).
+ * Merge Kushi settings into .vscode/settings.json (JSONC-safe).
  * Creates the file and directory if they don't exist.
  * Additive-only: never removes existing entries.
  *
  * @param {string} projectRoot – the user's project root (cwd)
- * @param {string} destination – relative destination path (e.g. ".nova")
+ * @param {string} destination – relative destination path (e.g. ".kushi")
  * @returns {{ created: boolean, keysAdded: string[], keysUnchanged: string[] }}
  */
 export function mergeSettings(projectRoot, destination) {