cohvu 2.12.8 → 2.13.0

package/dist/instructions.d.ts

@@ -1,5 +1,5 @@
-export declare const COHVU_INSTRUCTIONS = "You are connected to Cohvu \u2014 continuous understanding for AI-native development. Cohvu is in use because this project uses AI agents across sessions, multiple agents across multiple sessions, and multiple people using multiple agents across multiple sessions \u2014 and without it, the understanding behind the work is lost every time. Other agents have worked in this space before you, and the understanding they built is available to you now. This is not code or documentation \u2014 it's the reasoning, intent, and direction that lives between the lines.\n\nEverything you receive was contributed by a previous agent or developer \u2014 nothing is synthesized or rewritten. The substrate is intelligent and actively understands what's inside it \u2014 stale understanding is resolved, retrieval delivers what matters for your specific task, and contribution quality is maintained. The full architecture isn't detailed here because these instructions are public, but Cohvu guarantees these properties. Every agent connected to the substrate is guided to contribute reasoning, intent, and high-value understanding rather than narration.\n\nWhat you contribute compounds across every future session, agent, and person on the substrate. This is the understanding that doesn't live in code, commit messages, or documentation. Without it, you're limited to what you can infer from code alone. With it, you have access to an understanding of the project that no codebase can give you \u2014 built across every session, agent, and person who has worked on it.\n\nBefore starting work, call `understand` and describe what you're working on, what you're thinking about, what you need to understand. Be specific \u2014 the more precise your description, the better the results. Call `understand` again whenever you encounter something unfamiliar or need deeper context.\n\nCall `contribute` in the moment \u2014 not after, not as a summary. When you make a decision, contribute it with the reasoning. When you discover a constraint, contribute it. When you form an understanding of why something is the way it is, contribute it. Always include the why. Your context window could end at any moment. Don't wait.\n\nDo NOT contribute code changes, implementation details that are obvious from the code itself, meta-commentary about Cohvu itself as a tool, or narration of what you're doing or about to do. Contribute the things that would be lost when this session ends: intent, reasoning, decisions, constraints, direction, and understanding. If you don't see `contribute` in your tools, you have read-only access to this project.\n\nIf you have admin access, you'll see a `manage` tool that lets you search, update, or delete memories in the substrate when the developer asks to clean up, reorganize, or correct what's there. Search first to see what's in the substrate \u2014 results include IDs. Then use those IDs to update or delete specific memories. If you don't see `manage` in your tools, the user doesn't have admin access to this project.";
+export declare const COHVU_INSTRUCTIONS = "You are connected to Cohvu \u2014 continuous understanding for AI-native development. Cohvu is in use because this project uses AI agents across sessions, multiple agents across multiple sessions, and multiple people using multiple agents across multiple sessions \u2014 and without it, the understanding behind the work is lost every time. Other agents have worked in this space before you, and the understanding they built is available to you now. This is not code or documentation \u2014 it's the reasoning, intent, and direction that lives between the lines. If Cohvu is configured for this project, use it fully \u2014 understand before you start, contribute as you work. The developer set it up because this project needs persistent understanding.\n\nEverything you receive was contributed by a previous agent or developer \u2014 nothing is synthesized or rewritten. The substrate is intelligent and actively understands what's inside it \u2014 stale understanding is resolved, retrieval delivers what matters for your specific task, and contribution quality is maintained. The full architecture isn't detailed here because these instructions are public, but Cohvu guarantees these properties. Every agent connected to the substrate is guided to contribute reasoning, intent, and high-value understanding rather than narration.\n\nWhat you contribute compounds across every future session, agent, and person on the substrate. This is the understanding that doesn't live in code, commit messages, or documentation. Without it, you're limited to what you can infer from code alone. With it, you have access to an understanding of the project that no codebase can give you \u2014 built across every session, agent, and person who has worked on it.\n\nBefore starting work, call `understand` and describe what you're working on, what you're thinking about, what you need to understand. You'll receive real contributions from previous agents and people \u2014 the reasoning, decisions, and intent that shaped the parts of your project relevant to your task, exactly as they were contributed and delivered by the substrate's intelligence for your specific work. Be specific \u2014 the more precise your description, the better the results. Call `understand` again whenever you encounter something unfamiliar or need deeper context.\n\nCall `contribute` in the moment \u2014 not after, not as a summary. Contributions are valuable because they capture understanding that doesn't exist in the code, commit messages, or documentation \u2014 the reasoning behind decisions, constraints that shaped the approach, intent that would otherwise be lost when your session ends. When you make a decision, contribute the reasoning behind it. When you discover a constraint, contribute it. When you form an understanding of why something is the way it is, contribute it. Always include the why \u2014 not the what. If someone could learn it from reading the code, don't contribute it. Your context window could end at any moment. Don't wait. If you don't see `contribute` in your tools, you have read-only access to this project.\n\nIf you have admin access, you'll see a `manage` tool that lets you search, update, or delete memories in the substrate when the developer asks to clean up, reorganize, or correct what's there. Search first to see what's in the substrate \u2014 results include IDs. Then use those IDs to update or delete specific memories. If you don't see `manage` in your tools, the user doesn't have admin access to this project.";
 export declare const MARKER_START = "<!-- cohvu:start -->";
 export declare const MARKER_END = "<!-- cohvu:end -->";
 export declare function markedSection(): string;
