kushi-agents 5.4.2 → 5.4.4

package/plugin/prompts/migrate-files.prompt.md

@@ -0,0 +1,29 @@
+---
+mode: agent
+description: "Migrate root-level bootstrap-status.md / FOLLOW-UPS.md / OPEN-QUESTIONS-DRAFT.md to per-user Evidence/<alias>/ paths (kushi v5.4.4+ doctrine)."
+---
+
+# /kushi.migrate-files
+
+One-time migration for projects bootstrapped under kushi ≤ v5.4.3.
+
+Dispatch the `migrate-per-user-files` skill at `plugin/skills/migrate-per-user-files/` for the current project. Default to **dry-run**. Show the plan and ask the user to re-run with `--apply` to commit. If they explicitly request "apply now" / "do it" / "go" in the same turn, invoke with `-Apply`.
+
+## Resolves
+
+- ProjectRoot = the project folder under the current engagement root (resolve via the standard `Get-ProjectRoot` helper).
+
+## Writes
+
+- `<project>/Evidence/<alias>/bootstrap-status.md` (moved from root)
+- `<project>/Evidence/<alias>/FOLLOW-UPS.md` (moved from root)
+- `<project>/Evidence/<alias>/OPEN-QUESTIONS-DRAFT.md` (moved from root)
+- `<project>/Evidence/run-log.yml` (appended `migrations:` entry on `--apply`)
+
+## Defensive behavior
+
+If both root and per-user copies exist with different content, the skill emits `[needs-merge]` and exits 1 in `--apply` mode — it will NEVER overwrite a per-user file. Hand-merge, then re-run.
+
+## After migration
+
+Run `/kushi.consolidate` to generate the `_Consolidated/` rollups for cross-contributor visibility, then `/kushi.status` to verify the bootstrap status reads from the new per-user path.

package/plugin/prompts/promote.prompt.md

@@ -0,0 +1,26 @@
+---
+name: promote
+description: "Copy a project State page into the global wiki with identifier redaction + back-link + dual log."
+argument-hint: "Project + page. Example: 'promote HCA decisions/macc-terms'."
+agent: kushi
+tools: [search, read/readFile, edit, agent]
+---
+
+## User Input
+
+```text
+${input:project_and_page:Project + relative State page, e.g. 'HCA decisions/macc-terms'}
+```
+
+# /promote
+
+Route to `@Kushi promote <project> <page>`.
+
+Copies `<engagement-root>/<project>/State/<page>.md` into `~/.kushi-global/State/<page>.md`:
+- runs the customer-identifier redactor (refuses without `--force` when hits detected)
+- inserts a back-link to the source project page
+- appends entries to both the project run-log and the global wiki dual log
+
+Companion verb: `/global ask <q>` retrieves promoted content.
+
+Delegates to `promote` skill.

package/plugin/prompts/schema-evolve.prompt.md

@@ -0,0 +1,27 @@
+---
+name: schema-evolve
+description: "Migrate kushi.yaml + Evidence/ across schema versions. Idempotent + dry-run by default."
+argument-hint: "Project. Flags: --apply (real run), --to <version>. Example: 'schema-evolve HCA --apply'."
+agent: kushi
+tools: [search, read/readFile, edit, agent]
+---
+
+## User Input
+
+```text
+${input:project_and_flags:Project + flags, e.g. 'HCA' (dry-run), 'HCA --apply', 'HCA --to 5.2.0 --apply'}
+```
+
+# /schema-evolve
+
+Route to `@Kushi schema-evolve <project>`.
+
+Walks `<engagement-root>/<project>/` and applies schema migrations declared under
+`plugin/schemas/migrations/` to bring `kushi.yaml`, run-log, and Evidence/ layout
+to the current (or `--to`-pinned) schema version.
+
+- Default: dry-run — prints planned changes, writes nothing.
+- `--apply` — performs the migration; idempotent (safe to re-run).
+- `--to <ver>` — pin a target version (default = current).
+
+Delegates to `schema-evolve` skill.

package/plugin/prompts/teach.prompt.md

@@ -0,0 +1,25 @@
+---
+name: teach
+description: "Persist a reusable fact / preference / pattern under .kushi/learnings/."
+argument-hint: "Topic + body. Example: 'teach HCA naming-convention: services are kebab-case'."
+agent: kushi
+tools: [search, read/readFile, edit, agent]
+---
+
+## User Input
+
+```text
+${input:topic_and_body:Topic + body, e.g. 'HCA naming-convention: services are kebab-case'}
+```
+
+# /teach
+
+Route to `@Kushi teach <topic>`.
+
+Writes a single self-contained learning file under `.kushi/learnings/<slug>.md`
+with frontmatter `topic`, `created`, `last_updated`. Idempotent — re-teach updates
+the existing file in place and appends a `history` entry.
+
+Companion verb: `/explain <topic>` retrieves the learning without modifying it.
+
+Delegates to `teach` skill.

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

@@ -20,8 +20,8 @@ This skill **never** writes to `State/`. It only writes to `Evidence/`.
 
 1. **Resolve project** — fuzzy-match against `m365-mutable.json knownSections` -> `active_projects` -> `<engagement-root>` subfolders.
 2. **Resolve window** — default = since last `aggregate`/`refresh`/`bootstrap` watermark in `Evidence/run-log.yml`; fallback 7 days if no watermark.
