Npcink Workflow Toolbox
| 开发者 |
muze233
npcink |
|---|---|
| 更新时间 | 2026年10月11日 21:58 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Npcink Workflow Toolbox helps WordPress operators turn proven AI-assisted
content and site-operations practices into fixed, review-only buttons.
The plugin provides a WordPress admin surface and post-editor panel for:
- a Dashboard Zhihu hot-topic pool for deciding what may be worth researching today before any draft generation or publishing decision;
- read-only Zhihu capability checks for connected Cloud search, hot-list, and direct-answer lanes;
- writing preparation, title ideas, outline support, summary suggestions, and publish-readiness checks;
- one article writing pack contract for URL, typed manual, or mixed inputs, combining optional exact-source evidence with related site knowledge, structured human review, and an optional confirmed plain-text draft preview that may be loaded only into an empty current Gutenberg body and is never saved or published automatically;
- a compact default URL flow that blocks metadata or navigation-only captures before drafting and keeps brief/evidence details in optional disclosures;
- SEO, AEO, and GEO guidance from operator-maintained site context;
- existing-category and existing-tag recommendations for review;
- internal-link candidates and source-coverage notes;
- image-source candidates, reviewed hosted image candidates, current-article media ALT/caption review sets, and media planning handoff packets;
- a contextual single-image optimization workbench with verified previews, format/crop controls, reusable text or logo watermark templates, an optional safe output basename, request-scoped Toolkit replacement, automatic rollback backups, visible restore review, and a bounded 30- or 90-day retention choice;
- Cloud-managed site knowledge search, status, and sync requests when a compatible host runtime is connected;
- review-only Scheduled Review previews, with Cloud runtime inspection and recovery routed to Cloud Addon;
- scoped editor access so authors and editors can run the post editor's suggestion-only content-support flows without administrator rights;
- read-only comment moderation and flagged media review sets that send one bounded sample to the Cloud runtime and render suggestion-only classifications or safety statuses without changing comment status or media.
- editors want AI-assisted content checks without one-click publishing;
- administrators need fixed buttons for repeatable review workflows;
- editors want a low-friction "what should we research today?" surface backed by a connected Cloud hot-list runtime;
- a site uses Npcink Cloud or a host-provided runtime for web search, image candidates, site knowledge, or hosted AI suggestions;
- accepted changes must stay reviewable and auditable before any WordPress write.
安装:
- Upload the
npcink-workflow-toolboxfolder to/wp-content/plugins/, or install it through the WordPress plugin installer. - Activate Npcink Workflow Toolbox in WordPress.
- Open Npcink -> Workflow Toolbox when a Npcink menu is available, or Tools -> Npcink Workflow Toolbox for standalone installs.
- Fill the Site Context fields with non-secret positioning, audience, brand voice, keyword, and SEO/AEO/GEO guidance.
- Connect the required Npcink Cloud Addon or host runtime before using Cloud-managed search, image-source, site knowledge, hosted AI, or Pro Cloud Runtime features.
npcink_toolbox_editor_supported_post_types
filter.常见问题:
Does this plugin write or publish my content automatically?
The default content-support flows only return suggestions, candidates, previews, and handoff plans. The Media Library Optimization workflow is the narrow exception: after an administrator checks and confirms one exact attachment-and-SHA-256 manifest, the browser delegates each reversible file replacement to Abilities Toolkit. It never publishes posts or runs as an unattended batch.
Can I use it without Npcink Cloud?
Partially. Local settings, Site Context, editor surfaces, and review-only local planning remain available. Cloud-managed web search, image-source candidates, site knowledge, hosted AI suggestions, reviewed hosted image candidate requests, and Pro Cloud Runtime checks require a connected runtime.
Does the Zhihu hot-topic pool generate posts?
No. The Dashboard topic pool is a research-selection surface. It can show Cloud-provided hot-list candidates for operator review, but it does not create drafts, rewrite content, or publish posts.
Does Toolbox create new categories or tags?
No. The first version recommends existing categories and tags for review. New vocabulary remains a separate governance decision outside Toolbox shortcuts.
Is Unsplash image search the same as hosted image candidate requests?
No. Unsplash, Pixabay, and Pexels are image-source providers. Reviewed host-generated image candidates are a separate explicit mode and still do not import media or set featured images by themselves.
What happens when I accept a suggestion?
Accepted choices can be packaged into a governed handoff plan. Core proposal approval, preflight, audit, and final WordPress ability execution remain outside Toolbox except for the explicitly confirmed local media operations described above.
更新日志:
0.6.0
- Security: every post-context read now requires edit_post permission for the acting user before the title, status, excerpt, or content is packaged for the Cloud, at the media-brief, editor content-support, and hosted-AI layers.
- Security: URLs returned by the Cloud are normalized to http(s) at the provider boundary, and every admin/editor link sink validates the protocol before rendering a clickable link.
- Performance: the editor content-support bundle loads only on post and page editors (extendable through the npcink_toolbox_editor_supported_post_types filter), and release packages ship minified assets (roughly forty percent smaller).
- Performance: editor Cloud-result caching is per user, front-end traffic no longer pays maintenance queries, media optimization batch creation bounds its fingerprint pre-flight, and unchanged media files are never re-hashed between scans.
- Provider routes accept only their documented request fields, image generation and image-source searches coalesce identical repeat requests for sixty seconds per user, and provider error responses expose only allow-listed diagnostic data.
- Added the review-set adoption tally: every review-set result panel carries local Accept/Ignore +1 buttons with a Last-7-days line, so the batch-apply decision data builds itself during normal use (Toolbox settings counts only; no suggestion content is stored).
- Hardened editor plain-text extraction to the inert DOMParser path (inline handlers and resource fetches in block HTML can no longer execute during text extraction).
- Guarded the advisory review workflow against missing LLM configuration and fixed the form that briefly stopped all review rounds.
- Restructured the editor content-support service into five cohesive units behind one facade (paragraph check, audio text, flow cache, taxonomy shaping) with unchanged behavior.
- Fixed the four Cloud-dependent review sets (taxonomy and tag, internal link, comment moderation, flagged media) against the current Npcink Cloud runtime: the site-helper payload no longer sends timeout fields the converged Cloud schema rejects, and the sparse-post samples now reach the request instead of shipping empty (Cloud previously refused to invent suggestions from nothing, and the schema rejection returned an error on every run).
- Release packaging no longer includes the PHPStan baseline file.
- The admin Site Knowledge status owner matrix now renders every row Cloud reports: index lifecycle, freshness policy, diagnostics detail, and embedding execution owners plus the freshness and diagnostics truth rows join the existing set, and a static contract keeps rows from silently dropping again.
- Permission failures in the editor sidebar now read as plain operator copy ("This action needs a site administrator. Nothing was written.") instead of the raw REST denial, keyed on scope denials only - core cookie and nonce failures keep their reload or sign-in guidance.
- Guided-onboarding product design proposed; the operator trial script gained review-set adoption data collection and the owner-matrix and permission-copy checks.
- Retired the ten route-only editor content-support intents (generic writing support, both editor-route Zhihu aliases, article checkup, title and summary suggestions, outline, combined taxonomy tags, comment reply suggestions, and discoverability) following the accepted editor intent convergence decision; they now return the invalid-intent error. The admin content-support route keeps its own hosted intent set.
- Folded the local article-checkup prose signals into publish preflight: the pre-publish review now includes a prose-quality row plus the local checkup detail, so sentence-density, fact-gap, tone, structure, and format review notes stay available without the retired standalone intent.
- Froze the editor content-support intent allowlist to twelve intents, enforced by a new static contract.
- Completed the five-review-set arc: taxonomy and tag review, internal-link review, comment moderation review, flagged media review, and media ALT/caption review all share the same bounded, suggestion-only pattern.
- Added the taxonomy and tag review set as a site-level site-helper intent: samples published posts with sparse term assignments and suggests existing categories and tags. No term creation, no assignment.
- Added the internal-link review set: samples published posts with sparse internal linking and suggests link candidates from existing content. No link insertion from this surface.
- Added admin panels for both new review sets alongside the existing comment moderation and flagged media panels.
- Restructured the REST controller into nine focused service classes behind a thin facade (520 lines, down from 8,517), making future cluster work independently revertible.
- Split editor JavaScript into part files behind explicit namespaces with a per-handle translation policy for translated parts.
- Enrolled in the Static Analysis Standard with PHPStan level 5 and PHPCS WordPress-Core as required CI gates after a full phpcbf formatting pass.
- Added a zero-dependency undefined-call audit gate for the editor bundle.
- Verified the split bundle on a live five-plugin WordPress site with green progressive browser smokes and internal-link batch behavior checks.
- Added scoped editor permissions so authors and editors can use the post editor Content Support suggestion flows without administrator access.
- Added the read-only comment moderation review set with strict pending-comment privacy limits and native WordPress moderation links.
- Added the read-only flagged media review set in Image Handling for bounded recent image samples with Cloud safety statuses; no media are changed.
- Removed the retired vector-search, knowledge-search, article-brief, and article-assistant compatibility routes and legacy admin URL aliases.
- Split the provider client into focused services behind the same facade and hardened service behavior coverage.
- Kept every suggestion review-only; final WordPress writes still require Core proposal approval.
- Added bounded paragraph/list/line-break repair to Cloud content formatting.
- Added Cloud-backed content formatting in the Gutenberg sidebar, with local integrity checks, stale-response rejection and undo; no automatic save.
- Added the administrator-confirmed exact-manifest Media Library optimization flow with foreground progress, failure isolation, history, and restore.
- Restricted local write exceptions to same-origin WordPress cookie sessions with a valid REST nonce.
- Completed uninstall cleanup for Toolbox-owned settings, caches, continuation state, batch history, previews, locks, and scheduled hooks.
- Moved bounded media recognition continuation into Toolbox with stable ID cursors, single-event WP-Cron progress, bounded retries, and failure-only administrator recovery.
- Switched Cloud media artifact delivery to the dedicated Addon facade while preserving Core review, Adapter execution, and WordPress write boundaries.
- Added missing-only contextual ALT pagination, explicit editor apply, and namespaced decorative metadata that persists through native WordPress save.
- Added attachment-scoped single-image replacement and restore through request-scoped Abilities Toolkit transactions with exact preview confirmation.
- Added automatic rollback backups and a bounded 30-day or 90-day retention setting while keeping backup files, cleanup, and restore execution in Toolkit.
- Added the review-only Dashboard
知乎热榜选题topic-pool surface for daily research selection. - Added read-only Zhihu capability checks for connected Cloud search, hot-list, and direct-answer lanes.
- Tightened the Zhihu hot-topic table so machine identifiers and URL-like values are hidden from the operator-facing signal column.
- Clarified current-article media ALT/caption review-set positioning in the WordPress.org-facing readme.
- Kept hot topics, media ALT/caption suggestions, and accepted choices suggestion-only with no direct WordPress or media metadata writes.
- Initial WordPress admin toolbox and post-editor content-support surface.
- Added review-only writing preparation, summary, taxonomy/tag, internal-link, image candidate, current-article image ALT, and publish-readiness support.
- Added Site Context fields for non-secret SEO/AEO/GEO guidance.
- Added Cloud-managed search, image-source, site knowledge, hosted AI, and Cloud Addon runtime-detail links that fail closed without a connected runtime.
- Added governed handoff plans for article, media, image candidate, site knowledge, and metadata review workflows.
- Added WordPress Abilities API registrations for suggestion and planning actions.
- Added static release and boundary tests.