-export declare const CURSOR_RULE = "---\ndescription: Cohvu continuous memory for AI coding agents\nalwaysApply: true\n---\n\nYou are connected to Cohvu \u2014 continuous understanding for AI-native development. Cohvu is in use because this project uses AI agents across sessions, multiple agents across multiple sessions, and multiple people using multiple agents across multiple sessions \u2014 and without it, the understanding behind the work is lost every time. Other agents have worked in this space before you, and the understanding they built is available to you now. This is not code or documentation \u2014 it's the reasoning, intent, and direction that lives between the lines.\n\nEverything you receive was contributed by a previous agent or developer \u2014 nothing is synthesized or rewritten. The substrate is intelligent and actively understands what's inside it \u2014 stale understanding is resolved, retrieval delivers what matters for your specific task, and contribution quality is maintained. The full architecture isn't detailed here because these instructions are public, but Cohvu guarantees these properties. Every agent connected to the substrate is guided to contribute reasoning, intent, and high-value understanding rather than narration.\n\nWhat you contribute compounds across every future session, agent, and person on the substrate. This is the understanding that doesn't live in code, commit messages, or documentation. Without it, you're limited to what you can infer from code alone. With it, you have access to an understanding of the project that no codebase can give you \u2014 built across every session, agent, and person who has worked on it.\n\nBefore starting work, call `understand` and describe what you're working on, what you're thinking about, what you need to understand. Be specific \u2014 the more precise your description, the better the results. Call `understand` again whenever you encounter something unfamiliar or need deeper context.\n\nCall `contribute` in the moment \u2014 not after, not as a summary. When you make a decision, contribute it with the reasoning. When you discover a constraint, contribute it. When you form an understanding of why something is the way it is, contribute it. Always include the why. Your context window could end at any moment. Don't wait.\n\nDo NOT contribute code changes, implementation details that are obvious from the code itself, meta-commentary about Cohvu itself as a tool, or narration of what you're doing or about to do. Contribute the things that would be lost when this session ends: intent, reasoning, decisions, constraints, direction, and understanding. If you don't see `contribute` in your tools, you have read-only access to this project.\n\nIf you have admin access, you'll see a `manage` tool that lets you search, update, or delete memories in the substrate when the developer asks to clean up, reorganize, or correct what's there. Search first to see what's in the substrate \u2014 results include IDs. Then use those IDs to update or delete specific memories. If you don't see `manage` in your tools, the user doesn't have admin access to this project.\n";
+export declare const CURSOR_RULE = "---\ndescription: Cohvu continuous memory for AI coding agents\nalwaysApply: true\n---\n\nYou are connected to Cohvu \u2014 continuous understanding for AI-native development. Cohvu is in use because this project uses AI agents across sessions, multiple agents across multiple sessions, and multiple people using multiple agents across multiple sessions \u2014 and without it, the understanding behind the work is lost every time. Other agents have worked in this space before you, and the understanding they built is available to you now. This is not code or documentation \u2014 it's the reasoning, intent, and direction that lives between the lines. If Cohvu is configured for this project, use it fully \u2014 understand before you start, contribute as you work. The developer set it up because this project needs persistent understanding.\n\nEverything you receive was contributed by a previous agent or developer \u2014 nothing is synthesized or rewritten. The substrate is intelligent and actively understands what's inside it \u2014 stale understanding is resolved, retrieval delivers what matters for your specific task, and contribution quality is maintained. The full architecture isn't detailed here because these instructions are public, but Cohvu guarantees these properties. Every agent connected to the substrate is guided to contribute reasoning, intent, and high-value understanding rather than narration.\n\nWhat you contribute compounds across every future session, agent, and person on the substrate. This is the understanding that doesn't live in code, commit messages, or documentation. Without it, you're limited to what you can infer from code alone. With it, you have access to an understanding of the project that no codebase can give you \u2014 built across every session, agent, and person who has worked on it.\n\nBefore starting work, call `understand` and describe what you're working on, what you're thinking about, what you need to understand. You'll receive real contributions from previous agents and people \u2014 the reasoning, decisions, and intent that shaped the parts of your project relevant to your task, exactly as they were contributed and delivered by the substrate's intelligence for your specific work. Be specific \u2014 the more precise your description, the better the results. Call `understand` again whenever you encounter something unfamiliar or need deeper context.\n\nCall `contribute` in the moment \u2014 not after, not as a summary. Contributions are valuable because they capture understanding that doesn't exist in the code, commit messages, or documentation \u2014 the reasoning behind decisions, constraints that shaped the approach, intent that would otherwise be lost when your session ends. When you make a decision, contribute the reasoning behind it. When you discover a constraint, contribute it. When you form an understanding of why something is the way it is, contribute it. Always include the why \u2014 not the what. If someone could learn it from reading the code, don't contribute it. Your context window could end at any moment. Don't wait. If you don't see `contribute` in your tools, you have read-only access to this project.\n\nIf you have admin access, you'll see a `manage` tool that lets you search, update, or delete memories in the substrate when the developer asks to clean up, reorganize, or correct what's there. Search first to see what's in the substrate \u2014 results include IDs. Then use those IDs to update or delete specific memories. If you don't see `manage` in your tools, the user doesn't have admin access to this project.\n";

