replicas-engine 0.1.627 → 0.1.628

package/dist/src/index.js

@@ -1586,35 +1586,8 @@ var GITLAB_ABILITY = {
   referenceFile: { name: "GITLAB.md", content: REFERENCE4 }
 };
 
-// ../shared/src/default-skills/replicas-agent/abilities/learnings.ts
-var SECTION5 = `### Learnings
-Propose additions, updates, or deletions to curated organization knowledge.
-
-**Reference:** \`references/LEARNINGS.md\``;
-var REFERENCE5 = `# Learnings
-
-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.
-
-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.
-
-A human approves every proposal before it takes effect, so don't agonize over borderline calls \u2014 but keep proposals genuinely useful rather than reflexive.
-
-- Propose \`add\` for anything repeatable and org-useful: user corrections and preferences, hard-won environment or process knowledge, conventions and decisions worth following, and gotchas that would waste time again. If you learned it the hard way this task, capture it.
-- Never store task-specific details that won't recur, facts trivially derivable by reading the repo, or secrets/credentials.
-- 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: "Propose changes to curated org knowledge for human review.",
-  bullet: "- Proposing changes to organization Learnings (curated, human-approved knowledge)",
-  section: SECTION5,
-  referenceFile: { name: "LEARNINGS.md", content: REFERENCE5 }
-};
-
 // ../shared/src/default-skills/replicas-agent/abilities/linear.ts
-var SECTION6 = `### Linear
+var SECTION5 = `### Linear
 Fetch issues, update state, add comments, and search through the workspace-scoped TypeScript SDK.
 
 **Reference:** \`references/LINEAR.md\`
@@ -1623,7 +1596,7 @@ Use this when:
 - You encounter a Linear issue link and need to understand the task
 - You need to update an issue's state or add a comment
 - You need to search Linear issues`;
-var REFERENCE6 = `# Linear Integration
+var REFERENCE5 = `# Linear Integration
 
 Use \`@replicas/sdk\`; never request or handle a Linear OAuth token. Replicas refreshes the organization credential behind the gateway.
 
@@ -1673,12 +1646,12 @@ var LINEAR_ABILITY = {
   label: "Linear",
   description: "Fetch issues, comment, and update state through @replicas/sdk.",
   bullet: "- Interacting with Linear (fetching issues, updating state, commenting, etc.)",
-  section: SECTION6,
-  referenceFile: { name: "LINEAR.md", content: REFERENCE6 }
+  section: SECTION5,
+  referenceFile: { name: "LINEAR.md", content: REFERENCE5 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/media.ts
-var SECTION7 = `### Media
+var SECTION6 = `### Media
 Share screenshots, screen recordings, generated diagrams, audio clips, and self-contained HTML pages through Replicas and external messages.
 
 **Reference:** \`references/MEDIA.md\`
@@ -1688,7 +1661,7 @@ Use this when:
 - You produce a self-contained HTML report that should be linked from a pull request
 - You record video output (browser automation, screen capture) \u2014 including the recommended aspect ratio and FPS
 - You need to embed media in a Slack/Linear/GitHub message AND keep a referenceable copy in the Replicas dashboard`;
-var REFERENCE7 = `# Media (Screenshots, Recordings, Audio, HTML)
+var REFERENCE6 = `# Media (Screenshots, Recordings, Audio, HTML)
 
 This guide covers how to share screenshots, screen recordings, generated diagrams, audio clips, and self-contained HTML pages through Replicas and external surfaces (Slack, Linear, GitHub).
 
