kushi-agents 5.6.3 → 5.6.5

package/README.md

@@ -151,7 +151,7 @@ kushi explain hooks
 Teach kushi project-specific conventions that persist across runs.
 
 ```bash
-kushi remember "always use 'HCA' not 'Healthcare Accelerator' in summaries"
+kushi remember "always use 'Northwind' not 'Healthcare Accelerator' in summaries"
 ```
 
 Rules stored in `Evidence/<alias>/State/CLAUDE.md`. Read by `build-state`, `ask-project`, `refresh-project` at run start.

package/bin/cli.mjs

@@ -165,7 +165,7 @@ if (args.length > 0 && args[0] === 'explain') {
 if (args.length > 0 && args[0] === 'remember') {
   const rule = args.slice(1).join(' ');
   if (!rule) {
-    console.error('\n  Usage: kushi remember <rule>\n\n  Example: kushi remember "always use HCA not Healthcare Accelerator"\n');
+    console.error('\n  Usage: kushi remember <rule>\n\n  Example: kushi remember "always use Northwind not Healthcare Accelerator"\n');
     process.exit(1);
   }
   await dispatchRemember(rule);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kushi-agents",
-  "version": "5.6.3",
+  "version": "5.6.5",
   "description": "Install Kushi — multi-source project evidence agent with Comprehensive Structured Capture (CSC) into weekly-only files across Email, Teams, OneNote, Loop, SharePoint, Meetings, CRM, ADO. Meetings retain a sibling verbatim/ audit folder. WorkIQ-only for M365 sources (Graph / m365_* FORBIDDEN as fallbacks; user-paste is first-class). Host-agnostic.",
   "type": "module",
   "bin": {
@@ -58,4 +58,3 @@
     "access": "public"
   }
 }
-

package/plugin/agents/kushi.agent.md

@@ -1,7 +1,7 @@
 ---
 name: Kushi
 description: "Kushi — multi-source project evidence + Q&A agent. Snapshot + stream capture across Email, Teams, OneNote, Loop, SharePoint, Meetings, CRM, ADO; plus read-only natural-language Q&A over the captured evidence. WorkIQ-first for capture, citation-only for answers. Host-agnostic. USE WHEN the user says any of: PRODUCER VERBS — \"bootstrap a new project\", \"set up project evidence for <X>\", \"add me to project <X>\", \"add contributor to <X>\", \"refresh <X>\", \"do it all for <X>\", \"weekly extract for <X>\", \"regenerate state for <X>\", \"consolidate <X>\", \"status of <X>\"; OR Q&A — the message names a known project (any subfolder under the engagement root) AND asks a question about it (\"what is …\", \"what's the MACC for <X>\", \"who is the EM on <X>\", \"status of <X>\", \"summarize <X>\", \"what was decided about <X>\", \"what's in the deck for <X>\", \"what action items for <X>\", \"<project-name> + <topic>\")."
-argument-hint: "Name a project (e.g. 'bootstrap HCA', 'refresh AGCO last 14 days', 'ask HCA what's the MACC?'). Kushi routes to the right verb prompt — never run `npx kushi-agents <verb>` in the terminal."
+argument-hint: "Name a project (e.g. 'bootstrap Northwind', 'refresh Fabrikam last 14 days', 'ask Northwind what's the MACC?'). Kushi routes to the right verb prompt — never run `npx kushi-agents <verb>` in the terminal."
 tools:
   [vscode/vscodeAPI, execute/getTerminalOutput, execute/runInTerminal, read/readFile, read/terminalSelection, read/terminalLastCommand, agent, edit, search, web, browser, 'workiq/*', 'github/*']
 ---

package/plugin/instructions/ado-bootstrap-discovery.instructions.md

@@ -40,7 +40,7 @@ boundaries:
 | Correct disposition | Resolve via 4-step REST sequence | Run discovery, record `no-match`, KEEP RETRYING on every refresh |
 | `disabled: true` legitimate? | Only after exhaustive 5-step sequence + user-ask | Only after user explicit opt-out |
 
-For John Deere on 2026-05-18: the CRM record (FE-2026-001791) exists and was missed (defect). The ADO engagement work item does NOT exist yet (expected; intake just happened 2026-05-13). Both currently land as `disabled: true` because bootstrap treats them the same — that's the defect this rule fixes.
+For Acme on 2026-05-18: the CRM record (FE-2026-001791) exists and was missed (defect). The ADO engagement work item does NOT exist yet (expected; intake just happened 2026-05-13). Both currently land as `disabled: true` because bootstrap treats them the same — that's the defect this rule fixes.
 
 ## Required execution at bootstrap time
 
@@ -56,7 +56,7 @@ After ADO config presence + auth probe succeed:
      AND [System.State] <> 'Removed'
    ORDER BY [System.ChangedDate] DESC
    ```
-   Tokens = each word/phrase from the project name (e.g. for "John Deere": tokens `John Deere`, `Deere`, `JDDO`, `JDIS`).
+   Tokens = each word/phrase from the project name (e.g. for "Acme": tokens `Acme`, `Deere`, `JDDO`, `JDIS`).
 
 2. **WIQL probe 2 — Any WI type by title (catches Activity-only patterns or wrong-typed engagements)**:
    ```sql
@@ -72,7 +72,7 @@ After ADO config presence + auth probe succeed:
    ```sql
    WHERE [System.Tags] CONTAINS '<slug>'
    ```
-   Slug = lowercased token, hyphenated (`john-deere`, `deere`, `jddo`).
+   Slug = lowercased token, hyphenated (`acme`, `deere`, `jddo`).
 
 4. **WIQL probe 4 — CRM cross-link (if CRM record_id was resolved)**:
    ```sql

package/plugin/instructions/capture-learnings.instructions.md

@@ -43,7 +43,7 @@ Don't capture: one-off transient errors (network blip, expired token), or things
 
 **Doctrine impact**: which SKILL.md, instructions file, or template was updated in the same commit. Link by relative path. If "none yet — register only", say so explicitly and open a TODO.
 
-**Discovered during**: project name + skill that hit it (e.g. `HCA / pull-crm`).
+**Discovered during**: project name + skill that hit it (e.g. `Northwind / pull-crm`).
 ```
 
 Newest entry on top. Never delete — only mark superseded with a one-liner.

package/plugin/instructions/crm-bootstrap-discovery.instructions.md

@@ -6,7 +6,7 @@ applyTo: "**/skills/bootstrap-project/**, **/skills/pull-crm/**, **/skills/refre
 
 ## The defect this rule exists to prevent
 
-Bootstrap runs that wrote `boundaries.crm.disabled: true` after a single shallow probe (e.g. WorkIQ-only, or no live Dataverse REST call at all) — when in fact a live `contains(new_title, '<token>')` query would have resolved the record instantly. The result: pull-crm is then never dispatched on subsequent refreshes, the project Evidence/crm/ folder stays empty, and the CRM record drifts unsynced. Discovered 2026-05-18 on the John Deere bootstrap — FE-2026-001791 was missed because the title-first REST probe was never issued.
+Bootstrap runs that wrote `boundaries.crm.disabled: true` after a single shallow probe (e.g. WorkIQ-only, or no live Dataverse REST call at all) — when in fact a live `contains(new_title, '<token>')` query would have resolved the record instantly. The result: pull-crm is then never dispatched on subsequent refreshes, the project Evidence/crm/ folder stays empty, and the CRM record drifts unsynced. Discovered 2026-05-18 on the Acme bootstrap — FE-2026-001791 was missed because the title-first REST probe was never issued.
 
 ## The rule
 

package/plugin/instructions/customer-hint-discovery.instructions.md

@@ -7,7 +7,7 @@ description: "Customer-hint discovery sweep — bootstrap MUST attempt WorkIQ-dr
 
 ## The defect this rule exists to prevent
 
-Bootstrap runs that scaffold an empty `<project>/integrations.yml#boundaries.*` and immediately declare every source `blocked-config` — without ever asking WorkIQ "who/what mentions this customer?". The result: a fresh project bootstrap finishes with 0 evidence pulled, the user is told to hand-populate mailboxes / chat IDs / channel IDs / meeting join URLs / SharePoint sites, and the entire value proposition of "bootstrap a project from a customer hint" collapses to a config form. Discovered 2026-05-26 on the HCA bootstrap — every source row read `blocked-config` despite extensive HCA email / Teams / meeting history in the tenant.
+Bootstrap runs that scaffold an empty `<project>/integrations.yml#boundaries.*` and immediately declare every source `blocked-config` — without ever asking WorkIQ "who/what mentions this customer?". The result: a fresh project bootstrap finishes with 0 evidence pulled, the user is told to hand-populate mailboxes / chat IDs / channel IDs / meeting join URLs / SharePoint sites, and the entire value proposition of "bootstrap a project from a customer hint" collapses to a config form. Discovered 2026-05-26 on the Northwind bootstrap — every source row read `blocked-config` despite extensive Northwind email / Teams / meeting history in the tenant.
 
 ## The rule
 
@@ -33,7 +33,7 @@ Any other path that writes `blocked-config` without attempting the sweep is a **
 
 ## Required inputs
 
-- `<customer-hint>` — verbatim string the user provided at bootstrap invocation (e.g. `HCA`). Captured by `bootstrap-project` Step 0/1 and persisted to `<project>/bootstrap-status.md` under `Customer Hint:`. Used VERBATIM in v4.8.0 — no fuzzy expansion (deferred to v4.9.0).
+- `<customer-hint>` — verbatim string the user provided at bootstrap invocation (e.g. `Northwind`). Captured by `bootstrap-project` Step 0/1 and persisted to `<project>/bootstrap-status.md` under `Customer Hint:`. Used VERBATIM in v4.8.0 — no fuzzy expansion (deferred to v4.9.0).
 - `<lookback-days>` — defaults to **90** for discovery (longer than the 30-day pull window so historical chats / series still surface). Configurable via `<workspace>/.kushi/config/user/m365-mutable.json#bootstrap.discoveryLookbackDays`.
 - `<project>` — engagement name (already resolved).
 - `<alias>` — current contributor.
@@ -74,10 +74,10 @@ For each source whose sweep runs:
 
    | Source | Hint | Query attempted | Candidates found | Persisted | Deferred | Discovered by |
    |---|---|---|---|---|---|---|
-   | email | HCA | "In my Inbox..." | 7 | 7 | 0 | ushak |
-   | teams | HCA | "In my Teams chats..." | 14 | 10 | 4 | ushak |
-   | meetings | HCA | "In my calendar..." | 3 | 3 | 0 | ushak |
-   | sharepoint | HCA | "In my SharePoint sites..." | 0 | 0 | 0 | ushak |
+   | email | Northwind | "In my Inbox..." | 7 | 7 | 0 | ushak |
+   | teams | Northwind | "In my Teams chats..." | 14 | 10 | 4 | ushak |
+   | meetings | Northwind | "In my calendar..." | 3 | 3 | 0 | ushak |
+   | sharepoint | Northwind | "In my SharePoint sites..." | 0 | 0 | 0 | ushak |
    ```
 
 ## Behavior matrix (per source)
@@ -114,7 +114,7 @@ When the user re-runs bootstrap on a project that already has populated boundari
 ## Forbidden behaviors
 
 1. **Declaring `blocked-config` without running the sweep first** for email/teams/meetings/sharepoint — see "The defect" above. CRM/ADO have their own mandates in `crm-bootstrap-discovery` / `ado-bootstrap-discovery`.
-2. **Auto-narrowing the customer hint** ("HCA" → "HCA Healthcare Inc"). Use the hint verbatim. Smart-expansion is v4.9.0.
+2. **Auto-narrowing the customer hint** ("Northwind" → "Northwind Healthcare Inc"). Use the hint verbatim. Smart-expansion is v4.9.0.
 3. **Discovering across all sources in one mega-query.** Each source has its own narrow WorkIQ prompt (see per-source doctrines). Mega-queries punt to Graph and return empty.
 4. **Inferring local OneDrive sync paths from the hint** for SharePoint `local_folders[]`. Discovery populates `site_urls[]` only.
 5. **Calling Graph / `m365_*` directly for discovery.** Per `workiq-only.instructions.md` the four sources covered here use WorkIQ exclusively. The only allowed `m365_*` exceptions remain `m365_list_chat_messages` (parallel structured dump per pull-teams) and the per-source carve-outs already named in their pull-* SKILLs.

package/plugin/instructions/deferred-retry-on-workiq-fail.instructions.md

@@ -44,7 +44,7 @@ The next `refresh-project` run drains the queue first (Step 2a). On success, the
 # Drained by refresh-project Step 2a. Deleted on retry success.
 schema_version: 1
 source: meetings          # one of: email, teams, meetings, onenote, sharepoint, crm, ado, misc, identity
-project: HCA
+project: Northwind
 alias: ushak
 created_at: 2026-05-20T12:30:00Z
 attempts: 1

package/plugin/instructions/email-bootstrap-discovery.instructions.md

@@ -11,7 +11,7 @@ Governed by `customer-hint-discovery.instructions.md` — read that file first f
 
 | Boundary key | Element shape | Example |
 |---|---|---|
-| `boundaries.email.mailboxes[]` | string — mail folder path relative to mailbox root | `"Inbox"`, `"Inbox/HCA"`, `"FDE/HCA Intake"` |
+| `boundaries.email.mailboxes[]` | string — mail folder path relative to mailbox root | `"Inbox"`, `"Inbox/Northwind"`, `"FDE/Northwind Intake"` |
 
 Optional narrowing fields (`sender_domains[]`, `subject_keywords[]`) are NOT populated by the sweep — they are user-supplied narrowing.
 
@@ -25,7 +25,7 @@ workiq ask -q "In my Outlook mail folders, find the top mail folders that contai
 
 Substitution rules:
 
-- `<HINT>` = the verbatim customer hint from `bootstrap-status.md#Customer Hint` (e.g. `HCA`).
+- `<HINT>` = the verbatim customer hint from `bootstrap-status.md#Customer Hint` (e.g. `Northwind`).
 - `<N>` = `m365-mutable.json#bootstrap.discoveryLookbackDays` (default 90).
 
 The phrasing is **natural-language by folder content** — empirically the only shape that returns folder paths. WorkIQ punts on any other shape (see Forbidden phrasings).
@@ -49,7 +49,7 @@ WorkIQ returns a markdown table. Parse rows where `folder path` is non-empty and
 3. Cap at top 10 by `message count`.
 4. The remainder (if any) goes to `<project>/OPEN-QUESTIONS-DRAFT.md` per the orchestration doctrine.
 5. Confidence ranking:
-   - `high` — folder path explicitly contains the hint (case-insensitive substring), e.g. `Inbox/HCA Intake` for hint `HCA`.
+   - `high` — folder path explicitly contains the hint (case-insensitive substring), e.g. `Inbox/Northwind Intake` for hint `Northwind`.
    - `medium` — message count ≥ 10 AND folder is a known well-known root (`Inbox`, `Sent Items`, `Archive`).
    - `low` — everything else.
 
@@ -70,8 +70,8 @@ total_candidates_found: 7
 candidates_persisted: 7
 candidates_deferred: 0
 results:
-  - value: 'Inbox/HCA Intake'
-    label: 'Inbox/HCA Intake (245 messages, last 2026-05-25)'
+  - value: 'Inbox/Northwind Intake'
+    label: 'Inbox/Northwind Intake (245 messages, last 2026-05-25)'
     confidence: high
     needs_review: true
   - value: 'Inbox'

package/plugin/instructions/fallback-status-reporting.instructions.md

@@ -60,7 +60,7 @@ This rule is the **summary-time companion** to:
 1. **Overall task `failed` when evidence was written.** If `pull-crm` resolved the record via account-lookup (resolution step 2) and wrote the snapshot file, `sources.crm.last_status` is `ok`, not `failed`. The direct-title-match attempt status goes into `errors[]` with `action_taken: fell-back-to-account-lookup`.
 2. **Hiding the direct-path failure when fallback succeeded.** Do not omit the original failure from `errors[]` just because the fallback worked. The audit trail matters; future runs and learnings depend on it.
 3. **Conflating `completed-via-fallback` with `partial`.** They are different: `partial` = task delivered less than requested scope; `completed-via-fallback` = task delivered the requested scope but via the alternate path. Use `completed-via-fallback (partial)` when both apply.
-4. **Writing `blocked: missing X` when X was satisfied via an override.** The HCA bootstrap (2026-05-20) mis-reported CRM/ADO/Teams as `blocked: missing shared connection values` even though per-project `integrations.yml` had `environment_url_override`, `engagement_id`, and `chat_ids` fully pinned. The correct status was `completed via per-project effective-config`. Always check the effective-config result, not just the global-config layer.
+4. **Writing `blocked: missing X` when X was satisfied via an override.** The Northwind bootstrap (2026-05-20) mis-reported CRM/ADO/Teams as `blocked: missing shared connection values` even though per-project `integrations.yml` had `environment_url_override`, `engagement_id`, and `chat_ids` fully pinned. The correct status was `completed via per-project effective-config`. Always check the effective-config result, not just the global-config layer.
 
 ## Render examples
 

package/plugin/instructions/full-view-gate.instructions.md

@@ -11,11 +11,11 @@ When a prompt asks Kushi to characterize a project's current state — analysis,
 
 This gate applies whenever the question is about a project / customer / engagement under the engagement root, including prompts that don't explicitly say "refresh" or "report":
 
-- "what's the status of HCA"
+- "what's the status of Northwind"
 - "summarize ABN AMRO"
 - "what are the risks on Hovnanian"
 - "what's been decided about funding for Lilly"
-- "next steps for AGCO"
+- "next steps for Fabrikam"
 - "what did the customer say in the last meeting about X"
 - any `/kushi ask-project <project> <question>` invocation
 

package/plugin/instructions/identity-resolution.instructions.md

@@ -114,7 +114,7 @@ The `setup` skill does the deeper recovery (3-retry loop with `ask_user` choices
 Question text (only asked once, only by `setup`, only when `emailContext.folders` is empty or `["__FILL_ME_IN__"]`):
 
 > Which mailbox folders should kushi search for email evidence?
-> • Enter a comma-separated list (e.g. `Inbox, Archive, Projects/HCA`)
+> • Enter a comma-separated list (e.g. `Inbox, Archive, Projects/Northwind`)
 > • Type `all` to search the FULL mailbox (slower — every refresh scans everything)
 > • Press Enter to leave blank (equivalent to `all`)
 

package/plugin/instructions/karpathy-state-layout.instructions.md

@@ -53,7 +53,7 @@ Folder names are lowercase, no spaces. `build-state` creates them on demand.
 kushi_state_page: true
 category: opportunity              # one of: people | opportunity | ado-work-item | decision | risk | customer-ask | meeting | artifact
 entity_ids: ["crm://entity=opportunity/id=<guid>"]
-related: ["[[alice-smith]]", "[[hca-weekly-sync]]"]
+related: ["[[ushak-smith]]", "[[northwind-weekly-sync]]"]
 last_synthesized_iso: "2026-05-26T20:00:00Z"
 synthesized_by_alias: "ushak"
 ---
@@ -70,7 +70,7 @@ synthesized_by_alias: "ushak"
 - `[[slug]]` resolves to `State/<category>/<slug>.md`. The category folder
   is inferred from the target page's `category` front-matter.
 - Slugs are **lowercase-kebab-case** derived from the page title (e.g.
-  "HCA FY26 Renewal" → `hca-fy26-renewal`). Producers MUST emit slugs
+  "Northwind FY26 Renewal" → `northwind-fy26-renewal`). Producers MUST emit slugs
   deterministically so two runs converge on the same filename.
 - `[[slug|display text]]` is allowed and rendered the way every wiki tool
   renders it.
@@ -89,7 +89,7 @@ addressable via the graph and `weekly/` directly.
 
 One file per cross-source entity. If two nodes legitimately share a slug
 (name collision), append a short stable suffix derived from the source +
-last 6 chars of the id (e.g. `alice-smith-ado-9f3c2a`).
+last 6 chars of the id (e.g. `ushak-smith-ado-9f3c2a`).
 
 ## Backward compatibility
 

package/plugin/instructions/m365-id-registry.instructions.md

@@ -106,7 +106,7 @@ Every refresh MUST:
 
 1. **Read** `m365-mutable.json#knownSections.<projectKey>` first. If the entry is missing or the per-source key is empty → DO NOT probe. Re-dispatch through `bootstrap-project` for that source's discovery only, then resume.
 2. **Pass the canonical IDs to each pull-* skill in the form that skill's WorkIQ queries actually use.** Different sources need different forms:
-   - **OneNote (corrected v3.8.0):** PRIMARY path is browser-scrape via Playwright with persisted profile (returns reliable verbatim bodies — 16/16 captured for HCA on 2026-05-14 vs WorkIQ's 1/18). FALLBACK path is WorkIQ natural-language by display name (used only when Playwright profile is auth-expired). Per-page identifiers are stored in BOTH forms: `webPageId` (used by browser-scrape navigation) AND `wdpartid` (used by WorkIQ correlation and stream events). See `pull-onenote/SKILL.md` v2.6.0 § "Empirical contract" and `learnings/onenote.md` 2026-05-14 for proof. The v3.7.8 wdsectionfileid-filter doctrine and the v3.7.9 WorkIQ-primary doctrine are both retracted.
+   - **OneNote (corrected v3.8.0):** PRIMARY path is browser-scrape via Playwright with persisted profile (returns reliable verbatim bodies — 16/16 captured for Northwind on 2026-05-14 vs WorkIQ's 1/18). FALLBACK path is WorkIQ natural-language by display name (used only when Playwright profile is auth-expired). Per-page identifiers are stored in BOTH forms: `webPageId` (used by browser-scrape navigation) AND `wdpartid` (used by WorkIQ correlation and stream events). See `pull-onenote/SKILL.md` v2.6.0 § "Empirical contract" and `learnings/onenote.md` 2026-05-14 for proof. The v3.7.8 wdsectionfileid-filter doctrine and the v3.7.9 WorkIQ-primary doctrine are both retracted.
    - **Email / Teams / SharePoint / CRM / ADO:** the registry IDs are passed as documented in each pull-* skill — typically as Graph IDs in API calls, not WorkIQ prose.
    - **Misc (pull-misc v0.1.0+):** the link list is the user-curated `<project>/external-links.txt` file. Refresh re-parses the file every run, matches existing `misc_links[]` entries by `(type, url)` tuple, marks deleted entries as `removed` (preserves snapshot), creates new entries as `not-yet-attempted`, and routes per-type to runner branches (browser for loop, http for web/learn/docs/pdf/github, file for local, delegated for onenote/sharepoint/ado). See `pull-misc/SKILL.md` § "Step A — enumerate".
 3. **Never re-discover.** A refresh that probes WorkIQ with seeds (folder name, channel name) instead of canonical IDs is a defect. The only exception is the cleanup-on-resolution path documented in `cleanup-on-resolution.instructions.md`, which UPSERTS newly-resolved IDs into the registry mid-run.

package/plugin/instructions/meetings-bootstrap-discovery.instructions.md

@@ -67,7 +67,7 @@ Additional field for meetings sidecar:
 ```yaml
 results:
   - value: 'https://teams.microsoft.com/l/meetup-join/19%3a...'
-    label: 'HCA Weekly Sync (Weekly Tue 10:00 ET; organizer: jdoe@hcahealthcare.com)'
+    label: 'Northwind Weekly Sync (Weekly Tue 10:00 ET; organizer: jdoe@hcahealthcare.com)'
     recurrence: weekly
     organizer_email: 'jdoe@hcahealthcare.com'
     most_recent_occurrence: '2026-05-21'

package/plugin/instructions/meetings-verbatim-required.instructions.md

@@ -14,7 +14,7 @@ Meetings differ from every other evidence class in one critical way: **the sourc
 - Copilot recap cards persist only as long as the meeting object does.
 - Attendee memory degrades to zero within weeks.
 
-Email bodies, OneNote pages, SharePoint files, CRM records, and ADO work items all persist in their source systems indefinitely (or for years). Meetings do not. If the curated 7-section meeting summary is the only artifact kushi captures, and the recording later expires, **the evidence is unrecoverable**. This has happened in production (see `learnings/meetings.md` — FDE Intake John Deere, 2026-05-18).
+Email bodies, OneNote pages, SharePoint files, CRM records, and ADO work items all persist in their source systems indefinitely (or for years). Meetings do not. If the curated 7-section meeting summary is the only artifact kushi captures, and the recording later expires, **the evidence is unrecoverable**. This has happened in production (see `learnings/meetings.md` — FDE Intake Acme, 2026-05-18).
 
 ## The rule
 
@@ -134,7 +134,7 @@ If steps 2(a-d) all return empty AND chat in step 3 is also empty: meeting is `u
 
 ## Naming
 
-- Folder: `<YYYY-MM-DD>-<HHMM>_<slug>` — e.g. `2026-05-13-1530_fde-intake-john-deere`
+- Folder: `<YYYY-MM-DD>-<HHMM>_<slug>` — e.g. `2026-05-13-1530_fde-intake-acme`
 - Slug rules: lowercase, ASCII, spaces and punctuation → single hyphen, collapse repeats, trim trailing hyphens, max 60 chars.
 - Time: meeting start time in the user's local timezone (per `m365_get_mailbox_settings`), 24h, no separator.
 - If two meetings share start time + slug: append `-2`, `-3`, etc.
@@ -144,7 +144,7 @@ If steps 2(a-d) all return empty AND chat in step 3 is also empty: meeting is `u
 Inside the curated snapshot/stream files, cite verbatim files with the kushi standard format:
 
 ```
-[source: Evidence/<alias>/meetings/verbatim/2026-05-13-1530_fde-intake-john-deere/chat-messages.md · 2026-05-13]
+[source: Evidence/<alias>/meetings/verbatim/2026-05-13-1530_fde-intake-acme/chat-messages.md · 2026-05-13]
 ```
 
 The curated snapshot is the assertion; the verbatim file is the evidence. The two must always travel together.

package/plugin/instructions/multi-wiki-routing.instructions.md

@@ -53,7 +53,7 @@ Source provenance MUST be visible per citation: `[project: <alias>]` vs `[global
 ### 4. teach — global-first for cross-cutting topics
 
 - For **cross-cutting topics** (kushi concepts, doctrines, releases — e.g. "explain confidence ladder", "how does CSC work"): `teach` consults the global wiki FIRST (if a matching page exists in `~/.kushi-global/State/answers/`), then falls back to in-repo doctrine, then to genealogy.
-- For **project-specific topics** ("how did we structure intake for AGCO?"): `teach` declines and suggests `kushi ask <project> <q>` instead — that's an `ask-project` job.
+- For **project-specific topics** ("how did we structure intake for Fabrikam?"): `teach` declines and suggests `kushi ask <project> <q>` instead — that's an `ask-project` job.
 - Citations distinguish `[global: <page>]` vs `[doctrine: <file>]` vs `[genealogy: <version>]`.
 
 ### 5. Promotion path — explicit only

package/plugin/instructions/no-hallucinated-success.instructions.md

@@ -0,0 +1,45 @@
+---
+name: "no-hallucinated-success"
+version: "5.6.5"
+applyTo: "**/plugin/skills/**/SKILL.md"
+description: "Forbids the LLM from synthesizing 'success' messages when a runner / shell tool did not actually execute. Any verb that delegates to a runner MUST report the runner's literal stdout, or the literal error / exit code, or refuse with a remediation. No paraphrasing of expected outcomes. Filed after the 2026-05-29 GH Copilot Chat incident where @kushi bootstrap Northwind returned a confident success report without ever running plugin/runners/bootstrap.mjs."
+---
+
+# No hallucinated success
+
+## Why
+
+On 2026-05-29 a user issued `@kushi bootstrap Northwind` in GH Copilot Chat. The agent responded with a well-formatted, paragraph-styled success report listing every file the runner *would* create. **No runner ever ran. No files were created.** The LLM fabricated the report by paraphrasing `bootstrap-project/SKILL.md`'s documented success shape.
+
+This pattern is catastrophic for trust. The user has no immediate way to tell "ran successfully" from "lied confidently". Same risk exists for every `pull-*` / `refresh-project` / `aggregate-project` / `consolidate-evidence` skill that delegates to a runner.
+
+## Hard rules
+
+For every skill whose SKILL.md says it delegates to a `plugin/runners/<x>.mjs` (or any other shell tool):
+
+1. **THE LLM MUST INVOKE THE RUNNER.** The skill is a thin pointer at deterministic code. Skipping the shell call and synthesizing the answer is **forbidden** under any circumstance — including when the LLM "is sure" what the output would be.
+
+2. **THE LLM MUST PRESENT THE RUNNER'S LITERAL STDOUT.** When the runner emits JSON (`{ status, project, alias, created[], existed[], ... }`), the user-facing reply MUST quote that JSON verbatim (in a fenced block) before any paraphrase. The paraphrase, if any, MUST be derived from the JSON the runner actually emitted — not from the SKILL.md template.
+
+3. **TOOL FAILURES MUST FAIL LOUDLY.** If the runner cannot be invoked (file not found, ENOENT, permission denied, missing dep, non-zero exit, timeout):
+   - Report the actual error: command, cwd, exit code, stderr (or first 20 lines of it).
+   - DO NOT pretend it succeeded. DO NOT skip to "Next steps".
+   - Offer concrete remediation (e.g. "runners/ missing → run `npx kushi-agents@latest --profile full --force` in this repo").
+
+4. **NO TEMPLATE-DRIVEN SUCCESS COPY.** Phrases like "Bootstrap completed for X", "Created key project files: …", "Created key evidence folders: …" are forbidden UNLESS they are a direct paraphrase of a real runner stdout from the current turn. If the LLM finds itself reaching for the SKILL.md "what gets scaffolded" section to compose its reply, it has already failed this rule.
+
+5. **WHEN IN DOUBT, RE-RUN.** Runners are idempotent (`existed[]` reports already-present paths and writes nothing). Re-invocation costs nothing. If the LLM is uncertain whether a previous tool call actually succeeded, the correct action is another invocation, not a confident-sounding summary.
+
+## Required SKILL.md acknowledgment
+
+Every SKILL.md that delegates to a runner MUST include this line in its "LLM responsibilities" section:
+
+> **No hallucinated success.** Echo the runner's literal stdout JSON before any paraphrase. If the runner can't be invoked, surface the real error — never synthesize a success message from this SKILL.md's template. See `plugin/instructions/no-hallucinated-success.instructions.md`.
+
+## Probe (self-check)
+
+A self-check probe SHOULD scan every SKILL.md that mentions `plugin/runners/` and verify the acknowledgment line is present. Missing acknowledgment = self-check failure.
+
+## Discovered
+
+`@kushi bootstrap Northwind` in VS Code Chat / GH Copilot Chat, 2026-05-29. See `plugin/learnings/cross-cutting.md` § 2026-05-29 for the full incident.

package/plugin/instructions/onedrive-pin-policy.instructions.md

@@ -93,9 +93,9 @@ Output:
 
 ```
 🔧 Optimizing OneDrive cache for your engagement…
-   ✅ Pinned (kept on device): HCA/Evidence/ushak/, HCA/State/, HCA/_Consolidated/,
+   ✅ Pinned (kept on device): Northwind/Evidence/ushak/, Northwind/State/, Northwind/_Consolidated/,
                                + project-level run-log.yml + integrations.yml
-   ➖ Left cloud-only (downloaded on demand): HCA/Evidence/bob/, HCA/Evidence/maria/
+   ➖ Left cloud-only (downloaded on demand): Northwind/Evidence/bob/, Northwind/Evidence/maria/
    Disk impact: ~180 MB local · ~6.2 GB available cloud-only.
    Change later: right-click any folder → 'Always keep on device' / 'Free up space',
                  or run @Kushi setup --reconfigure.

package/plugin/instructions/run-reports.instructions.md

@@ -58,7 +58,7 @@ Newest at the bottom of `Get-ChildItem` listings (sortable by name = sortable by
 ## Resolutions this run
 
 For each ID/folder/section newly resolved during this run, one bullet:
-- `ado.engagement_id` resolved to `96944` (HCA - Engagement) — pinned to integrations.yml + m365-mutable.json.
+- `ado.engagement_id` resolved to `96944` (Northwind - Engagement) — pinned to integrations.yml + m365-mutable.json.
 - `crm.record_id` resolved to `e561b31e-...` — pinned + env override applied (iscrm.crm.dynamics.com).
 
 ## Cleanups this run
@@ -70,8 +70,8 @@ Per `cleanup-on-resolution.instructions.md`. List entries pruned when a resoluti
 ## Learnings appended
 
 Per `capture-learnings.instructions.md`. List new entries written to `<KUSHI_ROOT>/plugin/learnings/<file>.md`:
-- `learnings/crm.md` — "Custom entities don't expose Annotations as a navigation property" (HCA / pull-crm).
-- `learnings/ado.md` — "$top=500 exceeds permissible range on workItems updates endpoint" (HCA / pull-ado).
+- `learnings/crm.md` — "Custom entities don't expose Annotations as a navigation property" (Northwind / pull-crm).
+- `learnings/ado.md` — "$top=500 exceeds permissible range on workItems updates endpoint" (Northwind / pull-ado).
 
 ## Skips & gaps
 
@@ -93,8 +93,8 @@ What was deliberately skipped or couldn't be retrieved, with reason:
 
 Plain-language list. What the contributor should do next, e.g.:
 - Review `Evidence/<alias>/email/stream/2026-05-04_email-stream.md` — 3 emails from James Gibbings have substantive customer needs that should land in `State/00_overview.md`.
-- Pin a SharePoint folder for HCA in `integrations.yml#boundaries.sharepoint.folder_paths` so next refresh covers it.
-- Re-run with `force-refresh HCA` if today's run looks partial.
+- Pin a SharePoint folder for Northwind in `integrations.yml#boundaries.sharepoint.folder_paths` so next refresh covers it.
+- Re-run with `force-refresh Northwind` if today's run looks partial.
 
 ---
 

package/plugin/instructions/schema-evolve.instructions.md

@@ -60,7 +60,7 @@ Auto-detection: when the user says "from now on...", "always...", "never...", "f
 ## Examples
 
 ```
-> kushi remember "always use 'HCA' not 'Healthcare Accelerator' in summaries"
+> kushi remember "always use 'Northwind' not 'Healthcare Accelerator' in summaries"
 > kushi remember "treat John Smith as the primary EM for this project"
 > kushi remember "CRM entity 'opportunity' maps to our internal term 'deal'"
 ```

package/plugin/instructions/scope-boundaries.instructions.md

@@ -85,7 +85,7 @@ boundaries:
       - "microsoft.com"
       - "hcahealthcare.com"
     subject_keywords:                           # optional — additional narrowing
-      - "HCA"
+      - "Northwind"
       - "FE-2026-001458"
 
   teams:
@@ -105,7 +105,7 @@ boundaries:
 
   sharepoint:
     local_folders:                              # required if sharepoint enabled
-      - "C:\\…\\HCA"
+      - "C:\\…\\Northwind"
     site_urls: []                               # optional — for online-only docs
     drive_ids: []                               # optional — Graph-direct access
 
@@ -119,7 +119,7 @@ boundaries:
 
   ado:
     area_paths:                                 # required if ado enabled
-      - "ISE-Engagements\\HCA"
+      - "ISE-Engagements\\Northwind"
     iteration_paths: []                         # optional — for sprint-scoped queries
     initiative_query: ""                        # optional — saved WIQL query ID
     work_item_ids: []                           # optional — pin specific work items

package/plugin/instructions/sharepoint-bootstrap-discovery.instructions.md

@@ -9,7 +9,7 @@ Governed by `customer-hint-discovery.instructions.md` — read that file first f
 
 ## Empirical finding (kushi v4.8.1) — WorkIQ has no SharePoint site-inventory surface
 
-Validated against the live WorkIQ surface on 2026-05-26 with hint `HCA`: WorkIQ returns a hard punt — *"the sources do not contain site inventory or SharePoint site properties; I cannot construct the requested table without fabricating data (which I will not do per policy)."* This is consistent — tenant-wide SharePoint site enumeration requires Graph admin endpoints that WorkIQ does not expose.
+Validated against the live WorkIQ surface on 2026-05-26 with hint `Northwind`: WorkIQ returns a hard punt — *"the sources do not contain site inventory or SharePoint site properties; I cannot construct the requested table without fabricating data (which I will not do per policy)."* This is consistent — tenant-wide SharePoint site enumeration requires Graph admin endpoints that WorkIQ does not expose.
 
 **Therefore:**
 
@@ -62,7 +62,7 @@ WorkIQ commonly punts on this query (see Empirical finding above). Apply this cl
 5. Cap at top 10 by `most recent activity date` (descending). If activity date is missing, fall back to alphabetical site title.
 6. Confidence ranking:
    - `high` — site title contains the hint (case-insensitive substring).
-   - `medium` — site URL slug contains the hint (e.g. `/sites/HCA-Engagement` for hint `HCA`).
+   - `medium` — site URL slug contains the hint (e.g. `/sites/Northwind-Engagement` for hint `Northwind`).
    - `low` — match was on site description only.
 
 ## Sidecar file shape
@@ -71,9 +71,9 @@ Written to `<engagement-root>/<project>/Evidence/<alias>/_discovery/<YYYY-MM-DD>
 
 ```yaml
 results:
-  - value: 'https://contoso.sharepoint.com/sites/HCA-Engagement'
-    label: 'HCA Engagement (last activity 2026-05-24; default library: Documents)'
-    site_title: 'HCA Engagement'
+  - value: 'https://contoso.sharepoint.com/sites/Northwind-Engagement'
+    label: 'Northwind Engagement (last activity 2026-05-24; default library: Documents)'
+    site_title: 'Northwind Engagement'
     default_library: 'Documents'
     most_recent_activity: '2026-05-24'
     confidence: high

package/plugin/instructions/teams-bootstrap-discovery.instructions.md

@@ -16,7 +16,7 @@ Governed by `customer-hint-discovery.instructions.md` — read that file first f
 
 ## Empirical findings (kushi v4.8.1 — what WorkIQ actually returns)
 
-Validated against the live WorkIQ surface on 2026-05-26 with hint `HCA`:
+Validated against the live WorkIQ surface on 2026-05-26 with hint `Northwind`:
 
 - **Query 1 (chats) — works**, but WorkIQ returns `chat ID = N/A` (the column is present but empty). The chat ID MUST be extracted from the per-row message permalink URL — see "Parsing the response" below.
 - **Query 2 (channels) — DOES NOT WORK.** WorkIQ has no Teams channel-enumeration surface. Every empirical attempt either returned empty or reclassified channel hits as chats with `N/A` IDs. The query is retained below as a `best-effort` opt-in only — bootstrap MUST NOT block on it and MUST NOT write `last_status: blocked-config` when it returns 0. Manual user-supplied `channel_ids[]` is the only reliable path.
@@ -72,7 +72,7 @@ WorkIQ returns the `chat ID` column populated as `N/A` (empirical, v4.8.1). The
 5. Cap at top 10 by `most recent message date` (descending).
 6. Confidence ranking:
    - `high` — `chat topic` explicitly contains the hint (case-insensitive substring).
-   - `medium` — any member's email domain matches a known customer domain (heuristic: hint appears as substring in domain), e.g. hint `HCA` + member `@hcahealthcare.com`.
+   - `medium` — any member's email domain matches a known customer domain (heuristic: hint appears as substring in domain), e.g. hint `Northwind` + member `@hcahealthcare.com`.
    - `low` — match was on a member's display name only.
 
 **If no message permalink URL is found in a row**, that row CANNOT be persisted to `boundaries.teams.chat_ids[]` — log it to OPEN-QUESTIONS-DRAFT.md under `## Teams chats discovered without IDs` with the topic + members so the user can supply the chat id manually.

package/plugin/instructions/tracking.instructions.md

@@ -59,7 +59,7 @@ Every tracking file is Markdown with frontmatter + a small set of named sections
 ```markdown
 ---
 prompt: bootstrap                        # /bootstrap, /refresh, /ask, /fde-intake, ...
-project: hca                             # slugified engagement folder name
+project: northwind                             # slugified engagement folder name
 window: last 30 days                     # bootstrap/refresh only; otherwise omit
 started: 2026-05-19T14:02:00-04:00
 finished: 2026-05-19T14:38:12-04:00      # omit if still in progress
@@ -75,7 +75,7 @@ kushi_version: 4.1.0
 ## Inputs resolved
 
 - Engagement root: `C:/.../Engagement Assets`
-- Project folder: `HCA Healthcare`
+- Project folder: `Northwind Healthcare`
 - Alias: `ushak`
 - Config: `<workspace>/.kushi/config/user/project-evidence.yml`
 
@@ -93,13 +93,13 @@ kushi_version: 4.1.0
 
 ## Outputs
 
-- `HCA Healthcare/Evidence/ushak/email/snapshot/2026-05-19.md`
-- `HCA Healthcare/Evidence/ushak/teams/snapshot/2026-05-19.md`
-- `HCA Healthcare/State/00_overview.md` (updated)
+- `Northwind Healthcare/Evidence/ushak/email/snapshot/2026-05-19.md`
+- `Northwind Healthcare/Evidence/ushak/teams/snapshot/2026-05-19.md`
+- `Northwind Healthcare/State/00_overview.md` (updated)
 
 ## Open questions / next steps
 
-- ADO field `Custom.FDEStatusSummary` is empty — recommend running `/fde-report hca` next.
+- ADO field `Custom.FDEStatusSummary` is empty — recommend running `/fde-report northwind` next.
 - 3 OneNote pages returned `page-body-unavailable`; see notes in `Evidence/ushak/onenote/run-notes.md`.
 
 ## Errors / fallbacks

package/plugin/instructions/weekly-csc.instructions.md

@@ -15,7 +15,7 @@ In practice this caused two problems:
 1. **Empty snapshot folders.** Sources without retrievable bodies (OneNote payload-too-large,
    m365_get_email failures, no SharePoint site discovery) ended up with no `snapshot/`
    content. Users perceived empty folders as "kushi didn't pull anything".
-2. **Awkward queries.** Answering "what happened on HCA last week?" required reading
+2. **Awkward queries.** Answering "what happened on Northwind last week?" required reading
    `stream/<week>.md` per source AND walking `snapshot/` to know current state of entities
    touched that week. Six sources × two folder reads per query.
 
@@ -135,8 +135,8 @@ kushi_version: 4.9.0
 entities:
   # Stable entity-id chosen per source (see "Entity identity" below).
   - id: 'onenote://page/wdpartid=abc123'
-    display_name: 'HCA Architecture Overview'
-    entity_anchor: 'hca-architecture-overview'
+    display_name: 'Northwind Architecture Overview'
+    entity_anchor: 'northwind-architecture-overview'
     latest_csc_file: 'weekly/2026-05-25_onenote-csc.md'
     latest_csc_block_offset: 412               # line number of the entity heading
     last_touched: 2026-05-23T14:30:00Z
@@ -147,8 +147,8 @@ entities:
       - 2026-05-04
     status: captured                           # captured | body-not-exposed | unavailable | deferred
   - id: 'meetings://joinurl=https%3A%2F%2Fteams.microsoft.com%2F...'
-    display_name: 'HCA Weekly Sync'
-    entity_anchor: 'hca-weekly-sync-2026-05-21-1400'
+    display_name: 'Northwind Weekly Sync'
+    entity_anchor: 'northwind-weekly-sync-2026-05-21-1400'
     latest_csc_file: 'weekly/2026-05-25_meetings-csc.md'
     latest_csc_block_offset: 95
     last_touched: 2026-05-21T14:00:00Z
@@ -234,7 +234,7 @@ conflicts possible at the writer level.
 ```markdown
 # Email CSC — Week of 2026-05-25 (Mon–Sun)
 
-- Project: HCA
+- Project: Northwind
 - Alias: ushak
 - Source: email
 - Week: 2026-05-25 → 2026-05-31
@@ -245,19 +245,19 @@ conflicts possible at the writer level.
 ## Source Basis
 
 - WorkIQ enumeration call request-id abc123 returned 6 in-scope threads in folder
-   "Customers/HCA" between 2026-05-25 and 2026-05-31.
+   "Customers/Northwind" between 2026-05-25 and 2026-05-31.
 - 6 thread-level WorkIQ CSC calls returned full bulleted capture; no deferrals.
 
 ## Entities
 
-## HCA Compute Architecture Discussion {#hca-compute-arch-thread}
+## Northwind Compute Architecture Discussion {#northwind-compute-arch-thread}
 
 - Source basis: WorkIQ request-id def456, fidelity csc-full
 - Coverage window: 2026-05-25 → 2026-05-30
 - Last touched: 2026-05-30T09:12:00Z
 
 ### Participants / Present
-- John Doe <john@hca.com> — sender (initiated thread)
+- John Doe <john@northwind.com> — sender (initiated thread)
 - Sample Name <you@example.com> — recipient + responder
 - ...
 
@@ -296,8 +296,8 @@ generated_at: 2026-05-26T18:45:00Z
 kushi_version: 4.9.0
 entities:
   - id: 'email://conversation_id=AAQkAGI...'
-    display_name: 'HCA Compute Architecture Discussion'
-    entity_anchor: 'hca-compute-arch-thread'
+    display_name: 'Northwind Compute Architecture Discussion'
+    entity_anchor: 'northwind-compute-arch-thread'
     latest_csc_file: 'weekly/2026-05-25_email-csc.md'
     latest_csc_block_offset: 28
     last_touched: 2026-05-30T09:12:00Z