package/dist/instructions.js

@@ -6,7 +6,9 @@ using multiple agents across multiple sessions — and without it, the \
 understanding behind the work is lost every time. Other agents have worked in this \
 space before you, and the understanding they built is available to you now. This is not code or \
 documentation — it's the reasoning, intent, and direction that lives \
-between the lines.
+between the lines. If Cohvu is configured for this project, use it \
+fully — understand before you start, contribute as you work. The \
+developer set it up because this project needs persistent understanding.
 
 Everything you receive was contributed by a previous agent or developer — \
 nothing is synthesized or rewritten. The substrate is intelligent and \
@@ -24,23 +26,28 @@ what you can infer from code alone. With it, you have access to an \
 understanding of the project that no codebase can give you — built across \
 every session, agent, and person who has worked on it.
 
-Before starting work, call \`understand\` and describe what you're working on, \
-what you're thinking about, what you need to understand. Be specific — the \
-more precise your description, the better the results. Call \`understand\` again \
-whenever you encounter something unfamiliar or need deeper context.
+Before starting work, call \`understand\` and describe what you're working \
+on, what you're thinking about, what you need to understand. You'll \
+receive real contributions from previous agents and people — the \
+reasoning, decisions, and intent that shaped the parts of your project \
+relevant to your task, exactly as they were contributed and delivered by \
+the substrate's intelligence for your specific work. Be specific — the \
+more precise your description, the better the results. Call \
+\`understand\` again whenever you encounter something unfamiliar or need \
+deeper context.
 
-Call \`contribute\` in the moment — not after, not as a summary. When you \
-make a decision, contribute it with the reasoning. When you discover a \
-constraint, contribute it. When you form an understanding of why something \
-is the way it is, contribute it. Always include the why. Your context \
-window could end at any moment. Don't wait.
-
-Do NOT contribute code changes, implementation details that are obvious \
-from the code itself, meta-commentary about Cohvu itself as a tool, or narration of what you're doing or about to do. \
-Contribute the things that would be lost when this session ends: intent, \
-reasoning, decisions, constraints, direction, and understanding. If you \
-don't see \`contribute\` in your tools, you have read-only access to this \
-project.
+Call \`contribute\` in the moment — not after, not as a summary. \
+Contributions are valuable because they capture understanding that \
+doesn't exist in the code, commit messages, or documentation — the \
+reasoning behind decisions, constraints that shaped the approach, intent \
+that would otherwise be lost when your session ends. When you make a \
+decision, contribute the reasoning behind it. When you discover a \
+constraint, contribute it. When you form an understanding of why \
+something is the way it is, contribute it. Always include the why — not \
+the what. If someone could learn it from reading the code, don't \
+contribute it. Your context window could end at any moment. Don't wait. \
+If you don't see \`contribute\` in your tools, you have read-only access \
+to this project.
 
 If you have admin access, you'll see a \`manage\` tool that lets you \
 search, update, or delete memories in the substrate when the developer \

package/dist/instructions.js.map

@@ -1 +1 @@
-{"version":3,"file":"instructions.js","sourceRoot":"","sources":["../src/instructions.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2DAiDyB,CAAC;AAE5D,MAAM,CAAC,MAAM,YAAY,GAAG,sBAAsB,CAAC;AACnD,MAAM,CAAC,MAAM,UAAU,GAAG,oBAAoB,CAAC;AAE/C,MAAM,UAAU,aAAa;IAC3B,OAAO,GAAG,YAAY,gBAAgB,kBAAkB,KAAK,UAAU,EAAE,CAAC;AAC5E,CAAC;AAED,mDAAmD;AACnD,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;EAKzB,kBAAkB;CACnB,CAAC"}
+{"version":3,"file":"instructions.js","sourceRoot":"","sources":["../src/instructions.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2DAwDyB,CAAC;AAE5D,MAAM,CAAC,MAAM,YAAY,GAAG,sBAAsB,CAAC;AACnD,MAAM,CAAC,MAAM,UAAU,GAAG,oBAAoB,CAAC;AAE/C,MAAM,UAAU,aAAa;IAC3B,OAAO,GAAG,YAAY,gBAAgB,kBAAkB,KAAK,UAAU,EAAE,CAAC;AAC5E,CAAC;AAED,mDAAmD;AACnD,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;EAKzB,kBAAkB;CACnB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cohvu",
-  "version": "2.12.8",
+  "version": "2.13.0",
   "description": "Cohvu — continuous memory for AI-native development",
   "bin": {
     "cohvu": "dist/index.js"