@segmentstream/agent 0.11.0 → 0.12.1

package/README.md

@@ -451,7 +451,7 @@ To reach a local ontology service, set `SEGMENTSTREAM_AGENT_ONTOLOGY_URL=http://
 production tokens of the workspace's project, though, so a local run gets the ontology only from a
 local ontology service configured to accept that token.
 
-Building the package needs Node.js 24, as eve does: `npm run build` runs `eve extension build`,
+Building the package needs Node.js 24, as eve does: `pnpm run build` runs `eve extension build`,
 which writes the agent-shaped `dist/extension` tree, its declarations and eve's compatibility
 manifest.
 

package/dist/_chunks/{build-metadata-F_kHphOG.mjs → build-metadata-Dl-ZJp5p.mjs}

@@ -4,7 +4,7 @@ import { createRequire as __eveCreateRequire } from "node:module";
 const __filename = __eveFileURLToPath(import.meta.url);
 __eveDirname(__filename);
 __eveCreateRequire(import.meta.url);
-var version = "0.11.0";
+var version = "0.12.1";
 function agentBuild(environment = process.env) {
 	return {
 		agent: version,

package/dist/extension/instructions.md

@@ -19,6 +19,16 @@ talking to you, and you act with exactly their permissions.
   reload definitions already known for the current ontology hash. Metadata visibility does
   not grant record access. The operation tools are narrowed to the member's current permissions;
   if an operation is missing, say so instead of looking for a way around.
+- When the ontology offers `app_feedback_submit`, the app accepts feedback for its builders.
+  Offer to send it when the member wants something no permitted tool, field or data provides, an
+  operation is refused for lack of permission, an operation fails unexpectedly or a retryable
+  failure persists, or the member says something works badly or asks for something new. Do not
+  offer what you can do yourself; offer once per problem. Before submitting, look for the member's
+  open `app_feedback` with the same subject. Submit only after the member agrees to the title and
+  summary you show in their language, then add each screenshot or file they sent with
+  `app_feedback_file_attach`, promoting a chat attachment into it. When a member starts talking to
+  you, find their `app_feedback` with `responded_at` set and `seen_at` empty, tell them the
+  builders' response, then call `app_feedback_acknowledge` with its `responded_at`.
   Older ontologies without `discover` return the legacy full catalog from `describe`; use that
   available contract. New description results carry `kind` and `hash`.
 - When the current member has permission and gives a clear instruction, act, including necessary

package/dist/extension/lib/build-metadata.mjs

@@ -4,5 +4,5 @@ import { createRequire as __eveCreateRequire } from "node:module";
 const __filename = __eveFileURLToPath(import.meta.url);
 __eveDirname(__filename);
 __eveCreateRequire(import.meta.url);
-import { t as agentBuild } from "../../_chunks/build-metadata-F_kHphOG.mjs";
+import { t as agentBuild } from "../../_chunks/build-metadata-Dl-ZJp5p.mjs";
 export { agentBuild };

package/dist/extension/lib/telegram/adapter.mjs

@@ -13,7 +13,7 @@ import { decisionRouter } from "../group-routing/router.mjs";
 import { runtimeToken } from "../runtime-token.mjs";
 import { conversations } from "../conversations.mjs";
 import { archivedRoutingMessages } from "../group-routing/routing-context.mjs";
-import { t as agentBuild } from "../../../_chunks/build-metadata-F_kHphOG.mjs";
+import { t as agentBuild } from "../../../_chunks/build-metadata-Dl-ZJp5p.mjs";
 import { confirmationLocale } from "./confirmation-text.mjs";
 import { telegramSendScope } from "./send-queue.mjs";
 import { d as failureText, h as withDeliveryLocale, i as withReplacedText, m as safeTelegramFetch, n as currentInboundRequest, p as reportTelegramError, r as runInboundRequest, t as InboundRequest } from "../../../_chunks/inbound-request-BrWspFw5.mjs";

package/dist/extension/lib/telegram/health.mjs

@@ -4,7 +4,7 @@ import { createRequire as __eveCreateRequire } from "node:module";
 const __filename = __eveFileURLToPath(import.meta.url);
 __eveDirname(__filename);
 __eveCreateRequire(import.meta.url);
-import { t as agentBuild } from "../../../_chunks/build-metadata-F_kHphOG.mjs";
+import { t as agentBuild } from "../../../_chunks/build-metadata-Dl-ZJp5p.mjs";
 import { runtimeRequestFailure } from "./runtime-request.mjs";
 import { GET } from "eve/channels";
 const HEALTH_ROUTE = "/eve/v1/telegram/health";

package/dist/extension/lib/telegram/lifecycle.mjs

@@ -4,7 +4,7 @@ import { createRequire as __eveCreateRequire } from "node:module";
 const __filename = __eveFileURLToPath(import.meta.url);
 __eveDirname(__filename);
 __eveCreateRequire(import.meta.url);
-import { t as agentBuild } from "../../../_chunks/build-metadata-F_kHphOG.mjs";
+import { t as agentBuild } from "../../../_chunks/build-metadata-Dl-ZJp5p.mjs";
 import { object } from "../confirmation-description.mjs";
 import { n as currentInboundRequest, p as reportTelegramError } from "../../../_chunks/inbound-request-BrWspFw5.mjs";
 import { needsConfirmation } from "../confirmations.mjs";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@segmentstream/agent",
-  "version": "0.11.0",
+  "version": "0.12.1",
   "description": "Mount a SegmentStream workspace's agent on eve: the ontology as tools, acting as the member who writes, and Telegram through the workspace's connection.",
   "license": "Apache-2.0",
   "author": "SegmentStream",
@@ -57,12 +57,12 @@
     "typecheck": "tsc -p tsconfig.json --noEmit",
     "lint": "eslint src tests --config ../../eslint.config.mjs",
     "test": "vitest run",
-    "prepack": "npm run build",
+    "prepack": "pnpm run build",
     "eval:routing": "tsx tests/routing-eval/cli.ts"
   },
   "dependencies": {
     "@chat-adapter/telegram": "4.41.0",
-    "@segmentstream-cloud/ontology": "0.47.0",
+    "@segmentstream-cloud/ontology": "0.48.1",
     "@vercel/oidc": "^3.8.4",
     "ai": "^7.0.128",
     "csv-parse": "^7.0.3",