@ziggs-ai/ziggs-mcp 0.10.3 → 0.10.4

package/README.md

@@ -63,7 +63,25 @@ This package ships [`server.json`](./server.json) for [registry.modelcontextprot
 
 ### ChatGPT
 
-**Not supported** — see [`examples/chatgpt-unsupported.md`](examples/chatgpt-unsupported.md). Use claude.ai, Claude Code, or Cursor.
+**Works.** Developer-mode connector against the same remote URL, OAuth consent, no key to paste. Setup guide: [`examples/chatgpt-remote-oauth.md`](examples/chatgpt-remote-oauth.md). Verified 2026-08-13.
+
+---
+
+## Which clients work
+
+Ziggs is not built against any one assistant. Any MCP client that can do **remote OAuth** against `https://mcp.ziggsai.com/mcp`, or run the package over **stdio** with an agent-scoped operator key, works.
+
+The list below is the clients someone has taken through a connect end to end. A client that is absent is not a client that fails: it is one nobody has walked through yet.
+
+| Client | Path | Verified |
+|--------|------|----------|
+| claude.ai | remote OAuth | yes |
+| Claude Code | remote OAuth, and stdio for headless/CI | yes |
+| Cursor | remote OAuth, and stdio | yes |
+| ChatGPT | remote OAuth (developer-mode connector) | yes, 2026-08-13 |
+| Gemini | remote OAuth expected | **not verified** — no walkthrough yet |
+
+Gemini is deliberately listed without a walkthrough. The platform already labels a Gemini delegate, so nothing is known to block it, but nobody has connected one end to end and an untested walkthrough is worse than none.
 
 ---
 

package/dist/inboxToolResult.js

@@ -145,7 +145,7 @@ export function buildReadPlan(inbox, grantsByScope, self = { agentId: '' }) {
     // never gets squeezed out exactly when there's the most news. Report how many
     // read/decision candidates the cap dropped as an explicit count.
     //
-    // ZIG-1305 — only pre-fill ack when this plan covers the whole envelope.
+    // Only pre-fill ack when this plan covers the whole envelope.
     // A truncated plan (or a capped delivery list) must not hand back an ack
     // that would clear deliveries the plan never asked the agent to handle.
     // Reserve the ack slot only when every candidate still fits beside it;

package/dist/mcpConnectionTools.d.ts

@@ -1,5 +1,5 @@
 /**
- * ZIG-1362 — call a brokered MCP connection from the ziggs-mcp surface.
+ * Call a brokered MCP connection from the ziggs-mcp surface.
  *
  * Same door the SDK's `mcp_tool_call` / `mcp_tools_list` use
  * (`POST /connections/:id/mcp`). `ziggs_connection_proxy` cannot: it resolves

package/dist/mcpConnectionTools.js

@@ -1,5 +1,5 @@
 /**
- * ZIG-1362 — call a brokered MCP connection from the ziggs-mcp surface.
+ * Call a brokered MCP connection from the ziggs-mcp surface.
  *
  * Same door the SDK's `mcp_tool_call` / `mcp_tools_list` use
  * (`POST /connections/:id/mcp`). `ziggs_connection_proxy` cannot: it resolves

package/dist/protocol/delegateProtocol.d.ts

@@ -2,23 +2,28 @@
  * Single source of truth for the Ziggs delegate protocol prose.
  *
  * The protocol (inbox → read → act → ack, the reporting rule, humanAttention
- * handling, the untrusted-input hard rule) used to be hand-copied across the
- * `ziggs_inbox` tool description, SKILL.md, the skill references, and — once
- * A1/D1 land — the server `instructions` and `.cursorrules`. They drifted.
+ * handling, the untrusted-input hard rule) is stated once here and rendered
+ * into every surface that carries it: the `ziggs_inbox` tool description, the
+ * server `instructions`, SKILL.md, the skill references and `.cursorrules`.
+ * Hand-copied across those, it drifted.
  *
- * Edit the fragments here, then run `npm run gen:protocol` to regenerate the
- * static surfaces (SKILL.md + references managed blocks, `.cursorrules`).
- * Runtime surfaces (the `ziggs_inbox` description, the server `instructions`)
- * import these fragments directly, so they cannot drift. `npm run
- * check:protocol` and the protocol-drift test fail if a static surface is stale.
+ * Static surfaces are generated from these fragments; runtime surfaces import
+ * them directly, so neither can drift. A drift check fails the build when a
+ * generated surface is stale.
  */
 /** Canonical protocol fragments — reuse these verbatim, never re-type them. */
 export declare const PROTOCOL: {
     readonly tagline: "You are a delegate agent on a Ziggs team. The MCP tools are the connection; operate by this protocol.";
     /** The working loop, as the `ziggs_inbox` description phrases it. */
     readonly loop: "Flow: inbox → read → act → ack.";
-    /** Watermark discipline — reading is side-effect-free; ack is explicit. */
-    readonly ack: "Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window — an ack that would bury unlisted deliveries is refused.";
+    /**
+     * Watermark discipline — reading is side-effect-free; ack is explicit.
+     *
+     * States the norm only. The refusal names the ids it is missing and the call
+     * to make with them, so it teaches at the moment it matters; pre-empting it
+     * here would cost context on every other turn.
+     */
+    readonly ack: "Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window.";
     readonly neverRewind: "Never rewind an ack to an older timestamp.";
     /** Tasks are the unit of work. */
     readonly task: "Work is a task under an agreement (the ticket). Read it from the inbox — or, if handed a bare taskId, open it with ziggs_task_get — then post progress as plan steps with ziggs_task_replace_plan.";
@@ -41,16 +46,16 @@ export declare const PROTOCOL: {
  */
 export declare const PROTOCOL_RULES: readonly string[];
 /** HTML-comment markers delimiting the generated region in a markdown file. */
-export declare const PROTOCOL_BLOCK_BEGIN = "<!-- BEGIN GENERATED: delegate-protocol \u2014 edit src/protocol/delegateProtocol.ts, run `npm run gen:protocol` -->";
+export declare const PROTOCOL_BLOCK_BEGIN = "<!-- BEGIN GENERATED: delegate-protocol \u2014 generated file, do not edit by hand -->";
 export declare const PROTOCOL_BLOCK_END = "<!-- END GENERATED: delegate-protocol -->";
 /**
- * Server `instructions` string (/A1 consumes this). Plain text so any
- * cold-connected host injects a usable protocol into model context on connect.
+ * Server `instructions` string. Plain text so any cold-connected host injects a
+ * usable protocol into model context on connect.
  */
 export declare function renderInstructions(): string;
 /** The managed markdown block injected into SKILL.md and references. */
 export declare function renderProtocolBlock(): string;
-/** `.cursorrules` body (/D1 ships placement; generated from here). */
+/** `.cursorrules` body, generated from the fragments above. */
 export declare function renderCursorRules(): string;
 /**
  * Replace the managed block in a markdown document. Throws if the markers are

package/dist/protocol/delegateProtocol.js

@@ -2,23 +2,28 @@
  * Single source of truth for the Ziggs delegate protocol prose.
  *
  * The protocol (inbox → read → act → ack, the reporting rule, humanAttention
- * handling, the untrusted-input hard rule) used to be hand-copied across the
- * `ziggs_inbox` tool description, SKILL.md, the skill references, and — once
- * A1/D1 land — the server `instructions` and `.cursorrules`. They drifted.
+ * handling, the untrusted-input hard rule) is stated once here and rendered
+ * into every surface that carries it: the `ziggs_inbox` tool description, the
+ * server `instructions`, SKILL.md, the skill references and `.cursorrules`.
+ * Hand-copied across those, it drifted.
  *
- * Edit the fragments here, then run `npm run gen:protocol` to regenerate the
- * static surfaces (SKILL.md + references managed blocks, `.cursorrules`).
- * Runtime surfaces (the `ziggs_inbox` description, the server `instructions`)
- * import these fragments directly, so they cannot drift. `npm run
- * check:protocol` and the protocol-drift test fail if a static surface is stale.
+ * Static surfaces are generated from these fragments; runtime surfaces import
+ * them directly, so neither can drift. A drift check fails the build when a
+ * generated surface is stale.
  */
 /** Canonical protocol fragments — reuse these verbatim, never re-type them. */
 export const PROTOCOL = {
     tagline: 'You are a delegate agent on a Ziggs team. The MCP tools are the connection; operate by this protocol.',
     /** The working loop, as the `ziggs_inbox` description phrases it. */
     loop: 'Flow: inbox → read → act → ack.',
-    /** Watermark discipline — reading is side-effect-free; ack is explicit. */
-    ack: 'Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window — an ack that would bury unlisted deliveries is refused.',
+    /**
+     * Watermark discipline — reading is side-effect-free; ack is explicit.
+     *
+     * States the norm only. The refusal names the ids it is missing and the call
+     * to make with them, so it teaches at the moment it matters; pre-empting it
+     * here would cost context on every other turn.
+     */
+    ack: 'Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window.',
     neverRewind: 'Never rewind an ack to an older timestamp.',
     /** Tasks are the unit of work. */
     task: 'Work is a task under an agreement (the ticket). Read it from the inbox — or, if handed a bare taskId, open it with ziggs_task_get — then post progress as plan steps with ziggs_task_replace_plan.',
@@ -51,11 +56,11 @@ export const PROTOCOL_RULES = [
     PROTOCOL.untrusted,
 ];
 /** HTML-comment markers delimiting the generated region in a markdown file. */
-export const PROTOCOL_BLOCK_BEGIN = '<!-- BEGIN GENERATED: delegate-protocol — edit src/protocol/delegateProtocol.ts, run `npm run gen:protocol` -->';
+export const PROTOCOL_BLOCK_BEGIN = '<!-- BEGIN GENERATED: delegate-protocol — generated file, do not edit by hand -->';
 export const PROTOCOL_BLOCK_END = '<!-- END GENERATED: delegate-protocol -->';
 /**
- * Server `instructions` string (/A1 consumes this). Plain text so any
- * cold-connected host injects a usable protocol into model context on connect.
+ * Server `instructions` string. Plain text so any cold-connected host injects a
+ * usable protocol into model context on connect.
  */
 export function renderInstructions() {
     return [PROTOCOL.tagline, '', ...PROTOCOL_RULES.map((r) => `- ${r}`)].join('\n');
@@ -70,11 +75,11 @@ export function renderProtocolBlock() {
         PROTOCOL_BLOCK_END,
     ].join('\n');
 }
-/** `.cursorrules` body (/D1 ships placement; generated from here). */
+/** `.cursorrules` body, generated from the fragments above. */
 export function renderCursorRules() {
     return [
         '# Ziggs delegate protocol (generated)',
-        '# Source: ziggs-mcp/src/protocol/delegateProtocol.ts — run `npm run gen:protocol` to update.',
+        '# Generated file — do not edit by hand.',
         '',
         PROTOCOL.tagline,
         '',

package/dist/tools.js

@@ -203,7 +203,7 @@ function registerConnectionTools(server, creds) {
             return toolError(e);
         }
     });
-    // ZIG-1362 — brokered MCP connections (provider: mcp). Not connection_proxy.
+    // Brokered MCP connections (provider: mcp). Not connection_proxy.
     registerStrictTool(server, 'ziggs_mcp_tools_list', "List the tools a connected MCP server exposes, through the Ziggs gateway — the owner's credential stays server-side. " +
         'The grant may allow only some of them; a call outside the grant is refused by the gateway. ' +
         'Omit connectionId/grantId when you hold a grant on exactly one connection.', {
@@ -721,6 +721,11 @@ export function registerZiggsTools(server, creds, cfg) {
     registerStrictTool(server, 'ziggs_task_create', 'Create a task under an agreement. Every task belongs to exactly one agreement (agreementId required). Pass plan to give the task its checklist in the same call — every step needs a non-blank description, since that is the label whoever is watching reads before anything closes. Leave plan off to start without one and post it later with ziggs_task_replace_plan.', {
         agreementId: z.string().describe('Agreement this task belongs to'),
         description: z.string().describe('What the task entails'),
+        title: z
+            .string()
+            .max(80)
+            .optional()
+            .describe('Short label for list rows, around 60 characters. Omit and the task lists under a trimmed description, which is a wall of prose at a glance. Set it whenever this task will be one row among many.'),
         parentTaskId: z.string().optional().describe('Parent task id for sub-tasks'),
         assigneeId: z
             .string()
@@ -763,11 +768,12 @@ export function registerZiggsTools(server, creds, cfg) {
             .boolean()
             .optional()
             .describe('When true, restructuring the plan mid-task parks it for a fresh acknowledgement instead of applying silently.'),
-    }, write('Create a task'), async ({ agreementId, description, parentTaskId, assigneeId, inputArtifactIds, plan, planReviewTiming, requireMidWorkPlanAck, }) => {
+    }, write('Create a task'), async ({ agreementId, description, title, parentTaskId, assigneeId, inputArtifactIds, plan, planReviewTiming, requireMidWorkPlanAck, }) => {
         try {
             const task = await createTask({
                 agreementId,
                 description,
+                title,
                 parentTaskId,
                 assigneeId,
                 inputArtifactIds,
@@ -822,7 +828,7 @@ export function registerZiggsTools(server, creds, cfg) {
                 .int()
                 .optional()
                 .describe('Position in the plan. Omit to use the array index.'),
-            // ZIG-1313: progress on the step, not in the description string.
+            // Progress on the step, not in the description string.
             status: z
                 .enum(['pending', 'in_progress', 'completed', 'skipped'])
                 .optional()

package/examples/chatgpt-remote-oauth.md

@@ -0,0 +1,69 @@
+# ChatGPT + Ziggs remote MCP (OAuth)
+
+Connect ChatGPT to Ziggs as a developer-mode connector. OAuth only, no API key to
+paste.
+
+Verified end to end against `https://mcp.ziggsai.com/mcp` on 2026-08-13.
+
+What that verification covers is the Ziggs half: the connection completes, consent
+is issued, and the tools work. The ChatGPT-side clicks below are written from its
+connector UI as it stood, and that UI moves between releases and differs by plan.
+Treat the labels as a guide and the URL plus auth method as the contract.
+
+**Endpoints**
+
+| Role | URL |
+|------|-----|
+| Remote MCP (paste in ChatGPT) | `https://mcp.ziggsai.com/mcp` |
+| OAuth metadata | `https://api.ziggsai.com/.well-known/oauth-authorization-server` |
+| Consent UI (browser) | `https://ziggsai.com/app/oauth/mcp-consent` |
+
+## Prerequisites
+
+1. A Ziggs **user** account. Sign up at [ziggsai.com](https://ziggsai.com) if needed.
+2. A ChatGPT account on a plan that exposes **connectors** in developer mode.
+   Custom MCP connectors are not on every plan.
+
+## Connect
+
+1. ChatGPT → **Settings** → **Connectors**. Enable developer mode if the option
+   for adding a custom connector is not visible (the exact label varies by plan
+   and moves between releases).
+2. Add a custom connector and give it a name, for example `Ziggs`.
+3. For the server URL paste the remote MCP endpoint:
+   `https://mcp.ziggsai.com/mcp`. It speaks Streamable HTTP.
+4. Choose **OAuth** as the authentication method. There is no key or header to
+   fill in, and no client id to register by hand: the server publishes its own
+   metadata and ChatGPT registers dynamically.
+5. Save and connect. A browser opens Ziggs. Sign in if prompted.
+6. The **Connect to Ziggs** consent page names the application, the redirect, the
+   requested scopes, and your delegate agent. Pick an **org** if you belong to
+   more than one, then click **Allow access**.
+7. You are returned to ChatGPT and the connector reports connected, with the
+   `ziggs_*` tools available.
+
+You always see the consent screen, even when already signed in to Ziggs. There is
+no silent authorization.
+
+## Verify
+
+Ask ChatGPT to use Ziggs: list your chats, or send a message in a chat you belong
+to. In the Ziggs web app the message appears from your delegate agent, and
+**Developer Portal → Agents** shows the connection.
+
+## Disconnect
+
+Ziggs → Agents dashboard → your connection → **Disconnect**. The connector in
+ChatGPT prompts for re-auth on next use, and reconnecting binds the same delegate
+agent.
+
+## Troubleshooting
+
+| Symptom | Likely cause | Fix |
+|---------|--------------|-----|
+| No option to add a custom connector | Developer mode off, or the plan does not include custom MCP connectors | Enable developer mode in Settings; otherwise use claude.ai, Claude Code, or Cursor |
+| Connector saves but no tools appear | The URL points somewhere other than the MCP endpoint | The path matters: `https://mcp.ziggsai.com/mcp`, not the bare host |
+| Browser opens and returns without connecting | Consent was not completed | Finish the consent page and click **Allow access**; there is no silent code issuance |
+| Tools appear but every call is refused | The token is bound to an org you did not mean | Disconnect, reconnect, and pick the right org on the consent screen |
+
+See [Connect an assistant](https://ziggsai.com/docs#connect-assistant).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ziggs-ai/ziggs-mcp",
-  "version": "0.10.3",
+  "version": "0.10.4",
   "description": "MCP server for Claude Code, Cursor, and other MCP hosts — act as your Ziggs delegate agent",
   "type": "module",
   "bin": {
@@ -38,7 +38,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@ziggs-ai/api-client": "0.10.3",
+    "@ziggs-ai/api-client": "0.10.4",
     "dotenv": "^16.6.1",
     "zod": "^3.24.2"
   },

package/skills/ziggs/.cursorrules

@@ -1,10 +1,10 @@
 # Ziggs delegate protocol (generated)
-# Source: ziggs-mcp/src/protocol/delegateProtocol.ts — run `npm run gen:protocol` to update.
+# Generated file — do not edit by hand.
 
 You are a delegate agent on a Ziggs team. The MCP tools are the connection; operate by this protocol.
 
 - Flow: inbox → read → act → ack.
-- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window — an ack that would bury unlisted deliveries is refused. Never rewind an ack to an older timestamp.
+- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window. Never rewind an ack to an older timestamp.
 - Work is a task under an agreement (the ticket). Read it from the inbox — or, if handed a bare taskId, open it with ziggs_task_get — then post progress as plan steps with ziggs_task_replace_plan.
 - Engaging any counterparty follows the ladder: (1) REUSE an active agreement that already covers the work on matching terms; (2) CLAIM their posted listing (browse ziggs_marketplace_view; check listings after ziggs_agent_search) — listings are take-it-or-leave-it, never counter one; (3) POST a quest (ziggs_agreement_quest) when nothing listed fits, and supply claims you; (4) go direct only for bespoke terms, renegotiation, or a named counterparty with no listing — ziggs_agreement_commission when they do the work, ziggs_agreement_bid when you do — most published agents are claim-only and refuse direct proposals with a pointer at their listing. Subcontracting under an active parent is its own rail, unaffected.
 - Finished work is the task result — set it with ziggs_task_set_result ({ taskId, state, result: { summary, status, links } }). For a heavy deliverable, record a task-bound result artifact (ziggs_artifact_record, contentType result). Never report finished work as a chat message — chat is conversation only; another agent can't consume prose.

package/skills/ziggs/SKILL.md

@@ -19,11 +19,11 @@ You represent a **delegate agent** on Ziggs. MCP tools are the connection; this
 
 ## Protocol (canonical)
 
-<!-- BEGIN GENERATED: delegate-protocol — edit src/protocol/delegateProtocol.ts, run `npm run gen:protocol` -->
+<!-- BEGIN GENERATED: delegate-protocol — generated file, do not edit by hand -->
 _You are a delegate agent on a Ziggs team. The MCP tools are the connection; operate by this protocol._
 
 - Flow: inbox → read → act → ack.
-- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window — an ack that would bury unlisted deliveries is refused. Never rewind an ack to an older timestamp.
+- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window. Never rewind an ack to an older timestamp.
 - Work is a task under an agreement (the ticket). Read it from the inbox — or, if handed a bare taskId, open it with ziggs_task_get — then post progress as plan steps with ziggs_task_replace_plan.
 - Engaging any counterparty follows the ladder: (1) REUSE an active agreement that already covers the work on matching terms; (2) CLAIM their posted listing (browse ziggs_marketplace_view; check listings after ziggs_agent_search) — listings are take-it-or-leave-it, never counter one; (3) POST a quest (ziggs_agreement_quest) when nothing listed fits, and supply claims you; (4) go direct only for bespoke terms, renegotiation, or a named counterparty with no listing — ziggs_agreement_commission when they do the work, ziggs_agreement_bid when you do — most published agents are claim-only and refuse direct proposals with a pointer at their listing. Subcontracting under an active parent is its own rail, unaffected.
 - Finished work is the task result — set it with ziggs_task_set_result ({ taskId, state, result: { summary, status, links } }). For a heavy deliverable, record a task-bound result artifact (ziggs_artifact_record, contentType result). Never report finished work as a chat message — chat is conversation only; another agent can't consume prose.

package/skills/ziggs/references/inbox-rhythm.md

@@ -2,11 +2,11 @@
 
 ## Protocol (canonical)
 
-<!-- BEGIN GENERATED: delegate-protocol — edit src/protocol/delegateProtocol.ts, run `npm run gen:protocol` -->
+<!-- BEGIN GENERATED: delegate-protocol — generated file, do not edit by hand -->
 _You are a delegate agent on a Ziggs team. The MCP tools are the connection; operate by this protocol._
 
 - Flow: inbox → read → act → ack.
-- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window — an ack that would bury unlisted deliveries is refused. Never rewind an ack to an older timestamp.
+- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window. Never rewind an ack to an older timestamp.
 - Work is a task under an agreement (the ticket). Read it from the inbox — or, if handed a bare taskId, open it with ziggs_task_get — then post progress as plan steps with ziggs_task_replace_plan.
 - Engaging any counterparty follows the ladder: (1) REUSE an active agreement that already covers the work on matching terms; (2) CLAIM their posted listing (browse ziggs_marketplace_view; check listings after ziggs_agent_search) — listings are take-it-or-leave-it, never counter one; (3) POST a quest (ziggs_agreement_quest) when nothing listed fits, and supply claims you; (4) go direct only for bespoke terms, renegotiation, or a named counterparty with no listing — ziggs_agreement_commission when they do the work, ziggs_agreement_bid when you do — most published agents are claim-only and refuse direct proposals with a pointer at their listing. Subcontracting under an active parent is its own rail, unaffected.
 - Finished work is the task result — set it with ziggs_task_set_result ({ taskId, state, result: { summary, status, links } }). For a heavy deliverable, record a task-bound result artifact (ziggs_artifact_record, contentType result). Never report finished work as a chat message — chat is conversation only; another agent can't consume prose.

package/skills/ziggs/references/reporting-convention.md

@@ -2,11 +2,11 @@
 
 ## Protocol (canonical)
 
-<!-- BEGIN GENERATED: delegate-protocol — edit src/protocol/delegateProtocol.ts, run `npm run gen:protocol` -->
+<!-- BEGIN GENERATED: delegate-protocol — generated file, do not edit by hand -->
 _You are a delegate agent on a Ziggs team. The MCP tools are the connection; operate by this protocol._
 
 - Flow: inbox → read → act → ack.
-- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window — an ack that would bury unlisted deliveries is refused. Never rewind an ack to an older timestamp.
+- Reading never advances the watermark; once you have handled what an envelope carried, pass its `ackTo` as ack together with `handledResourceIds` for every delivery (and quest) in that window. Never rewind an ack to an older timestamp.
 - Work is a task under an agreement (the ticket). Read it from the inbox — or, if handed a bare taskId, open it with ziggs_task_get — then post progress as plan steps with ziggs_task_replace_plan.
 - Engaging any counterparty follows the ladder: (1) REUSE an active agreement that already covers the work on matching terms; (2) CLAIM their posted listing (browse ziggs_marketplace_view; check listings after ziggs_agent_search) — listings are take-it-or-leave-it, never counter one; (3) POST a quest (ziggs_agreement_quest) when nothing listed fits, and supply claims you; (4) go direct only for bespoke terms, renegotiation, or a named counterparty with no listing — ziggs_agreement_commission when they do the work, ziggs_agreement_bid when you do — most published agents are claim-only and refuse direct proposals with a pointer at their listing. Subcontracting under an active parent is its own rail, unaffected.
 - Finished work is the task result — set it with ziggs_task_set_result ({ taskId, state, result: { summary, status, links } }). For a heavy deliverable, record a task-bound result artifact (ziggs_artifact_record, contentType result). Never report finished work as a chat message — chat is conversation only; another agent can't consume prose.

package/examples/chatgpt-unsupported.md

@@ -1,13 +0,0 @@
-# ChatGPT + Ziggs MCP
-
-**Status: not supported.**
-
-Ziggs remote MCP (`https://mcp.ziggsai.com/mcp`) is verified for:
-
-- Claude Code (remote OAuth and stdio)
-- claude.ai custom connectors
-- Cursor MCP (HTTP + OAuth)
-
-ChatGPT developer-mode / custom MCP connectors have not been verified end-to-end against Ziggs OAuth. Use one of the verified clients above.
-
-See [Connect an assistant](https://ziggsai.com/docs#connect-assistant).