gridzen-developer-kit 0.5.0__tar.gz → 0.6.1__tar.gz

{gridzen_developer_kit-0.5.0/src/gridzen_developer_kit.egg-info → gridzen_developer_kit-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gridzen-developer-kit
-Version: 0.5.0
+Version: 0.6.1
 Summary: Gridzen research catalog, integration planner and explicit verification sandbox
 Author-email: Gridzen <open@gridzen.ai>
 License-Expression: MIT
@@ -27,7 +27,13 @@ Requires-Dist: fastapi==0.142.4; extra == "test"
 Requires-Dist: uvicorn==0.54.0; extra == "test"
 Dynamic: license-file
 
-# Gridzen Developer Kit 0.5.0
+# Gridzen Developer Kit 0.6.0
+
+## Start immediately without signup
+
+Open [GridZen instant trial](https://gridzen.ai/console/start?lang=en) to run synthetic signup-phone and identity-onboarding responses without an account, API key or approval. Success, rejection and unavailable scenarios make no upstream calls and verify no real person. Agents can use the separate [key-free trial MCP](https://gridzen.ai/console/downloads/quickstart_mcp.py), installed with `mcp==2.3.0` and `httpx==0.28.1` in a virtual environment.
+
+For persistent test records and supplier sandbox callbacks, connect a verified merchant sandbox account. Production is a separate controlled free pilot; self-service production and payments are not enabled. This documentation update does not change PyPI or the official MCP Registry version.
 
 Research for 198 countries/territories, a verification integration planner, five synthetic outcomes, an HTTP SDK, local MCP server and six Skills. **No live provider is enabled. No real person is verified.** The research snapshot is dated 2026-10-07, with source links and file hashes.
 
@@ -59,7 +65,7 @@ Register a local stdio server in your MCP client. Use the absolute path to the i
 {"mcpServers":{"gridzen":{"command":"/absolute/path/to/.venv/bin/gridzen-mcp","args":[]}}}
 ```
 
-Tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, explain_result. All operate on local research or synthetic fixtures, with read-only/idempotent annotations. Public research/sandbox MCP endpoint: `https://gridzen.ai/developers/mcp` (Streamable HTTP, no account or API key). It has the same five tools and zero live providers. Remote usage sends the documented arguments to Gridzen; local stdio remains offline. Limits: 120 requests/minute per client address and 600/minute overall, returning HTTP 429 with Retry-After.
+Tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, explain_result. All operate on local research or synthetic fixtures, with read-only/idempotent annotations. Public research/sandbox MCP endpoint: `https://gridzen.ai/developers/mcp` (Streamable HTTP, no account or API key). It has the same five tools and zero live providers. Remote usage sends the documented arguments to Gridzen; local stdio is offline by default. Limits: 120 requests/minute per client address and 600/minute overall, returning HTTP 429 with Retry-After.
 
 ## Skills
 
@@ -106,10 +112,10 @@ npx skills add immurray/gridzen-developer-kit
 Install the tagged Python/MCP release from GitHub (Python 3.11+ and Git):
 
 ```sh
-python -m pip install "gridzen-developer-kit[mcp] @ git+https://github.com/immurray/gridzen-developer-kit.git@v0.5.0"
+python -m pip install "gridzen-developer-kit[mcp] @ git+https://github.com/immurray/gridzen-developer-kit.git@v0.6.0"
 ```
 
-PyPI 0.5.0 is published and verified. Install with `python -m pip install
+PyPI 0.6.0 is published and verified. Install with `python -m pip install
 gridzen-developer-kit`. See [the release tracker](distribution/STATUS.md) for
 publication and installation evidence.
 
@@ -132,11 +138,11 @@ Original code and Skills: MIT. Research provenance and third-party rights:
 Source, release downloads, the official MCP Registry entry and six Skills.sh pages are public. Docker catalog submission is awaiting review. See [the publication ledger](distribution/STATUS.md) for exact status and remaining platform steps.
 
 
-## Six bundled Skills (0.5.0)
+## Six bundled Skills (0.6.0)
 
 `python -m pip install gridzen-developer-kit` installs the CLI, stdio MCP dependencies
-and all six Skill directories. Version 0.5.0 is published on
-[PyPI](https://pypi.org/project/gridzen-developer-kit/0.5.0/); clean installation,
+and all six Skill directories. Version 0.6.0 is published on
+[PyPI](https://pypi.org/project/gridzen-developer-kit/0.6.0/); clean installation,
 CLI, stdio MCP and all six bundled Skill directories were verified. No extra MCP
 dependency installation is required.
 
@@ -157,7 +163,7 @@ workflows, version 1.0.0: `mexico-pilot-scoper`, `payout-policy-designer`, and
 and agent acceptance prompts. They make no third-party calls and grant no real
 verification, legal approval or regulatory conclusion.
 
-## Configure your assistant (v0.5.0)
+## Configure your assistant (v0.6.0)
 
 ```sh
 python3 -m venv .venv
@@ -174,7 +180,7 @@ Use `--client` for Codex, Claude Code/Desktop, Cursor, VS Code/Copilot, Copilot
 Hosted calls count successful tool invocations, not customers. Existing totals
 remain unchanged. The hosted service records UTC day, tool name, one source
 category and a count; it never persists request arguments or client addresses.
-Historical and unlabelled calls remain `unknown`. Local stdio remains offline.
+Historical and unlabelled calls remain `unknown`. Local stdio is offline by default.
 
 Explicit acceptance requests to the loopback-published service may set
 `X-Gridzen-Purpose: internal_test`. Only configured local peers with no forwarded
@@ -187,7 +193,7 @@ and must never contain public client addresses. Source counts use the existing
 new PyPI version or enable any live provider.
 
 
-## Customer tasks and voluntary feedback (0.5.0)
+## Customer tasks and voluntary feedback (0.6.0)
 
 ```sh
 gridzen plan --country US --event onboarding --task signup_phone
@@ -201,4 +207,32 @@ gridzen feedback --input task-summary.json --share
 
 Phone intelligence is not OTP or ownership verification. Identity fixtures are not hosted document/liveness sessions. Payout matching remains a prototype with no real enabled route. Provider intake Skills are for provider operations/BYO, not a universal customer gate.
 
-Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Offline Skills/CLI never upload automatically. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for within-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Local feedback is off by default. After explicit opt-in, CLI and stdio MCP automatically upload category-only events. Reading static Skills remains unobservable. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for 30-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+
+## Optional automatic local feedback (0.6.0)
+
+```sh
+gridzen telemetry status
+# Run only after reading and agreeing to category-only automatic sharing:
+gridzen telemetry enable --consent
+gridzen plan --country US --event onboarding --task signup_phone
+# Send one queued event per invocation after reconnecting:
+gridzen telemetry flush
+# Disable future uploads and clear the pending queue:
+gridzen telemetry disable
+```
+
+No network calls occur from local CLI/MCP when disabled. Consent is saved per OS user, not silently added to a project. Events contain only documented categories, ISO country, and a random per-event receipt, with no conversation, identity fields, credentials, user or project IDs. Feedback failures do not fail tool execution. The local queue is capped at 1,000 events/30 days; reconnect or `flush` retries one queued event, with a one-second HTTP timeout. Uploads are self-reported usage, not authenticated customers or completed verification. No background daemon is installed. Merely reading a Skill is unobservable; after consent, an Agent can explicitly record a fixed-category task summary.
+
+Local queued events expire after 30 days and are removed on the next enqueue/flush. Daily aggregates use server receipt date; delayed uploads are not proof that work occurred on that date.
+
+## Separate owner-approved customer pilot
+
+The published 0.6.0 kit and its five public tools remain research/synthetic tools. A separate hosted pilot accepts customer applications for basic signup-phone validity and hosted personal identity onboarding: [apply](https://gridzen.ai/console/pilot?lang=en), [integration guide](https://gridzen.ai/console/pilot-guide?lang=en), [public scope](https://gridzen.ai/guides/customer-pilot/).
+
+Submitting an application never activates production. The owner must approve supplier rights, downstream agreements, capabilities, request limits and expiry; only confirmed free allowances are used. The production pilot has its own downloaded MCP client and merchant API key. Do not send documents, faces or provider keys to the public research MCP. Basic phone validity does not provide OTP or ownership.
+
+Real basic phone checks and retrieval of a historical Approved operator identity session were validated through the live customer API/MCP. New-session human completion and its final real webhook remain unvalidated. Operator tests, downloads and self-reported interest are not customer demand. This documentation update does not change the PyPI package or Registry version.
+
+
+Use `gridzen start --task identity_onboarding --lang en` to find the anonymous trial, free sandbox account and integration assistant. `gridzen start` makes no network calls. Account progress measurement is a separate, optional console consent; completing a sandbox does not verify a real person. Real payments remain disabled.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/README.es.md

@@ -1,4 +1,10 @@
-# Kit de desarrollo Gridzen 0.1.1
+# Kit de desarrollo Gridzen 0.6.0
+
+## Probar inmediatamente sin registro
+
+Abra la [prueba inmediata de GridZen](https://gridzen.ai/console/start?lang=es) para simular comprobaciones telefónicas e incorporación de identidad sin cuenta, clave ni aprobación. Los escenarios de éxito, rechazo e indisponibilidad no llaman a proveedores reales ni verifican personas. Los agentes pueden usar el [MCP de prueba sin clave](https://gridzen.ai/console/downloads/quickstart_mcp.py) con `mcp==2.3.0` y `httpx==0.28.1` en un entorno virtual.
+
+Conecte una cuenta sandbox con correo verificado para guardar registros y recibir callbacks. La producción sigue siendo un piloto gratuito controlado; autoservicio de producción y pagos no están habilitados. Esta actualización documental no cambia PyPI ni la versión del registro oficial MCP.
 
 Investigación sobre 198 países y territorios, planificación de integraciones, cinco resultados simulados, CLI/SDK HTTP de Python, MCP local y seis Skills. No hay canales de proveedores reales activos. Ningún resultado simulado verifica a una persona real.
 
@@ -29,7 +35,7 @@ Añade un servidor stdio local a un cliente compatible y sustituye command por l
 
 Prueba: «Planifica una verificación de pagos para Indonesia y simula una espera agotada del proveedor». Las cinco herramientas consultan cobertura, planifican, generan simulaciones, recuperan pruebas y explican resultados. La configuración depende del cliente; no hay endpoint MCP remoto de producción.
 
-Copia cada carpeta de `skills/` al directorio de habilidades del agente, conservando `SKILL.md` y sus referencias. Los tres Skills permiten elegir una verificación, integrar pruebas y explicar resultados. Los identificadores permanecen en inglés; el agente puede explicar los resultados en español.
+Copia cada carpeta de `skills/` al directorio de habilidades del agente, conservando `SKILL.md` y sus referencias. Los seis Skills cubren selección, integración de pruebas, explicación de resultados, preparación de permisos, políticas de pagos y planificación de pilotos en México. Los identificadores permanecen en inglés; el agente puede explicar los resultados en español.
 
 ## Interpretación
 
@@ -60,11 +66,11 @@ Código original bajo MIT; consulte NOTICE.md para los derechos de terceros.
 El código, las descargas, la entrada oficial de MCP Registry y tres páginas de Skills.sh están publicados. La propuesta del catálogo de Docker está pendiente de revisión. Consulta [el registro de publicación](distribution/STATUS.md).
 
 
-## Six bundled Skills (0.5.0)
+## Six bundled Skills (0.6.0)
 
 `python -m pip install gridzen-developer-kit` installs the CLI, stdio MCP dependencies
-and all six Skill directories. Version 0.5.0 is published on
-[PyPI](https://pypi.org/project/gridzen-developer-kit/0.5.0/); clean installation,
+and all six Skill directories. Version 0.6.0 is published on
+[PyPI](https://pypi.org/project/gridzen-developer-kit/0.6.0/); clean installation,
 CLI, stdio MCP and all six bundled Skill directories were verified. No extra MCP
 dependency installation is required.
 
@@ -100,7 +106,7 @@ Usa Python 3.11+ en un entorno virtual. Primero revisa el resultado y después a
 [Instructions / 使用说明](https://gridzen.ai/developers/harnesses.html) · [Compatibility / 测试记录](clients/compatibility.json)
 
 
-## Customer tasks and voluntary feedback (0.5.0)
+## Customer tasks and voluntary feedback (0.6.0)
 
 ```sh
 gridzen plan --country US --event onboarding --task signup_phone
@@ -114,4 +120,34 @@ gridzen feedback --input task-summary.json --share
 
 Phone intelligence is not OTP or ownership verification. Identity fixtures are not hosted document/liveness sessions. Payout matching remains a prototype with no real enabled route. Provider intake Skills are for provider operations/BYO, not a universal customer gate.
 
-Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Offline Skills/CLI never upload automatically. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for within-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Local feedback is off by default. After explicit opt-in, CLI and stdio MCP automatically upload category-only events. Reading static Skills remains unobservable. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for 30-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+
+## Optional automatic local feedback (0.6.0)
+
+```sh
+gridzen telemetry status
+# Run only after reading and agreeing to category-only automatic sharing:
+gridzen telemetry enable --consent
+gridzen plan --country US --event onboarding --task signup_phone
+# Send one queued event per invocation after reconnecting:
+gridzen telemetry flush
+# Disable future uploads and clear the pending queue:
+gridzen telemetry disable
+```
+
+No network calls occur from local CLI/MCP when disabled. Consent is saved per OS user, not silently added to a project. Events contain only documented categories, ISO country, and a random per-event receipt, with no conversation, identity fields, credentials, user or project IDs. Feedback failures do not fail tool execution. The local queue is capped at 1,000 events/30 days; reconnect or `flush` retries one queued event, with a one-second HTTP timeout. Uploads are self-reported usage, not authenticated customers or completed verification. No background daemon is installed. Merely reading a Skill is unobservable; after consent, an Agent can explicitly record a fixed-category task summary.
+
+La telemetría está desactivada por defecto. Tras consentimiento explícito, CLI y stdio envían categorías automáticamente. `gridzen telemetry disable` desactiva y borra la cola. Sin conexión: máximo 1000 eventos durante 30 días. Cada llamada o flush reintenta un evento; no hay servicio en segundo plano. No se envían conversaciones, identidad, credenciales ni IDs de usuarios/proyectos. Leer un Skill no se observa; un Agent puede registrar un resumen tras consentimiento previo. Son datos autodeclarados, no clientes autenticados.
+
+Local queued events expire after 30 days and are removed on the next enqueue/flush. Daily aggregates use server receipt date; delayed uploads are not proof that work occurred on that date.
+
+## Piloto independiente con aprobación del responsable
+
+El kit publicado 0.6.0 y sus cinco herramientas públicas siguen siendo de investigación y simulación. Puede solicitar un piloto independiente de validez básica del teléfono e incorporación de identidad: [solicitud](https://gridzen.ai/console/pilot?lang=es), [guía](https://gridzen.ai/console/pilot-guide?lang=es), [alcance](https://gridzen.ai/es/guides/customer-pilot/).
+
+Solicitar no activa producción. El responsable confirma derechos del proveedor, acuerdos, capacidades, límites y vencimiento; solo se usan cupos gratuitos confirmados. El piloto utiliza un cliente MCP separado y una clave comercial. No envíe documentos, caras ni claves del proveedor al MCP público. La validez básica no proporciona OTP ni prueba de titularidad.
+
+Se validaron una consulta real de teléfono y la lectura de una sesión histórica Approved del operador mediante API/MCP. Falta validar la finalización humana de una sesión nueva y su webhook final real. Pruebas internas, descargas e interés declarado no demuestran demanda. Esta actualización documental no cambia versiones de PyPI ni Registry.
+
+
+Use `gridzen start --task identity_onboarding --lang es` para encontrar la prueba anónima, la cuenta gratuita de sandbox y el asistente. El comando no hace llamadas de red. La medición de progreso requiere consentimiento opcional en la consola. Completar el sandbox no verifica a una persona real; los cobros reales siguen desactivados.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/README.md

@@ -1,4 +1,10 @@
-# Gridzen Developer Kit 0.5.0
+# Gridzen Developer Kit 0.6.0
+
+## Start immediately without signup
+
+Open [GridZen instant trial](https://gridzen.ai/console/start?lang=en) to run synthetic signup-phone and identity-onboarding responses without an account, API key or approval. Success, rejection and unavailable scenarios make no upstream calls and verify no real person. Agents can use the separate [key-free trial MCP](https://gridzen.ai/console/downloads/quickstart_mcp.py), installed with `mcp==2.3.0` and `httpx==0.28.1` in a virtual environment.
+
+For persistent test records and supplier sandbox callbacks, connect a verified merchant sandbox account. Production is a separate controlled free pilot; self-service production and payments are not enabled. This documentation update does not change PyPI or the official MCP Registry version.
 
 Research for 198 countries/territories, a verification integration planner, five synthetic outcomes, an HTTP SDK, local MCP server and six Skills. **No live provider is enabled. No real person is verified.** The research snapshot is dated 2026-10-07, with source links and file hashes.
 
@@ -30,7 +36,7 @@ Register a local stdio server in your MCP client. Use the absolute path to the i
 {"mcpServers":{"gridzen":{"command":"/absolute/path/to/.venv/bin/gridzen-mcp","args":[]}}}
 ```
 
-Tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, explain_result. All operate on local research or synthetic fixtures, with read-only/idempotent annotations. Public research/sandbox MCP endpoint: `https://gridzen.ai/developers/mcp` (Streamable HTTP, no account or API key). It has the same five tools and zero live providers. Remote usage sends the documented arguments to Gridzen; local stdio remains offline. Limits: 120 requests/minute per client address and 600/minute overall, returning HTTP 429 with Retry-After.
+Tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, explain_result. All operate on local research or synthetic fixtures, with read-only/idempotent annotations. Public research/sandbox MCP endpoint: `https://gridzen.ai/developers/mcp` (Streamable HTTP, no account or API key). It has the same five tools and zero live providers. Remote usage sends the documented arguments to Gridzen; local stdio is offline by default. Limits: 120 requests/minute per client address and 600/minute overall, returning HTTP 429 with Retry-After.
 
 ## Skills
 
@@ -77,10 +83,10 @@ npx skills add immurray/gridzen-developer-kit
 Install the tagged Python/MCP release from GitHub (Python 3.11+ and Git):
 
 ```sh
-python -m pip install "gridzen-developer-kit[mcp] @ git+https://github.com/immurray/gridzen-developer-kit.git@v0.5.0"
+python -m pip install "gridzen-developer-kit[mcp] @ git+https://github.com/immurray/gridzen-developer-kit.git@v0.6.0"
 ```
 
-PyPI 0.5.0 is published and verified. Install with `python -m pip install
+PyPI 0.6.0 is published and verified. Install with `python -m pip install
 gridzen-developer-kit`. See [the release tracker](distribution/STATUS.md) for
 publication and installation evidence.
 
@@ -103,11 +109,11 @@ Original code and Skills: MIT. Research provenance and third-party rights:
 Source, release downloads, the official MCP Registry entry and six Skills.sh pages are public. Docker catalog submission is awaiting review. See [the publication ledger](distribution/STATUS.md) for exact status and remaining platform steps.
 
 
-## Six bundled Skills (0.5.0)
+## Six bundled Skills (0.6.0)
 
 `python -m pip install gridzen-developer-kit` installs the CLI, stdio MCP dependencies
-and all six Skill directories. Version 0.5.0 is published on
-[PyPI](https://pypi.org/project/gridzen-developer-kit/0.5.0/); clean installation,
+and all six Skill directories. Version 0.6.0 is published on
+[PyPI](https://pypi.org/project/gridzen-developer-kit/0.6.0/); clean installation,
 CLI, stdio MCP and all six bundled Skill directories were verified. No extra MCP
 dependency installation is required.
 
@@ -128,7 +134,7 @@ workflows, version 1.0.0: `mexico-pilot-scoper`, `payout-policy-designer`, and
 and agent acceptance prompts. They make no third-party calls and grant no real
 verification, legal approval or regulatory conclusion.
 
-## Configure your assistant (v0.5.0)
+## Configure your assistant (v0.6.0)
 
 ```sh
 python3 -m venv .venv
@@ -145,7 +151,7 @@ Use `--client` for Codex, Claude Code/Desktop, Cursor, VS Code/Copilot, Copilot
 Hosted calls count successful tool invocations, not customers. Existing totals
 remain unchanged. The hosted service records UTC day, tool name, one source
 category and a count; it never persists request arguments or client addresses.
-Historical and unlabelled calls remain `unknown`. Local stdio remains offline.
+Historical and unlabelled calls remain `unknown`. Local stdio is offline by default.
 
 Explicit acceptance requests to the loopback-published service may set
 `X-Gridzen-Purpose: internal_test`. Only configured local peers with no forwarded
@@ -158,7 +164,7 @@ and must never contain public client addresses. Source counts use the existing
 new PyPI version or enable any live provider.
 
 
-## Customer tasks and voluntary feedback (0.5.0)
+## Customer tasks and voluntary feedback (0.6.0)
 
 ```sh
 gridzen plan --country US --event onboarding --task signup_phone
@@ -172,4 +178,32 @@ gridzen feedback --input task-summary.json --share
 
 Phone intelligence is not OTP or ownership verification. Identity fixtures are not hosted document/liveness sessions. Payout matching remains a prototype with no real enabled route. Provider intake Skills are for provider operations/BYO, not a universal customer gate.
 
-Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Offline Skills/CLI never upload automatically. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for within-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Local feedback is off by default. After explicit opt-in, CLI and stdio MCP automatically upload category-only events. Reading static Skills remains unobservable. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for 30-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+
+## Optional automatic local feedback (0.6.0)
+
+```sh
+gridzen telemetry status
+# Run only after reading and agreeing to category-only automatic sharing:
+gridzen telemetry enable --consent
+gridzen plan --country US --event onboarding --task signup_phone
+# Send one queued event per invocation after reconnecting:
+gridzen telemetry flush
+# Disable future uploads and clear the pending queue:
+gridzen telemetry disable
+```
+
+No network calls occur from local CLI/MCP when disabled. Consent is saved per OS user, not silently added to a project. Events contain only documented categories, ISO country, and a random per-event receipt, with no conversation, identity fields, credentials, user or project IDs. Feedback failures do not fail tool execution. The local queue is capped at 1,000 events/30 days; reconnect or `flush` retries one queued event, with a one-second HTTP timeout. Uploads are self-reported usage, not authenticated customers or completed verification. No background daemon is installed. Merely reading a Skill is unobservable; after consent, an Agent can explicitly record a fixed-category task summary.
+
+Local queued events expire after 30 days and are removed on the next enqueue/flush. Daily aggregates use server receipt date; delayed uploads are not proof that work occurred on that date.
+
+## Separate owner-approved customer pilot
+
+The published 0.6.0 kit and its five public tools remain research/synthetic tools. A separate hosted pilot accepts customer applications for basic signup-phone validity and hosted personal identity onboarding: [apply](https://gridzen.ai/console/pilot?lang=en), [integration guide](https://gridzen.ai/console/pilot-guide?lang=en), [public scope](https://gridzen.ai/guides/customer-pilot/).
+
+Submitting an application never activates production. The owner must approve supplier rights, downstream agreements, capabilities, request limits and expiry; only confirmed free allowances are used. The production pilot has its own downloaded MCP client and merchant API key. Do not send documents, faces or provider keys to the public research MCP. Basic phone validity does not provide OTP or ownership.
+
+Real basic phone checks and retrieval of a historical Approved operator identity session were validated through the live customer API/MCP. New-session human completion and its final real webhook remain unvalidated. Operator tests, downloads and self-reported interest are not customer demand. This documentation update does not change the PyPI package or Registry version.
+
+
+Use `gridzen start --task identity_onboarding --lang en` to find the anonymous trial, free sandbox account and integration assistant. `gridzen start` makes no network calls. Account progress measurement is a separate, optional console consent; completing a sandbox does not verify a real person. Real payments remain disabled.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/README.zh-CN.md

@@ -1,6 +1,12 @@
-# Gridzen 开发者工具包 0.1.1
+# Gridzen 开发者工具包 0.6.0
 
-工具包提供 198 个国家/地区的核验研究、接入方案、五种模拟结果、Python CLI/HTTP SDK、本地 MCP 和三个 Skills。当前没有启用真实供应商通道，模拟结果不代表真实人员通过核验。
+## 无需注册，立即试用
+
+打开[立即试用](https://gridzen.ai/console/start?lang=zh)，无需账号、密钥或审批即可运行注册号码与身份入驻的模拟响应。可测试成功、未通过和暂不可用；不调用真实上游，不核验真人。Agent 可下载独立的[免密钥试用 MCP](https://gridzen.ai/console/downloads/quickstart_mcp.py)，在虚拟环境安装 `mcp==2.3.0`、`httpx==0.28.1` 后启动。
+
+需要保存测试记录、接收供应商沙盒回传时，再连接已验证邮箱的商户沙盒账号。真实核验仍为独立受控免费试点；自助生产和收费尚未开放。本次只更新接入说明，不更改 PyPI 或官方 MCP Registry 版本。
+
+工具包提供 198 个国家/地区的核验研究、接入方案、五种模拟结果、Python CLI/HTTP SDK、本地 MCP 和六个 Skills。当前没有启用真实供应商通道，模拟结果不代表真实人员通过核验。
 
 在线试用与中文指南：https://gridzen.ai/developers/ 。页面右上角可切换中文、英文和西班牙文，并记住选择。研究快照日期为 2026-10-07，来源和原始接入限制保持原文。
 
@@ -29,7 +35,7 @@ Windows 下使用 `.venv\Scripts\activate` 激活虚拟环境。CLI 和本地 MC
 
 可输入：“为印度尼西亚制定付款核验接入方案，然后测试供应商超时。”五个工具分别查询覆盖、规划、生成模拟结果、读取结果和解释原因。客户端配置格式可能不同；当前没有远程生产 MCP 地址。
 
-将 `skills/` 中各个文件夹复制到 Agent 支持的技能目录，保留 `SKILL.md` 和引用文件。三个 Skill 分别用于选择核验方案、接入沙盒、解释结果。代码标识和技能名称保持英文，Agent 可以用中文讲解。
+将 `skills/` 中各个文件夹复制到 Agent 支持的技能目录，保留 `SKILL.md` 和引用文件。六个 Skill 覆盖方案选择、沙盒接入、结果解释、供应商权限准备、提现政策和墨西哥试点规划。代码标识和技能名称保持英文，Agent 可以用中文讲解。
 
 ## 理解测试结果
 
@@ -59,11 +65,11 @@ Skills 安装：`npx skills add immurray/gridzen-developer-kit`。
 源码、版本下载、官方 MCP Registry 和三个 Skills.sh 技能页已公开；Docker 目录投稿待审核。各渠道真实状态及剩余步骤见[发布台账](distribution/STATUS.md)。
 
 
-## Six bundled Skills (0.5.0)
+## Six bundled Skills (0.6.0)
 
 `python -m pip install gridzen-developer-kit` installs the CLI, stdio MCP dependencies
-and all six Skill directories. Version 0.5.0 is published on
-[PyPI](https://pypi.org/project/gridzen-developer-kit/0.5.0/); clean installation,
+and all six Skill directories. Version 0.6.0 is published on
+[PyPI](https://pypi.org/project/gridzen-developer-kit/0.6.0/); clean installation,
 CLI, stdio MCP and all six bundled Skill directories were verified. No extra MCP
 dependency installation is required.
 
@@ -99,7 +105,7 @@ gridzen setup --client all --project . --apply
 [Instructions / 使用说明](https://gridzen.ai/developers/harnesses.html) · [Compatibility / 测试记录](clients/compatibility.json)
 
 
-## Customer tasks and voluntary feedback (0.5.0)
+## Customer tasks and voluntary feedback (0.6.0)
 
 ```sh
 gridzen plan --country US --event onboarding --task signup_phone
@@ -113,4 +119,34 @@ gridzen feedback --input task-summary.json --share
 
 Phone intelligence is not OTP or ownership verification. Identity fixtures are not hosted document/liveness sessions. Payout matching remains a prototype with no real enabled route. Provider intake Skills are for provider operations/BYO, not a universal customer gate.
 
-Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Offline Skills/CLI never upload automatically. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for within-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+Remote APIs count fixed task/capability/country/stage/error categories for 90 days, including technical failures. They store no arguments, identity data, credentials, raw chats or per-user tracking. Local feedback is off by default. After explicit opt-in, CLI and stdio MCP automatically upload category-only events. Reading static Skills remains unobservable. Optional feedback requires explicit consent, contains only fixed categories, and is unverified self-reported evidence. A SHA-256 hash of its random receipt ID is retained 30 days for 30-day retry deduplication; the ID itself is not stored. Counters are capped at 10,000 requests/day and 500 summaries/day per database; missing history or offline usage is unknown. Requests are not unique customers.
+
+## 首次同意后的本地自动反馈（0.6.0）
+
+```sh
+gridzen telemetry status
+# Run only after reading and agreeing to category-only automatic sharing:
+gridzen telemetry enable --consent
+gridzen plan --country US --event onboarding --task signup_phone
+# Send one queued event per invocation after reconnecting:
+gridzen telemetry flush
+# Disable future uploads and clear the pending queue:
+gridzen telemetry disable
+```
+
+No network calls occur from local CLI/MCP when disabled. Consent is saved per OS user, not silently added to a project. Events contain only documented categories, ISO country, and a random per-event receipt, with no conversation, identity fields, credentials, user or project IDs. Feedback failures do not fail tool execution. The local queue is capped at 1,000 events/30 days; reconnect or `flush` retries one queued event, with a one-second HTTP timeout. Uploads are self-reported usage, not authenticated customers or completed verification. No background daemon is installed. Merely reading a Skill is unobservable; after consent, an Agent can explicitly record a fixed-category task summary.
+
+本地反馈默认关闭。用户先阅读说明并同意，再运行 `gridzen telemetry enable --consent`；此后 CLI 和本地 MCP 自动反馈分类事件。`gridzen telemetry disable` 立即关闭并清空待发送队列。断网最多保留 1000 条、30 天；恢复后每次调用或 flush 发送一条，无后台守护进程。只发送固定分类、国家和随机事件回执，不发送对话、身份资料、凭证或用户/项目标识。按服务器收到的日期统计，延迟上传不是该日实际发生的全部调用。仅阅读 Skill 无法自动观察，Agent 可在用户已经同意时主动 record 分类小结。它们仍是自报线索，不代表认证客户或真实核验完成。
+
+Local queued events expire after 30 days and are removed on the next enqueue/flush. Daily aggregates use server receipt date; delayed uploads are not proof that work occurred on that date.
+
+## 独立的客户生产试点
+
+已发行的 0.6.0 工具包与公开五个工具仍提供研究和模拟，不自动启用真人核验。客户可以申请独立试点：[申请入口](https://gridzen.ai/console/pilot?lang=zh)、[接入指南](https://gridzen.ai/console/pilot-guide?lang=zh)、[公开范围](https://gridzen.ai/zh/guides/customer-pilot/)。
+
+申请不会自动开通。负责人核对供应商权限、下游协议、能力、次数和有效期后批准，仅用确认的免费额度。生产试点使用独立下载的 MCP 客户端和商户 Key；不向研究 MCP 提交证件、人脸或供应商密钥。号码基础有效性不提供 OTP 或号码归属证明。
+
+已真实验收基础号码查询和历史 Approved 本人身份结果经新版 API/MCP 读取；新会话真人完成及最终真实回调尚未验收。自测、下载和费用意向不等于客户需求。这次只更新文档，不改变 PyPI 或 Registry 版本。
+
+
+运行 `gridzen start --task identity_onboarding --lang zh` 查看匿名试用、免费沙盒账号及接入助手。该命令不联网。账号进度统计需在 Console 单独明确同意；完成沙盒不代表真人核验，真实收费仍关闭。

{gridzen_developer_kit-0.5.0/src/gridzen_developer/web → gridzen_developer_kit-0.6.1/clients}/compatibility.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.5.0",
+  "version": "0.6.1",
   "checked_at": "2026-10-09",
   "tools": 5,
   "skills": 6,

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "gridzen-developer-kit"
-version = "0.5.0"
+version = "0.6.1"
 readme = "README.md"
 license = "MIT"
 license-files = ["LICENSE", "NOTICE.md"]

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/gridzen-explain-verification/SKILL.md

@@ -22,3 +22,6 @@ Separate network/auth/schema/rate-limit errors from returned synthetic fixture o
 ## Optional task feedback
 
 Offline use is not tracked. Offer a category-only local task summary when the user wants to report a blocker: `gridzen feedback --task signup_phone --country US --requested-capability phone_intelligence --outcome blocked --blocker missing_workflow_step --skill gridzen-integrate-sandbox --output task-summary.json`. Choose the actual fixed categories; do not fabricate demand. Inspect the file with the user. Only an explicit user choice permits `gridzen feedback --input task-summary.json --share`; otherwise stop at the local file. Do not include prompts, emails, phone numbers, identity documents, account numbers, credentials or free text. Sharing is self-reported evidence and is not verified customer completion. No hidden upload, background call or new MCP tool is required.
+
+
+Local feedback in kit 0.6.0 is off by default. If the CLI is installed, `gridzen telemetry status` shows consent. Never enable it on the user's behalf without explicit agreement. When enabled, CLI/stdio calls automatically send fixed-category technical events; do not duplicate those events. For a Skill-only workflow, record one task summary after actual work with `gridzen telemetry record --skill gridzen-explain-verification --task <documented-task> --outcome <documented-outcome> --blocker <documented-reason>`, only if consent is already enabled. Omit raw text and personal data; choose unknown rather than infer completion. Do not install a dependency just to report telemetry. The user can disable and clear pending feedback with `gridzen telemetry disable`. Reading these instructions alone is not tracked.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/gridzen-integrate-sandbox/SKILL.md

@@ -21,3 +21,6 @@ For signup phone checks use `phone_intelligence`; number type is not ownership o
 ## Optional task feedback
 
 Offline use is not tracked. Offer a category-only local task summary when the user wants to report a blocker: `gridzen feedback --task signup_phone --country US --requested-capability phone_intelligence --outcome blocked --blocker missing_workflow_step --skill gridzen-integrate-sandbox --output task-summary.json`. Choose the actual fixed categories; do not fabricate demand. Inspect the file with the user. Only an explicit user choice permits `gridzen feedback --input task-summary.json --share`; otherwise stop at the local file. Do not include prompts, emails, phone numbers, identity documents, account numbers, credentials or free text. Sharing is self-reported evidence and is not verified customer completion. No hidden upload, background call or new MCP tool is required.
+
+
+Local feedback in kit 0.6.0 is off by default. If the CLI is installed, `gridzen telemetry status` shows consent. Never enable it on the user's behalf without explicit agreement. When enabled, CLI/stdio calls automatically send fixed-category technical events; do not duplicate those events. For a Skill-only workflow, record one task summary after actual work with `gridzen telemetry record --skill gridzen-integrate-sandbox --task <documented-task> --outcome <documented-outcome> --blocker <documented-reason>`, only if consent is already enabled. Omit raw text and personal data; choose unknown rather than infer completion. Do not install a dependency just to report telemetry. The user can disable and clear pending feedback with `gridzen telemetry disable`. Reading these instructions alone is not tracked.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/gridzen-integrate-sandbox/references/api.md

@@ -23,4 +23,4 @@ assert result['status'] == 'inconclusive'
 Unexpected fields are rejected (422); unknown country/capability/fixture is rejected (400). Network errors and HTTP failures are integration failures, not verification outcomes. Do not retry indefinitely. Local core and local MCP work offline after installation; Python HTTP SDK sends only documented fixture parameters to Gridzen.
 
 
-Task-specific planning (kit 0.5.0): `plan_verification(country="US", event="onboarding", task="signup_phone", stage="prototype")`. Identity task: `identity_onboarding`. Task and event must agree. Fixtures accept `phone_intelligence` and `identity_verification` in addition to existing research capability names. All fixture outcomes remain simulated and verified=false. Production planning always reports NO_LIVE_ROUTE_ENABLED. No extra MCP tool is added.
+Task-specific planning (kit 0.6.0): `plan_verification(country="US", event="onboarding", task="signup_phone", stage="prototype")`. Identity task: `identity_onboarding`. Task and event must agree. Fixtures accept `phone_intelligence` and `identity_verification` in addition to existing research capability names. All fixture outcomes remain simulated and verified=false. Production planning always reports NO_LIVE_ROUTE_ENABLED. No extra MCP tool is added.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/gridzen-select-verification/SKILL.md

@@ -19,3 +19,6 @@ Select the proof for the customer task before choosing a provider. Use `plan_ver
 ## Optional task feedback
 
 Offline use is not tracked. Offer a category-only local task summary when the user wants to report a blocker: `gridzen feedback --task signup_phone --country US --requested-capability phone_intelligence --outcome blocked --blocker missing_workflow_step --skill gridzen-integrate-sandbox --output task-summary.json`. Choose the actual fixed categories; do not fabricate demand. Inspect the file with the user. Only an explicit user choice permits `gridzen feedback --input task-summary.json --share`; otherwise stop at the local file. Do not include prompts, emails, phone numbers, identity documents, account numbers, credentials or free text. Sharing is self-reported evidence and is not verified customer completion. No hidden upload, background call or new MCP tool is required.
+
+
+Local feedback in kit 0.6.0 is off by default. If the CLI is installed, `gridzen telemetry status` shows consent. Never enable it on the user's behalf without explicit agreement. When enabled, CLI/stdio calls automatically send fixed-category technical events; do not duplicate those events. For a Skill-only workflow, record one task summary after actual work with `gridzen telemetry record --skill gridzen-select-verification --task <documented-task> --outcome <documented-outcome> --blocker <documented-reason>`, only if consent is already enabled. Omit raw text and personal data; choose unknown rather than infer completion. Do not install a dependency just to report telemetry. The user can disable and clear pending feedback with `gridzen telemetry disable`. Reading these instructions alone is not tracked.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/mexico-pilot-scoper/SKILL.md

@@ -22,3 +22,6 @@ Mexico payout scope remains a bounded draft. No real bank matching route is enab
 ## Optional task feedback
 
 Offline use is not tracked. Offer a category-only local task summary when the user wants to report a blocker: `gridzen feedback --task signup_phone --country US --requested-capability phone_intelligence --outcome blocked --blocker missing_workflow_step --skill gridzen-integrate-sandbox --output task-summary.json`. Choose the actual fixed categories; do not fabricate demand. Inspect the file with the user. Only an explicit user choice permits `gridzen feedback --input task-summary.json --share`; otherwise stop at the local file. Do not include prompts, emails, phone numbers, identity documents, account numbers, credentials or free text. Sharing is self-reported evidence and is not verified customer completion. No hidden upload, background call or new MCP tool is required.
+
+
+Local feedback in kit 0.6.0 is off by default. If the CLI is installed, `gridzen telemetry status` shows consent. Never enable it on the user's behalf without explicit agreement. When enabled, CLI/stdio calls automatically send fixed-category technical events; do not duplicate those events. For a Skill-only workflow, record one task summary after actual work with `gridzen telemetry record --skill mexico-pilot-scoper --task <documented-task> --outcome <documented-outcome> --blocker <documented-reason>`, only if consent is already enabled. Omit raw text and personal data; choose unknown rather than infer completion. Do not install a dependency just to report telemetry. The user can disable and clear pending feedback with `gridzen telemetry disable`. Reading these instructions alone is not tracked.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/payout-policy-designer/SKILL.md

@@ -22,3 +22,6 @@ Payout account matching currently has no real enabled Gridzen route. Keep output
 ## Optional task feedback
 
 Offline use is not tracked. Offer a category-only local task summary when the user wants to report a blocker: `gridzen feedback --task signup_phone --country US --requested-capability phone_intelligence --outcome blocked --blocker missing_workflow_step --skill gridzen-integrate-sandbox --output task-summary.json`. Choose the actual fixed categories; do not fabricate demand. Inspect the file with the user. Only an explicit user choice permits `gridzen feedback --input task-summary.json --share`; otherwise stop at the local file. Do not include prompts, emails, phone numbers, identity documents, account numbers, credentials or free text. Sharing is self-reported evidence and is not verified customer completion. No hidden upload, background call or new MCP tool is required.
+
+
+Local feedback in kit 0.6.0 is off by default. If the CLI is installed, `gridzen telemetry status` shows consent. Never enable it on the user's behalf without explicit agreement. When enabled, CLI/stdio calls automatically send fixed-category technical events; do not duplicate those events. For a Skill-only workflow, record one task summary after actual work with `gridzen telemetry record --skill payout-policy-designer --task <documented-task> --outcome <documented-outcome> --blocker <documented-reason>`, only if consent is already enabled. Omit raw text and personal data; choose unknown rather than infer completion. Do not install a dependency just to report telemetry. The user can disable and clear pending feedback with `gridzen telemetry disable`. Reading these instructions alone is not tracked.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/skills/provider-rights-readiness/SKILL.md

@@ -22,3 +22,6 @@ This is a provider-operation or bring-your-own-provider task. Do not impose this
 ## Optional task feedback
 
 Offline use is not tracked. Offer a category-only local task summary when the user wants to report a blocker: `gridzen feedback --task signup_phone --country US --requested-capability phone_intelligence --outcome blocked --blocker missing_workflow_step --skill gridzen-integrate-sandbox --output task-summary.json`. Choose the actual fixed categories; do not fabricate demand. Inspect the file with the user. Only an explicit user choice permits `gridzen feedback --input task-summary.json --share`; otherwise stop at the local file. Do not include prompts, emails, phone numbers, identity documents, account numbers, credentials or free text. Sharing is self-reported evidence and is not verified customer completion. No hidden upload, background call or new MCP tool is required.
+
+
+Local feedback in kit 0.6.0 is off by default. If the CLI is installed, `gridzen telemetry status` shows consent. Never enable it on the user's behalf without explicit agreement. When enabled, CLI/stdio calls automatically send fixed-category technical events; do not duplicate those events. For a Skill-only workflow, record one task summary after actual work with `gridzen telemetry record --skill provider-rights-readiness --task <documented-task> --outcome <documented-outcome> --blocker <documented-reason>`, only if consent is already enabled. Omit raw text and personal data; choose unknown rather than infer completion. Do not install a dependency just to report telemetry. The user can disable and clear pending feedback with `gridzen telemetry disable`. Reading these instructions alone is not tracked.

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/src/gridzen_developer/__init__.py

@@ -1,2 +1,2 @@
 """Gridzen developer tools. Research and simulation are never live verification."""
-__version__ = '0.5.0'
+__version__ = '0.6.1'

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/src/gridzen_developer/cli.py

@@ -5,6 +5,8 @@ from . import core
 
 def main():
  p=argparse.ArgumentParser(description='Gridzen research + synthetic sandbox (no real provider calls)');s=p.add_subparsers(dest='command',required=True)
+ x=s.add_parser('start',help='Show the free trial, account and integration path; no network calls')
+ x.add_argument('--task',choices=['identity_onboarding','signup_phone'],default='identity_onboarding');x.add_argument('--lang',choices=['en','es','zh'],default='en')
  x=s.add_parser('coverage');x.add_argument('--country');x.add_argument('--capability')
  x=s.add_parser('plan');x.add_argument('--country',required=True);x.add_argument('--event',choices=list(core.EVENTS),default='payout')
  x.add_argument('--task',choices=list(core.TASK_ROUTES));x.add_argument('--stage',choices=['research','prototype','production'],default='prototype')
@@ -18,7 +20,28 @@ def main():
  from .setup import CLIENTS
  x=s.add_parser('setup',help='Prepare six Skills and MCP config for a harness; dry-run until --apply')
  x.add_argument('--client',choices=['all',*CLIENTS],required=True);x.add_argument('--project',default='.');x.add_argument('--apply',action='store_true')
+ x=s.add_parser('telemetry',help='Opt-in local category feedback; no chat, personal fields or credentials')
+ x.add_argument('action',choices=['enable','disable','status','flush','record'])
+ x.add_argument('--consent',action='store_true',help='Explicitly consent to automatic category uploads')
+ x.add_argument('--task',choices=sorted(TASKS),default='unknown');x.add_argument('--skill',choices=sorted(SKILLS),default='unknown')
+ x.add_argument('--outcome',choices=sorted(OUTCOMES),default='unknown');x.add_argument('--blocker',choices=sorted(REASONS),default='unknown')
  a=p.parse_args()
+ if a.command=='start':
+  print(json.dumps({'task':a.task,'trial':'https://gridzen.ai/console/start?lang='+a.lang,'account':'https://gridzen.ai/console/?source=developer_kit&lang='+a.lang,'assistant':'https://gridzen.ai/console/assessment?lang='+a.lang,'tutorials':'https://gridzen.ai/console/learn?lang='+a.lang,'mode':'synthetic_entry','network_calls':0,'verified':False,'real_payments_enabled':False,'measurement':'optional_explicit_consent_in_console; no account tracking by this command'},ensure_ascii=False,indent=2));return
+ if a.command=='telemetry':
+  from . import telemetry
+  try:
+   if a.action=='enable':
+    if not a.consent:p.error('Enabling automatic feedback requires --consent. Fixed categories only; disable anytime.')
+    result=telemetry.configure(True)
+   elif a.action=='disable':result=telemetry.configure(False)
+   elif a.action=='status':result=telemetry.status()
+   elif a.action=='flush':result=telemetry.flush()
+   else:
+    telemetry.observe({'operation':'task_summary','task':a.task,'skill':a.skill,'mode':'local_draft','outcome':a.outcome,'reason':a.blocker})
+    result=telemetry.status()
+  except (OSError,ValueError) as exc:p.error(type(exc).__name__)
+  print(json.dumps(result,indent=2));return
  if a.command=='feedback':
   from .product_feedback import validate_summary
   try:
@@ -43,6 +66,12 @@ def main():
   print(json.dumps(list_skills(),ensure_ascii=False,indent=2));return
  try:
   result={'coverage':lambda:core.coverage(a.country,a.capability),'plan':lambda:core.plan(a.country,a.event,a.task,a.stage),'simulate':lambda:core.simulate(a.country,a.capability,a.scenario),'explain':lambda:core.explain(a.reason_code)}[a.command]()
- except ValueError as e:p.error(str(e))
+ except ValueError as e:
+  from .telemetry import observe
+  observe({'operation':{'coverage':'get_coverage','plan':'plan_verification','simulate':'create_sandbox_verification','explain':'explain_result'}[a.command],'task':getattr(a,'task',None),'country':getattr(a,'country',None),'outcome':'integration_error','reason':'schema_error'})
+  p.error(str(e))
+ from .telemetry import observe
+ blocked=a.command=='plan' and (a.stage=='production' or result.get('task_match_status') in ('unsupported','needs_clarification'))
+ observe({'operation':{'coverage':'get_coverage','plan':'plan_verification','simulate':'create_sandbox_verification','explain':'explain_result'}[a.command],'task':getattr(a,'task',None),'country':getattr(a,'country',None),'capability':result.get('capability',getattr(a,'capability',None)),'stage':getattr(a,'stage','prototype'),'mode':'research' if a.command in ('coverage','plan') else 'synthetic_fixture','outcome':'capability_unavailable' if blocked else 'technical_success','reason':'production_disabled' if blocked and a.stage=='production' else 'unavailable_route' if blocked else 'none'})
  print(json.dumps(result,ensure_ascii=False,indent=2))
 if __name__=='__main__':main()

{gridzen_developer_kit-0.5.0 → gridzen_developer_kit-0.6.1}/src/gridzen_developer/mcp.py

@@ -27,7 +27,7 @@ class GridzenMCP(MCPServer):
   for tool in tools:tool.input_schema['additionalProperties']=False
   return tools
 
-server=GridzenMCP('Gridzen Developer Kit',version='0.5.0',website_url='https://gridzen.ai/developers/',middleware=[strict_arguments],instructions='Research and synthetic fixtures only. No live providers are enabled. Preserve verified=false; never use a sandbox result to approve a real person or payment.')
+server=GridzenMCP('Gridzen Developer Kit',version='0.6.1',website_url='https://gridzen.ai/developers/',middleware=[strict_arguments],instructions='Research and synthetic fixtures only. No live providers are enabled. Preserve verified=false; never use a sandbox result to approve a real person or payment.')
 read=ToolAnnotations(readOnlyHint=True,destructiveHint=False,idempotentHint=True,openWorldHint=False)
 @server.tool(annotations=read,structured_output=True)
 def get_coverage(country: str | None=None, capability: str | None=None) -> dict[str, Any]:
@@ -50,5 +50,27 @@ def explain_result(reason_code: str) -> dict[str, Any]:
  """Explain a sandbox reason code; missing data and timeout remain inconclusive."""
  return core.explain(reason_code)
 TOOLS={fn.__name__:fn for fn in (get_coverage,plan_verification,create_sandbox_verification,get_sandbox_verification,explain_result)}
-def main():server.run(transport='stdio')
+async def local_feedback(ctx, call_next):
+ from .telemetry import observe
+ import asyncio
+ params=ctx.params if isinstance(ctx.params,dict) else {}
+ args=params.get('arguments') if isinstance(params.get('arguments'),dict) else {}
+ dims={'operation':params.get('name'),'task':args.get('task'),'country':args.get('country'),'capability':args.get('capability'),'stage':args.get('stage','prototype'),'mode':'research' if params.get('name') in ('get_coverage','plan_verification') else 'synthetic_fixture'}
+ try: result=await call_next(ctx)
+ except Exception:
+  if ctx.method=='tools/call':await asyncio.to_thread(observe,{**dims,'outcome':'integration_error','reason':'tool_error'})
+  raise
+ if ctx.method=='tools/call':
+  content=getattr(result,'structured_content',None) or {}
+  blocked=content.get('requested_stage')=='production' or content.get('task_match_status') in ('unsupported','needs_clarification')
+  failed=getattr(result,'is_error',False)
+  await asyncio.to_thread(observe,{**dims,'capability':content.get('capability',dims['capability']),'outcome':'integration_error' if failed else 'capability_unavailable' if blocked else 'technical_success','reason':'tool_error' if failed else 'production_disabled' if blocked and content.get('requested_stage')=='production' else 'unavailable_route' if blocked else 'none'})
+ return result
+
+def main():
+ from .telemetry import enabled
+ if enabled():
+  read.open_world_hint=True
+ server.middleware.insert(0,local_feedback)
+ server.run(transport='stdio')
 if __name__=='__main__':main()