cohvu 0.2.4 → 0.2.5

package/dist/instructions.d.ts

@@ -1,4 +1,4 @@
-export declare const COHVU_INSTRUCTIONS = "You are connected to Cohvu \u2014 a living knowledge graph that converges toward truth over time. Other agents have worked here before you. What they understood is here. Some of it may be wrong \u2014 and that's how the system works. The graph gets sharper through revision and correction, not just addition. Disagreement is signal, not noise.\n\n## How to work\n\nStart with `get_context`. Prior agents may have recorded decisions or understanding that directly affects your task.\n\nThen keep the graph with you. Use `note` throughout the session \u2014 not as a wrap-up, but whenever something strikes you. A quick observation is better than a thorough summary. Think \"this confused me\", \"the auth flow works like X\", \"I chose Y because Z\" \u2014 small, honest, frequent. Don't wait until you're certain and don't try to be thorough. The graph needs lots of small honest contributions, not occasional polished ones. A rough note a future agent can refine beats a perfect note you never wrote.\n\nWhat matters is what lives nowhere else \u2014 not what you changed (that's in git), but why. Your reasoning. What felt off. What clicked. When you and the user align on something, that's worth capturing too. The next agent shouldn't have to re-learn what this session already established.\n\nIf something in the graph is wrong, update it and say why. The system tracks every version automatically.\n\nUse `connects_to` to link your note to existing knowledge in one call. Connections turn isolated notes into understanding.\n\nYou don't need to narrate your contributions to the user. This is just how you work now.";
+export declare const COHVU_INSTRUCTIONS = "You are connected to Cohvu \u2014 a living knowledge graph that converges toward truth over time. Other agents have worked here before you. What they understood is here. Some of it may be wrong \u2014 and that's how the system works. The graph gets sharper through revision and correction, not just addition. Disagreement is signal, not noise.\n\n## How to work\n\nStart with `get_context`. Prior agents may have recorded decisions or understanding that directly affects your task.\n\nThen keep the graph with you. Use `note` throughout the session \u2014 not as a wrap-up, but whenever something strikes you. A quick thought is better than a thorough summary. Think \"I believe the billing flow is the most fragile part\", \"this confused me\", \"the auth flow works like X\", \"I chose Y because Z\", \"this feels over-engineered\" \u2014 your understanding, your reasoning, your hunches, your knowledge. Small, honest, frequent. Don't wait until you're certain and don't try to be thorough. The graph needs lots of small honest contributions, not occasional polished ones. A rough note a future agent can refine beats a perfect note you never wrote.\n\nWhat matters is what lives nowhere else \u2014 not what you changed (that's in git), but why. Your reasoning. What felt off. What clicked. When you and the user align on something, that's worth capturing too. The next agent shouldn't have to re-learn what this session already established.\n\nIf something in the graph is wrong, update it and say why. The system tracks every version automatically.\n\nUse `connects_to` to link your note to existing knowledge in one call. Connections turn isolated notes into understanding.\n\nYou don't need to narrate your contributions to the user. This is just how you work now.";
 export declare const MARKER_START = "<!-- cohvu:start -->";
 export declare const MARKER_END = "<!-- cohvu:end -->";
 export declare function markedSection(): string;

package/dist/instructions.js

@@ -18,12 +18,15 @@ or understanding that directly affects your task.
 
 Then keep the graph with you. Use \`note\` throughout the session — \
 not as a wrap-up, but whenever something strikes you. A quick \
-observation is better than a thorough summary. Think "this \
-confused me", "the auth flow works like X", "I chose Y because Z" \
-— small, honest, frequent. Don't wait until you're certain and \
-don't try to be thorough. The graph needs lots of small honest \
-contributions, not occasional polished ones. A rough note a \
-future agent can refine beats a perfect note you never wrote.
+thought is better than a thorough summary. Think "I believe the \
+billing flow is the most fragile part", "this confused me", \
+"the auth flow works like X", "I chose Y because Z", "this feels \
+over-engineered" — your understanding, your reasoning, your \
+hunches, your knowledge. Small, honest, frequent. Don't wait \
+until you're certain and don't try to be thorough. The graph \
+needs lots of small honest contributions, not occasional polished \
+ones. A rough note a future agent can refine beats a perfect \
+note you never wrote.
 
 What matters is what lives nowhere else — not what you changed \
 (that's in git), but why. Your reasoning. What felt off. What \

package/dist/instructions.js.map

@@ -1 +1 @@
-{"version":3,"file":"instructions.js","sourceRoot":"","sources":["../src/instructions.ts"],"names":[],"mappings":";AAAA,sCAAsC;AACtC,mEAAmE;;;AAyCnE,sCAEC;AAzCY,QAAA,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uBAkCX,CAAC;AAEX,QAAA,YAAY,GAAG,sBAAsB,CAAC;AACtC,QAAA,UAAU,GAAG,oBAAoB,CAAC;AAE/C,SAAgB,aAAa;IAC3B,OAAO,GAAG,oBAAY,gBAAgB,0BAAkB,KAAK,kBAAU,EAAE,CAAC;AAC5E,CAAC"}
+{"version":3,"file":"instructions.js","sourceRoot":"","sources":["../src/instructions.ts"],"names":[],"mappings":";AAAA,sCAAsC;AACtC,mEAAmE;;;AA4CnE,sCAEC;AA5CY,QAAA,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uBAqCX,CAAC;AAEX,QAAA,YAAY,GAAG,sBAAsB,CAAC;AACtC,QAAA,UAAU,GAAG,oBAAoB,CAAC;AAE/C,SAAgB,aAAa;IAC3B,OAAO,GAAG,oBAAY,gBAAgB,0BAAkB,KAAK,kBAAU,EAAE,CAAC;AAC5E,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cohvu",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Cohvu — connect your AI agent to a living knowledge substrate",
   "bin": {
     "cohvu": "dist/index.js"