@@ -1994,12 +1967,12 @@ var MEDIA_ABILITY = {
   label: "Media",
   description: "Share screenshots, recordings, generated images, audio clips, and HTML pages.",
   bullet: "- Producing or showing the user any media \u2014 screenshots, screen recordings, generated images or diagrams, audio clips, or HTML recap pages \u2014 including in your Replicas chat reply, PR descriptions/comments, and other external platforms",
-  section: SECTION7,
-  referenceFile: { name: "MEDIA.md", content: REFERENCE7 }
+  section: SECTION6,
+  referenceFile: { name: "MEDIA.md", content: REFERENCE6 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/previews.ts
-var SECTION8 = `### Previews
+var SECTION7 = `### Previews
 Expose locally running services (web apps, APIs, databases) as public preview URLs so humans can interact with them directly.
 
 **Reference:** \`references/PREVIEWS.md\`
@@ -2008,7 +1981,7 @@ Use this when:
 - You need to start a service that a human should view or interact with
 - The task involves UI work that benefits from human review
 - You are verifying frontend/backend integrations visually`;
-var REFERENCE8 = `# Preview URLs
+var REFERENCE7 = `# Preview URLs
 
 When you run services on ports \u2014 such as a web app, API server, or database \u2014 humans may want to interact with them directly. You can expose your locally running services as public preview URLs.
 
@@ -2084,12 +2057,12 @@ var PREVIEWS_ABILITY = {
   label: "Previews",
   description: "Expose locally running services on public preview URLs for humans.",
   bullet: "- Creating preview URLs for locally running services",
-  section: SECTION8,
-  referenceFile: { name: "PREVIEWS.md", content: REFERENCE8 }
+  section: SECTION7,
+  referenceFile: { name: "PREVIEWS.md", content: REFERENCE7 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/plugins.ts
-var SECTION9 = `### Plugins
+var SECTION8 = `### Plugins
 Discover and execute installed marketplace tools through the workspace-scoped TypeScript SDK.
 
 **Reference:** \`references/PLUGINS.md\`
@@ -2104,7 +2077,7 @@ Use this when:
 - The user asks for PlanetScale organizations, databases, branches, or Insights data
 - The user asks to analyze text with Pangram
 - The user asks for Stripe customers, payments, invoices, subscriptions, or balances`;
-var REFERENCE9 = `# Plugins
+var REFERENCE8 = `# Plugins
 
 Plugins are TypeScript libraries, not MCP servers. Import \`@replicas/sdk\`; Replicas authenticates the workspace and selects only the owner\u2019s personal connection or the organization fallback. Provider credentials, sessions, and project keys are never exposed.
 
@@ -2212,12 +2185,12 @@ var PLUGINS_ABILITY = {
   label: "Plugins",
   description: "Use installed marketplace tools through @replicas/sdk.",
   bullet: "- Interacting with installed marketplace plugins through TypeScript",
-  section: SECTION9,
-  referenceFile: { name: "PLUGINS.md", content: REFERENCE9 }
+  section: SECTION8,
+  referenceFile: { name: "PLUGINS.md", content: REFERENCE8 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/replicas.ts
-var SECTION10 = `### Replicas (in-workspace CLI)
+var SECTION9 = `### Replicas (in-workspace CLI)
 Take action *with* Replicas itself \u2014 manage automations, environments (variables, files), repos, and \`replicas.json\` config \u2014 using the pre-installed, pre-authenticated \`replicas\` CLI.
 
 **Reference:** \`references/REPLICAS.md\`
@@ -2228,7 +2201,7 @@ Use this when:
 - The user asks "what envs / repos / automations do I have?"
 - The user asks you to scaffold a \`replicas.json\` / \`replicas.yaml\` in a repo
 - You need to run a long-lived service (dev server, daemon) \u2014 always use \`replicas service start\` so it survives workspace sleep/wake`;
-var REFERENCE10 = `# Replicas (in-workspace CLI)
+var REFERENCE9 = `# Replicas (in-workspace CLI)
 
 This guide covers how to take action *with* Replicas itself from inside a Replicas workspace \u2014 managing automations, environments (and their variables/files), repos, previews, and the user's \`replicas.json\` config \u2014 using the pre-installed \`replicas\` CLI.
 
@@ -2455,13 +2428,13 @@ var REPLICAS_ABILITY = {
   description: "Teach the agent about Replicas itself \u2014 automations, environments, the in-workspace CLI.",
   // No bullet — help_instructions covers the `replicas` CLI surface in detail.
   bullet: "",
-  section: SECTION10,
-  referenceFile: { name: "REPLICAS.md", content: REFERENCE10 },
+  section: SECTION9,
+  referenceFile: { name: "REPLICAS.md", content: REFERENCE9 },
   locked: true
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/sentry.ts
-var SECTION11 = `### Sentry
+var SECTION10 = `### Sentry
 Read issues and project data through the workspace-scoped TypeScript SDK.
 
 **Reference:** \`references/SENTRY.md\`
@@ -2469,7 +2442,7 @@ Read issues and project data through the workspace-scoped TypeScript SDK.
 Use this when:
 - You need to inspect Sentry projects or issues
 - A user asks for error-monitoring context outside a webhook-triggered task`;
-var REFERENCE11 = `# Sentry Integration
+var REFERENCE10 = `# Sentry Integration
 
 Use \`@replicas/sdk\`; never request or read a Sentry token. Sentry access is organization-scoped and read-only.
 
@@ -2488,12 +2461,12 @@ var SENTRY_ABILITY = {
   label: "Sentry",
   description: "Read Sentry projects and issues through @replicas/sdk.",
   bullet: "- Interacting with Sentry (reading projects, issues, and error context)",
-  section: SECTION11,
-  referenceFile: { name: "SENTRY.md", content: REFERENCE11 }
+  section: SECTION10,
+  referenceFile: { name: "SENTRY.md", content: REFERENCE10 }
 };
 
 // ../shared/src/default-skills/replicas-agent/abilities/slack.ts
-var SECTION12 = `### Slack
+var SECTION11 = `### Slack
 Send messages, read threads, search conversations, and upload files through the workspace-scoped TypeScript SDK.
 
 **Reference:** \`references/SLACK.md\`
@@ -2502,7 +2475,7 @@ Use this when:
 - You need to send a message to a Slack channel or thread
 - You need to read or search Slack conversations
 - You encounter a Slack message link and need its full thread`;
-var REFERENCE12 = `# Slack Integration
+var REFERENCE11 = `# Slack Integration
 
 Use \`@replicas/sdk\`; never read or send a Slack token directly. The SDK calls Replicas, which selects only this workspace's organization connection.
 
@@ -2575,8 +2548,8 @@ var SLACK_ABILITY = {
   label: "Slack",
   description: "Send messages, read threads, and search through @replicas/sdk.",
   bullet: "- Interacting with Slack (sending messages, reading threads, etc.)",
-  section: SECTION12,
-  referenceFile: { name: "SLACK.md", content: REFERENCE12 }
+  section: SECTION11,
+  referenceFile: { name: "SLACK.md", content: REFERENCE11 }
 };
 
 // ../shared/src/default-skills/replicas-agent/registry.ts
@@ -2586,7 +2559,6 @@ var REPLICAS_AGENT_ABILITY_REGISTRY = {
   docker: DOCKER_ABILITY,
   github: GITHUB_ABILITY,
   gitlab: GITLAB_ABILITY,
-  learnings: LEARNINGS_ABILITY,
   linear: LINEAR_ABILITY,
   media: MEDIA_ABILITY,
   plugins: PLUGINS_ABILITY,
@@ -3315,7 +3287,8 @@ var workspaceChangedEventSchema = z2.discriminatedUnion("type", [
     workspaceId: z2.string(),
     completion: z2.object({
       workspaceName: z2.string(),
-      completedAt: z2.string()
+      completedAt: z2.string(),
+      processing: z2.boolean().optional()
     }).optional(),
     ts: z2.string()
   }),
@@ -11029,7 +11002,7 @@ var DEFAULT_CODEX_ARGS = [
 var MIN_CODEX_CLI_VERSION = "0.144.6";
 var CODEX_UPGRADE_TIMEOUT_MS = 12e4;
 var codexCliVersionEnsured = null;
-var ENGINE_PACKAGE_VERSION = "0.1.627";
+var ENGINE_PACKAGE_VERSION = "0.1.628";
 var INITIALIZE_METHOD = "initialize";
 var INITIALIZED_NOTIFICATION = "initialized";
 var ACCOUNT_LOGIN_START_METHOD = "account/login/start";
@@ -17092,17 +17065,18 @@ var ChatService = class {
     chat.activeMessageId = null;
     this.agentChatActivityTrackerService.noteTurnEnded(chatId);
     const completedAt = (/* @__PURE__ */ new Date()).toISOString();
+    const processing = chat.provider.getQueue().length > 0;
     this.publish({
       type: "chat.turn.completed",
       payload: {
         chatId,
         isComplete: true,
-        processing: false,
+        processing,
         completedAt
       }
     }).catch(() => {
     });
-    monolithService.sendEvent({ type: "agent_response_complete", payload: { completedAt } }).catch(() => {
+    monolithService.sendEvent({ type: "agent_response_complete", payload: { completedAt, processing } }).catch(() => {
     });
     uploadChatTranscript(
       chatId,
@@ -17114,7 +17088,7 @@ var ChatService = class {
     flushAllCanvasItems().catch((err) => {
       console.error("[ChatService] Failed to upload canvas items:", { chatId, err });
     });
-    await this.publishAgentTurnCompleteWebhook(chat, completedAt);
+    await this.publishAgentTurnCompleteWebhook(chat, completedAt, processing);
   }
   getRuntimeChat(chatId) {
     const chat = this.chats.get(chatId) ?? null;
@@ -17196,7 +17170,7 @@ var ChatService = class {
     } catch {
     }
   }
-  async publishAgentTurnCompleteWebhook(chat, completedAt) {
+  async publishAgentTurnCompleteWebhook(chat, completedAt, processing = false) {
     await Promise.all([
       githubTokenManager.refreshOnce().catch(() => {
       }),
@@ -17229,6 +17203,7 @@ var ChatService = class {
       const payload = {
         ...linearSessionId ? { linearSessionId } : {},
         ...completedAt ? { completedAt } : {},
+        processing,
         repoStatuses,
         ...errors?.length ? { errors } : {},
         ...errors?.length && errorNotificationTarget ? { errorNotificationTarget } : {}

package/package.json

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