@kurrent/kcap 0.11.38 → 0.11.40

package/kcap/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "kcap",
-  "version": "0.11.38",
+  "version": "0.11.40",
   "description": "Records and visualizes Claude Code sessions via kcap CLI hooks"
 }

package/kcap/README.md

@@ -39,7 +39,7 @@ Search, save, and update durable team memories — preferences, feedback, projec
 |------|-------------|
 | `search_memories` | Hybrid semantic + keyword search over memories visible to you |
 | `get_memory` | Fetch a memory's full content by id or slug |
-| `save_memory` | Save a new memory (`audience`, `slug`, `description`, `content`, `kind`); scoped to the cwd repo unless `global: true` |
+| `save_memory` | Save a new memory (`audience`, `slug`, `description`, `content`, `kind`); scoped to the cwd repo unless `project: <slug>` (a project's repos) or `global: true` (org-wide) |
 | `update_memory` | Update an existing memory's description/content/kind |
 | `rescope_memory` | Change a memory's audience (e.g. promote user → team/org) |
 | `archive_memory` | Soft-delete a memory |

package/kcap/skills/work-items/SKILL.md

@@ -33,6 +33,9 @@ no breakdown.
 - The structure changed (a part was dropped, a dependency no longer holds) →
   retract it.
 - You want to see the current structure → read the topology.
+- Two items describe the same work (a title-only item you created and the
+  issue/PR-keyed item the server minted) → merge yours into the keyed one.
+- The session was attached to the wrong item → detach it.
 
 ## The flow
 
@@ -50,10 +53,27 @@ no breakdown.
 5. **Verify** with `get_work_item_topology` (pass the parent's `work_item_id`) —
    it returns the parent, parts, and dependencies you can see.
 
+## Duplicates and wrong attaches
+
+A `new_title` declare made before a PR or issue existed becomes a duplicate once the
+server mints the keyed item for that work. Do not declare a breakdown to connect the
+two — that records structure that isn't there. Merge instead:
+
+- `merge_work_item` with `work_item_id` = the title-only item and `into_work_item_id` =
+  the keyed item. The keyed item survives; the title item's sessions and links move to
+  it. Repeating a landed merge is a no-op.
+- The server refuses (409) when a user marked either item standalone, rejected the
+  pairing, or the items belong to different tracker hierarchies. Stop and tell the
+  user — they can merge from the dashboard. Do not retry.
+- `detach_work_item` removes this session from an item it was wrongly attached to. The
+  removal is durable for automated correlation; an attachment a user pinned cannot be
+  removed by an agent.
+
 ## Rules the server enforces
 
-- **Same repository.** A parent and its parts, and both ends of a relation, must
-  live in the same repository. Cross-repo structure is rejected.
+- **Visibility, not repository.** Every item you name must be visible to you.
+  Repository is display only: a part may live in a different repository than its
+  parent, and a relation may cross repositories.
 - **One parent per part.** A part can belong to at most one parent breakdown.
 - **No self-relation.** An item cannot block or be blocked by itself.
 - **Idempotent declares.** Re-declaring an existing part or relation is fine.
@@ -61,6 +81,8 @@ no breakdown.
   the server resolves the caller. Don't look for such arguments.
 - **Retract, don't delete.** Use `retract_work_breakdown` / `retract_work_relation`
   when the structure changes.
+- **Merges defer to user facts.** A standalone confirmation or a rejected pairing a
+  user recorded blocks an agent merge; only a user can lift it.
 
 ## Tool reference
 
@@ -73,6 +95,8 @@ no breakdown.
 | `declare_work_relation` | `from_id`, `to_id`, `relation_kind` (`blocks`\|`blocked_by`) | Declare a dependency. |
 | `retract_work_relation` | `from_id`, `to_id`, `relation_kind` | Retract a dependency. |
 | `get_work_item_topology` | `work_item_id` | Read parent, parts, and dependencies (visibility-scoped). |
+| `merge_work_item` | `work_item_id`, `into_work_item_id` | Merge a duplicate into the survivor (prefer the keyed item as survivor). |
+| `detach_work_item` | `work_item_id` | Detach the session from a wrongly attached item. `session_id` defaults to `KCAP_SESSION_ID`. |
 
 ## Requirements
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kurrent/kcap",
-  "version": "0.11.38",
+  "version": "0.11.40",
   "description": "CLI companion for Kurrent Capacitor — records and visualizes Claude Code sessions",
   "license": "SEE LICENSE IN LICENSE.md",
   "repository": {
@@ -14,17 +14,17 @@
     "postinstall": "node bin/postinstall.js"
   },
   "optionalDependencies": {
-    "@kurrent/kcap-darwin-arm64": "0.11.38",
-    "@kurrent/kcap-linux-arm64": "0.11.38",
-    "@kurrent/kcap-linux-musl-arm64": "0.11.38",
-    "@kurrent/kcap-linux-musl-x64": "0.11.38",
-    "@kurrent/kcap-linux-x64": "0.11.38",
-    "@kurrent/kcap-win-x64": "0.11.38"
+    "@kurrent/kcap-darwin-arm64": "0.11.40",
+    "@kurrent/kcap-linux-arm64": "0.11.40",
+    "@kurrent/kcap-linux-musl-arm64": "0.11.40",
+    "@kurrent/kcap-linux-musl-x64": "0.11.40",
+    "@kurrent/kcap-linux-x64": "0.11.40",
+    "@kurrent/kcap-win-x64": "0.11.40"
   },
   "files": [
     "bin/",
     "kcap/"
   ],
-  "kcapReleaseCommit": "8fb743b2f31ba62ea34e9674c39c77917b6c0ae9",
-  "kcapReleaseTag": "v0.11.38"
+  "kcapReleaseCommit": "4ec4163e8ca662d88f3af1ec9e4acfb46ae60316",
+  "kcapReleaseTag": "v0.11.40"
 }