Npcink Cloud Addon

描述

Npcink Cloud Addon 将本地 WordPress 站点连接到 npcink-cloud。

它会存储 Cloud Base URL 和 Cloud API Key，解析 Cloud 签发的密钥，签名运行时请求，探测健康状态，读取 Cloud 权益摘要，并可在管理员明确选择启用后上传仅元数据的插件行为事件。

它不执行 WordPress 写入、不审批提案、不拥有计费事实，也不管理提示词、路由、预设、工作流/任务队列、调度事实或工作流引擎。它的可观测性缓冲区只是用于监控元数据的受限投递缓冲区，不是 Core 审计、提案、执行、计费或工作流事实来源。

对于媒体衍生任务，本地主机代码可以将只读的 npcink-abilities-toolkit/build-media-derivative-cloud-request ability 输出和短 TTL 的源 artifact 描述符传给 addon，用于签名后的 Cloud 派发。addon 要求 Cloud 设置已通过验证，会拒绝携带凭据的 ability payload，并返回包含 final_write_owner=local_wordpress_host 的提案就绪数据。最终审阅、记录、替换、回滚和 WordPress 写入仍保留在本地主机/Core 审批路径中。

For plugin monitoring, the addon may upload operational metadata such as plugin
slug/version, event kind, status, timing, error code, route, proposal id,
ability id, correlation id, and counters. It must not upload prompts,
generated content, article body content, media bytes, raw request or response
payloads, provider credentials, Cloud API secrets, passwords, cookies, nonces,
Authorization headers, database names, table names, or filesystem paths.
Customer-journey monitoring is limited to supported editor steps such as
generation started, succeeded, failed, retried, accepted, saved, or abandoned.
It does not send raw WordPress user or post IDs, email addresses, URLs, DOM
data, or free-form error messages. Uploads are authenticated to the configured
Cloud site, so they may be associated with that site; they are not used for
advertising, individual user scoring, or automatic WordPress content changes.

外部服务

此插件通过 Cloud Base URL 设置连接到站点管理员配置的 Npcink Cloud 服务。

The plugin contacts the configured Cloud service after Portal authorization and connection verification, or when an administrator uses the advanced recovery form with a Cloud Base URL and API key. A local Npcink component may also explicitly use the Cloud runtime client.

Requests may include the configured site identifier, key identifier, request timestamp, nonce, trace identifier, idempotency key, HMAC signature headers, and read-only requests for health, run status, run result, usage statistics, entitlement summaries, observability summaries, and Agent feedback quality summaries. WordPress AI/runtime requests can include the prompt, source text, and task configuration supplied for that operation. Optional metadata-only monitoring is separate and does not include prompt or content data. The stored Cloud API Key secret is used server-side for request signing and is not printed in wp-admin.

对于主机提供的媒体衍生运行时任务，请求还可能包含短 TTL 的源 artifact 描述符，以及来自本地只读 ability 输出的衍生请求参数。Cloud 凭据和签名请求头由 addon 传输层添加，不会复制到 ability payload 中。

For Site Knowledge transport, requests may include public post/page identifiers,
public article/page content and public metadata when delivery is enabled, approved
comment change hints, local delivery consent state, and explicit administrator
delivery intents for Cloud-owned index operations. Drafts, private posts,
password-protected posts, credentials, and raw database fields must not be sent.

The Site Knowledge change bridge health seam returns
site_knowledge_change_bridge_status.v1. Local consumers should surface it as
change_bridge and treat buffer_count as bounded delivery-buffer depth only,
not queue truth, freshness truth, index lifecycle truth, or Cloud diagnostics
truth.

For WordPress AI connector scene runtime, image context evidence, Runtime Runs
detail, artifact preview download, and Agent feedback event transport, requests
may include the bounded scene request, media URL or artifact descriptor, run id,
artifact id, or local operator feedback metadata needed for that specific Cloud
runtime/read endpoint. The addon does not create Core proposals, approve
changes, execute WordPress writes, own retry queues, or own Site Knowledge index
lifecycle.

已配置的 Cloud 服务负责其自身的隐私政策、服务条款、数据保留和账号/密钥签发。由于 Cloud Base URL 由管理员配置，站点管理员只应将此插件连接到已经审阅过服务条款、隐私政策、数据保留政策以及账号/密钥签发流程的 Cloud 服务。

Npcink Cloud 服务信息：

• 服务条款：https://cloud.npc.ink/terms/en/terms.html
• 隐私政策：https://cloud.npc.ink/terms/en/privacy.html
• 数据保留：https://cloud.npc.ink/terms/en/data-retention.html