ZZD public AI gateway · zzd_public_ai_gateway_v3
Resource: 14 · Validation and final handoff / 交付
Canonical map: https://zzd.show/docs/ai/map.json
Full handbook: https://zzd.show/llms-full.txt
REST capabilities: https://zzd.show/api/v1/capabilities/

# Validation matrix and final handoff

Before saying "deployed", verify applicable rows:

- environments: blank desktop, blank mobile, real editor preview
  iframe, ordinary embed iframe;
- phases: loader, ready, settled, empty, denied, offline, error;
- scroll: start, intermediate checkpoints, end, and reverse;
- input: hover, pointer, click, keyboard, wheel/touch, drag/slider;
- state: menu, modal, detail, route, return, recursive next phases;
- media: image currentSrc/dimensions, video readiness/time/error,
  audio mute/autoplay fallback, canvas/WebGL nonblank and motion;
- runtime: console, page error, unhandled rejection, request failure,
  4xx/5xx, external/source hosts, anchors/forms, overflow;
- source: meaningful live Pieces own structure/content/state/motion;
- assets: all needed runtime files are managed, described, and bound;
- private asset lifecycle: draft owner access, publication promotion,
  and public-copy removal on re-draft behave as documented;
- BaaS: allowed/denied, schema, idempotency, empty/error/job/realtime;
- rights/privacy: license, consent, no secrets or private data;
- publication: canonical `visibility` matches user intent;
- thumbnail: fresh final usable state, not loader or stale image.

A completed agent response should include:

- outcome and current lifecycle state;
- REST capabilities URL/API version used and the non-secret local
  credential profile name, never the bearer value;
- Show title, PK (`id`) and Work ID (`public_id`) as explicit,
  copyable text, never identifiers hidden only inside URLs;
- edit, detail, blank, and embed URLs returned by ZZD;
- architecture and Piece map;
- uploaded assets, bindings, dependencies, and remaining external
  runtime dependencies;
- BaaS resources/services and access behavior, if any;
- validation environments, meaningful interactions, console/network
  status, and notable fixes;
- canonical public/private visibility;
- Sale/listing status, only if requested;
- remaining risks, known differences, and rollback/maintenance notes.

If REST v1 could not perform an operation, name the supported UI
handoff explicitly. Typical current examples are favicon/component
controls, broad BaaS configuration, asset deletion, thumbnail
deletion, collection detach/
deletion, Sale management, and all destructive deletion. Verified
thumbnail upload/replacement is available in REST v1 and is not a UI
handoff. Never describe an invented endpoint as work completed.

Do not claim success if a required environment or meaningful state
was not checked. Say exactly what remains and keep the Show at
`visibility="private"` when the quality gates do not pass.

每次围绕具体作品的普通用户进度、部署、修复、回退和最终回复，都显式给出作品名称、PK（真实id）、UID/作品号（真实public_id）、API返回的正式打开链接和实际状态。优先复制 data.delivery.feedback_line；英文用 feedback_line_en。PK与作品号须是可复制文本，不能只藏在Run/Edit链接中，也不能只回复名称和链接。缺字段时沿用原身份GET同一已有作品补取，不造号、不建替代作品、不重领或注册worker、不额外向用户要授权。尚未创建就明确标识尚未取得，取得后立即补回；批量逐项给出，修复沿用原标识。私有作品注明需原有访问权限；普通链接和作品号不授予访问权，不附凭据、share token或runtime ticket。不得把计划/保存/清单核验冒称已部署或页面验收通过。交付表中分别写新站点名称与原站/原模板具体名称，未知原站写待核实，不猜测。reply_instruction/delivery仅用于普通回复，不回填manifest或严格JSON工具契约，也不在严格JSON输出前添加自然语言。漏报就补齐回复，不增加服务端拒绝、设备确认或审批流程。
In every normal user-facing progress update, deployment, repair, rollback and final handoff about a Show, explicitly display its title, PK (id), Work ID (public_id), API-returned canonical open link and actual state. Prefer data.delivery.feedback_line_en (feedback_line for Chinese). Both identifiers must be copyable text, not only part of a Run/Edit URL. Retrieve missing fields with the existing authorized GET for the same Show; do not invent IDs, create a replacement, register/claim again or ask for extra authorization. Report each Show separately and retain its identity across revisions. Note when original private access is required. Never append credentials, share tokens or runtime tickets. Distinguish planning, saving, manifest verification and actual browser/deployment results. Name the new site and the specific original site/template separately when tabulating; mark unknown source names unverified. delivery/reply_instruction are presentation guidance, not manifest or strict JSON input fields. Remedy an omitted identifier in the reply without adding a deployment gate.