Npcink AI Client Adapter

Changelog

0.4.2

• Reject non-numeric limit query parameters on proposal and sensitive read-request list routes with the standard WordPress REST 400 error envelope instead of silently coercing them to 1.
• Unify consumer-facing REST error details and complete /help and connection-manifest discovery for the shipped route surface, including actionable administrator-session and malformed-id responses.
• Synchronize consumer documentation with the 26 explicit post-Core execution profiles and add a route-drift release gate.
• Surface missing dependencies, contract mismatches, and recent client errors in the Adapter admin page; clean up tracked fallback Application Password credentials on revocation and uninstall.
• Mark the 0.4.0 administrator-session restriction for unified approve-and-execute as a breaking change for signed clients.

0.4.1

• Verification integrity with Governance Core 0.3.0 (ADR-012/ADR-013): executions request execution-attached verification reads at commit preflight and present them on action results; after execution, block readbacks that could not be verified get a Core-recorded, result-bound second chance (provisional-record supplement), so objects created inside the same batch verify through Core-minted evidence instead of degrading. The recorded readback metadata always reflects the latest attempt, and the supplement re-runs log through the same request context as the first pass. Verification-read features require Governance Core 0.3.0 or newer.
• Adopt the Governance Core 0.2.x/0.3.0 REST contract changes: recoverable preflight handoffs (409 envelope with correlation id and expiry), app_auth_expired hints, the 429 retry relay honoring delay-seconds Retry-After, contract:read fallback, and audit offset passthrough.
• Administrator review hardening from the 2026-10 AI review backlog: server-side ability_id enforcement on governed routes, hardened governed-write locks and handoff consumption, structured CLI schema enforcement with redaction, and admin-surface fixes.
• Complete the zh_CN catalog (0 fuzzy, 0 untranslated) and gate translation coverage at release.
• Split the controller into behavior-preserving domain services (signing auth, execution records, upstream dispatch, dependency status, preflight handoffs, read governance, proposal review, contract metadata) and promote static analysis (PHPStan, PHPCS) plus the delivered-review triage gate to required CI.
• Return structured, actionable authentication errors for signed requests: credential completeness, clock skew, and body-hash mismatches now carry distinct stable codes with reason and next_step data instead of a generic rest_forbidden; key-record and signature failures share one pre-verification code so key liveness is never observable without the private key; scope and nonce-replay causes are reported only after the signature verifies. Requests without credentials receive npcink_openclaw_adapter_authentication_required pointing at the device-pairing entry, and logged-in non-administrator accounts receive npcink_openclaw_adapter_privilege_required.
• Pairing rate-limit responses now set the standard Retry-After response header alongside the existing error data.
• Remove stale GET /terms/GET /term purpose strings from /help route discovery.
• Companion CLI 0.6.0: failed Adapter responses now print the full error envelope including data.operator_feedback, next_step, and retry_after (redacted); the bounded AI image ratio crop recipe helper now mirrors the reviewed recipe contract locally because Adapter /help no longer carries recipe playbooks.

0.4.0

• Restrict the unified approve-and-execute action to WordPress administrator sessions. Signed AI clients now wait for human approval in the Npcink Governance Core admin and then call the execute route; signed attempts on the unified route fail closed with npcink_openclaw_adapter_approve_requires_admin_session.
• Add client_policy.boundary_enforcement (client policy version 2) so clients can distinguish enforced key-pair connections from conventional WordPress-native credentials.
• Add the connection readiness checklist and CLI boundary status reporting.
• Document the governed MCP tool surface of the companion CLI (@npcink/openclaw-adapter-cli 0.5.0): read, propose, preflight, and execute-after-human-approval tools only, with no self-approval tool.

0.3.3

• Harden release packaging, uninstall cleanup, and batch execution contract checks.
• Preserve actionable, redacted CLI output when the signed local acceptance fixture fails.

0.3.2

• Close the release-candidate boundary by keeping media derivative transport outside Adapter and retaining only reviewed adoption handoff.
• Require explicit signed-client execute scope for final Adapter write routes.
• Restore Core capability forwarding and default execution response compatibility for consumer smoke coverage.

0.3.1

• Bind Adapter final execution to Core approval and commit-preflight execution handoffs.
• Forward signed local client fingerprints to trusted Core app-token requests and fail closed on mismatched Core contexts.
• Validate Core dependency contract semantics for site and signed-client bindings before reporting dependency readiness.

0.3.0

• Add Adapter-declared Core and Abilities Toolkit compatibility floors to the machine-readable contract metadata.
• Record a signed local AI client create-draft proposal, approve-and-execute, readback, and cleanup acceptance pass.

0.2.1

• Add contract snapshot smoke coverage across health, help, and connection manifest responses.
• Reject batch write actions that request core_proxy_execute=true before Adapter execution.
• Expand negative smoke coverage for core_proxy_execute and commit_execution batch fail-closed behavior.

0.2.0

• Add machine-readable Adapter contract metadata and stable contract hashes on health, help, and manifest responses.
• Add the local AI client acceptance command for non-destructive Adapter/Core boundary checks.
• Align block theme visual acceptance, batch review feedback, and release package smoke documentation with the governed execution profile boundary.

0.1.1

• Add local AI client CLI helper commands, output redaction, and machine-readable client policy.

0.1.0

• Initial thin AI client adapter for Npcink Governance Core and WordPress Abilities API routing.