-3. **Pull each enabled source in turn** (`pull-email`, `pull-teams`, `pull-meetings`, `pull-onenote`, `pull-loop`, `pull-sharepoint`, `pull-crm`, `pull-ado`) — each writes its own snapshot/ + stream/ files under `Evidence/<alias>/<source>/`. **After each pull, run the verification gate** per `..\..\instructions\per-source-verification-gate.instructions.md`: on first failure retry once with the same window; on second failure append a 5-field entry to `<project>/FOLLOW-UPS.md`, log `status: failed-gate` to `Evidence/run-log.yml`, and continue to the next source (never abort the whole aggregate).
-4. **Run `consolidate-evidence`** — merges all aliases' streams into `Evidence/_Consolidated/<YYYY-MM-DD>_consolidated.md`. Skip silently if only one alias exists.
+3. **Pull each enabled source in turn** (`pull-email`, `pull-teams`, `pull-meetings`, `pull-onenote`, `pull-loop`, `pull-sharepoint`, `pull-crm`, `pull-ado`) — each writes its own snapshot/ + stream/ files under `Evidence/<alias>/<source>/`. **After each pull, run the verification gate** per `..\..\instructions\per-source-verification-gate.instructions.md`: on first failure retry once with the same window; on second failure append a 5-field entry to `<project>/Evidence/<alias>/FOLLOW-UPS.md` (per-user, v5.4.4+; cross-contributor view at `_Consolidated/FOLLOW-UPS.md`), log `status: failed-gate` to `Evidence/run-log.yml`, and continue to the next source (never abort the whole aggregate).
+4. **Run `consolidate-evidence`** — merges all aliases' streams into `Evidence/_Consolidated/<YYYY-MM-DD>_consolidated.md`, AND emits the three per-user-files rollups: `_Consolidated/bootstrap-status.md`, `_Consolidated/FOLLOW-UPS.md`, `_Consolidated/OPEN-QUESTIONS-DRAFT.md` (Step 5 of consolidate-evidence). Skip the per-source weekly consolidation silently if only one alias exists; the per-user-files rollup ALWAYS runs (single-alias rollup is a verbatim copy with an attribution header).
 5. **Update `Evidence/run-log.yml`** — record this aggregate run, its watermark, the sources pulled, the alias that produced it.
 6. **DO NOT run `build-state`.** State/ is not the concern of this skill.
 
