kushi-agents 3.13.0 → 3.14.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kushi-agents",
-  "version": "3.13.0",
+  "version": "3.14.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/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) {