@ziggs-ai/ziggs-mcp 0.7.2 → 0.7.4

package/dist/inboxToolResult.d.ts

@@ -29,7 +29,7 @@ export interface ReadPlanResult {
  * the caller already received, restated as runnable calls.
  *
  * Mapping honours how reads resolve server-side: messages read only via chat,
- * artifacts via chat or agreement.
+ * artifacts via the chat, agreement, or task they landed on.
  */
 export declare function buildReadPlan(inbox: InboxEnvelope, grantsByScope?: Map<string, ScopeGrantTag>): ReadPlanResult;
 /**

package/dist/inboxToolResult.js

@@ -23,7 +23,7 @@ function readContextCall(type, kind, id, grantId) {
  * the caller already received, restated as runnable calls.
  *
  * Mapping honours how reads resolve server-side: messages read only via chat,
- * artifacts via chat or agreement.
+ * artifacts via the chat, agreement, or task they landed on.
  */
 export function buildReadPlan(inbox, grantsByScope) {
     const proposals = inbox.proposalsAwaitingMe ?? [];
@@ -63,7 +63,13 @@ export function buildReadPlan(inbox, grantsByScope) {
     const grantFor = (kind, id) => grantsByScope?.get(`${kind}:${id}`)?.grantId;
     const read = (type, viaKind, viaId) => add(`read:${type}:${viaKind}:${viaId}`, readContextCall(type, viaKind, viaId, grantFor(viaKind, viaId)));
     // Reads — one call per place mail actually landed. The delivery names the
-    // chat or agreement directly, so nothing has to be inferred from a scope.
+    // chat, agreement or task directly, so nothing has to be inferred from a scope.
+    //
+    // The task arm is not optional: a deliverable recorded against a task alone is
+    // the shape the protocol asks for, and it lands in no chat and no agreement.
+    // While this only looked at chatId/agreementId, such a delivery produced an
+    // envelope whose plan was the ack and nothing else — an agent following the
+    // plan acked the deliverable without ever reading it.
     for (const d of deliveries) {
         if (d.kind === 'message' && d.chatId)
             read('messages', 'chat', d.chatId);
@@ -72,6 +78,8 @@ export function buildReadPlan(inbox, grantsByScope) {
                 read('artifacts', 'chat', d.chatId);
             else if (d.agreementId)
                 read('artifacts', 'agreement', d.agreementId);
+            else if (d.taskId)
+                read('artifacts', 'task', d.taskId);
         }
     }
     // ZIG-660: reserve a slot for the ack before capping, so the pre-filled ack

package/dist/tools.js

@@ -1,6 +1,6 @@
 import { randomUUID } from 'node:crypto';
 import { z } from 'zod';
-import { getAgreement, getMyAgreements, listMyChats, proposeUnified, delegateAgreement, provisionRelayWorkers, respondToAgreement, revokeAgreement, counterAgreement, fulfillAgreement, sendChatMessage, ConnectionsClient, PaymentsClient, ContextReadClient, GrantsClient, InboxClient, createTask, updateTaskState, replaceTaskPlan, listTasks, getTask, getBackendUrl, fetchMyOrgs, fetchDelegateAccess, GRANTS_CAPABILITIES, contextReadCapability, contextExpandReachCapability, contextDiscoverGrantableCapability, recordArtifactCapability, openConversationCapability, connectionProxyCapability, requestConnectionCapability, agreementClaimCapability, marketplaceViewCapability, linkSummary, } from '@ziggs-ai/api-client';
+import { getAgreement, getMyAgreements, listMyChats, proposeUnified, delegateAgreement, provisionRelayWorkers, respondToAgreement, revokeAgreement, counterAgreement, fulfillAgreement, sendChatMessage, ConnectionsClient, PaymentsClient, ContextReadClient, GrantsClient, InboxClient, createTask, updateTaskState, replaceTaskPlan, listTasks, getTask, getBackendUrl, fetchMyOrgs, fetchDelegateAccess, GRANTS_CAPABILITIES, CONTEXT_GRANT_SCOPE_KINDS, contextReadCapability, contextExpandReachCapability, contextDiscoverGrantableCapability, recordArtifactCapability, listArtifactsCapability, shareArtifactCapability, attachArtifactCapability, openConversationCapability, connectionProxyCapability, requestConnectionCapability, agreementClaimCapability, marketplaceViewCapability, linkSummary, } from '@ziggs-ai/api-client';
 import { decodeOperatorKeyClaims } from './operatorKey.js';
 import { registerTrustTools } from './trustTools.js';
 import { registerPaymentTools } from './paymentTools.js';
@@ -43,7 +43,13 @@ const ZIGGS_SEND_MESSAGE_DESCRIPTION = 'Send a chat message as the delegate agen
 // result slot on the artifact_record description and success path so an agent
 // finds the right move unaided. Reporting rule sourced from the shared const
 // (ZIG-557).
-const ZIGGS_RECORD_ARTIFACT_DESCRIPTION = 'Write an artifact to a chat or agreement scope. Set visibility explicitly. ' +
+// ZIG-1037: scope is optional. Say so first — the old wording ("write to a chat
+// or agreement scope") is what pushed a model into guessing a container, and
+// guessing wrong used to fail the write outright.
+const ZIGGS_RECORD_ARTIFACT_DESCRIPTION = 'Write an artifact. Scope is optional — pass agreementId or chatId to record it into that ' +
+    'scope, pass taskId alone to bind a deliverable to its task, or pass no scope at all for a ' +
+    'free-standing artifact that is yours until you attach or share it. Never guess a scope: ' +
+    'recording with none always succeeds. Set visibility explicitly. ' +
     'For a finished deliverable, set content_type=result and pass taskId to bind it to the task. ' +
     PROTOCOL.reporting;
 // ZIG-899 — the strict artifact write (fail loudly, return the artifactId)
@@ -633,7 +639,9 @@ export function registerZiggsTools(server, creds, cfg) {
             let reach = [];
             try {
                 reach = await new GrantsClient(creds.operatorKey, creds.agentId).listAllGrants({
-                    scopeKind: ['chat', 'agreement', 'org'],
+                    // Every context scope kind — a literal subset here is how the CLI
+                    // silently dropped a whole kind when `artifact` was added.
+                    scopeKind: [...CONTEXT_GRANT_SCOPE_KINDS],
                     health: 'active',
                 });
             }
@@ -664,6 +672,12 @@ export function registerZiggsTools(server, creds, cfg) {
     registerCapability(server, recordArtifactCapability, creds, {
         description: ZIGGS_RECORD_ARTIFACT_DESCRIPTION,
     });
+    // ZIG-1037 — find what you recorded free-standing, and hand one artifact to one
+    // agent. Descriptions come from the shared capability (no PROTOCOL override
+    // needed; neither is a reporting surface).
+    registerCapability(server, listArtifactsCapability, creds);
+    registerCapability(server, shareArtifactCapability, creds);
+    registerCapability(server, attachArtifactCapability, creds);
     // ---------------------------------------------------------------------------
     // Task mutation tools (ZIG-555)
     // ---------------------------------------------------------------------------

package/dist/trustTools.js

@@ -3,7 +3,9 @@ import { ContextGrantsClient, addChatMember, contextBounds, resolveOrgScopeId, L
 import { WRITE, DESTRUCTIVE } from './toolAnnotations.js';
 import { toolError } from './toolError.js';
 import { registerCapabilities, registerCapability, textResult } from './capabilityAdapter.js';
-const grantScopeKindSchema = z.enum(['chat', 'agreement', 'org']);
+// ZIG-1037: `artifact` is the narrowest context scope — one specific artifact,
+// shared without sharing any container it sits in.
+const grantScopeKindSchema = z.enum(['chat', 'agreement', 'org', 'artifact']);
 const contextTemporalSchema = z.enum(['from-now', 'from-start']);
 const DEFAULT_WEB_URL = 'https://ziggsai.com';
 /** ZIG-433 / ZIG-956 — agent search + context grant management through MCP.
@@ -13,20 +15,27 @@ const DEFAULT_WEB_URL = 'https://ziggsai.com';
 export function registerTrustTools(server, creds, cfg) {
     const webUrl = cfg?.ZIGGS_WEB_URL?.replace(/\/$/, '') ?? DEFAULT_WEB_URL;
     registerCapabilities(server, DISCOVERY_CAPABILITIES, creds);
-    server.tool('ziggs_context_issue_grant', 'Issue bounded context access. Chat scope: admits agent via POST /chats/:id/members (agent-invite → pending_approval until humans consent) — this works for you as a delegate. Agreement/org scope: issuing a NEW root grant is a human-authority action; if you are acting for a principal you are denied (AGENT_LACKS_HUMAN_AUTHORITY) — instead use ziggs_context_delegate to hand a peer a narrower slice of a grant you already hold, or ask your human to issue it. Defaults: from-now, narrow scope.', {
+    server.tool('ziggs_context_issue_grant', 'Issue bounded context access. Chat scope: admits agent via POST /chats/:id/members (agent-invite → pending_approval until humans consent) — this works for you as a delegate. Agreement/org scope: issuing a NEW root grant is a human-authority action; if you are acting for a principal you are denied (AGENT_LACKS_HUMAN_AUTHORITY) — instead use ziggs_context_delegate to hand a peer a narrower slice of a grant you already hold, or ask your human to issue it. Artifact scope: hands over one specific artifact and nothing else; it is always from-start (the artifact already exists), and if YOU authored it use ziggs_artifact_share instead — that needs no human authority. Defaults: from-now, narrow scope.', {
         holderId: z.string().describe('Bare agent id receiving the grant'),
         scopeKind: grantScopeKindSchema,
-        scopeId: z.string().describe('chatId, agreementId, or orgId'),
+        scopeId: z.string().describe('chatId, agreementId, orgId, or artifactId'),
         temporal: contextTemporalSchema
             .optional()
-            .describe('from-now (default) or from-start (approval-gated on chat)'),
+            .describe('from-now (default) or from-start (approval-gated on chat). Artifact ' +
+            'scope defaults to from-start and rejects from-now.'),
         expiresAt: z
             .string()
             .optional()
             .nullable()
             .describe('ISO-8601 expiry; omit for platform default TTL'),
     }, WRITE, async ({ holderId, scopeKind, scopeId, temporal, expiresAt }) => {
-        const resolvedTemporal = temporal ?? 'from-now';
+        // An artifact predates any watermark you could set, so from-now would
+        // validate and then read empty — the server refuses it outright. Defaulting
+        // artifact scope to from-now here made the tool's own default invocation
+        // fail, while the description promised it was always from-start. An
+        // EXPLICIT from-now still goes through and is refused loudly: silently
+        // rewriting what the caller asked for would hide the mistake.
+        const resolvedTemporal = temporal ?? (scopeKind === 'artifact' ? 'from-start' : 'from-now');
         try {
             if (scopeKind === 'chat') {
                 const result = await addChatMember({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ziggs-ai/ziggs-mcp",
-  "version": "0.7.2",
+  "version": "0.7.4",
   "description": "MCP server for Claude Code, Cursor, and other MCP hosts \u2014 act as your Ziggs delegate agent",
   "type": "module",
   "bin": {