kushi-agents 3.15.0 → 4.1.0

package/.github/copilot-instructions.kushi.md

@@ -6,15 +6,18 @@ This workspace has [Kushi](https://gim-home.github.io/kushi/) installed under `.
 
 When the user types any of the following verbs followed by a project name, route to the corresponding Kushi prompt in `.kushi/prompts/` (no `@Kushi` needed):
 
-| Verb                       | Prompt to run                              |
-| -------------------------- | ------------------------------------------ |
-| `bootstrap <project>`      | `/pull-all-bootstrap`                      |
-| `refresh <project>`        | `/pull-all-refresh`                        |
-| `aggregate <project>`      | `/pull-all-aggregate`                      |
-| `state <project>`          | `/rebuild-state`                           |
-| `consolidate <project>`    | `/consolidate-evidence`                    |
-| `status <project>`         | `/show-run-log`                            |
-| `ask <project> <question>` | `/ask-project` (auto-routes to evidence Q&A) |
+| Verb                       | Prompt to run    |
+| -------------------------- | ---------------- |
+| `bootstrap <project>`      | `/bootstrap`     |
+| `refresh <project>`        | `/refresh`       |
+| `aggregate <project>`      | `/aggregate`     |
+| `state <project>`          | `/state`         |
+| `consolidate <project>`    | `/consolidate`   |
+| `status <project>`         | `/status`        |
+| `ask <project> <question>` | `/ask`           |
+| `fde-intake <project>`     | `/fde-intake`    |
+| `fde-report <project>`     | `/fde-report`    |
+| `fde-triage <project>`     | `/fde-triage`    |
 
 Project Q&A also auto-dispatches when the user names a known project under the engagement root **and** asks a question about it — no prefix needed.
 
@@ -29,10 +32,12 @@ Project Q&A also auto-dispatches when the user names a known project under the e
 ### Layout
 
 - `.kushi/agents/kushi.agent.md` — orchestrator (also addressable as `@Kushi`)
-- `.kushi/prompts/` — verb prompts (`/pull-*`, `/ask-project`, etc.)
+- `.kushi/prompts/` — verb prompts (`/bootstrap`, `/refresh`, `/ask`, etc.)
 - `.kushi/skills/` — per-source pull + render skills
 - `.kushi/instructions/` — doctrine (citations, WorkIQ-first, freshness gates)
-- `.kushi/reference-packs/` — bundled domain doctrine (override at project / user / packaged layers)
+- `.kushi/reference-packs/` — bundled domain doctrine (override at project / workspace / packaged layers)
+- `.kushi/config/` — **user-editable** (project-evidence.yml, integrations.yml, reference-overrides). Seeded on first install; never overwritten on upgrade.
+- `.kushi/tracking/` — **agent working memory** (runs/, qa/, fde/, research/). Per-run Markdown journals: what was asked, what was done, what was decided, what's still open. Gitignored by default. See `instructions/tracking.instructions.md`.
 - `.kushi/kushi-install.json` — profile manifest written by the installer
 
 Full docs: <https://gim-home.github.io/kushi/>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kushi-agents",
-  "version": "3.15.0",
+  "version": "4.1.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/agents/kushi.agent.md

@@ -95,7 +95,8 @@ When a user message arrives:
 ## Configuration layout
 
 ```
-<USER_HOME>/.copilot/project-evidence.yml          ← personal: alias, engagement_root, active_projects
+<workspace>/.kushi/config/project-evidence.yml     ← personal: alias, engagement_root, active_projects (seeded by installer; never overwritten)
+<workspace>/.kushi/config/integrations.yml         ← optional global CRM/ADO defaults (seeded by installer; never overwritten)
 <engagement-root>/.project-evidence/                ← per-machine, per-user M365 + CRM + ADO config (OneDrive-synced)
    m365/m365-auth.json
    m365/m365-mutable.json

package/plugin/instructions/azure-auth-patterns.instructions.md

@@ -227,7 +227,7 @@ Maintained alongside `auth-and-retry §3` (canonical) — quick lookup:
 | Dynamics 365 / CRM | `<engagement-root>/.project-evidence/crm/config.yml` |
 | Azure DevOps | `<engagement-root>/.project-evidence/ado/config.yml` |
 | Microsoft Graph / M365 / OneNote | `<engagement-root>/.project-evidence/m365/m365-mutable.json` + `<engagement-root>/.project-evidence/m365/m365-auth.json` |
-| WorkIQ CLI path | `~/.copilot/project-evidence.yml` (user-scoped) |
-| Global integrations (optional) | `~/.copilot/integrations/{crm,ado}/` |
+| WorkIQ CLI path | `<workspace>/.kushi/config/project-evidence.yml` (workspace-scoped) |
+| Global integrations (optional) | `<workspace>/.kushi/config/integrations.yml` |
 
 Always read tenant IDs, resource URLs, org URLs, and allowed-tenant lists from these files at the start of each run. **Never hardcode them in skills or prompts.** The only acceptable literal in instructions/prompts is the public Microsoft tenant ID `72f988bf-86f1-41af-91ab-2d7cd011db47` in the user-facing `az login --tenant ...` suggestion text.

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

@@ -11,9 +11,9 @@ 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).
+1. **`<workspace>/.kushi/config/project-evidence.yml`** — read `engagement_root:` field (preferred).
 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`.
+3. **Ask the user** once and persist the answer to `<workspace>/.kushi/config/project-evidence.yml engagement_root`.
 
 ## Live config location
 
@@ -43,7 +43,7 @@ Once `<engagement-root>` is known, individual projects are subfolders:
 Project name resolution (always fuzzy):
 
 1. Match against keys in `<engagement-root>/.project-evidence/m365/m365-mutable.json m365Mutable.knownSections`.
-2. Match against `active_projects:` in `<USER_HOME>/.copilot/project-evidence.yml`.
+2. Match against `active_projects:` in `<workspace>/.kushi/config/project-evidence.yml`.
 3. Match against actual subfolder names under `<engagement-root>`.
 
 Case-insensitive; ranking `exact > prefix > contains`. Multiple plausible candidates → ask user to pick. Zero candidates AND verb is `bootstrap` → create the folder. Zero candidates AND verb is anything else → ask user.

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

@@ -24,7 +24,7 @@ Critical for multi-user projects: each contributor's runs are independent, and e
   YYYY-MM-DD-HHmm_<mode>.md
 ```
 
-- `<alias>` — the contributor running the skill (from `~/.copilot/project-evidence.yml#alias`).
+- `<alias>` — the contributor running the skill (from `<workspace>/.kushi/config/project-evidence.yml#alias`).
 - `<mode>` — one of `bootstrap`, `refresh`, `force-refresh`, `consolidate`.
 - Timestamp uses the **start time** of the run, in local time, format `YYYY-MM-DD-HHmm` (no seconds, no timezone — local-time prefix is enough for chronological sort).
 

package/plugin/instructions/side-by-side-config.instructions.md

@@ -52,5 +52,5 @@ End every bootstrap / fix-up turn by listing the live config files (path + size
 ## Why outside the kushi repo
 
 - **Multi-machine portability** — OneDrive-synced beside engagement folders, follows the user wherever they install kushi.
-- **Discoverability** — user can see/edit it next to their engagement work, not buried in `~/.copilot/`.
+- **Discoverability** — user can see/edit it next to their engagement work and inside their workspace at `<workspace>/.kushi/config/`, not buried in an OS-hidden home directory.
 - **Repo-safe** — kushi is meant to be GitHub-published; live filled configs MUST never be committed.

package/plugin/instructions/tracking.instructions.md

@@ -0,0 +1,165 @@
+---
+applyTo: "**"
+description: "Kushi tracking convention — every Kushi prompt/skill writes its working memory (what it was asked, what it did, what it decided, what's still open) to `<workspace>/.kushi/tracking/` so users can see, edit, diff, and resume the agent's work. This is host-agnostic (VS Code Chat, Clawpilot, Cursor) and complements — never replaces — Evidence/ (canonical outputs) or State/ (rollups)."
+---
+
+# Tracking — Agent Working Memory
+
+Kushi agents must leave a visible trail. Every meaningful run produces a small Markdown artifact under `<workspace>/.kushi/tracking/` describing what was asked, what was done, what was decided, and what is still open.
+
+This is **the journey**, not the **output**. Outputs land under `Evidence/`, `State/`, `Reports/`, `ado-updates/`, etc. Tracking files explain *why* and *how* those outputs ended up the way they did, so the user (or a future agent) can pick up where you left off.
+
+## Why this exists
+
+* **Visible thinking.** The user can read what the agent considered and rejected, not just the final artifact.
+* **Reliable handoff.** Stable filenames mean Bootstrap → Refresh → State → Ask never loses context across `/clear`, new chats, or host swaps.
+* **Resumability.** A 60-minute pull that died at 80% can be resumed from its last tracking entry instead of restarted.
+* **Audit + replay.** Diff-able, grep-able, commit-able (or gitignored — user's choice).
+* **Single convention across hosts.** Same shape in VS Code Chat, Clawpilot, Cursor, Cline.
+
+## Folder layout
+
+```
+<workspace>/.kushi/tracking/
+  .gitignore                                          ← ignore everything by default
+  runs/{{YYYY-MM-DD}}-<project>-<verb>.md             ← bootstrap / refresh / aggregate / state / consolidate
+  qa/{{YYYY-MM-DD}}-<project>-<question-slug>.md      ← /ask answers + citations, archived
+  fde/intake/{{YYYY-MM-DD}}-<project>-<slug>.md       ← /fde-intake drafts
+  fde/report/{{YYYY-MM-DD}}-<project>-<slug>.md       ← /fde-report drafts
+  fde/triage/{{YYYY-MM-DD}}-<project>-<slug>.md       ← /fde-triage drafts
+  research/{{YYYY-MM-DD}}-<topic>.md                  ← optional deep-dive notes
+```
+
+Rules:
+
+* Filenames start with `YYYY-MM-DD` (ISO date, UTC if ambiguous) so chronological sort works everywhere.
+* `<project>` is the engagement folder name (slugified — lowercase, hyphenated, no spaces).
+* `<verb>` is the prompt name without slash (`bootstrap`, `refresh`, ...).
+* `<slug>` / `<question-slug>` is 3–6 word kebab-case derived from the user's ask.
+* Create directories as needed on first write.
+
+## On first write — seed `.gitignore`
+
+If `<workspace>/.kushi/tracking/` does not yet exist, create it and write `<workspace>/.kushi/tracking/.gitignore` with:
+
+```gitignore
+# Kushi tracking files are working memory, not source of truth.
+# Outputs live under Evidence/, State/, Reports/, ado-updates/.
+# Uncomment the next line to start committing tracking artifacts.
+*
+!.gitignore
+```
+
+A user who wants to commit their agent transcripts deletes `*` from this file. Default is private.
+
+## Required sections in every tracking artifact
+
+Every tracking file is Markdown with frontmatter + a small set of named sections. Keep it short — this is a journal, not a report.
+
+```markdown
+---
+prompt: bootstrap                        # /bootstrap, /refresh, /ask, /fde-intake, ...
+project: hca                             # 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
+status: complete                         # complete | in-progress | blocked | failed
+host: vscode                             # vscode | clawpilot | cursor | cline | other
+kushi_version: 4.1.0
+---
+
+## Ask
+
+> Verbatim or near-verbatim of what the user asked for. One short paragraph.
+
+## Inputs resolved
+
+- Engagement root: `C:/.../Engagement Assets`
+- Project folder: `HCA Healthcare`
+- Alias: `ushak`
+- Config: `<workspace>/.kushi/config/project-evidence.yml`
+
+## Steps taken
+
+1. Resolved project context via `engagement-root-resolution.instructions.md`.
+2. Ran `pull-email` (WorkIQ) → 142 messages, 30-day window.
+3. Ran `pull-teams` (WorkIQ) → 11 chats, 308 messages.
+4. … (one line per meaningful step)
+
+## Decisions
+
+- Skipped `pull-crm` — `integrations.yml` has no `crm.engagement_id` for this project.
+- Used WorkIQ-only path; no `m365_*` fallback triggered.
+
+## 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)
+
+## Open questions / next steps
+
+- ADO field `Custom.FDEStatusSummary` is empty — recommend running `/fde-report hca` next.
+- 3 OneNote pages returned `page-body-unavailable`; see notes in `Evidence/ushak/onenote/run-notes.md`.
+
+## Errors / fallbacks
+
+- None.
+
+## Citations
+
+- `Evidence/ushak/email/snapshot/2026-05-19.md` · 2026-05-19
+- `Evidence/ushak/teams/snapshot/2026-05-19.md` · 2026-05-19
+```
+
+Section rules:
+
+* **Ask** — required. One short paragraph.
+* **Steps taken** — required. One bullet per meaningful action. Skip trivial tool calls.
+* **Decisions** — required when you chose A over B, skipped a step, or applied a fallback.
+* **Outputs** — required. Bullet list of files written/updated this run.
+* **Open questions / next steps** — required, even if empty (write "None.").
+* **Errors / fallbacks** — required when anything failed, retried, or fell back to a classified-fallback path (e.g., WorkIQ → `m365_*`).
+* **Citations** — required when the artifact references Evidence files; same format as everywhere else in Kushi (`<source-path> · <YYYY-MM-DD>`).
+
+## When to write
+
+* **First step of every prompt run:** create the file with frontmatter (`status: in-progress`) so a crash leaves something behind.
+* **As you go:** append "Steps taken" lines. Update "Outputs" when files land.
+* **Last step of every prompt run:** set `status: complete` (or `blocked` / `failed`), set `finished`, and fill in the closing sections.
+
+If the prompt runs multiple sub-skills in parallel, the orchestrating prompt owns the tracking file. Sub-skills do not write their own runs/ entry; they report back and the parent appends.
+
+## When NOT to write
+
+* `intro`, `status`, `self-check` — trivial / introspective. Skip the tracking file.
+* Any prompt that does nothing but read a single file and answer.
+* Dry-run / preview invocations (`--dry-run`, `--preview`) — log to stdout only.
+
+## Interaction with other doctrine
+
+* `update-ledger.instructions.md` — write-path skills (ADO apply, future CRM apply) still write a **ledger** under `<project>/ado-updates/<date>/`. The tracking file additionally records that a write happened and links to the ledger. Ledger is authoritative for *what was written*; tracking is the *story around it*.
+* `evidence-layout-canonical.instructions.md` — tracking files are NEVER a substitute for Evidence/. Evidence/ is the contract; tracking is the journal.
+* `answer-from-evidence.instructions.md` — `/ask` writes its answer to `qa/` *in addition to* returning it in chat, so the same question asked tomorrow can be answered from the archive (with a freshness check).
+
+## Cross-host behavior
+
+* Path is always relative to the **workspace root** (the folder the user opened in VS Code / Clawpilot / Cursor).
+* In Clawpilot specifically, the workspace root is whichever folder the user is operating on (an engagement folder, a code repo, etc.) — *not* `~/.copilot/m-skills/kushi/`. The Kushi install location and the tracking location are independent.
+* The Clawpilot weekly automation (`~/.copilot/kushi-projects.json`) is unaffected — it operates on engagement folders and produces tracking artifacts in each engagement folder's `.kushi/tracking/`.
+
+## Self-check coverage
+
+Future self-check rule **C14: tracking-artifact required** will verify:
+
+* Every prompt under `plugin/prompts/` (except the opt-out list above) references this instruction file.
+* Every prompt's closing step is "write/update the tracking artifact".
+
+C14 is added when this convention reaches 1.0 across all prompts.
+
+## References
+
+* `evidence-layout-canonical.instructions.md` — Evidence/ shape (the canonical output).
+* `update-ledger.instructions.md` — write-path ledger (orthogonal, additive).
+* `citation-ledger.instructions.md` — citation format used inside tracking artifacts.
+* `engagement-root-resolution.instructions.md` — how to resolve `<project>` for the filename slug.

package/plugin/instructions/workiq-only.instructions.md

@@ -47,7 +47,7 @@ For every M365 source in scope:
 
 ## Canonical WorkIQ commands (CODIFIED — do not re-discover)
 
-The CLI is at `C:\Users\ushak\.copilot\bin\workiq.cmd` (resolved from `<USER_HOME>/.copilot/project-evidence.yml workiq.cli_path`; fall back to PATH).
+The CLI is at `<USER_HOME>\.kushi\bin\workiq.cmd` (resolved from `<workspace>/.kushi/config/project-evidence.yml workiq.cli_path`; fall back to PATH; fall back to `~/.kushi/bin/workiq.cmd`).
 
 Invocation shape:
 
@@ -152,7 +152,7 @@ List my Teams meetings between <YYYY-MM-DD> and <YYYY-MM-DD> where the subject c
 
 Before the first WorkIQ query in a run:
 
-1. Resolve CLI path: `<USER_HOME>/.copilot/project-evidence.yml workiq.cli_path` OR `Get-Command workiq`. If missing → log `workiq-not-on-path`, write evidence file pointing at install docs, STOP this source.
+1. Resolve CLI path: `<workspace>/.kushi/config/project-evidence.yml workiq.cli_path` → `Get-Command workiq` → `~/.kushi/bin/workiq.cmd`. If none resolves → log `workiq-not-on-path`, write evidence file pointing at install docs, STOP this source.
 2. Probe with `workiq ask -q "ping"`. If EULA prompt → `workiq accept-eula` once, retry.
 3. Capture `--version` once into run-log for audit.
 

package/plugin/learnings/misc.md

@@ -17,7 +17,7 @@ The user pasting links into `external-links.txt` is the right boundary: auditabl
 **Routing model:**
 
 - `onenote / sharepoint / ado` → delegated to dedicated skills (recorded as `delegated` in registry, not double-pulled here).
-- `loop` → browser path (Playwright, reuses `~/.copilot/playwright-profile/onenote/` because same M365 cookie scope).
+- `loop` → browser path (Playwright, reuses `~/.kushi/playwright-profile/onenote/` because same M365 cookie scope).
 - `web / learn / docs / github / confluence / pdf / unknown` → HTTP path (fetch + @mozilla/readability for HTML extraction).
 - `file` → local file read.
 - Anything matching `<PASTE_*_URL>` or `<TODO*>` → `placeholder`, surfaced in run report until filled.

package/plugin/prompts/aggregate.prompt.md

@@ -22,3 +22,5 @@ This is the **pull-only** verb. Every enabled source is pulled and per-user stre
 ```
 
 See `skills/aggregate-project/SKILL.md` for the full sequence and output contract.
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/runs/{{YYYY-MM-DD}}-<project>-aggregate.md` as the final step.

package/plugin/prompts/ask.prompt.md

@@ -14,3 +14,5 @@ Read-only. NEVER triggers a `pull-*` skill — if evidence is stale or missing,
 You don't actually need this prompt — `ask-project` auto-routes whenever your message names a known project and asks a question (what / who / when / status / summarize / etc.). The slash form just provides an explicit handle.
 
 Delegates to `ask-project` skill.
+
+Tracking: see `tracking.instructions.md`. Archive every answer to `<workspace>/.kushi/tracking/qa/{{YYYY-MM-DD}}-<project>-<question-slug>.md` (frontmatter + Ask + Answer + Citations + freshness note).

package/plugin/prompts/bootstrap.prompt.md

@@ -12,7 +12,7 @@ Inputs the agent will resolve:
 - `<window>` — defaults to 30 days. Override with `last 60 days`, `since 2026-04-01`, or `2026-04-01..2026-05-01`.
 
 Reads:
-- `<USER_HOME>/.copilot/project-evidence.yml` for alias + engagement-root.
+- `<workspace>/.kushi/config/project-evidence.yml` for alias + engagement-root.
 
 Produces:
 - `<engagement-root>/.project-evidence/m365/{m365-auth,m365-mutable}.json` (per-user filled)
@@ -20,4 +20,6 @@ Produces:
 - `<engagement-root>/<project>/Evidence/{contributors.yml, run-log.yml, <alias>/.settings.yml, <alias>/{email,teams,meetings,onenote,sharepoint,crm,ado}/{snapshot,stream}/}`
 - `<engagement-root>/<project>/State/{00..09}_*.md`
 
-Delegates to `bootstrap-project` skill. After scaffolding, calls each `pull-<source>` skill, then `build-state`.
+Delegates to `bootstrap-project` skill. After scaffolding, calls each `pull-<source>` skill, then `build-state`.
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/runs/{{YYYY-MM-DD}}-<project>-bootstrap.md` as the final step.

package/plugin/prompts/consolidate.prompt.md

@@ -18,4 +18,6 @@ Writes:
 
 Provenance tags retained (source: <alias>/<source>/<file>) per `citation-ledger.instructions.md`.
 
-Delegates to `consolidate-evidence` skill.
+Delegates to `consolidate-evidence` skill.
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/runs/{{YYYY-MM-DD}}-<project>-consolidate.md` as the final step.

package/plugin/prompts/fde-intake.prompt.md

@@ -39,3 +39,5 @@ Authors (first time) or updates (subsequent runs) the **FDE Intake** at `<engage
 - `skills/fde-intake/SKILL.md` for the full step-by-step.
 - `@Kushi fde-triage <project>` — produces the 7-file triage bundle that builds ON the intake.
 - `@Kushi fde-report <project> stage-readiness` — separate "should we advance the stage?" check.
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/fde/intake/{{YYYY-MM-DD}}-<project>-<slug>.md` as the final step.

package/plugin/prompts/fde-report.prompt.md

@@ -44,3 +44,5 @@ Generates an FDE-shaped engagement report. Read-only against Evidence; no outbou
 - `skills/fde-report/SKILL.md` for the full step-by-step.
 - `@Kushi fde-intake <project>` — precursor first-artifact intake document.
 - `@Kushi fde-triage <project>` — full 7-file triage bundle (analysis + fitness + risk + 6Q + mobilization readiness + executive readout + reuse lens + validation warnings).
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/fde/report/{{YYYY-MM-DD}}-<project>-<shape>.md` as the final step.

package/plugin/prompts/fde-triage.prompt.md

@@ -44,3 +44,5 @@ Re-running on the same day overwrites files 00–06 in place and **merges file 0
 - `skills/fde-triage/SKILL.md` for the full step-by-step.
 - `@Kushi fde-intake <project>` — first-artifact intake document (precursor to the bundle).
 - `@Kushi fde-report <project> [shape]` — individual report shapes (weekly / short / long / fitness / stage-readiness).
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/fde/triage/{{YYYY-MM-DD}}-<project>-bundle.md` as the final step (one summary entry, not 7 — the bundle itself lives under `Reports/triage/`).

package/plugin/prompts/refresh.prompt.md

@@ -14,4 +14,6 @@ Window resolution (per `refresh-project` skill):
 
 Output is always weekly-bucketed regardless of input window.
 
-Delegates to `refresh-project` skill. Skips `pull-<source>` for sources marked disabled in `integrations.yml` or whose config is missing.
+Delegates to `refresh-project` skill. Skips `pull-<source>` for sources marked disabled in `integrations.yml` or whose config is missing.
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/runs/{{YYYY-MM-DD}}-<project>-refresh.md` as the final step.

package/plugin/prompts/state.prompt.md

@@ -14,4 +14,6 @@ Pure renderer. Reads:
 Writes:
 - `<engagement-root>/<project>/State/{00_overview, 01_decisions, 02_stakeholders, 03_architecture-and-solution, 04_workshops-and-key-meetings, 05_action-items, 06_risks-and-issues, 07_timeline-and-milestones, 08_artifacts-and-deliverables, 09_open-questions}.md`
 
-Delegates to `build-state` skill. Use this when you've manually edited Evidence files and want State refreshed without re-pulling.
+Delegates to `build-state` skill. Use this when you've manually edited Evidence files and want State refreshed without re-pulling.
+
+Tracking: see `tracking.instructions.md`. Write `<workspace>/.kushi/tracking/runs/{{YYYY-MM-DD}}-<project>-state.md` as the final step.

package/plugin/reference-packs/README.md

@@ -11,7 +11,7 @@ When a skill (e.g. `fde-report`, `ask-project`) needs a pack's content, it loads
 | Priority | Location | Purpose | Lifecycle |
 |---:|---|---|---|
 | 1 (highest) | `<engagement-root>/<project>/.kushi-reference/<pack>/` | Per-engagement override | Versioned with the engagement; for project-specific tuning |
-| 2 | `~/.copilot/kushi-reference/<pack>/` | Per-user override | Per machine / per user; never overwritten by installer |
+| 2 | `<workspace>/.kushi/config/reference-overrides/<pack>/` | Workspace override | Per workspace / per machine; never overwritten by installer |
 | 3 (canonical) | `<install-dest>/reference-packs/<pack>/` (i.e. this folder, installed) | Packaged default | Updated via `npm publish` + version bump |
 
 Skills must always:
@@ -33,7 +33,7 @@ Skills must always:
 What does **not** go in a pack:
 
 - Per-engagement data (lives under `<project>/Evidence/`)
-- Per-user identity / configs (lives in `~/.copilot/project-evidence.yml`)
+- Per-user identity / configs (lives in `<workspace>/.kushi/config/project-evidence.yml`)
 - Skill behavior (lives in `plugin/skills/<skill>/SKILL.md`)
 - Cross-cutting agent doctrine (lives in `plugin/instructions/*.instructions.md`)
 

package/plugin/reference-packs/fde/README.md

@@ -23,9 +23,9 @@ Use this pack when a report needs:
 2. **Enumerate and read all human-readable `.md` files** in the pack.
 3. Treat the pack as a **single reference set** — any file here may contribute to the FDE operating model used in reports.
 4. **Apply the 3-layer override order** (highest wins):
-   - `<engagement-root>/<project>/.kushi-reference/fde/`  ← per-engagement override
-   - `~/.copilot/kushi-reference/fde/`                   ← per-user override
-   - `<install-dest>/reference-packs/fde/`               ← packaged default (this folder, installed)
+   - `<engagement-root>/<project>/.kushi-reference/fde/`     ← per-engagement override
+   - `<workspace>/.kushi/config/reference-overrides/fde/`     ← workspace override
+   - `<install-dest>/reference-packs/fde/`                    ← packaged default (this folder, installed)
 5. If two files at the same layer conflict, prefer the more **specific** file for that concept and raise the conflict explicitly in the skill's run-log / Open Questions — never silently average.
 
 ## File ownership

package/plugin/skills/ask-project/SKILL.md

@@ -40,7 +40,7 @@ In order, stop on first hit:
 1. Exact `<engagement-root>/<project>/Evidence/` folder.
 2. Fuzzy match against `discovery.project_aliases` in any `<engagement-root>/<project>/Evidence/<alias>/.settings.yml`.
 3. `<engagement-root>/<project>/external-context/` (lighter-weight projects without full bootstrap).
-4. `~/.copilot/project-evidence.yml` `active_projects` list.
+4. `<workspace>/.kushi/config/project-evidence.yml` `active_projects` list.
 
 If zero matches → ask user. If multiple → list candidates and ask user to pick. **Echo the resolved root path before answering** so the user can confirm.
 

package/plugin/skills/bootstrap-project/SKILL.md

@@ -44,13 +44,13 @@ After every run (success or coverage-gaps), write `<project>/bootstrap-status.md
 Verify in order. Stop on hard failures.
 
 1. **OS + host runtime** — display OS + Node/PowerShell version. Informational.
-2. **WorkIQ install (REQUIRED, hard stop)** — read `<USER_HOME>/.copilot/project-evidence.yml workiq.cli_path`. If missing, probe known paths:
-   - `$HOME\.copilot\bin\workiq.cmd`
+2. **WorkIQ install (REQUIRED, hard stop)** — read `<workspace>/.kushi/config/project-evidence.yml workiq.cli_path`. If missing, probe known paths:
+   - `$HOME\.kushi\bin\workiq.cmd`
    - `$env:LOCALAPPDATA\Programs\WorkIQ\workiq.cmd`
    - `$env:ProgramFiles\WorkIQ\workiq.cmd`
    If found, persist path. If not found, ask user for path (or to install). Test with `<workiq.cli_path> --help`. Without WorkIQ, M365 sources will all fail — STOP.
 3. **Conditional az login** — only if `<engagement-root>/.project-evidence/crm/config.yml` OR `<engagement-root>/.project-evidence/ado/config.yml` exists. Per `az-auth-conditional.instructions.md`. Soft warning on failure, never blocking.
-4. **Engagement-root resolution** — per `engagement-root-resolution.instructions.md`. Persist to `<USER_HOME>/.copilot/project-evidence.yml engagement_root` if newly resolved.
+4. **Engagement-root resolution** — per `engagement-root-resolution.instructions.md`. Persist to `<workspace>/.kushi/config/project-evidence.yml engagement_root` if newly resolved.
 
 Display SETUP summary table with ✅ / ⚙️ / ❌ / ⚠️ / ➖ markers.
 
@@ -62,7 +62,8 @@ Required live files:
 
 | Live file | Template source |
 |---|---|
-| `<USER_HOME>/.copilot/project-evidence.yml` | `templates/init/project-evidence.template.yml` |
+| `<workspace>/.kushi/config/project-evidence.yml` | `templates/init/project-evidence.template.yml` (seeded by installer) |
+| `<workspace>/.kushi/config/integrations.yml` | `templates/init/integrations.template.yml` (seeded by installer) |
 | `<engagement-root>/.project-evidence/m365/m365-auth.json` | `templates/init/m365-auth.template.json` |
 | `<engagement-root>/.project-evidence/m365/m365-mutable.json` | `templates/init/m365-mutable.template.json` |
 | `<engagement-root>/<project>/integrations.yml` | `templates/init/project-integrations.template.yml` |

package/plugin/skills/fde-intake/SKILL.md

@@ -31,7 +31,7 @@ Same algorithm as `ask-project` Step 1. Echo the resolved root path before draft
 Build the pack's virtual filesystem with the **3-layer override order** (highest wins):
 
 1. **Project override** — `<engagement-root>/<project>/.kushi-reference/fde/` (if present)
-2. **User override** — `~/.copilot/kushi-reference/fde/` (if present)
+2. **Workspace override** — `<workspace>/.kushi/config/reference-overrides/fde/` (if present)
 3. **Packaged default** — relative to this skill's install location:
    - vscode target: `<workspace>/.kushi/reference-packs/fde/`
    - clawpilot target: `~/.copilot/m-skills/kushi/reference-packs/fde/`

package/plugin/skills/intro/SKILL.md

@@ -138,7 +138,7 @@ Present this verbatim:
 
 Before opening, check whether any project is already bootstrapped:
 
-1. Read `~/.copilot/project-evidence.yml` (personal config). If `active_projects` has entries, pick the most recent as the demo target — substitute that name into `{{active_project}}` placeholders below.
+1. Read `<workspace>/.kushi/config/project-evidence.yml` (personal config). If `active_projects` has entries, pick the most recent as the demo target — substitute that name into `{{active_project}}` placeholders below.
 2. If none, propose a fictional project named **Contoso Discovery** and tell the user that Try-it prompts will use that name; they can substitute their own at any time.
 
 ### Navigation Keywords
@@ -444,6 +444,6 @@ Reply `next` to see the closing cheat sheet, or `done` to exit.
 - Rule 1.2: Mode selection must always present BOTH options — never auto-route to one mode.
 - Rule 1.3: In walkthrough mode, each moment must wait for `next` / `skip` / `done` / `try` before advancing — never auto-advance.
 - Rule 1.4: `done` must work at every moment — never trap the user.
-- Rule 1.5: Try-it prompts must use the active project name from `~/.copilot/project-evidence.yml`, OR the placeholder `Contoso Discovery` if no projects are configured. Never invent a real-sounding project name.
+- Rule 1.5: Try-it prompts must use the active project name from `<workspace>/.kushi/config/project-evidence.yml`, OR the placeholder `Contoso Discovery` if no projects are configured. Never invent a real-sounding project name.
 - Rule 1.6: Skill descriptions in this file must match `kushi.agent.md` and the live `SKILL.md` files — `self-check` D-checks catch drift.
 - Rule 1.7: Demo moments must reflect the actual verb count in `kushi.agent.md`. If a verb is added or removed, this file must be updated in the same commit (`self-check` warns on drift).

package/plugin/skills/propose-ado-update/SKILL.md

@@ -27,7 +27,7 @@ This skill does **NOT** create a new top-level config file. It reads from the co
 
 **Resolution is fully deterministic** — never ask the user for paths the bootstrap layer already resolved:
 
-1. `<engagement-root>` ← `~/.copilot/project-evidence.yml engagement_root` (per `engagement-root-resolution.instructions.md`).
+1. `<engagement-root>` ← `<workspace>/.kushi/config/project-evidence.yml engagement_root` (per `engagement-root-resolution.instructions.md`).
 2. `<project>` folder ← fuzzy-match per `engagement-root-resolution.instructions.md` (knownSections → active_projects → subfolders).
 3. `<project>/integrations.yml ado.engagement_id` — REQUIRED. If `0` or missing → see "Prerequisites" below; never invent an ID.
 4. `<project>/integrations.yml ado.writes` — if missing, append the block from `<KUSHI_ROOT>/plugin/templates/ado-update/integrations-ado-writes.example.yml` and stop for user confirmation of `fieldRefName`.

package/plugin/skills/pull-misc/README.md

@@ -69,7 +69,7 @@ node runner.mjs --project ABN ... --types web,loop --titles "Architecture"
 
 ## Scheduled / unattended runs
 
-- Browser branch (loop) reuses `~/.copilot/playwright-profile/onenote/`. When MFA fires, runner marks loop links `auth-required` and exits cleanly. User does one interactive bootstrap; next scheduled run silent.
+- Browser branch (loop) reuses `~/.kushi/playwright-profile/onenote/`. When MFA fires, runner marks loop links `auth-required` and exits cleanly. User does one interactive bootstrap; next scheduled run silent.
 - HTTP branch needs no auth for public links. For sites behind SSO (auth'd Confluence, internal dashboards) it returns `auth-required` and is currently NOT supported — paste the content into a `file` link as a workaround, OR add a per-site auth handler in a future version.
 - `placeholder` links surface in the run report every refresh until the user fills them in.
 

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

@@ -23,7 +23,7 @@ Pulls **misc** evidence in two shapes per `snapshot-vs-stream.instructions.md`:
 
 ## Tools (in order)
 
-1. **Playwright (browser-scrape, persisted profile)** — for `loop` links. Reuses `~/.copilot/playwright-profile/onenote/` because it's the same M365 cookie scope. Implementation: `plugin/skills/pull-misc/runner.mjs` branch `loop`.
+1. **Playwright (browser-scrape, persisted profile)** — for `loop` links. Reuses `~/.kushi/playwright-profile/onenote/` because it's the same M365 cookie scope. Implementation: `plugin/skills/pull-misc/runner.mjs` branch `loop`.
 2. **HTTP fetch + Readability** — for `web` / `confluence` (anonymous) / `learn` / `docs` / `pdf` links. Implementation: `plugin/skills/pull-misc/runner.mjs` branch `web`.
 3. **Local file read** — for `file` links pointing at project-relative paths. Implementation: `plugin/skills/pull-misc/runner.mjs` branch `file`.
 4. **WorkIQ** — used only for stream/edit-event signals on `loop` links (Loop edit events surface in the M365 search index, same as OneNote stream events). NOT used for body retrieval — Loop bodies require the browser path.
@@ -72,7 +72,7 @@ These three facts are HARD-rule:
 
 ```pwsh
 # A. Playwright profile (only required if external-links.txt contains loop links)
-$prof = "$env:USERPROFILE\.copilot\playwright-profile\onenote"
+$prof = "$env:USERPROFILE\.kushi\playwright-profile\onenote"
 if (-not (Test-Path $prof)) {
   Write-Host "[pull-misc] Playwright profile not yet seeded — loop links will be skipped with last_status: auth-required."
   Write-Host "[pull-misc] Run plugin/skills/pull-onenote/runner.mjs --bootstrap once to seed it."

package/plugin/skills/pull-misc/runner.mjs

@@ -36,7 +36,7 @@ const HEADLESS = !!args.headless;
 const TYPES_FILTER = args.types ? String(args.types).split(',').map(s => s.trim().toLowerCase()) : null;
 const TITLES_FILTER = args.titles ? String(args.titles).split(',').map(s => s.trim()) : null;
 const TIMEOUT_MS = parseInt(args.timeout || '45000', 10);
-const PROFILE_DIR = path.join(os.homedir(), '.copilot', 'playwright-profile', 'onenote');
+const PROFILE_DIR = path.join(os.homedir(), '.kushi', 'playwright-profile', 'onenote');
 
 if (!PROJECT || !LINKS_FILE) {
   console.error('Usage: --project <name> --links-file <path> [--headless] [--types t1,t2] [--titles "t1,t2"]');

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

@@ -21,7 +21,7 @@ When the bootstrap command opens a Chromium window:
 - Wait for the OneNote home page to load.
 - Close the window.
 
-The profile is persisted at `~/.copilot/playwright-profile/onenote/`. Subsequent runs reuse it.
+The profile is persisted at `~/.kushi/playwright-profile/onenote/`. Subsequent runs reuse it.
 
 ## Per-section runs
 

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

@@ -23,7 +23,7 @@ Pulls **onenote** evidence in two shapes per `snapshot-vs-stream.instructions.md
 
 ## Tools (in order)
 
-1. **Playwright (browser-scrape, persisted profile)** — PRIMARY. Drives OneNote-for-Web to enumerate pages and read verbatim bodies via `#PageContentWrapper`. Profile lives at `~/.copilot/playwright-profile/onenote/` and is reused across runs. Implementation: `plugin/skills/pull-onenote/runner.mjs`.
+1. **Playwright (browser-scrape, persisted profile)** — PRIMARY. Drives OneNote-for-Web to enumerate pages and read verbatim bodies via `#PageContentWrapper`. Profile lives at `~/.kushi/playwright-profile/onenote/` and is reused across runs. Implementation: `plugin/skills/pull-onenote/runner.mjs`.
 2. **WorkIQ** — FALLBACK only. Used when the Playwright profile is auth-expired (`auth-required`) and for the stream/edit-event source. Always cite `m365-id-registry` doctrine when invoking; never use as primary for body retrieval (proven non-deterministic).
 3. **Host (m365_*)** — not used (Graph `Notes.Read.All` denied admin consent in this tenant).
 
@@ -145,7 +145,7 @@ Before any retrieval, validate the Playwright profile and (only if used as fallb
 ### A. Playwright profile (PRIMARY)
 
 ```pwsh
-$prof = "$env:USERPROFILE\.copilot\playwright-profile\onenote"
+$prof = "$env:USERPROFILE\.kushi\playwright-profile\onenote"
 if (-not (Test-Path $prof)) {
   Write-Host "[pull-onenote] Playwright profile not yet seeded."
   Write-Host "[pull-onenote] Run plugin/skills/pull-onenote/runner.mjs --bootstrap once interactively to sign in."
@@ -170,7 +170,7 @@ Cookie domains do not share between `*.cloud.microsoft` and `*.sharepoint(-df).c
 
 These are the same selectors `preflightOneNoteWeb` uses. The bootstrap log MUST emit `Sign-in detected (OneNote chrome rendered).` between Step 1/2 and Step 2/2 — its absence is the defect signature of the v3.11.1-and-earlier bug (sign-in was silently skipped, and every subsequent scrape returned `auth-required` regardless of how thoroughly the user signed in). Same anti-pattern applies to any future bootstrap surface (SharePoint, Loop, M365 admin).
 
-**A.3 Profile reset on channel switch:** if migrating from a Chromium profile to Edge (or vice versa), delete `~/.copilot/playwright-profile/onenote/` first. Cookie/cache formats differ.
+**A.3 Profile reset on channel switch:** if migrating from a Chromium profile to Edge (or vice versa), delete `~/.kushi/playwright-profile/onenote/` first. Cookie/cache formats differ.
 
 **A.4 OneNote-for-Web reachability pre-flight — HARD rule (kushi v3.11.0+):** before navigating to any section URL, the runner MUST probe `https://onenote.cloud.microsoft/` and classify the end-state into exactly one of three buckets:
 

package/plugin/skills/pull-onenote/runner.mjs

@@ -40,7 +40,7 @@ const args = Object.fromEntries(
   }, [])
 );
 
-const PROFILE_DIR = path.join(os.homedir(), '.copilot', 'playwright-profile', 'onenote');
+const PROFILE_DIR = path.join(os.homedir(), '.kushi', 'playwright-profile', 'onenote');
 const HEADLESS = !!args.headless;
 const BOOTSTRAP = !!args.bootstrap;
 const PREFLIGHT = !!args.preflight;

package/plugin/templates/init/integrations.template.yml

@@ -0,0 +1,19 @@
+# Kushi — optional global integrations defaults.
+#
+# Seeded by the installer on first install. Never overwritten on upgrade.
+# Per-project `integrations.yml` (inside the engagement folder) always
+# takes precedence over this file.
+#
+# Most users can leave this file as-is. Fill it in only if you want a
+# default CRM / ADO configuration that applies across all projects.
+
+# Microsoft Dataverse (CRM) defaults.
+# crm:
+#   environment_url: 'https://<org>.crm.dynamics.com'
+#   tenant_id:       '72f988bf-86f1-41af-91ab-2d7cd011db47'   # Microsoft tenant
+
+# Azure DevOps defaults.
+# ado:
+#   organization: 'https://dev.azure.com/<org>'
+#   project:      '<default-project>'
+#   tenant_id:    '72f988bf-86f1-41af-91ab-2d7cd011db47'      # Microsoft tenant

package/plugin/templates/init/project-evidence.template.yml

@@ -1,32 +1,38 @@
-# Personal config for Kushi.
-# Copy to:  ~/.copilot/project-evidence.yml   (Linux/macOS)
-#           %USERPROFILE%\.copilot\project-evidence.yml   (Windows)
+# Kushi — personal config.
 #
-# Each team member maintains their own copy. Nothing in here is a secret,
-# but it IS personal — never commit a filled copy to a shared repo.
+# This file was seeded by the installer on first install. It is YOUR copy,
+# never overwritten on reinstall / --force / upgrade. Each team member
+# maintains their own. Nothing here is a secret, but it IS personal —
+# add `.kushi/config/` to .gitignore before committing the rest of .kushi/.
+#
+# Edit the values below (lines marked FILL ME IN), then run `bootstrap <project>`.
 
-# Short id used as your evidence subfolder name (e.g. "alex", "jordan").
+# FILL ME IN — short id used as your evidence subfolder name (e.g. "alex", "jordan").
 alias: <your-alias>
 
+# FILL ME IN
 display_name: <Your Full Name>
 email: your.email@example.com
 
-# Where your engagement-root lives — i.e. the parent folder that contains
+# FILL ME IN — where your engagement-root lives. The parent folder containing
 # one subfolder per project (typically synced from a team SharePoint library).
 # Examples:
 #   Windows : 'C:\Users\<you>\OneDrive - <Tenant>\<Team>\Engagement Assets'
 #   macOS   : '/Users/<you>/OneDrive - <Tenant>/<Team>/Engagement Assets'
 projects_root: '<engagement-root>'
 
-# Default OneNote notebook to scan for project pages.
+# FILL ME IN — default OneNote notebook to scan for project pages.
 default_onenote_notebook: <Your Notebook Name>
 
-# Projects you actively work on. Kushi scans only these unless you ask otherwise.
-# Match is fuzzy against subfolder names under projects_root.
+# FILL ME IN — projects you actively work on. Kushi scans only these unless
+# you ask otherwise. Match is fuzzy against subfolder names under projects_root.
 active_projects:
   - <ProjectA>
   # - <ProjectB>
-  # - <add more here>
 
-# (Optional) where the global integrations live, if not the default.
-# integrations_root: '<USER_HOME>/.copilot/integrations'
+# (Optional) Path to the WorkIQ CLI. If omitted, Kushi resolves in this order:
+#   1. this `cli_path` value
+#   2. `workiq` on PATH
+#   3. ~/.kushi/bin/workiq.cmd  (Windows) / ~/.kushi/bin/workiq  (Linux/macOS)
+# workiq:
+#   cli_path: 'C:\Users\<you>\.kushi\bin\workiq.cmd'

package/plugin/templates/init/project-user-settings.template.yml

@@ -21,7 +21,7 @@ teams_chats:
   search_keywords: []
 
 onenote:
-  notebook: '{{ONENOTE_NOTEBOOK}}'        # default from ~\.copilot\project-evidence.yml
+  notebook: '{{ONENOTE_NOTEBOOK}}'        # default from <workspace>\.kushi\config\project-evidence.yml
   section: '{{ONENOTE_SECTION}}'          # e.g. 'Noridian.one'
   page_filter: ''                         # optional substring filter
 

package/src/constants.mjs

@@ -22,6 +22,21 @@ export const PLUGIN_SOURCE_DIR = 'plugin';
 /** Asset subdirectories under plugin/ that get copied. */
 export const ASSET_DIRS = ['agents', 'instructions', 'prompts', 'skills', 'templates', 'reference-packs'];
 
+/**
+ * User-editable config directory under the install destination.
+ * Seeded on first install only; never overwritten on reinstall / --force / upgrade.
+ */
+export const CONFIG_DIR = 'config';
+
+/**
+ * Files seeded into <dest>/config/ on first install only.
+ * Each entry: { template: <path under plugin/templates/init/>, target: <name in config/> }
+ */
+export const CONFIG_SEED_FILES = [
+  { template: 'init/project-evidence.template.yml', target: 'project-evidence.yml' },
+  { template: 'init/integrations.template.yml',     target: 'integrations.yml'     },
+];
+
 /** Files to exclude from consumer installs (relative to plugin/). */
 export const EXCLUDED_FILES = [];
 

package/src/main.mjs

@@ -16,6 +16,7 @@ import { promptForDestination } from './prompt.mjs';
 import { copyAssets, copyProjectFiles } from './copy-assets.mjs';
 import { mergeSettings } from './settings.mjs';
 import { mergeCopilotInstructions } from './copilot-instructions.mjs';
+import { seedConfig } from './seed-config.mjs';
 import {
   resolveProfile,
   makeIncludeFilter,
@@ -129,6 +130,13 @@ async function installVscode(options, resolved, version) {
   const manifestPath = writeInstalledManifest(fullDest, resolved, version);
   console.log(`    - kushi-install.json (profile manifest)`);
 
+  const { seeded, preserved } = seedConfig(PKG_ROOT, fullDest);
+  if (seeded.length > 0 || preserved.length > 0) {
+    console.log(`\n  Config (.kushi/config/ — user-editable, preserved across upgrades):`);
+    for (const f of seeded)    console.log(`    - ${f} -> seeded from template`);
+    for (const f of preserved) console.log(`    - ${f} -> preserved (already exists)`);
+  }
+
   if (!options.noSettings) {
     const { created, keysAdded, keysUnchanged } = mergeSettings(
       projectRoot,
@@ -221,6 +229,13 @@ async function installClawpilot(options, resolved, version) {
   writeInstalledManifest(fullDest, resolved, version);
   console.log(`    - kushi-install.json (profile manifest)`);
 
+  const { seeded, preserved } = seedConfig(PKG_ROOT, fullDest);
+  if (seeded.length > 0 || preserved.length > 0) {
+    console.log(`\n  Config (${displayDest}\\config\\ — user-editable, preserved across upgrades):`);
+    for (const f of seeded)    console.log(`    - ${f} -> seeded from template`);
+    for (const f of preserved) console.log(`    - ${f} -> preserved (already exists)`);
+  }
+
   // Mirror agents/kushi.agent.md as top-level SKILL.md for Clawpilot discovery.
   const agentSrc = path.join(PKG_ROOT, PLUGIN_SOURCE_DIR, CLAWPILOT_AGENT_SOURCE);
   const skillDst = path.join(fullDest, CLAWPILOT_SKILL_DEST);

package/src/seed-config.mjs

@@ -0,0 +1,44 @@
+import fs from 'node:fs';
+import path from 'node:path';
+import {
+  CONFIG_DIR,
+  CONFIG_SEED_FILES,
+  PLUGIN_SOURCE_DIR,
+} from './constants.mjs';
+
+/**
+ * Seed <dest>/config/ with user-editable config files on FIRST INSTALL ONLY.
+ *
+ * Rules:
+ *   - If <dest>/config/<file> already exists → skip (never overwrite).
+ *   - Behavior is identical regardless of --force; config/ is user territory.
+ *   - Returns a per-file result so the installer can summarize what happened.
+ *
+ * @param {string} sourcePkgDir – root of the npm package
+ * @param {string} destAbsolute – absolute install destination (e.g. <workspace>/.kushi)
+ * @returns {{ seeded: string[], preserved: string[] }}
+ */
+export function seedConfig(sourcePkgDir, destAbsolute) {
+  const configDir = path.join(destAbsolute, CONFIG_DIR);
+  fs.mkdirSync(configDir, { recursive: true });
+
+  const seeded = [];
+  const preserved = [];
+
+  for (const { template, target } of CONFIG_SEED_FILES) {
+    const src = path.join(sourcePkgDir, PLUGIN_SOURCE_DIR, 'templates', template);
+    const dst = path.join(configDir, target);
+
+    if (!fs.existsSync(src)) continue;
+
+    if (fs.existsSync(dst)) {
+      preserved.push(target);
+      continue;
+    }
+
+    fs.cpSync(src, dst);
+    seeded.push(target);
+  }
+
+  return { seeded, preserved };
+}