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: `private` and `hidden` match 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 ID and title;
- 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;
- public/unlisted/private status;
- 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, link-only visibility, broad BaaS configuration, asset
replacement or 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 private/
hidden when the quality gates do not pass.