內容簡介
Npcink Cloud Addon 將本地 WordPress 網站連接至 npcink-cloud，提供雲端 API 金鑰管理、健康檢查、事件監控等功能，協助網站管理員有效監控外掛行為及雲端服務。
【主要功能】
• 連接 npcink-cloud 服務
• 上傳外掛操作元數據
• 健康檢查與狀態監控
• 支援雲端 API 金鑰管理
• 限制資料上傳以保護隱私
外掛標籤
開發者團隊
原文外掛簡介
Npcink Cloud Addon connects a local WordPress site to npcink-cloud.
It stores the Cloud Base URL and Cloud API Key, parses Cloud-issued keys, signs runtime requests, probes health, reads Cloud entitlement summaries, and can upload metadata-only plugin behavior events after explicit administrator opt-in.
It does not execute WordPress writes, approve proposals, own billing truth, or manage prompts, routers, presets, workflow/task queues, scheduler truth, or workflow engines. Its observability buffer is only a bounded delivery buffer for monitoring metadata and is not Core audit, proposal, execution, billing, or workflow truth.
For media derivative jobs, local host code may pass the read-only
npcink-abilities-toolkit/build-media-derivative-cloud-request ability output and a short TTL
source artifact descriptor to the addon for signed Cloud dispatch. The addon
requires verified Cloud settings, rejects credential-bearing ability payloads,
and returns proposal-ready data with final_write_owner=local_wordpress_host.
Final review, recording, replacement, rollback, and WordPress writes remain in
the local host/Core approval path.
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.
External Services
This plugin connects to the Npcink Cloud service configured by the site administrator through the Cloud Base URL setting.
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.
For host-supplied media derivative runtime jobs, requests may also include a
short TTL source artifact descriptor and derivative request parameters from the
local read-only ability output. Cloud credentials and signed headers are added
by the addon transport and are not copied into the 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.
The configured Cloud service is responsible for its own privacy policy, terms of service, data retention, and account/key issuance. Because the Cloud Base URL is administrator-configured, site administrators should only connect this plugin to a Cloud service whose terms of service, privacy policy, data retention policy, and account/key issuance process they have reviewed.
Npcink Cloud service information:
Terms of Service: https://cloud.npc.ink/terms/en/terms.html
Privacy Policy: https://cloud.npc.ink/terms/en/privacy.html
Data Retention: https://cloud.npc.ink/terms/en/data-retention.html
