{"id":333624,"date":"2026-07-03T01:35:31","date_gmt":"2026-07-03T01:35:31","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/npcink-toolbox\/"},"modified":"2026-10-11T13:58:21","modified_gmt":"2026-10-11T13:58:21","slug":"npcink-workflow-toolbox","status":"publish","type":"plugin","link":"https:\/\/fa-af.wordpress.org\/plugins\/npcink-workflow-toolbox\/","author":16786901,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.6.0","stable_tag":"0.6.0","tested":"7.1.3","requires":"6.9","requires_php":"8.0","requires_plugins":null,"header_name":"Npcink Workflow Toolbox","header_author":"Npcink","header_description":"Fixed AI workflow buttons for WordPress operators, with review-only suggestions and governed handoff plans.","assets_banners_color":"cacbcc","last_updated":"2026-10-11 13:58:21","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":554,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.1.1":{"tag":"0.1.1","author":"muze233","date":"2026-07-03 01:35:02","revision":3594652},"0.3.0":{"tag":"0.3.0","author":"muze233","date":"2026-10-01 19:49:25","revision":3723781},"0.4.0":{"tag":"0.4.0","author":"muze233","date":"2026-10-06 09:43:34","revision":3730454},"0.5.0":{"tag":"0.5.0","author":"muze233","date":"2026-10-07 04:46:21","revision":3731876},"0.5.1":{"tag":"0.5.1","author":"muze233","date":"2026-10-07 18:36:47","revision":3733201},"0.5.2":{"tag":"0.5.2","author":"muze233","date":"2026-10-08 01:37:01","revision":3733528},"0.5.3":{"tag":"0.5.3","author":"muze233","date":"2026-10-08 12:03:11","revision":3734482},"0.6.0":{"tag":"0.6.0","author":"muze233","date":"2026-10-11 13:58:21","revision":3739544}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3594652,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3594652,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3594652,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3594652,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.1","0.3.0","0.4.0","0.5.0","0.5.1","0.5.2","0.5.3","0.6.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3594652,"resolution":"1","location":"assets","locale":"","width":1440,"height":1000},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3594652,"resolution":"2","location":"assets","locale":"","width":1440,"height":1000},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3594652,"resolution":"3","location":"assets","locale":"","width":1440,"height":1000},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3594652,"resolution":"4","location":"assets","locale":"","width":1280,"height":720}},"screenshots":[]},"plugin_section":[262246],"plugin_tags":[2353,529,96456,84,186],"plugin_category":[50,55],"plugin_contributors":[265919],"plugin_business_model":[],"class_list":["post-333624","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-ai","plugin_tags-content","plugin_tags-editorial-workflow","plugin_tags-media","plugin_tags-seo","plugin_category-media","plugin_category-seo-and-marketing","plugin_contributors-muze233","plugin_committers-muze233"],"banners":{"banner":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/banner-772x250.png?rev=3594652","banner_2x":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/banner-1544x500.png?rev=3594652","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/icon-128x128.png?rev=3594652","icon_2x":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/icon-256x256.png?rev=3594652","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/screenshot-1.png?rev=3594652","caption":""},{"src":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/screenshot-2.png?rev=3594652","caption":""},{"src":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/screenshot-3.png?rev=3594652","caption":""},{"src":"https:\/\/ps.w.org\/npcink-workflow-toolbox\/assets\/screenshot-4.png?rev=3594652","caption":""}],"raw_content":"<!--section=description-->\n<p>Npcink Workflow Toolbox helps WordPress operators turn proven AI-assisted\ncontent and site-operations practices into fixed, review-only buttons.<\/p>\n\n<p>The plugin provides a WordPress admin surface and post-editor panel for:<\/p>\n\n<ul>\n<li>a Dashboard Zhihu hot-topic pool for deciding what may be worth researching\ntoday before any draft generation or publishing decision;<\/li>\n<li>read-only Zhihu capability checks for connected Cloud search, hot-list, and\ndirect-answer lanes;<\/li>\n<li>writing preparation, title ideas, outline support, summary suggestions, and\npublish-readiness checks;<\/li>\n<li>one article writing pack contract for URL, typed manual, or mixed inputs,\ncombining optional exact-source evidence with related site knowledge,\nstructured human review, and an optional confirmed plain-text draft preview\nthat may be loaded only into an empty current Gutenberg body and is never\nsaved or published automatically;<\/li>\n<li>a compact default URL flow that blocks metadata or navigation-only captures\nbefore drafting and keeps brief\/evidence details in optional disclosures;<\/li>\n<li>SEO, AEO, and GEO guidance from operator-maintained site context;<\/li>\n<li>existing-category and existing-tag recommendations for review;<\/li>\n<li>internal-link candidates and source-coverage notes;<\/li>\n<li>image-source candidates, reviewed hosted image candidates, current-article\nmedia ALT\/caption review sets, and media planning handoff packets;<\/li>\n<li>a contextual single-image optimization workbench with verified previews,\nformat\/crop controls, reusable text or logo watermark templates, an optional\nsafe output basename, request-scoped Toolkit replacement, automatic rollback\nbackups, visible restore review, and a bounded 30- or 90-day retention choice;<\/li>\n<li>Cloud-managed site knowledge search, status, and sync requests when a\ncompatible host runtime is connected;<\/li>\n<li>review-only Scheduled Review previews, with Cloud runtime inspection and recovery routed to Cloud Addon;<\/li>\n<li>scoped editor access so authors and editors can run the post editor's\nsuggestion-only content-support flows without administrator rights;<\/li>\n<li>read-only comment moderation and flagged media review sets that send one\nbounded sample to the Cloud runtime and render suggestion-only\nclassifications or safety statuses without changing comment status or media.<\/li>\n<\/ul>\n\n<p>Toolbox returns suggestions, candidates, previews, and planning artifacts. It\ndoes not publish posts, approve proposals, import media, create terms, update SEO\nmetadata, mutate media metadata, or run a local workflow queue as part of the\ndefault content-support flow.<\/p>\n\n<p>When a write-like action is needed, Toolbox prepares a governed handoff plan for\nthe host's Npcink Governance Core, OpenClaw Adapter, and WordPress Abilities\nstack. Final approval, preflight, audit, and WordPress writes remain outside\nToolbox.<\/p>\n\n<h4>Good Fit<\/h4>\n\n<p>Npcink Workflow Toolbox is useful when:<\/p>\n\n<ul>\n<li>editors want AI-assisted content checks without one-click publishing;<\/li>\n<li>administrators need fixed buttons for repeatable review workflows;<\/li>\n<li>editors want a low-friction \"what should we research today?\" surface backed\nby a connected Cloud hot-list runtime;<\/li>\n<li>a site uses Npcink Cloud or a host-provided runtime for web search, image\ncandidates, site knowledge, or hosted AI suggestions;<\/li>\n<li>accepted changes must stay reviewable and auditable before any WordPress write.<\/li>\n<\/ul>\n\n<h4>Not A Good Fit<\/h4>\n\n<p>Npcink Workflow Toolbox is not a standalone article generator, SEO autopilot,\nmedia import bot, indexing system, or workflow scheduler. Cloud-backed features\nrequire a connected Npcink Cloud Addon or compatible host runtime. Without that\nruntime, the plugin still shows local settings, context forms, and review-only\nlocal planning surfaces, but Cloud-managed searches and AI runtime actions fail\nclosed.<\/p>\n\n<h3>External Services<\/h3>\n\n<p>Npcink Workflow Toolbox can contact external services only after an\nadministrator uses a feature that requires the connected service or configures\nthe related runtime. The plugin does not load third-party JavaScript or CSS from\nthose services.<\/p>\n\n<h4>Npcink Cloud runtime<\/h4>\n\n<p>Used for Cloud-managed web search, image-source candidates, site knowledge\nsearch\/sync\/status, hosted AI content-support suggestions, reviewed hosted\nimage candidates, and Cloud Addon Runtime Runs inspection details.<\/p>\n\n<p>Npcink Workflow Toolbox is designed to work with the official Npcink hosted\nruntime service, Npcink Cloud. The plugin does not include or hard-code a Cloud\nservice endpoint. A site administrator connects to Npcink Cloud through a\ncompanion connector such as Npcink Cloud Addon, or a host may provide an\nequivalent runtime through documented filters.<\/p>\n\n<p>Npcink Cloud is responsible for account\/key issuance, service terms, privacy\npolicy, data retention, hosted runtime execution, and any provider subprocessors\nused behind the Cloud runtime. Site administrators should review these service\ndocuments before connecting a WordPress site to Npcink Cloud:<\/p>\n\n<p>Terms of Service: https:\/\/cloud.npc.ink\/terms\/en\/terms.html\nPrivacy Policy: https:\/\/cloud.npc.ink\/terms\/en\/privacy.html\nData Retention: https:\/\/cloud.npc.ink\/terms\/en\/data-retention.html<\/p>\n\n<p>If a site host configures a non-Npcink runtime through Toolbox filters, that host\nruntime is responsible for its own terms of service, privacy policy, data\nretention, account\/key issuance, and provider subprocessors. Site administrators\nshould review the configured host runtime's policies before connecting it to\nToolbox.<\/p>\n\n<p>Data that may be sent depends on the feature used and may include the submitted\nquery, selected post identifiers, public post\/page titles, public excerpts,\npublic URLs, approved public comment excerpts for selected public entries,\npending comment content with author display name, author URL, and the public\nparent post title for the bounded comment moderation review (never comment\nauthor email, IP address, or user agent, and no parent post title is sent when\nthe parent post is not public), bounded recent\nimage metadata (never image pixels) for the flagged media safety review, image\nmetadata already visible in WordPress, operator-entered content context, and\noperator-entered prompts or review notes. Provider API keys are not exposed to AI\ncallers through Toolbox responses.<\/p>\n\n<h4>Unsplash<\/h4>\n\n<p>When a connected runtime uses Unsplash for image-source candidates, image search\nqueries and candidate selection metadata may be sent to Unsplash. Unsplash\ncandidate payloads preserve attribution and download tracking metadata.<\/p>\n\n<p>Terms: https:\/\/unsplash.com\/terms\nPrivacy: https:\/\/unsplash.com\/privacy<\/p>\n\n<h4>Pixabay<\/h4>\n\n<p>When a connected runtime uses Pixabay for image-source candidates, image search\nqueries may be sent to Pixabay and returned candidates may be shown for operator\nreview.<\/p>\n\n<p>Terms: https:\/\/pixabay.com\/service\/terms\/\nPrivacy: https:\/\/pixabay.com\/service\/privacy\/<\/p>\n\n<h4>Pexels<\/h4>\n\n<p>When a connected runtime uses Pexels for image-source candidates, image search\nqueries may be sent to Pexels and returned candidates may be shown for operator\nreview.<\/p>\n\n<p>Terms: https:\/\/www.pexels.com\/terms-of-service\/\nPrivacy: https:\/\/www.pexels.com\/privacy-policy\/<\/p>\n\n<h3>Privacy<\/h3>\n\n<p>Npcink Workflow Toolbox stores local WordPress options for feature settings,\nnon-secret site guidance, media optimization settings and templates, bounded\nforeground media optimization history, media-recognition continuation, the\nlatest local Nightly Inspection dry-run preview, and a fallback hot-topic\nsnapshot. Short-lived transients cache hot-topic and editor request results.<\/p>\n\n<p>Uninstall removes those Toolbox-owned options, transients, locks, and scheduled\nhooks. It does not delete posts, imported or optimized Media Library items, or\nAbilities Toolkit-owned media backups and lineage records.<\/p>\n\n<p>Do not store provider secrets, private customer data, billing details, or write\nauthorization in the content context fields.<\/p>\n\n<p>Cloud-backed features may send bounded review data to the connected Npcink Cloud\nor host runtime. The plugin is designed to send suggestions and evidence for\noperator review, not to grant direct WordPress write authority to an external\nservice.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>npcink-workflow-toolbox<\/code> folder to <code>\/wp-content\/plugins\/<\/code>, or install it\nthrough the WordPress plugin installer.<\/li>\n<li>Activate <strong>Npcink Workflow Toolbox<\/strong> in WordPress.<\/li>\n<li>Open <strong>Npcink -&gt; Workflow Toolbox<\/strong> when a Npcink menu is available, or\n<strong>Tools -&gt; Npcink Workflow Toolbox<\/strong> for standalone installs.<\/li>\n<li>Fill the Site Context fields with non-secret positioning, audience, brand\nvoice, keyword, and SEO\/AEO\/GEO guidance.<\/li>\n<li>Connect the required Npcink Cloud Addon or host runtime before using\nCloud-managed search, image-source, site knowledge, hosted AI, or Pro Cloud\nRuntime features.<\/li>\n<\/ol>\n\n<p>Upgrade note: the editor Content Support sidebar now loads only on post and\npage editors. Sites that used it on a custom post type can restore it by\nadding the post type through the <code>npcink_toolbox_editor_supported_post_types<\/code>\nfilter.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20plugin%20write%20or%20publish%20my%20content%20automatically%3F\"><h3>Does this plugin write or publish my content automatically?<\/h3><\/dt>\n<dd><p>The default content-support flows only return suggestions, candidates,\npreviews, and handoff plans. The Media Library Optimization workflow is the\nnarrow exception: after an administrator checks and confirms one exact\nattachment-and-SHA-256 manifest, the browser delegates each reversible file\nreplacement to Abilities Toolkit. It never publishes posts or runs as an\nunattended batch.<\/p><\/dd>\n<dt id=\"can%20i%20use%20it%20without%20npcink%20cloud%3F\"><h3>Can I use it without Npcink Cloud?<\/h3><\/dt>\n<dd><p>Partially. Local settings, Site Context, editor surfaces, and review-only local\nplanning remain available. Cloud-managed web search, image-source candidates,\nsite knowledge, hosted AI suggestions, reviewed hosted image candidate requests,\nand Pro Cloud Runtime checks require a connected runtime.<\/p><\/dd>\n<dt id=\"does%20the%20zhihu%20hot-topic%20pool%20generate%20posts%3F\"><h3>Does the Zhihu hot-topic pool generate posts?<\/h3><\/dt>\n<dd><p>No. The Dashboard topic pool is a research-selection surface. It can show\nCloud-provided hot-list candidates for operator review, but it does not create\ndrafts, rewrite content, or publish posts.<\/p><\/dd>\n<dt id=\"does%20toolbox%20create%20new%20categories%20or%20tags%3F\"><h3>Does Toolbox create new categories or tags?<\/h3><\/dt>\n<dd><p>No. The first version recommends existing categories and tags for review. New\nvocabulary remains a separate governance decision outside Toolbox shortcuts.<\/p><\/dd>\n<dt id=\"is%20unsplash%20image%20search%20the%20same%20as%20hosted%20image%20candidate%20requests%3F\"><h3>Is Unsplash image search the same as hosted image candidate requests?<\/h3><\/dt>\n<dd><p>No. Unsplash, Pixabay, and Pexels are image-source providers. Reviewed\nhost-generated image candidates are a separate explicit mode and still do not\nimport media or set featured images by themselves.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20accept%20a%20suggestion%3F\"><h3>What happens when I accept a suggestion?<\/h3><\/dt>\n<dd><p>Accepted choices can be packaged into a governed handoff plan. Core proposal\napproval, preflight, audit, and final WordPress ability execution remain\noutside Toolbox except for the explicitly confirmed local media operations\ndescribed above.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>Security: every post-context read now requires edit_post permission\nfor the acting user before the title, status, excerpt, or content is\npackaged for the Cloud, at the media-brief, editor content-support,\nand hosted-AI layers.<\/li>\n<li>Security: URLs returned by the Cloud are normalized to http(s) at the\nprovider boundary, and every admin\/editor link sink validates the\nprotocol before rendering a clickable link.<\/li>\n<li>Performance: the editor content-support bundle loads only on post and\npage editors (extendable through the\nnpcink_toolbox_editor_supported_post_types filter), and release\npackages ship minified assets (roughly forty percent smaller).<\/li>\n<li>Performance: editor Cloud-result caching is per user, front-end\ntraffic no longer pays maintenance queries, media optimization batch\ncreation bounds its fingerprint pre-flight, and unchanged media files\nare never re-hashed between scans.<\/li>\n<li>Provider routes accept only their documented request fields, image\ngeneration and image-source searches coalesce identical repeat\nrequests for sixty seconds per user, and provider error responses\nexpose only allow-listed diagnostic data.<\/li>\n<\/ul>\n\n<h4>0.5.3<\/h4>\n\n<ul>\n<li>Added the review-set adoption tally: every review-set result panel\ncarries local Accept\/Ignore +1 buttons with a Last-7-days line, so the\nbatch-apply decision data builds itself during normal use (Toolbox\nsettings counts only; no suggestion content is stored).<\/li>\n<li>Hardened editor plain-text extraction to the inert DOMParser path\n(inline handlers and resource fetches in block HTML can no longer\nexecute during text extraction).<\/li>\n<li>Guarded the advisory review workflow against missing LLM configuration\nand fixed the form that briefly stopped all review rounds.<\/li>\n<li>Restructured the editor content-support service into five cohesive\nunits behind one facade (paragraph check, audio text, flow cache,\ntaxonomy shaping) with unchanged behavior.<\/li>\n<\/ul>\n\n<h4>0.5.2<\/h4>\n\n<ul>\n<li>Fixed the four Cloud-dependent review sets (taxonomy and tag, internal\nlink, comment moderation, flagged media) against the current Npcink\nCloud runtime: the site-helper payload no longer sends timeout fields\nthe converged Cloud schema rejects, and the sparse-post samples now\nreach the request instead of shipping empty (Cloud previously refused\nto invent suggestions from nothing, and the schema rejection returned\nan error on every run).<\/li>\n<li>Release packaging no longer includes the PHPStan baseline file.<\/li>\n<\/ul>\n\n<h4>0.5.1<\/h4>\n\n<ul>\n<li>The admin Site Knowledge status owner matrix now renders every row Cloud\nreports: index lifecycle, freshness policy, diagnostics detail, and\nembedding execution owners plus the freshness and diagnostics truth rows\njoin the existing set, and a static contract keeps rows from silently\ndropping again.<\/li>\n<li>Permission failures in the editor sidebar now read as plain operator\ncopy (\"This action needs a site administrator. Nothing was written.\")\ninstead of the raw REST denial, keyed on scope denials only - core\ncookie and nonce failures keep their reload or sign-in guidance.<\/li>\n<li>Guided-onboarding product design proposed; the operator trial script\ngained review-set adoption data collection and the owner-matrix and\npermission-copy checks.<\/li>\n<\/ul>\n\n<h4>0.5.0<\/h4>\n\n<ul>\n<li>Retired the ten route-only editor content-support intents (generic writing\nsupport, both editor-route Zhihu aliases, article checkup, title and\nsummary suggestions, outline, combined taxonomy tags, comment reply\nsuggestions, and discoverability) following the accepted editor intent\nconvergence decision; they now return the invalid-intent error. The admin\ncontent-support route keeps its own hosted intent set.<\/li>\n<li>Folded the local article-checkup prose signals into publish preflight: the\npre-publish review now includes a prose-quality row plus the local\ncheckup detail, so sentence-density, fact-gap, tone, structure, and format\nreview notes stay available without the retired standalone intent.<\/li>\n<li>Froze the editor content-support intent allowlist to twelve intents,\nenforced by a new static contract.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>Completed the five-review-set arc: taxonomy and tag review, internal-link\nreview, comment moderation review, flagged media review, and media\nALT\/caption review all share the same bounded, suggestion-only pattern.<\/li>\n<li>Added the taxonomy and tag review set as a site-level site-helper intent:\nsamples published posts with sparse term assignments and suggests existing\ncategories and tags. No term creation, no assignment.<\/li>\n<li>Added the internal-link review set: samples published posts with sparse\ninternal linking and suggests link candidates from existing content.\nNo link insertion from this surface.<\/li>\n<li>Added admin panels for both new review sets alongside the existing\ncomment moderation and flagged media panels.<\/li>\n<li>Restructured the REST controller into nine focused service classes behind\na thin facade (520 lines, down from 8,517), making future cluster work\nindependently revertible.<\/li>\n<li>Split editor JavaScript into part files behind explicit namespaces with a\nper-handle translation policy for translated parts.<\/li>\n<li>Enrolled in the Static Analysis Standard with PHPStan level 5 and PHPCS\nWordPress-Core as required CI gates after a full phpcbf formatting pass.<\/li>\n<li>Added a zero-dependency undefined-call audit gate for the editor bundle.<\/li>\n<li>Verified the split bundle on a live five-plugin WordPress site with green\nprogressive browser smokes and internal-link batch behavior checks.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>Added scoped editor permissions so authors and editors can use the post\neditor Content Support suggestion flows without administrator access.<\/li>\n<li>Added the read-only comment moderation review set with strict\npending-comment privacy limits and native WordPress moderation links.<\/li>\n<li>Added the read-only flagged media review set in Image Handling for bounded\nrecent image samples with Cloud safety statuses; no media are changed.<\/li>\n<li>Removed the retired vector-search, knowledge-search, article-brief, and\narticle-assistant compatibility routes and legacy admin URL aliases.<\/li>\n<li>Split the provider client into focused services behind the same facade and\nhardened service behavior coverage.<\/li>\n<li>Kept every suggestion review-only; final WordPress writes still require Core\nproposal approval.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>Added bounded paragraph\/list\/line-break repair to Cloud content formatting.<\/li>\n<li><p>Added Cloud-backed content formatting in the Gutenberg sidebar, with local\nintegrity checks, stale-response rejection and undo; no automatic save.<\/p><\/li>\n<li><p>Added the administrator-confirmed exact-manifest Media Library optimization\nflow with foreground progress, failure isolation, history, and restore.<\/p><\/li>\n<li>Restricted local write exceptions to same-origin WordPress cookie sessions\nwith a valid REST nonce.<\/li>\n<li>Completed uninstall cleanup for Toolbox-owned settings, caches, continuation\nstate, batch history, previews, locks, and scheduled hooks.<\/li>\n<li>Moved bounded media recognition continuation into Toolbox with stable ID\ncursors, single-event WP-Cron progress, bounded retries, and failure-only\nadministrator recovery.<\/li>\n<li>Switched Cloud media artifact delivery to the dedicated Addon facade while\npreserving Core review, Adapter execution, and WordPress write boundaries.<\/li>\n<li>Added missing-only contextual ALT pagination, explicit editor apply, and\nnamespaced decorative metadata that persists through native WordPress save.<\/li>\n<\/ul>\n\n<h4>0.1.1<\/h4>\n\n<ul>\n<li>Added attachment-scoped single-image replacement and restore through\nrequest-scoped Abilities Toolkit transactions with exact preview confirmation.<\/li>\n<li>Added automatic rollback backups and a bounded 30-day or 90-day retention\nsetting while keeping backup files, cleanup, and restore execution in Toolkit.<\/li>\n<li>Added the review-only Dashboard <code>\u77e5\u4e4e\u70ed\u699c\u9009\u9898<\/code> topic-pool surface for daily\nresearch selection.<\/li>\n<li>Added read-only Zhihu capability checks for connected Cloud search, hot-list,\nand direct-answer lanes.<\/li>\n<li>Tightened the Zhihu hot-topic table so machine identifiers and URL-like\nvalues are hidden from the operator-facing signal column.<\/li>\n<li>Clarified current-article media ALT\/caption review-set positioning in the\nWordPress.org-facing readme.<\/li>\n<li>Kept hot topics, media ALT\/caption suggestions, and accepted choices\nsuggestion-only with no direct WordPress or media metadata writes.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>Initial WordPress admin toolbox and post-editor content-support surface.<\/li>\n<li>Added review-only writing preparation, summary, taxonomy\/tag, internal-link,\nimage candidate, current-article image ALT, and publish-readiness support.<\/li>\n<li>Added Site Context fields for non-secret SEO\/AEO\/GEO guidance.<\/li>\n<li>Added Cloud-managed search, image-source, site knowledge, hosted AI, and\nCloud Addon runtime-detail links that fail closed without a connected runtime.<\/li>\n<li>Added governed handoff plans for article, media, image candidate, site\nknowledge, and metadata review workflows.<\/li>\n<li>Added WordPress Abilities API registrations for suggestion and planning\nactions.<\/li>\n<li>Added static release and boundary tests.<\/li>\n<\/ul>","raw_excerpt":"Fixed AI workflow buttons for WordPress operators, with review-only suggestions and governed handoff plans.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/333624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=333624"}],"author":[{"embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/muze233"}],"wp:attachment":[{"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=333624"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=333624"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=333624"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=333624"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=333624"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/fa-af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=333624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}