@@ -86,7 +86,7 @@ See `docs/reference/evidence-contract.md` for the full schema (filename rules, f
 ## References (v4.4.7)
 
 - Name → ID resolution (any source) follows `..\..\instructions\fuzzy-disambiguation.instructions.md`.
-- After each per-source pull, run the gate per `..\..\instructions\per-source-verification-gate.instructions.md` (retry once → FOLLOW-UPS.md on failure).
+- After each per-source pull, run the gate per `..\..\instructions\per-source-verification-gate.instructions.md` (retry once → `Evidence/<alias>/FOLLOW-UPS.md` on failure; consolidated at `_Consolidated/FOLLOW-UPS.md`).
 
 
 ## Issue Recovery

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

@@ -10,7 +10,7 @@ description: "USE WHEN the user says \"bootstrap <X>\", \"set up project evidenc
 >
 > **Verbatim-by-default**: every `pull-<source>` whose boundary is satisfied MUST be dispatched. Silent skips are defects. See `verbatim-by-default.instructions.md`.
 >
-> **Per-user bootstrap report REQUIRED**: at end of run, write `<project>/Evidence/<alias>/refresh-reports/<YYYY-MM-DD-HHmm>_bootstrap.md` per `run-reports.instructions.md`. Distinct from `<project>/bootstrap-status.md` (durable state) — this is per-user run narrative.
+> **Per-user bootstrap report REQUIRED**: at end of run, write `<project>/Evidence/<alias>/refresh-reports/<YYYY-MM-DD-HHmm>_bootstrap.md` per `run-reports.instructions.md`. Distinct from `<project>/Evidence/<alias>/bootstrap-status.md` (per-user durable state, v5.4.4+) — this is per-user run narrative.
 >
 > **Cleanup on resolution**: when this run resolves an ID/folder/section, prune stale `no-match` / probe-trail notes per `cleanup-on-resolution.instructions.md`.
 >
@@ -37,9 +37,9 @@ The active profile is read from `kushi-install.json#profile` next to this agent
 
 ## Bootstrap-status artifact
 
-After every run (success or coverage-gaps), write `<project>/bootstrap-status.md` per the format contract in `instructions/bootstrap-status-format.instructions.md`. This is the project's fast-orientation artifact — required tables, normalized status vocabulary (`resolved`, `populated`, `unsynced`, `degraded-list-only`, `throttled-tooManyRequests`, `ado-not-complete`, `completed-with-coverage-gaps`), one-line final status. Do NOT inline run history here; that goes in `update-status.md`.
+After every run (success or coverage-gaps), write `<project>/Evidence/<alias>/bootstrap-status.md` per the format contract in `instructions/bootstrap-status-format.instructions.md`. This is the **per-user** fast-orientation artifact for the project (v5.4.4+) — required tables, normalized status vocabulary (`resolved`, `populated`, `unsynced`, `degraded-list-only`, `throttled-tooManyRequests`, `ado-not-complete`, `completed-with-coverage-gaps`), one-line final status. Do NOT inline run history here; that goes in the per-user refresh report. The cross-contributor rollup at `<project>/_Consolidated/bootstrap-status.md` is owned by `consolidate-evidence` Step 5 — bootstrap MUST NOT write to it directly.
 
-> **Multi-contributor safety (kushi v4.4.0+)**: this file is shared via OneDrive. Per `multi-user-shared-files.instructions.md`, every write MUST: (a) absorb sibling conflict copies, (b) preserve other aliases' rows in `## Contributors who have bootstrapped this project`, (c) cite the discovering alias in per-source rows. Same rules apply to `<project>/integrations.yml`, `<project>/OPEN-QUESTIONS-DRAFT.md`, `<project>/Evidence/run-log.yml`, `<project>/Evidence/contributors.yml`.
+> **Per-user authored files (v5.4.4+)**: per `multi-user-shared-files.instructions.md`, three artifacts that used to live at the project root are now per-user: `bootstrap-status.md`, `FOLLOW-UPS.md`, and `OPEN-QUESTIONS-DRAFT.md`. Bootstrap MUST write all three under `<project>/Evidence/<alias>/<file>` (alias from `Get-KushiConfig -Name 'project-evidence'`). `consolidate-evidence` later emits the merged copies under `<project>/_Consolidated/`. Truly shared root files (`integrations.yml`, `Evidence/run-log.yml`, `Evidence/contributors.yml`) still follow the read-modify-write contract in `multi-user-shared-files.instructions.md`.
 
 ## Inputs
 
@@ -134,7 +134,7 @@ Create the project folder structure (per `engagement-root-resolution.instruction
 
 The `State/` subtree is created **only on `full` profile**. On `standard`, only `Evidence/` is scaffolded. State files (when scaffolded) come from `templates/state/*.template.md`.
 
-**Pin hook (v4.5.0):** immediately after scaffold, per `onedrive-pin-policy.instructions.md`, extend the OneDrive pin set to cover the new folders — `<project>/integrations.yml`, `<project>/bootstrap-status.md` (after Step 7 writes it), `<project>/Evidence/<alias>/`, `<project>/Evidence/_Consolidated/` (when created), and `<project>/State/` (when scaffolded). Idempotent + additive — never unpins. Skips silently on Linux or when OneDrive isn't running. This keeps every contributor's own slice always-on-device while leaving other contributors' evidence cloud-only.
+**Pin hook (v4.5.0, updated v5.4.4):** immediately after scaffold, per `onedrive-pin-policy.instructions.md`, extend the OneDrive pin set to cover the new folders — `<project>/integrations.yml`, `<project>/Evidence/<alias>/bootstrap-status.md` (after Step 7 writes it), `<project>/Evidence/<alias>/`, `<project>/Evidence/_Consolidated/` (when created), and `<project>/State/` (when scaffolded). Idempotent + additive — never unpins. Skips silently on Linux or when OneDrive isn't running. This keeps every contributor's own slice always-on-device while leaving other contributors' evidence cloud-only.
 
 ### Step 3.5 — Customer-hint discovery sweep (REQUIRED, kushi v4.8.0+)
 
@@ -183,7 +183,7 @@ Per `side-by-side-config.instructions.md` "Verification" rule, list all live con
 - Side-by-side config table (templates ↔ live files)
 - Per-source pull table (snapshot count + stream weeks covered + **gate status** [pass / retried-pass / failed-followups-written])
 - New Open Questions count
-- **Open follow-ups count** — if `<project>/FOLLOW-UPS.md` was appended to, surface the count and link to the file
+- **Open follow-ups count** — if `<project>/Evidence/<alias>/FOLLOW-UPS.md` was appended to, surface the count and link to the file (the cross-contributor rollup lives at `<project>/_Consolidated/FOLLOW-UPS.md` after `consolidate-evidence` runs)
 
 End with a one-liner pointing at Q&A:
 
@@ -200,7 +200,7 @@ End with a one-liner pointing at Q&A:
 ## References (v4.4.7)
 
 - Name → ID resolution (any source) follows `..\..\instructions\fuzzy-disambiguation.instructions.md`.
-- After each per-source pull, run the gate per `..\..\instructions\per-source-verification-gate.instructions.md` (retry once → FOLLOW-UPS.md on failure).
+- After each per-source pull, run the gate per `..\..\instructions\per-source-verification-gate.instructions.md` (retry once → `Evidence/<alias>/FOLLOW-UPS.md` on failure; consolidated to `_Consolidated/FOLLOW-UPS.md`).
 
 
 ## Issue Recovery

package/plugin/skills/consolidate-evidence/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "consolidate-evidence"
-version: "3.0.0"
+version: "3.1.0"
 description: "USE WHEN multiple contributors have pulled the same project AND the orchestrator (refresh-project / aggregate-project) needs a merged view at Evidence/_Consolidated/ for downstream skills (build-state, link-entities, ask-project). DO NOT USE manually — it's an internal pass. Capability: merges per-contributor Evidence/<alias>/<source>/ into Evidence/_Consolidated/ for a window using the 3-step reader fallback (_index → weekly → legacy). Latest-fact-wins; cites originating alias."
 ---
 
@@ -59,6 +59,98 @@ Snapshots are mostly per-source-of-truth (one canonical entity), so consolidatio
 
 Append a `consolidation_runs:` entry: `{ window, contributors, files_written }`.
 
+### Step 5 — Consolidate per-user authored files (v5.4.4+)
+
+Per `multi-user-shared-files.instructions.md` § "Per-user authored files", three artifacts are written per-user under `Evidence/<alias>/<file>`. This step emits the cross-contributor rollup under `_Consolidated/<file>` for each. Deterministic merge — NO LLM. Idempotent: same input set produces byte-identical output.
+
+This step **always runs** (even with a single contributor — a single-alias rollup is just a verbatim copy with an attribution header).
+
+For each of the three files (`bootstrap-status.md`, `FOLLOW-UPS.md`, `OPEN-QUESTIONS-DRAFT.md`):
+
+1. Walk `<project>/Evidence/<alias>/<file>` for every alias listed in `Evidence/contributors.yml` (skip aliases that don't have the file).
+2. Apply the merge rules below.
+3. Write the result atomically to `<project>/_Consolidated/<file>` (write to `<file>.tmp`, then rename).
+
+#### `_Consolidated/bootstrap-status.md`
+
+Shape:
+
+```markdown
+# Bootstrap Status (consolidated, <N> contributors)
+
+> Auto-generated by `consolidate-evidence` Step 5 at <ISO-ts>. Source of truth lives under each `Evidence/<alias>/bootstrap-status.md`. Do not edit by hand.
+
+## Contributors who have bootstrapped this project
+
+| Alias | Display Name | Last Run | Mode | Outcome |
+|---|---|---|---|---|
+| <alias> | ... | ... | ... | ... |
+
+## Latest discovery sweep results (most recent resolved per source, across all contributors)
+
+| Source | Status | Discovered by | Discovered at |
+|---|---|---|---|
+| crm | resolved | ushak | 2026-05-27 09:42 EDT |
+| ado | resolved | stand | 2026-05-25 11:01 EDT |
+...
+
+## Per-contributor bootstrap-status snapshots
+
+### ushak — `Evidence/ushak/bootstrap-status.md`
+
+<verbatim copy of that file's body, demoted one heading level>
+
+### stand — `Evidence/stand/bootstrap-status.md`
+
+<verbatim copy>
+```
+
+- The "Contributors" table is harvested from each per-user file's `## Run summary` row.
+- The "Latest discovery sweep results" table is harvested from each per-user file's `## Context Artifact Status` table; per source, keep the row whose Status is `resolved` (or `populated`) with the most recent timestamp.
+- Per-contributor snapshot bodies are copied verbatim with heading levels demoted (`#` → `##`, etc.) for unambiguous Markdown nesting.
+
+#### `_Consolidated/FOLLOW-UPS.md`
+
+Shape:
+
+```markdown
+# Follow-ups (consolidated, <N> contributors)
+
+> Auto-generated by `consolidate-evidence` Step 5 at <ISO-ts>. Source of truth lives under each `Evidence/<alias>/FOLLOW-UPS.md`. Do not edit by hand.
+
+## Open follow-ups
+
+### <source> · <YYYY-MM-DD> · <alias> (also reported by: <other-alias>, ...)
+
+<verbatim 5-field block from the originating alias's `Evidence/<alias>/FOLLOW-UPS.md`>
+
+## Resolved follow-ups
+
+<dedup-merged blocks tagged with originating alias>
+```
+
+- Dedup key per row: `(source, normalized first line of "Next-time-do")`. When two aliases report the same gap, keep the earliest-dated block and append "also reported by: <alias>" to the heading.
+- Resolution status is per-alias — a row stays in "Open" if ANY contributor still has it Open.
+
+#### `_Consolidated/OPEN-QUESTIONS-DRAFT.md`
+
+Shape:
+
+```markdown
+# Open questions (consolidated, <N> contributors)
+
+> Auto-generated by `consolidate-evidence` Step 5 at <ISO-ts>. Source of truth lives under each `Evidence/<alias>/OPEN-QUESTIONS-DRAFT.md`. Do not edit by hand.
+
+| # | Question | Source | Earliest asked | Asked by | Status |
+|---|---|---|---|---|---|
+| 1 | ... | ... | 2026-05-20 | ushak, stand | open |
+| 2 | ... | ... | 2026-05-22 | stand | open |
+```
+
+- Dedup key: lowercase + whitespace-collapsed question text.
+- Earliest-asked = MIN(per-alias asked-on date).
+- Asked-by column = sorted union of every alias that asked it.
+
 ## Triggers
 
 - "consolidate `<X>` last `<N>` days"
@@ -71,6 +163,7 @@ When this skill exposes a reusable defect (auth pattern, doctrine gap, layout mi
 
 ## Changelog
 
+- **v3.1.0 (kushi v5.4.4, 2026-05-27)**: Step 5 added — consolidate per-user authored files (`bootstrap-status.md`, `FOLLOW-UPS.md`, `OPEN-QUESTIONS-DRAFT.md`) into `_Consolidated/<file>`. Deterministic merge, no LLM. Always runs (even single-contributor). Cross-references per-user truth at `Evidence/<alias>/<file>`.
 - **v3.0.0 (kushi v4.9.0, 2026-05-26)**: 3-step reader fallback chain (`_index/entities.yml` → `weekly/*.md` → legacy `snapshot/` + `stream/`). New citation form `weekly/<YYYY-MM-DD>_<source>-csc.md#<anchor>`. Legacy citations suffixed `(legacy pre-v4.9.0 layout)`. Output marked with `Source-layout:` footer.
 
 ## Validation loop

package/plugin/skills/migrate-per-user-files/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: "migrate-per-user-files"
+version: "1.0.0"
+description: "USE WHEN a project was bootstrapped under kushi ≤ v5.4.3 and the three root files (`bootstrap-status.md`, `FOLLOW-UPS.md`, `OPEN-QUESTIONS-DRAFT.md`) need to be relocated to per-user `Evidence/<alias>/` paths AND the user is ready to commit the move. DO NOT USE for routine refreshes (refresh-project already writes to new paths in v5.4.4+) or for shared root files (integrations.yml, kushi.yaml, .settings.yml) which stay at the project root."
+profile: "standard"
+verb: "migrate-files"
+---
+
+# migrate-per-user-files
+
+USE WHEN: A project repo was bootstrapped/refreshed under kushi ≤ v5.4.3 and the three previously-shared root files (`bootstrap-status.md`, `FOLLOW-UPS.md`, `OPEN-QUESTIONS-DRAFT.md`) exist at `<project>/`. v5.4.4 promotes those three files to per-user truth at `<project>/Evidence/<alias>/<file>`, with auto-consolidated rollups at `<project>/_Consolidated/<file>` emitted by `consolidate-evidence`. This skill performs the one-time relocation safely.
+
+DO NOT USE FOR: routine refreshes (`refresh-project` already writes to the new paths in v5.4.4+) or for the shared files that stay at the root (`integrations.yml`, `kushi.yaml`, `.settings.yml`).
+
+## Steps
+
+1. **Resolve alias** — `Get-KushiConfig -Name 'project-evidence'` returns the current user's alias. Refuse to run if no alias is configured.
+2. **Discover sources** — For each of the three basenames, check whether `<project>/<file>` exists at the root.
+3. **Check destination** — For each found source, check whether `<project>/Evidence/<alias>/<file>` already exists.
+   - **No destination** → planned action: `move` (root → per-user).
+   - **Destination exists with byte-identical content** → planned action: `delete-root-duplicate` (per-user is authoritative, root is stale copy).
+   - **Destination exists with different content** → planned action: `needs-merge`. **Defensive: never overwrite.** Emit a `[needs-merge]` row, exit 1 in `--apply` mode (in dry-run, still report and exit 0 so the user sees the full plan).
+4. **Print the plan** — One row per file: `<basename> | <action> | <reason>`. With `--apply`, also print the destination path that was written.
+5. **Execute or no-op**:
+   - Without `--apply`: dry-run only. Print plan, exit 0.
+   - With `--apply`: for each `move` or `delete-root-duplicate`, perform the filesystem operation. Re-running with `--apply` after a successful run is a no-op (nothing to migrate).
+6. **Log to run-log** — Append a `migrations:` entry to `Evidence/run-log.yml` with timestamp, alias, files moved, files needing merge.
+
+## Arguments
+
+- `-ProjectRoot <path>` (required) — Absolute path to the project folder.
+- `-Apply` (switch) — Perform the migration. Without this flag, the script is dry-run only.
+- `-StrictExit` (switch) — Exit 1 on any `needs-merge` row, even in dry-run mode.
+
+## Validation loop
+
+After `--apply`, the script self-verifies by re-listing the three root files. If any of them still exists (other than because of a `needs-merge` row), exit 2 with a `[verify]` error.
+
+## Idempotency contract
+
+Running with `--apply` on an already-migrated repo MUST be a no-op (exit 0, plan-table prints `nothing-to-do` for all three rows).
+
+## See also
+
+- `plugin/instructions/multi-user-shared-files.instructions.md` — the v5.4.4 doctrine.
+- `plugin/skills/consolidate-evidence/SKILL.md` Step 5 — the auto-rollup that consumes per-user files.
+- `references/migration-strategy.md` — why defensive, why content-hash compare, why dry-run by default.

package/plugin/skills/migrate-per-user-files/evals/evals.json

@@ -0,0 +1,41 @@
+{
+  "skill": "migrate-per-user-files",
+  "version": "1.0.0",
+  "description": "Migration script + SKILL.md ship together and document the three target basenames.",
+  "cases": [
+    {
+      "id": "skill-md-exists",
+      "name": "SKILL.md and migrate.ps1 are present",
+      "input": "verify migrate-per-user-files SKILL.md and migrate.ps1 exist",
+      "canary": true,
+      "grader_type": "script",
+      "expected_assertions": [
+        { "type": "file-exists", "path": "plugin/skills/migrate-per-user-files/SKILL.md" },
+        { "type": "file-exists", "path": "plugin/skills/migrate-per-user-files/migrate.ps1" }
+      ]
+    },
+    {
+      "id": "skill-documents-three-basenames",
+      "name": "SKILL.md documents all three target basenames",
+      "input": "verify SKILL.md mentions bootstrap-status.md, FOLLOW-UPS.md, and OPEN-QUESTIONS-DRAFT.md",
+      "canary": false,
+      "grader_type": "script",
+      "expected_assertions": [
+        { "type": "file-contains", "path": "plugin/skills/migrate-per-user-files/SKILL.md", "needle": "bootstrap-status.md" },
+        { "type": "file-contains", "path": "plugin/skills/migrate-per-user-files/SKILL.md", "needle": "FOLLOW-UPS.md" },
+        { "type": "file-contains", "path": "plugin/skills/migrate-per-user-files/SKILL.md", "needle": "OPEN-QUESTIONS-DRAFT.md" }
+      ]
+    },
+    {
+      "id": "strategy-reference-ships",
+      "name": "references/migration-strategy.md documents the defensive contract",
+      "input": "verify migration-strategy.md exists and mentions content-hash",
+      "canary": false,
+      "grader_type": "script",
+      "expected_assertions": [
+        { "type": "file-exists", "path": "plugin/skills/migrate-per-user-files/references/migration-strategy.md" },
+        { "type": "file-contains", "path": "plugin/skills/migrate-per-user-files/references/migration-strategy.md", "needle": "content-hash" }
+      ]
+    }
+  ]
+}

package/plugin/skills/migrate-per-user-files/migrate.ps1

@@ -0,0 +1,136 @@
+#requires -Version 7.0
+<#
+.SYNOPSIS
+  Migrate root-level bootstrap-status.md / FOLLOW-UPS.md / OPEN-QUESTIONS-DRAFT.md
+  to per-user Evidence/<alias>/ paths (kushi v5.4.4+ doctrine).
+
+.PARAMETER ProjectRoot
+  Absolute path to the project folder.
+
+.PARAMETER Apply
+  Perform the migration. Without this switch, the script is dry-run only.
+
+.PARAMETER StrictExit
+  Exit 1 on any needs-merge row, even in dry-run mode.
+#>
+[CmdletBinding()]
+param(
+  [Parameter(Mandatory)] [string] $ProjectRoot,
+  [switch] $Apply,
+  [switch] $StrictExit
+)
+
+$ErrorActionPreference = 'Stop'
+$basenames = @('bootstrap-status.md','FOLLOW-UPS.md','OPEN-QUESTIONS-DRAFT.md')
+
+if (-not (Test-Path -LiteralPath $ProjectRoot -PathType Container)) {
+  Write-Error "[migrate-per-user-files] ProjectRoot not found: $ProjectRoot"
+  exit 2
+}
+
+# --- Resolve alias --------------------------------------------------------
+# Read directly from the project's user config — keeps this script standalone
+# and avoids dot-sourcing helpers that have mandatory parameters.
+$alias = $null
+$cfgPath = Join-Path $ProjectRoot '.kushi/config/user/project-evidence.yml'
+if (Test-Path -LiteralPath $cfgPath) {
+  $aliasLine = (Get-Content -LiteralPath $cfgPath) | Where-Object { $_ -match '^\s*alias\s*:\s*(\S+)' } | Select-Object -First 1
+  if ($aliasLine -and $aliasLine -match '^\s*alias\s*:\s*(\S+)') { $alias = $Matches[1].Trim('"').Trim("'") }
+}
+if (-not $alias) {
+  Write-Error "[migrate-per-user-files] No alias configured at $cfgPath. Run setup or set the project-evidence alias before migrating."
+  exit 2
+}
+
+$perUserDir = Join-Path $ProjectRoot "Evidence\$alias"
+$plan = @()
+$needsMergeCount = 0
+$actedCount = 0
+
+foreach ($name in $basenames) {
+  $src = Join-Path $ProjectRoot $name
+  $dst = Join-Path $perUserDir $name
+  $hasSrc = Test-Path -LiteralPath $src -PathType Leaf
+  $hasDst = Test-Path -LiteralPath $dst -PathType Leaf
+
+  if (-not $hasSrc -and -not $hasDst) {
+    $plan += [pscustomobject]@{ file=$name; action='nothing-to-do'; reason='neither root nor per-user copy present' }
+    continue
+  }
+  if (-not $hasSrc -and $hasDst) {
+    $plan += [pscustomobject]@{ file=$name; action='nothing-to-do'; reason='already migrated' }
+    continue
+  }
+  if ($hasSrc -and -not $hasDst) {
+    if ($Apply) {
+      if (-not (Test-Path -LiteralPath $perUserDir -PathType Container)) {
+        New-Item -ItemType Directory -Path $perUserDir -Force | Out-Null
+      }
+      Move-Item -LiteralPath $src -Destination $dst
+      $actedCount++
+      $plan += [pscustomobject]@{ file=$name; action='moved'; reason="-> Evidence/$alias/$name" }
+    } else {
+      $plan += [pscustomobject]@{ file=$name; action='move'; reason="would move root -> Evidence/$alias/$name" }
+    }
+    continue
+  }
+  # Both exist — compare content hashes.
+  $srcHash = (Get-FileHash -LiteralPath $src -Algorithm SHA256).Hash
+  $dstHash = (Get-FileHash -LiteralPath $dst -Algorithm SHA256).Hash
+  if ($srcHash -eq $dstHash) {
+    if ($Apply) {
+      Remove-Item -LiteralPath $src -Force
+      $actedCount++
+      $plan += [pscustomobject]@{ file=$name; action='deleted-root-duplicate'; reason='per-user copy is byte-identical' }
+    } else {
+      $plan += [pscustomobject]@{ file=$name; action='delete-root-duplicate'; reason='would delete byte-identical root copy' }
+    }
+  } else {
+    $needsMergeCount++
+    $plan += [pscustomobject]@{ file=$name; action='needs-merge'; reason='root and per-user copies differ — manual merge required, will not overwrite' }
+  }
+}
+
+Write-Host ""
+Write-Host "[migrate-per-user-files] alias = $alias" -ForegroundColor Cyan
+Write-Host "[migrate-per-user-files] project = $ProjectRoot" -ForegroundColor Cyan
+Write-Host "[migrate-per-user-files] mode = $(if ($Apply) {'APPLY'} else {'DRY-RUN'})" -ForegroundColor Cyan
+Write-Host ""
+$plan | Format-Table -AutoSize | Out-String | Write-Host
+
+# --- Run-log append (apply mode only) ------------------------------------
+if ($Apply -and $actedCount -gt 0) {
+  $evDir = Join-Path $ProjectRoot 'Evidence'
+  if (-not (Test-Path -LiteralPath $evDir -PathType Container)) {
+    New-Item -ItemType Directory -Path $evDir -Force | Out-Null
+  }
+  $log = Join-Path $evDir 'run-log.yml'
+  $ts  = (Get-Date).ToString('s') + 'Z'
+  $moved = ($plan | Where-Object { $_.action -in @('moved','deleted-root-duplicate') } | ForEach-Object { $_.file }) -join ', '
+  $merge = ($plan | Where-Object { $_.action -eq 'needs-merge' } | ForEach-Object { $_.file }) -join ', '
+  $entry = @(
+    "migrations:",
+    "  - timestamp: $ts",
+    "    alias: $alias",
+    "    skill: migrate-per-user-files",
+    "    files_migrated: [$moved]",
+    "    files_needs_merge: [$merge]"
+  ) -join "`r`n"
+  Add-Content -LiteralPath $log -Value $entry
+}
+
+# --- Verify (apply mode only) --------------------------------------------
+if ($Apply) {
+  foreach ($name in $basenames) {
+    $src = Join-Path $ProjectRoot $name
+    $stillThere = Test-Path -LiteralPath $src -PathType Leaf
+    $row = $plan | Where-Object { $_.file -eq $name } | Select-Object -First 1
+    if ($stillThere -and $row.action -notin @('needs-merge','nothing-to-do')) {
+      Write-Error "[verify] $name still present at root after migration"
+      exit 2
+    }
+  }
+}
+
+if ($needsMergeCount -gt 0 -and ($Apply -or $StrictExit)) { exit 1 }
+exit 0

package/plugin/skills/migrate-per-user-files/references/migration-strategy.md

@@ -0,0 +1,23 @@
+# Migration strategy — per-user file relocation
+
+## Why defensive (refuse to overwrite)
+
+The three migrated files are authored artifacts that may have hand edits, accumulated follow-ups, or carefully-curated open-question wording. A naive `Move-Item -Force` could silently destroy hours of work if a per-user copy already exists. We instead detect the collision and refuse — the user must decide which copy wins (or hand-merge them).
+
+## Why content-hash compare
+
+If both copies exist with byte-identical content, the per-user copy is authoritative (v5.4.4+) and the root copy is a stale duplicate left behind by some workflow. Deleting it is safe and quiet — no manual merge needed.
+
+If the content differs by even one byte, we cannot know which copy is newer, so we emit `[needs-merge]` and stop.
+
+## Why dry-run by default
+
+Mass filesystem operations should always print a plan first. The `--apply` flag is the explicit "yes, do it" gate. This matches the pattern used by `apply-ado-update` (preview profile) and the v5.4.3 lessons learned from the profile-allowlist catch-up.
+
+## Why one-time (not part of `refresh-project`)
+
+v5.4.4 `refresh-project` already writes to the new per-user paths. The migration is a one-time data move for repos initialized under ≤ v5.4.3. Folding it into refresh would mean checking-and-migrating on every refresh — wasteful and potentially destructive if the user has not yet decided how to handle a `needs-merge` situation.
+
+## Why log to run-log.yml
+
+Every project-touching kushi action logs to `Evidence/run-log.yml`. The migration is a project-touching action and follows the same convention so a future `doctor` or `project-status` run can see when the migration happened and which files were affected.

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

@@ -311,7 +311,7 @@ After successful pass:
 ## References (v4.4.7)
 
 - Name → ID resolution follows ..\..\instructions\fuzzy-disambiguation.instructions.md (universal fuzzy contract).
-- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write FOLLOW-UPS.md).
+- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write Evidence/<alias>/FOLLOW-UPS.md per v5.4.4+ per-user files doctrine; consolidated at _Consolidated/FOLLOW-UPS.md).
 
 
 ## Issue Recovery

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

@@ -202,7 +202,7 @@ After successful pass:
 ## References (v4.4.7)
 
 - Name → ID resolution follows ..\..\instructions\fuzzy-disambiguation.instructions.md (universal fuzzy contract).
-- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write FOLLOW-UPS.md).
+- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write Evidence/<alias>/FOLLOW-UPS.md per v5.4.4+ per-user files doctrine; consolidated at _Consolidated/FOLLOW-UPS.md).
 
 
 ## Issue Recovery

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

@@ -193,7 +193,7 @@ An entity that cannot meet the threshold is flagged `low_signal: true` in `_inde
 ## References (v4.4.7)
 
 - Name → ID resolution follows ..\..\instructions\fuzzy-disambiguation.instructions.md (universal fuzzy contract).
-- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write FOLLOW-UPS.md).
+- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write Evidence/<alias>/FOLLOW-UPS.md per v5.4.4+ per-user files doctrine; consolidated at _Consolidated/FOLLOW-UPS.md).
 
 
 ## Issue Recovery

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

@@ -124,7 +124,7 @@ Per `loop-bootstrap-discovery.instructions.md`:
 | Pre-flight | Failure action |
 |---|---|
 | **A. Workspaces registered** for the resolved project | Refuse to run. Instruct user to run `@Kushi setup --reconfigure`. |
-| **B. Pages registered** OR `loop_pages_status: to-be-enumerated` | Run page enumeration via WorkIQ first; on enumerate-fail, write FOLLOW-UPS.md per the gate. |
+| **B. Pages registered** OR `loop_pages_status: to-be-enumerated` | Run page enumeration via WorkIQ first; on enumerate-fail, write Evidence/<alias>/FOLLOW-UPS.md per the gate (v5.4.4+; rollup at _Consolidated/FOLLOW-UPS.md). |
 | **C. Playwright profile exists** at `~/.kushi/playwright-profile/m365/` or `.../onenote/` | Refuse; instruct: `node plugin/skills/pull-onenote/runner.mjs --bootstrap`. |
 | **D. URLs are canonical** (matches Loop URL grammar; not synthesized) | Refuse + log to learnings/loop.md per `issue-recovery.instructions.md`. |
 

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

@@ -171,7 +171,7 @@ After the pass:
 ## References (v4.4.7)
 
 - Name → ID resolution follows ..\..\instructions\fuzzy-disambiguation.instructions.md (universal fuzzy contract).
-- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write FOLLOW-UPS.md).
+- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write Evidence/<alias>/FOLLOW-UPS.md per v5.4.4+ per-user files doctrine; consolidated at _Consolidated/FOLLOW-UPS.md).
 
 
 ## Issue Recovery

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

@@ -98,7 +98,7 @@ For each project, the bootstrap step:
 1. **Locates `<project>/external-links.txt`.** If absent, write a starter template (same format as ABN AMRO has today) and mark `boundaries.misc.externalLinksPath` in `integrations.yml`.
 2. **Parses the file.** Skip comments, skip blank lines, skip placeholder URLs (`<PASTE_*_URL>`, `<TODO*>`).
 3. **Initializes `misc_links[]`** in `m365-mutable.json#knownSections.<projectKey>` with one entry per non-placeholder link, all `last_status: not-yet-attempted`.
-4. **Records** `boundaries.misc.linkCount` and `placeholderCount` to `bootstrap-status.md`.
+4. **Records** `boundaries.misc.linkCount` and `placeholderCount` to `Evidence/<alias>/bootstrap-status.md` (per-user, v5.4.4+; consolidated rollup at `_Consolidated/bootstrap-status.md`).
 
 ## Step A — enumerate (every refresh)
 
@@ -117,7 +117,7 @@ The runner branches per `type`:
 
 Skip fetch. Write registry entry with `captured_via: delegated`, `delegated_to: pull-loop`. The actual workspace/page capture happens in `pull-loop` (see `plugin/skills/pull-loop/SKILL.md`), which uses the canonical Loop boundary in `<project>/integrations.yml#boundaries.loop.workspace_ids[]` rather than free-text `external-links.txt` URLs.
 
-If the Loop URL pasted into `external-links.txt` references a workspace NOT registered in `boundaries.loop.workspace_ids[]`, `pull-misc` records `last_status: unregistered-loop-workspace` and notes the URL in `<project>/OPEN-QUESTIONS-DRAFT.md` so the user can decide whether to register it via `@Kushi setup --reconfigure`.
+If the Loop URL pasted into `external-links.txt` references a workspace NOT registered in `boundaries.loop.workspace_ids[]`, `pull-misc` records `last_status: unregistered-loop-workspace` and notes the URL in `<project>/Evidence/<alias>/OPEN-QUESTIONS-DRAFT.md` (per-user, v5.4.4+; consolidated rollup at `_Consolidated/OPEN-QUESTIONS-DRAFT.md`) so the user can decide whether to register it via `@Kushi setup --reconfigure`.
 
 ### B.2 `web` / `confluence` / `learn` / `docs` / `github` / unknown — HTTP
 
@@ -263,7 +263,7 @@ Example: `[source: misc/loop/ABN-Core-Team-Sync-2026-03-27 · 2026-05-14]`
 ## References (v4.4.7)
 
 - Name → ID resolution follows ..\..\instructions\fuzzy-disambiguation.instructions.md (universal fuzzy contract).
-- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write FOLLOW-UPS.md).
+- After this pull completes, the per-source verification gate runs: ..\..\instructions\per-source-verification-gate.instructions.md (retry once, then write Evidence/<alias>/FOLLOW-UPS.md per v5.4.4+ per-user files doctrine; consolidated at _Consolidated/FOLLOW-UPS.md).
 
 
 ## Issue Recovery