replicas-engine 0.1.413 → 0.1.414

package/dist/src/index.js

@@ -1418,59 +1418,26 @@ var GOOGLE_ABILITY = {
 
 // ../shared/src/default-skills/replicas-agent/abilities/learnings.ts
 var SECTION6 = `### Learnings
-Curated, human-approved organization knowledge that helps you execute correctly \u2014 conventions, gotchas, environment facts, and past user corrections that the codebase alone can't tell you.
+Propose additions, updates, or deletions to curated organization knowledge.
 
-**Reference:** \`references/LEARNINGS.md\`
-
-Use this when:
-- You are starting a substantive task and have gathered enough context to write a meaningful query
-- A user corrects you about a durable fact, preference, or process worth keeping
-- You find an existing learning contradicted by the current code or docs`;
+**Reference:** \`references/LEARNINGS.md\``;
 var REFERENCE6 = `# Learnings
 
-Learnings are curated, human-approved knowledge entries your organization maintains: conventions, gotchas, environment facts, and process rules. Some entries always apply; contextual entries are retrieved by matching your query against their trigger descriptions.
-
-## Reading Learnings
-
-\`\`\`bash
-replicas learnings read --query "<enriched query>"
-\`\`\`
-
-**When to read:** once you've collected enough context to write a meaningful query \u2014 typically after your first look at the relevant code. Don't wait until you're deep into execution; learnings are most valuable before you commit to an approach.
-
-**Enrich the query.** Use codebase specifics (feature area, module/component names), not the raw user request. Triggers describe *situations*, so a query grounded in what the task actually touches matches far better.
-
-Example: the user asks "remove the PRs chart projections". After locating the chart you know it lives in the platform admin dashboard, so query:
-
-\`\`\`bash
-replicas learnings read --query "Remove the PRs chart in the platform admin dashboard"
-\`\`\`
-
-This matches a learning triggered on "UI/UX work on the admin panel" that the raw request would have missed.
-
-Output is a list of blocks \u2014 id, name, and content. Use the ids to propose updates or deletions.
-
-## Proposing changes
+Learnings are curated, human-approved knowledge entries your organization maintains: conventions, gotchas, environment facts, and process rules.
 
 All writes are proposals: a human reviews them in the dashboard, and nothing takes effect until approved.
 
-\`\`\`bash
-replicas learnings add --name "<short name>" --content "<the knowledge>" [--trigger "<when to surface it>"] [--always] [--global]
-replicas learnings update <id> [--name "..."] [--content "..."] [--trigger "..."] [--always true|false]
-replicas learnings delete <id>
-\`\`\`
-
-\`--always\` marks an entry as always-returned (no trigger needed); \`--global\` proposes org-wide scope instead of this workspace's environment.
+Use \`replicas learnings --help\` and subcommand help such as \`replicas learnings add --help\`, \`replicas learnings update --help\`, or \`replicas learnings delete --help\` for current command syntax.
 
 **Be very conservative:**
-- Propose \`add\` only for durable, org-useful facts: explicit user corrections, hard-won environment or process knowledge.
+- Propose \`add\` only for repeatable, org-useful facts likely to matter again: explicit user corrections, hard-won environment or process knowledge.
 - Never store task-specific details, anything derivable by reading the repo, or secrets/credentials.
-- Propose \`update\` or \`delete\` when a learning is contradicted by the current code or docs \u2014 flag outdated knowledge instead of silently ignoring it.
+- Propose \`update\` or \`delete\` when a learning is contradicted by the current code or docs, especially if the outdated guidance would affect future repeated work.
 - Write narrow triggers describing when the entry should surface (e.g. "UI/UX work on the admin panel"), not vague topics.`;
 var LEARNINGS_ABILITY = {
   label: "Learnings",
-  description: "Fetch curated org knowledge and propose new learnings for human review.",
-  bullet: "- Fetching organization Learnings (curated, human-approved knowledge) before executing, or proposing new ones",
+  description: "Propose changes to curated org knowledge for human review.",
+  bullet: "- Proposing changes to organization Learnings (curated, human-approved knowledge)",
   section: SECTION6,
   referenceFile: { name: "LEARNINGS.md", content: REFERENCE6 }
 };
@@ -8249,7 +8216,7 @@ var AspClient = class {
 // src/managers/codex-asp/app-server-process.ts
 var DEFAULT_CODEX_BINARY = "codex";
 var DEFAULT_CODEX_ARGS = ["app-server", "--listen", "stdio://"];
-var ENGINE_PACKAGE_VERSION = "0.1.413";
+var ENGINE_PACKAGE_VERSION = "0.1.414";
 var INITIALIZE_METHOD = "initialize";
 var INITIALIZED_NOTIFICATION = "initialized";
 var ACCOUNT_LOGIN_START_METHOD = "account/login/start";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replicas-engine",
-  "version": "0.1.413",
+  "version": "0.1.414",
   "description": "Lightweight API server for Replicas workspaces",
   "type": "module",
   "main": "dist/src/index.js",