Npcink

<p>Npcink Abilities Toolkit provides a standalone toolkit for plugin authors who want to expose safe, agent-callable abilities through the WordPress Abilities API.</p>
<p>The plugin owns ability registration helpers, category helpers, schema normalization, annotation normalization, and optional canonical projection for Npcink AI when Npcink AI is installed.</p>
<p>It can be used by any WordPress plugin or client that consumes the WordPress Abilities API. Npcink AI is one optional consumer, not the owner of this plugin.</p>
<p>It does not own model routing, cloud execution, billing, quota, workflow runtime, MCP governance, or final write approval/governance.</p>
<p>Read-only host composition recipe metadata may document how hosts can compose abilities, but those records do not run queues, schedule jobs, execute workflows, or create a second registry.</p>
<p>Host composition recipe metadata is available through read-only helpers and Abilities API discovery abilities for hosts that need catalog discovery without execution ownership.</p>
<h3>External Services and Remote Requests</h3>
<p>This plugin does not automatically contact Npcink AI, model providers, analytics services, tracking services, or cloud services.</p>
<p>Some abilities can prepare request payloads for a separate host or cloud add-on, but this plugin does not send those payloads to an external service by itself.</p>
<p>The <code>npcink-abilities-toolkit/upload-media-from-url</code> ability can download a media file from a URL provided by an authenticated caller when an approved host runtime commits that ability. In that case WordPress sends an HTTP request to the caller-provided URL in order to fetch the media file for the local media library. The remote endpoint is chosen by the caller, not by this plugin.</p>
<h3>Requirements</h3>
<ul>
<li>WordPress 7.0 or later. This release intentionally targets the WordPress Abilities API baseline available in WordPress 7.0+.</li>
<li>PHP 8.0 or later.</li>
</ul>
<h3>Public API</h3>
<ul>
<li><code>npcink_abilities_toolkit_register_category( $category_id, $args )</code></li>
<li><code>npcink_abilities_toolkit_register_readonly( $ability_id, $definition )</code></li>
<li><code>npcink_abilities_toolkit_register_write_proposal( $ability_id, $definition )</code></li>
<li><code>npcink_abilities_toolkit_normalize_schema( $schema, $default_type )</code></li>
<li><code>npcink_abilities_toolkit_normalize_annotations( $annotations, $risk_level )</code></li>
<li><code>npcink_abilities_toolkit_get_registered()</code></li>
<li><code>npcink_abilities_toolkit_get_workflow_definitions()</code></li>
<li><code>npcink_abilities_toolkit_get_workflow_definition( $recipe_id )</code></li>
</ul>
<h3>Admin Page</h3>
<p>After activation with a Npcink AI host plugin, open Npcink AI -> Abilities in wp-admin. When this standalone package is installed without a Npcink AI host menu, open Tools -> Abilities API Packages instead.</p>
<p>The page verifies Abilities API availability, shows the registered ability catalog, provides copyable REST endpoint values for host/client setup, and can run two official read-only checks: site info and bounded redacted diagnostics summary. It is a connection and discovery surface; it does not run showcase workflows, model calls, write abilities, or demo abilities.</p>
<h3>Built-In Abilities</h3>
<p>The plugin includes migrated low-risk WordPress read abilities, deterministic comment helpers, and host-governed WordPress write/destructive abilities using canonical <code>npcink-abilities-toolkit/*</code> ids.</p>
<p>It also includes <code>npcink-abilities-toolkit/wp-diagnostics-summary</code>, a redacted WordPress-only diagnostics summary for Abilities API clients. This summary intentionally omits Npcink AI settings, MCP settings, API keys, database names, table prefixes, filesystem paths, error logs, and external HTTP probes.</p>
<p>It also includes <code>npcink-abilities-toolkit/search-posts</code> and <code>npcink-abilities-toolkit/search-post-meta</code>, bounded local WordPress search helpers for keyword and explicit post-meta discovery. These are read-only helpers and do not call external search indexes or mutate content.</p>
<p>It also includes <code>npcink-abilities-toolkit/list-workflow-recipes</code> and <code>npcink-abilities-toolkit/get-workflow-recipe</code>, read-only host composition recipe metadata discovery abilities. These expose metadata only and do not execute workflow runtime behavior.</p>
<p>Core governance handoff docs include a catalog snapshot, permission matrix, and schema boundary audit for hosts that consume this plugin through <code>npcink-ai-core</code>.</p>
<h3>Developer Verification</h3>
<p>When the plugin is installed in a local WordPress site, run:</p>
<pre><code>WP_PATH=/path/to/wordpress composer smoke:wp
</code></pre>
<p>For isolated bounded-chain performance validation, run:</p>
<pre><code>composer perf:smoke
</code></pre>


Npcink Abilities Toolkit

Standalone WordPress Abilities API package toolkit for registering agent-callable abilities.

Ibrahim

<p>Tessera is a developer library for plugin authors who register abilities via <code>wp_register_ability()</code> and want snapshot capture, audit logging, approval workflows, and one-click rollback for every invocation across REST, MCP, internal PHP, and WP-CLI without building it themselves.</p>
<p>Declare what state your ability touches; Tessera handles the safety wrapper.</p>
<h4>What you get out of the box</h4>
<ul>
<li><strong>Pre + post snapshots.</strong> Every safety-enabled invocation captures declared state before the callback and (on success) after, so the audit log can show a real diff.</li>
<li><strong>Audit log.</strong> One row per invocation with ability name, caller (REST/MCP/CLI/internal), user, args, result, status, duration, pre/post hashes, and parent_invocation_id for nested calls.</li>
<li><strong>One-click rollback.</strong> Restore captured state from post_meta, options, taxonomy term assignments, user roles + caps. File contents support tiered drift detection (mtime / mtime_size / critical_hash / full_hash) plus opt-in real byte-level rollback via <code>full_content</code> strategy.</li>
<li><strong>Drift check on rollback.</strong> Live state is hashed and compared to the snapshot’s post-state before restoring; if they differ the rollback returns an error unless forced.</li>
<li><strong>Concurrency lock.</strong> Capture + execute is serialised per surface set via a MySQL advisory lock so two simultaneous invocations do not capture each other’s mid-states.</li>
<li><strong>Encrypted redaction.</strong> Scrub secrets out of args, results, and snapshots. Stores redacted values as AES-256-GCM envelopes so rollback can still restore them.</li>
<li><strong>Approval queue.</strong> When <code>safety.requires_approval</code> is set, the wrapper blocks execution and returns a 202 pending response. A human approves or rejects via wp-admin, WP-CLI, or REST. Multi-stage sequential or parallel approval chains are supported.</li>
<li><strong>Multisite support.</strong> Each subsite gets its own set of <code>wp_<N>_abilityguard_*</code> tables, with auto-install on <code>wp_initialize_site</code> and auto-drop on <code>wpmu_drop_tables</code>.</li>
<li><strong>Retention.</strong> Daily WP-Cron prunes old log rows (defaults: 30 days normal, 180 days destructive) and orphaned snapshots.</li>
</ul>
<h4>Surfaces</h4>
<ul>
<li><strong>PHP API</strong> with <code>wp_register_ability( $name, [ ..., 'safety' => [...] ] )</code> and helpers <code>abilityguard_rollback</code>, <code>abilityguard_snapshot_meta</code>, <code>abilityguard_snapshot_options</code>.</li>
<li><strong>REST</strong>: <code>/abilityguard/v1/log</code>, <code>/log/<id></code>, <code>/log/export</code>, <code>/rollback/<id></code>, <code>/rollback/bulk</code>, <code>/approval</code>, <code>/approval/<id>/approve</code>, <code>/approval/<id>/reject</code>, <code>/approval/bulk</code>, <code>/approval/export</code>, <code>/retention</code>, <code>/retention/prune</code>, <code>/health</code>.</li>
<li><strong>WP-CLI</strong>: <code>wp abilityguard log list/show</code>, <code>wp abilityguard rollback <id></code>, <code>wp abilityguard approval list/approve/reject <id></code>, <code>wp abilityguard prune</code>.</li>
<li><strong>wp-admin</strong>: Tools > Tessera. Hybrid timeline + command-palette search, snapshot drawer, JSON-highlighted Input/Result tabs, invocation chain navigation, and real rollback against the captured snapshot.</li>
</ul>
<h4>Example</h4>
<pre><code>wp_register_ability( 'my-plugin/update-product-price', array(
    'label'               => 'Update product price',
    'description'         => 'Updates the price on a WooCommerce product.',
    'category'            => 'woocommerce',
    'input_schema'        => array( /* ... */ ),
    'permission_callback' => fn() => current_user_can( 'manage_woocommerce' ),
    'execute_callback'    => fn( $args ) => update_post_meta( $args['product_id'], '_price', $args['price'] ),
    'safety' => array(
        'destructive'       => true,
        'requires_approval' => false,
        'snapshot'          => fn( $input ) => array(
            'post_meta' => array( $input['product_id'] => array( '_price', '_regular_price' ) ),
            'options'   => array( 'woocommerce_last_price_change' ),
        ),
    ),
) );
</code></pre>
<h4>Documentation</h4>
<p>Full plugin-author documentation lives at the GitHub repo: https://github.com/ibrahimhajjaj/abilityguard</p>
<h3>Source Code</h3>
<p>The full source for Tessera, including the unminified React source for the admin app, lives on GitHub: https://github.com/ibrahimhajjaj/abilityguard</p>
<ul>
<li>The admin bundle <code>assets/admin.js</code> is compiled from <code>assets/admin.jsx</code> (React + JSX, no preprocessor magic beyond JSX).</li>
<li>The bundler is <a href="https://esbuild.github.io/" rel="nofollow ugc">esbuild</a>, configured in <code>scripts/build.mjs</code>.</li>
<li>To rebuild the admin bundle from a fresh checkout, run <code>npm install</code> once, then <code>npm run build</code> whenever <code>assets/admin.jsx</code> changes. This regenerates <code>assets/admin.js</code> in place.</li>
<li>The release zip published to the WordPress.org directory is produced by <code>scripts/build-release.sh</code>, which excludes development artifacts (tests, examples, build configs) but keeps everything required for the plugin to run.</li>
</ul>


Tessera for the Abilities API

Snapshot, audit, and rollback layer for plugins that register abilities via the WordPress Abilities API.

Npcink Abilities Toolkit vs Tessera for the Abilities API