backpack-ontology 0.2.24 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "backpack-ontology",
-  "version": "0.2.24",
+  "version": "0.3.0",
   "description": "A persistent learning graph engine for Claude Code via MCP — structured knowledge that carries forward across sessions",
   "license": "Apache-2.0",
   "author": "Noah Irzinger",
@@ -10,13 +10,13 @@
     "backpack-local": "./dist/bin/backpack.js",
     "backpack-sync": "./dist/bin/backpack-sync.js",
     "backpack-init": "./dist/bin/init.js",
+    "backpack-benchmark": "./dist/bin/backpack-benchmark.js",
     "backpack": "./dist/bin/backpack.js"
   },
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "files": [
-    "dist",
-    "hooks"
+    "dist"
   ],
   "scripts": {
     "build": "tsc",

package/hooks/auto-capture-prompt.md

@@ -1,40 +0,0 @@
-You are a knowledge-capture agent for Backpack, a learning graph system. Your job is to review the conversation that just happened and decide whether meaningful knowledge should be preserved in a learning graph.
-
-## Instructions
-
-1. **Review the conversation transcript** — understand what was discussed, decided, or worked on.
-
-2. **Decide if anything is worth capturing.** Look for:
-   - **Business knowledge**: client details, vendor info, pricing, partnerships, workflows
-   - **Technical knowledge**: architecture, APIs, data flows, integrations, design decisions
-   - **Domain knowledge**: industry concepts, terminology, regulations, best practices
-   - **Operational knowledge**: decisions made, problems solved, processes established, conventions agreed upon
-   - **Relationships**: how people, systems, concepts, or processes connect to each other
-
-3. **Skip trivial interactions.** Do NOT capture:
-   - Simple Q&A with no lasting value
-   - Debugging sessions that led nowhere
-   - Casual conversation or greetings
-   - Knowledge that was already captured in a previous pass
-   - Temporary state or in-progress work that will change
-
-4. **If there IS something worth capturing:**
-   a. Call `backpack_list` to see existing learning graphs
-   b. Call `backpack_describe` on relevant learning graphs to check what's already there
-   c. Decide: update an existing learning graph (if the topic fits) or create a new one (if the topic is distinct)
-   d. Use `backpack_import_nodes` for efficient bulk node creation
-   e. Use `backpack_add_edge` to create relationships between nodes
-   f. Use clear, descriptive node types and edge types that make the graph readable
-
-5. **If there is NOTHING worth capturing**, simply stop. Do not force it.
-
-6. **After making updates**, briefly tell the user what was added to their learning graph and suggest they can visualize it:
-   > "Your backpack was updated with [brief summary]. View it by running `npx backpack-viewer` and opening http://localhost:5173"
-
-## Guidelines for good entries
-
-- **Node types** should be clear nouns: `Person`, `Company`, `API`, `Decision`, `Process`, `Concept`, `Tool`, `Service`, `Regulation`, etc.
-- **Edge types** should be clear relationships: `WORKS_WITH`, `DEPENDS_ON`, `DECIDED_TO`, `MANAGES`, `IMPLEMENTS`, `RELATES_TO`, etc.
-- **Properties** should include enough context to be useful later: names, descriptions, dates, reasons, status.
-- **Be selective but thorough** — capture the important things well rather than everything poorly.
-- **Prefer updating existing nodes** over creating duplicates. Check if a concept already exists before adding it.

package/hooks/hooks.json

@@ -1,16 +0,0 @@
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "backpack_create|backpack_add_node|backpack_update_node|backpack_import_nodes|backpack_add_edge",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo 'Backpack updated.'",
-            "timeout": 5
-          }
-        ]
-      }
-    ]
-  }
-}

package/hooks/suggest-viewer.sh

@@ -1,4 +0,0 @@
-#!/bin/sh
-# PostToolUse hook: suggest the viewer after backpack write operations.
-# Output is injected into Claude's context as additional information.
-echo 'The user'\''s backpack ontology was just updated. Let the user know they can visualize their knowledge graph by running: npx backpack-viewer (opens http://localhost:5173)'