NV OOS MCP Bridge

NV Digital Open Operator System (NVoOS)

-green)

Version: 1.2.10 Release Date: 2026-10-23

See § Release History for the 12 most recent releases; every older release is in the Previous Releases table. Full detail: CHANGELOG.md.

🆕 v1.2.10 Highlights: Console migration Phase 5b–5d (Proposal 084) + console polish, crash fixes, a real transcript-storage meter, and a dependency advisory sweep. Phase 5b–5d (PR #7180) — the orphaned cost/analytics REST controllers register (real Analytics page), the Unified Blueprints catalogue bridges behind mcp-ai-pro/v1/blueprints, the Command Center absorbs into the Dashboard, and the console gains a semantic DataTable + grouped collapsible sidebar. Crash fixes (PR #7184) — the blueprints 500 (admin-context class gating), React error #310 on four console pages (a permanent rules-of-hooks ESLint gate), a reworked settings page, and chat dock UX. Storage meter (PR #7185) — the status bar reads real server transcript storage via the new storage_bytes envelope field. Dependencies (PR #7186) — markdown-it 14.3.3, MCP SDK 1.32.0, launch-editor 2.14.2 (14 of 16 alerts). Build (PR #7182) — full tracked-bundle rebuild after lockfile movement. Docs (PRs #7183, #7178) — rebuild discipline codified in the spa-ui/dependabot skills; Cloudways Anti-Bot Protection playbook. Tool count: ~355 base + ~1,377 Pro (~1,731 total; unchanged).

MCP Specification: 2026-07-28 (Stateless Core, Full Compliance)
Maintained by NV Digital
License: GPLv3 or later
Requires: WordPress 6.0+, PHP 7.4+
Patent Status: Patent Pending (Application #19/410,504)
Documentation: Grade A (95/100) — 1,617 files across 12 directories, 108 admin screenshots, 100% feature coverage

🔍 For Reviewers & Auditors

New to this repo? Start here → docs/project/FOR_REVIEWERS.md

That document answers every common question in one place: what the project is, current security posture, what's production vs experimental, PHP version requirements, AI development methodology, compliance status, and scoping advice for a limited-budget review.

Quick links for reviewers:

• Addon Inventory — what each of 30 addons does and its status
• Security Posture — current state of all 50 audit findings
• Compliance Traceability — every .org rejection reason → commit → verification command
• AI-Assisted Development — methodology, transparency, and what to scrutinize
• Architecture Overview — component diagram and data flow

📑 Table of Contents

Getting Started

• 🧩 Overview
• 🎯 Our Mission
• 🛡️ Active Security Monitoring
• ⚠️ Warranty & Safe Use
• 🏗 System Architecture
• 🚀 Features
• 📦 Installation
  • 🌱 Try It on Your PC
• 🔌 What You Lose Without Third-Party Plugins
• ⚙️ Configuration Checklist
• 📚 Documentation

Core Functionality

• 🧠 Memory & Tool Stack Overview
• 🛠 Built-in tools & automations
• 🗨️ Front-end chat surfaces
• 💬 Frontend Shortcode

Addons & Extensions

• 🏗 System Architecture (covers addon ecosystem)

Orchestration & AI Features

• 🏗 System Architecture (covers orchestration, harnessing, MCP servers, memory bridge)

AI Providers & Integration

• 🧠 Language Model Providers
• 🧱 ChatKit Integration
• 🌐 Crawl4AI Integration
• 📡 Job Notification System
• 🧊 Elementor Widgets

Performance & Optimization

• ⚡ Message Bundling
• 🎯 Agentic Loop Token Management
• 🔄 Chat Performance Optimizations
• 🌐 Mesh Compute Routing
• 🔗 Federation & Discovery System

Remote MCP Setup

• 🔒 MCP Server Authentication
• 🌐 Connecting Remote MCP Clients
• 🛰 REST API Endpoints
• 🌊 SSE Streaming Support
• 📝 MCP JSON-RPC 2.0 Endpoint
• 🔑 Assistant API Credentials
• 🎫 Token Management UI

Assistant Management

• 🛠 Assistant Editor Overview
• 📊 Assistant Storage: CPT vs CCT
• ⚡ Assistant Tool Shortcuts
• 🧠 Agent Skills
• 👔 Professional & Team Layers
• 🧵 REST Chat Payloads & Attachments

Development

• 🐳 Local Development with Docker
• 🧑‍💻 Development Tooling
• 📦 NPM Packages
• 🧪 Testing & QA
• 🧩 Hooks & Filters
• 🧰 WP-CLI Commands

Reference

• 🔐 JetEngine Capability Reference
• 🛰 JetEngine REST API Reference
• 🧮 Usage Tracking
• 🧷 Attachment MIME Controls
• 🧾 Logging
• 🧾 JetEngine REST Endpoint Report Helper
• 🔌 Optional Tools & Dependencies
• ✅ Manual QA Scenarios

Changelog

• 📜 Release History
• 📋 Previous Releases

Sponsor & Support

• ❤️ Sponsor & Support

🗺 Repository Map

🧩 Overview

Real-time AI Orchestration Toolkit / Harness for Wordpress - NV oOS is a modular AI framework (Object-Oriented System) for WordPress that connects your site's data with 18 language-model providers: OpenAI, Gemini, Anthropic, DeepSeek, OpenRouter, Baseten, Kimi (Moonshot), Z.AI (GLM), DigitalOcean, NVIDIA NIM, Cloudflare Worker AI, Azure, Ollama, LM Studio, Hugging Face, and TypeSafe Jev (decision-only), plus local WebLLM and embedded engines. It allows you to create and manage AI Assistants that can interact with users, access WordPress data, and perform custom tool functions.

✨ What's New at a Glance (v1.2.10)

• 🧭 Console migration Phase 5b–5d + console polish (Proposal 084, PR #7180). The orphaned cost/analytics REST controllers now register in includes/bootstrap/loader.php and power the real Analytics page (cost trend, provider donut, top tools/users); the Unified Blueprints page bridges behind GET /mcp-ai-pro/v1/blueprints as a searchable install catalogue; the Agent Command Center absorbs into the console Dashboard (fail-soft KPI + activity). Console-wide: a semantic DataTable (sortable headers, master–detail rows, sticky header) replaces the div-list tables, buttons are standardized, and the sidebar groups into Workspace / Automation / Command Centers / Insights / Admin (W3C disclosure, persisted state).
• 🧩 Crash fixes (PR #7184). The blueprints 500 — the admin_blueprints module gated the page class behind an admin context, so its static catalogue seams fataled on front-end REST; the class now loads unconditionally (only init() stays is_admin()). React error #310 (hooks after early returns) fixed on Schedule Manager, Workflows, Pro Ops, and Orchestration Stats — with a permanent react-hooks/rules-of-hooks ESLint gate that caught 21 latent violations. The settings page gains section cards, cross-tab search, and a sticky save footer; the chat dock gets mode-synced conversation-list collapse, a theme switch, a stacked composer, and a working drag-resize.
• 💾 Real transcript-storage meter (PR #7185). The status-bar "Sessions: X KB" meter measured localStorage keys that can never exist for the server-side transcript store (always 0). WP_MCP_AI_Transcript_Repository::get_storage_bytes() now aggregates per-user payload lengths, the /chat-transcripts envelope carries storage_bytes, and the StatusBar prefers the server figure with a localStorage fallback for older installs.
• 🛡 Dependency advisories closed (PR #7186). markdown-it → 14.3.3 (ReDoS + O(n²)), @modelcontextprotocol/sdk → 1.32.0 (gateway 22/22), launch-editor → 2.14.2 — 14 of 16 open alerts; the vite pair already fixed on the alpha line.
• 🔨 Full tracked-bundle rebuild (PR #7182). Lockfile-only advisory bumps had left tracked bundles silently stale for 13 days — the full artifact tree was rebuilt (16 files) and the rebuild discipline codified in the spa-ui + dependabot-loop skills (#7183).
• 🚀 Standalone SPA endpoint sync (PR #7181). The Vite mirror gains the three canonical ProSpaEndpoints keys (cost, blueprints, commandCenter) and points analytics at the core namespace — the Velocity build gate fixed.

🎯 Mission: Modernizing Small to Medium Business Websites

NV oOS is specifically designed to help small to medium-sized businesses fast-track their outdated, stale, or insecure company websites to modern technology standards—without the need to add yet another wrapper around API calls. Instead, we're trying to peel back decades of API wrappers with the help of AI, providing:

• Direct AI Integration - No middleware required. Connect directly to OpenAI, Gemini, Anthropic, Hugging Face, Cloudflare Worker AI, Ollama, LM Studio, OpenRouter, and DeepSeek without custom development
• Security-First Architecture - Built-in protection against nefarious usage with active monitoring and prevention systems
• Enterprise-Grade Features - Access to capabilities typically requiring expensive custom development
• Compliance & Audit Tools - Comprehensive logging, rate limiting, and usage tracking built-in
• Zero Technical Debt - Modern codebase following WordPress standards, ready for current technology stacks

🛡 Active Security Monitoring

NV oOS actively prevents and monitors against nefarious behavior. The plugin includes:

• Nefarious Usage Monitor - Real-time detection of suspicious patterns and automatic emergency shutdown capabilities【F:includes/class-wp-mcp-ai-nefarious-usage-monitor.php†L1-L676】
• Root Security Key - Optional emergency authentication layer to prevent unauthorized reactivation after security incidents【F:docs/features/security/root-security-key.md†L1-L511】
• Granular Capability Controls - Every tool and API endpoint enforces WordPress capabilities to prevent unauthorized access
• Rate Limiting - Built-in protection against abuse with configurable limits per user, model, and time period
• Comprehensive Audit Logging - Track all API calls, tool executions, and security events for compliance and forensic analysis
• Input Sanitization & Output Escaping - All user input sanitized, all output escaped following WordPress security best practices

This is not a tool for circumventing security or promoting bad practices. Every feature is designed with security, transparency, and responsible AI usage as core principles. The plugin actively works to stop and prevent misuse before it happens.

Latest audit: See docs/operations/compliance/SECURITY_AUDIT_2026_04.md — the published summary of the April 2026 security & compliance code review (no Critical findings; 5 High items, 3 Fixed and 2 Partially Fixed). Full deliverables under docs/project/audits/2026-04/.

WordPress.org compliance hardening (May 9, 2026): docs/operations/compliance/WORDPRESS_ORG_COMPLIANCE_2026_05_09.md — findings B3, B8, B10, B13, and production vendor remap all resolved.

⚠ Warranty & Safe Use

We make every effort to keep NV oOS safe and secure — but by design, it can be destructive and resource-intensive when not properly configured.

NV oOS grants AI assistants access to powerful WordPress operations. The same capability that automates real work can cause irreversible harm if misconfigured:

• Destructive tools — bulk content deletion, user management, file writes, mass email, WP-CLI, direct database operations
• API billing exposure — uncapped AI provider calls can exhaust quotas and trigger unexpected charges
• Server resource exhaustion — concurrent agentic loops and SSE streams can saturate CPU/memory on shared hosting

Before going live: test on staging, take verified backups, apply least-privilege tool permissions, enable rate limiting, and review the system prompt of every public-facing assistant.

📄 Full details: WARRANTY.md — security commitment, "AS IS" disclaimer, destructive-operations table, resource-consumption guide, and mitigation checklist aligned with OWASP, NIST SP 800-53, ISO/IEC 27001, and the WordPress Plugin Developer Handbook.

Patent Pending

NV oOS is the subject of a pending patent application for its novel System and Method for Dynamic AI Orchestration Layer with Real-Time Capability Gating and Resource Budgeting.

Application Number: 19/410,504

The patent covers NV oOS's innovative approach to implementing sophisticated AI orchestration in WordPress's request-based PHP architecture—a platform not designed for real-time streaming, asynchronous operations, or persistent state management. This technical achievement enables enterprise-grade AI capabilities on WordPress by recreating event-driven behavior within PHP's synchronous execution model.

Key Innovations Covered:

• Dynamic resource budget allocation during streaming operations
• Capability-based access control for AI tool execution
• Registry-state-based scheduling in stateless environments
• Metrics-driven budget adjustment for real-time optimization
• Persistent-behavior illusion in request-based architectures

The orchestration layer makes NV oOS unique in the WordPress ecosystem by solving fundamental architectural limitations that prevent traditional WordPress plugins from supporting advanced AI features. See the System Architecture section below for technical details on how these innovations work together.

🏗 System Architecture

NV oOS implements a comprehensive orchestration layer for managing AI operations during real-time streaming events. The system architecture comprises:

• 18 language-model providers — OpenAI, Gemini, Anthropic, DeepSeek, OpenRouter, Baseten, Kimi (Moonshot), Z.AI (GLM), DigitalOcean, NVIDIA NIM, Cloudflare Worker AI, Azure, Ollama, LM Studio, Hugging Face, TypeSafe Jev (decision-only), plus local WebLLM + embedded engines
• ~1,731 tool classes (~355 base + ~1,377 Pro; live count via WP_MCP_AI_Tool_Registry::get_tools() is authoritative) registered through a singleton Tool Registry
• 36 REST controllers (16 base + 20 pro) under the mcp-ai/v1 namespace
• 64 service classes powering orchestration, budgets, and workflows
• 5 authentication methods — WordPress nonce, assistant credentials, mesh keys, Auth0 JWT, guest tokens
• Toolkit MCP servers — per-toolkit JSON-RPC 2.0 servers exposed under /wp-json/mcp-ai-pro/v1/mcp/{slug}; discoverable at /.well-known/mcp
• 8 inline-async-tick consumers — cooperative tick-lock pattern eliminates WP-Cron startup latency for background jobs (transcript mining, async tool executor, SaaS Apply, Crawl4AI, Docs Hub rebuild, Graphify reindex, Harness eval, Gemini Veo polling)
• 7 LLM Harness layers (+ 1 Pro) — opt-in epistemic layers A–H activated per-assistant via the LLM Harness metabox
• Orchestration Phases 1–7 — HITL approval queue, prompt-injection detector, structured output, OTel exporter, DAG builder, durable runs, triggers/webhooks, sub-agents

📖 For a detailed explanation of how NV oOS extends standard SSE and MCP protocols with novel orchestration features, see ORCHESTRATION-LAYER-ARCHITECTURE.md

Core Orchestration Layer: Overcoming PHP's Limitations

Critical Context: Most real-time AI streaming systems are built with Node.js, Python FastAPI, or Go — platforms designed for asynchronous, event-driven operations. These platforms natively support:

• Long-lived connections and persistent state
• Non-blocking I/O and parallel execution
• Event loops and asynchronous callbacks
• WebSocket protocols and SSE streaming

NV oOS achieves the same capabilities in PHP/WordPress — an environment fundamentally not designed for these patterns — through a sophisticated orchestration layer that creates a "persistent-behavior illusion":

1. Real-Time Budget Enforcement - Monitors token/memory usage during streaming, prevents exhaustion through predictive allocation
2. Capability-Based Tool Gating - WordPress role-based access control for AI tool execution
3. Predictive Optimization - Analyzes usage patterns to prevent resource overruns before they occur
4. Distributed Orchestration - Multi-provider support with policy-aware routing
5. Auditability & Compliance - Complete governance layer with logging and rate limiting
6. Cron-Based Task Orchestration - Extends orchestration to async operations with budget inheritance

Multi-Agent Orchestration Enhancement (DeepSeek V4-Inspired)

Added: January 2026 (v1.1.0)

Building upon the core orchestration layer, NV oOS now includes a sophisticated multi-agent coordination framework inspired by DeepSeek V4's orchestration patterns:

Key Components:

• Agent Role System - Four specialized roles (Planner, Executor, Critic, Specialist) with role-specific capabilities
• Team Composition - Automated team assembly based on task requirements and profession expertise
• Coordinated Workflows - Multi-step workflows with agent delegation, result aggregation, and validation
• Team CPT Integration - Persistent team configurations with orchestration modes (single/sequential/parallel/swarm)
• Profession-Based Discovery - 296 professions auto-assigned agent roles via intelligent seeding across 17 knowledge bases

Example Multi-Agent Workflow:

// 1. Compose research team (planner + executors + critic)
$orchestrator = new WP_MCP_AI_Agent_Team_Orchestrator();
$team = $orchestrator->compose_team( array( 'task_type' => 'research' ) );

// 2. Execute coordinated workflow
// Planner decomposes task → Executors research subtasks → 
// Communication service aggregates → Critic validates quality
$result = $orchestrator->execute_team_workflow( $team, $task, $context );

Documentation:

• See Multi-Agent Orchestration for complete technical details
• See DEEPSEEK-V4-README.md for documentation suite overview
• See DEEPSEEK-V4-USAGE-GUIDE.md for practical examples

Why This Architecture Is Novel: Overcoming PHP's Limitations

• Event loops and background workers

PHP/WordPress, by contrast, is fundamentally request-based:

• Every HTTP request spawns a new process that dies after responding
• I/O operations block execution
• No persistent memory between requests
• No native event loop or async coordination

NV oOS solves this by implementing an orchestration layer that creates a "persistent-behavior illusion" — effectively recreating Node.js's event loop behavior within WordPress's synchronous, request-based architecture. This architectural compensation is the system's core technical innovation:

This makes NV oOS patent-worthy as a technical workaround — it achieves sophisticated AI orchestration in an environment specifically not designed for such patterns. See ORCHESTRATION-LAYER-ARCHITECTURE.md for the complete technical analysis.

Computer-Implemented Resource Management

The system operates as a computer-implemented method executing on a processor with memory, performing:

1. Dynamic Resource Budget Allocation: The orchestration layer dynamically allocates token and memory budgets to tool execution requests based on real-time system capacity and operation requirements. The WP_MCP_AI_Resource_Manager continuously monitors server resources (PHP memory limits, execution time constraints) and automatically adjusts operational parameters.

2. Capability-Based Access Control: Tool execution endpoints enforce granular capability-based access controls. Each tool in the registry declares required WordPress capabilities, and the REST API controller validates user permissions before allowing execution. This ensures secure, policy-driven access to all operations.

3. Registry-State-Based Scheduling: The WP_MCP_AI_Tool_Registry maintains tool availability state and schedules execution based on policy constraints. Tools are loaded conditionally based on dependency availability, and execution is scheduled according to assistant configuration and user permissions.

4. Metrics-Driven Budget Adjustment: The system continuously monitors execution metrics (memory usage, API response times, token consumption) and adjusts resource budgets in response to prevent resource exhaustion and reduce latency. The WP_MCP_AI_Token_Budget_Manager implements safety margins and dynamic chunking to prevent API limit overruns.

System Components

The system comprises a processor and memory storing instructions that:

• Monitor real-time resource availability through PHP runtime introspection
• Enforce capability checks at REST endpoint boundaries
• Schedule tool execution through a centralized registry
• Adjust token and memory budgets based on detected system metrics
• Maintain operation logs for audit and optimization

This architecture is embodied in non-transitory computer-readable media (PHP source files) that, when executed by a web server processor, cause the system to perform the complete resource management workflow. The implementation prioritizes stability, security, and efficient resource utilization across diverse hosting environments.

Symfony Process Integration (December 2025)

NV oOS Pro addon integrates the Symfony Process component for secure external command execution. This modern framework replaces direct exec() calls in 6 Pro tools and 2 supporting services, providing:

• Enhanced Security: Proper argument escaping and command validation
• Timeout Management: Configurable timeouts with graceful handling
• Better Error Handling: Comprehensive exception catching and WordPress-friendly error reporting
• Process Control: Real-time output streaming and cancellation support

Migrated Tools & Services:

• FFmpeg operations (video frame extraction, metadata reading)
• Python rembg (background removal)
• WP-CLI execution
• Meta AI Jukebox (music generation)
• Supporting services for video and audio processing

The Process Service (WP_MCP_AI_Process_Service) provides WordPress-friendly wrappers with WP_Error integration, making external process execution consistent with WordPress coding standards.【F:includes/services/class-wp-mcp-ai-process-service.php†L1-L220】【F:docs/history/2025/implementations/symfony-phases/SYMFONY_PHASE2B_PROCESS_INTEGRATION.md†L1-L100】

📜 Release History

The 12 most recent releases are documented in full below. Every older release has a one-line summary in the Previous Releases table, and complete per-release detail lives in CHANGELOG.md.

v1.2.10 — October 23, 2026

Console Migration Phase 5b–5d, Crash Fixes, Storage Meter & Advisory Sweep

• 🧭 Admin-surface console migration Phase 5b–5d + polish (Proposal 084, PR #7180). The orphaned WP_MCP_AI_REST_Cost_Manager + WP_MCP_AI_REST_Analytics_Manager controllers now register in includes/bootstrap/loader.php (Phase 5b) and power the real Analytics page (cost trend, provider donut, top tools/users — manage_options-gated, wrapping the existing service layers); the Unified Blueprints page bridges behind GET /mcp-ai-pro/v1/blueprints as a searchable install catalogue (5c); the Agent Command Center absorbs into the console Dashboard (5d, fail-soft KPI + activity). Console-wide polish: a semantic DataTable (sortable headers, master–detail expandable rows, sticky header, scroll containment, zebra striping) replaces the div-list tables; standardized primary/danger buttons; a grouped collapsible sidebar (ConsoleSidebar + nav-features: Workspace / Automation / Command Centers / Insights / Admin) with the W3C disclosure pattern, persisted state, and default-Workspace-expanded.
• 🧩 Crash fixes + settings + chat dock (PR #7184). The blueprints 500 — the admin_blueprints module gated the page class behind context => 'admin', so its static catalogue seams fataled on front-end REST; the class loads unconditionally now (only init() stays is_admin()), pinned by an 11-test REST suite. React error #310 (hooks after early returns) fixed on Schedule Manager, Workflows, Pro Ops, and Orchestration Stats — with a permanent react-hooks/rules-of-hooks ESLint gate that caught 21 latent violations across 4 files. The settings page gains section cards per tab (the schema's previously unused section/section_id), cross-tab search with breadcrumbs, a sticky save footer, and dirty-field indicators. The chat dock: mode-synced conversation-list collapse (docked starts collapsed, full-page open — boot-synced to avoid a first-frame flash), the visible status-bar ☰ toggle, a light/dark theme switch, a stacked composer (textarea no longer squashed to 31px), and drag-resize on the textarea itself.
• 💾 Server transcript storage meter (PR #7185). The status-bar "Sessions: X KB" meter measured same-origin localStorage keys that can never exist for the server-side transcript store. WP_MCP_AI_Transcript_Repository::get_storage_bytes() aggregates per-user payload lengths (0 when the CCT is unavailable), GET /mcp-ai/v1/chat-transcripts carries storage_bytes, and the StatusBar prefers the server figure with a localStorage fallback for older installs.
• 🛡 Dependency advisory sweep (PR #7186). markdown-it → 14.3.3 (ReDoS + O(n²), bounded override — 6 alerts), → 1.32.0 (gateway exact pin, 22/22 — 8 alerts), launch-editor floor → 2.14.2 (2 alerts) — 14 of 16 open alerts closed; the vite pair already fixed on the alpha line.

v1.2.9 — October 22, 2026

Complete Console App + Admin Console Migration, SA Visibility & New REST Routes

• 🖥 NV oOS Complete Console Velocity app (Proposal 083, PRs #7150, #7154). A new standalone Cloudways Velocity app (examples/nvoos-complete-velocity/) serving the full spa-v2 admin surface for Complete customers — build-time composition via the @nvoos/pro-spa-v2 Vite alias (no spa-v2 fork), cookie auth through the proven same-origin BFF proxy (serve.mjs, no connection screen), and a Schedule Anything-format shell: dashboard home, one route-split page per addon, a collapsible nav rail, and a persistent chat dock (single ChatPage instance — conversations keep streaming while browsing).
• 🧭 Admin-surface console migration, Phases 0–4d (Proposal 084, PRs #7164, #7166). WP_MCP_AI_Feature_Flags + GET /mcp-ai/v1/features gate the console nav (fail-open); Approvals/Slash Commands/Triggers/Portability/Security/Teams ports with per-page wp-admin kill-switches; a schema-driven Settings engine (/settings/schema + /settings/values, dirty-diff saves, secret masking); ops/diagnostics/token-manager pages + GET /mcp-ai-pro/v1/ops/overview; Schedule Manager (P9) + Workflow Builder (ReactFlow canvas) + records/dashboards/calendar/F&B/channels/media-ops pages. A REST contract parity audit fixed nine client/server mismatches — including the assistants GET/PUT routes that broke the edit form. Phase 5 (retirement soak + kill-switch flips) remains.
• 📅 Schedule Anything full visibility (PR #7147 — platform 0.1.1 → 0.1.2). The builder palette now reads the live registry via GET /mcp-ai-pro/v1/sa-tools (paged light rows, server search + group facet — replaces a hardcoded 19-tool fixture); GET /toolkits returns tier/platform_active/entitled (server-decided, greys out of-tier toggles); the missing flowhub + shopify-sync toolkit rows are back; multisite admins gain sa_manage_workspace idempotently; preset filters use server facet dropdowns + load-more; same-state toggles are a successful no-op.
• ⚙ New base settings/features routes (PRs #7157, #7164). GET/POST /mcp-ai/v1/settings (SPA-shaped { success, data }, secrets masked as the admin placeholder, whitelisted sanitize + key mapping + clamps), GET /mcp-ai/v1/features, GET /mcp-ai/v1/teams, and the settings schema/values pair.
• 🛡 Opt-in debug logging (PR #7161). The JetEngine CCT hot path no longer logs a debug event per request; debug-level events gate behind enable_debug_logging (default off) while errors/warnings/criticals stay always-on; the CG Pro logger port mirrors the gate and degrades to a safe no-op standalone.

v1.2.8 — October 19, 2026

Schedule Anything API + Single-Site Mode, F&B Worker Offload & MCP OAuth Hardening

• 📅 Schedule Anything presets + toolkits API (PR #7124, Proposal 081). Four mcp-ai-pro/v1 routes (rest_schedule_anything module): GET /toolkits + POST /toolkits/{slug}/toggle (server-side tier entitlements via the platform's SA_Toolkit_Manager, 403 sa_toolkit_not_entitled), GET /presets + /presets/{id} (12 presets across 6 toolkits), and idempotent POST /presets/{id}/install (replay returns the original schedule). Schedule records leaving REST are redacted (redact_schedule_for_public() — credential-bearing fields stripped), and the SPA builder payload aligns with the server contract (sonner error surfacing).
• 🏠 Schedule Anything Platform single-site mode (PR #7134, Proposal 082 — addon 0.1.0 → 0.1.1). No more activation wp_die on non-multisite: sole-tenant self-provisioning (tier default enterprise, filter sa_single_site_tier), a manage_options capability seam for SPA REST, 409 sa_cannot_offboard_sole_tenant, a SA_SAAS_API_KEY-gated heartbeat, and a 17-case suite wired into the root PHPUnit run via a self-guarding addon tests bootstrap.
• 🏭 F&B ingest × media-worker offload (PR #7114, Proposal 079 + Appendix B). The worker's POST /api/ingest/parse returns the F&B {columns, rows} matrix contract (XLSX/CSV/TSV/JSON/JSONL/PDF/photo; .xls/.ods → 503 capability_unavailable with local fallback), /api/image/batch gains the files[N] contract + per-file tolerance; the F&B loader parses heavy formats sidecar-first with local PhpSpreadsheet/PdfParser fallbacks; optimise_images_batch and the OCR-service PDF path offload; opt-in ocr_vision_fallback rung.
• 🛡 MCP OAuth authorize hardening (PR #7133). Exact-string redirect URI matching (RFC 9700 — the wildcard bypass is gone), registration-time URI validation, a nonce-bound consent page before any code is issued, unknown-scope rejection, and token-endpoint redirect_uri matching — Pro addon + the byte-identical Content Graph Pro mirror (19-test suites, 114 adjacent assertions on WP 6.9 + 7.1).
• 🖥 WP-CLI integration gaps closed (PR #7135). The dead mcp-ai content command registers again; a canonical WP_MCP_AI_Pro_Toolkit_Settings_Map (40 toolkits) fixes "Unknown toolkit key" for 11 real settings keys; toolkit enable|disable are manage_options-gated (); new //// commands with the integration CLIs discovered via .

v1.2.7 — October 17, 2026

F&B Universalisation, Sinhala TTS, and the Pro SPA Multi-Page Expansion

• 🍽️ Food & Beverage universalisation + open-format ingestion (PRs #7094–#7096, Proposal 078). The F&B toolkit moves from a single-tenant demo to a universal product: WP_MCP_AI_Fnb_Tenant_Profile de-couples currency (canonical neutral metric keys with legacy *_lkr aliases for the 20/20 oracle), render() de-venues both assistant surfaces via token substitution, demo_mode => false, and a new WP_MCP_AI_Fnb_Report_Exporter (DomPDF-first PDF + html_to_pdf fallback + CSV) powers fnb_export_report (+1 Pro). The universal reader scores a single Drive folder to table roles; the multi-format loader + Observation/terminology-map layer and a read-only Ingest & Review dashboard complete the ingestion track; an analytics dashboard adds KPI tiles + trend charts + panel tables.
• 🗣 Sinhala-native TTS (PR #7099). generate_sinhala_speech (+1 base) closes the generate_openai_speech gap (OpenAI voices are English-optimized, Google Cloud TTS has no si-LK voice) via SpeechGen (si-LK), Hugging Face facebook/mms-tts-sin, or a custom webhook; wired into the media_generation preset, with a teacher-assistant-sri-lanka.md system-prompt + tool pack.
• 🧩 Pro SPA multi-page expansion (PRs #7078–#7080). #/docs, #/media, and #/documents frame the Docs Hub / Media Studio / Document Editor SPAs in sandboxed iframes (mirroring #/knowledge-graph), with filterable docsHub/mediaStudio/documentEditor endpoints and nav-* commands; the standalone app defaults docsHub to the console docs hub.
• 🎙 Dictation-app skill bundling (PR #7077). mcp-ai-wpoos-dictation-app ships inside includes/bundled-skills/ and the bin/sync-agent-skills.php allowlist (base bundled 76 → 77).
• 🛡 Tool-schema hardening (PRs #7087, #7100, #7104). Per-property boolean required hoisted to the top-level array (both ChatOrchestrator + REST build_tools_payload()) and empty properties emitted as {} (seven no-arg tools + the central Tool_Schema_Auditor + the CG-AI mirror), fixing DeepSeek 400s.
• 🔍 Google Workspace unification + native Sheets (PRs #7097, #7101, #7105). search_gmail/ delegate to the shared clients (fixing the / rejection); reads native Google Sheets via the Sheets API v4 (, , ); surfaces the real 403 cause.

v1.2.6 — October 14, 2026

Drive OAuth Restored, F&B Reliability, OCR vLLM & the Dictation Browser Agent

• 🔐 Google Drive OAuth restored (PR #7053). The #6981 narrowing to the non-sensitive drive.file scope silently broke search_drive, get_drive_file, and the F&B tools for pre-existing content — a per-file scope that can't see anything the app didn't create. drive.readonly is restored as the default alongside drive.file, behind the unchanged wp_mcp_ai_google_drive_oauth_scope filter; the CG-AI-platform OAuth manager mirrors it (sub-project, flag-not-edited).
• 🍽 Food & Beverage reader reliability (PRs #7057, #7060, #7061, #7062). The Sheets reader assumed one Drive file per table; real clients use a single workbook. The WP_MCP_AI_Pro_Google_Drive_Client gains Sheets-API-v4 helpers (get_sheet_values()/get_sheets_metadata()) and the reader resolves table IDs to worksheet tabs with fuzzy matching (case/underscore/hyphen/substring) + a preserved split-file fallback. A DEMO_WORKBOOK_ID fallback + workbook_id() accessor fix the fresh-install file-lookup break; the spreadsheets.readonly OAuth scope + maybe_annotate_sheets_error() surface the real Sheets scope failure instead of a misleading split-file "not found". A new WP_MCP_AI_Fnb_Csv_Exporter (workbook → CSV-per-table with an admin export button) and the 18-table demo dataset (~10,700 rows) now ship in data/*.csv (the tests/ path was stripped from release builds).
• 🔒 Drive connection fixes (PR #7051). The WP_MCP_AI_Inline_Async_Tick_Trait double-declaration fatal in the harness eval scheduler (the non-once Composer classmap load raced a later require_once); Drive 400 responses now log the full body (so invalid_grant vs invalid_client is finally visible); folder_id can now be cleared (preserve only when the key is absent — the always-posted empty string was mistaken for an omission).
• 🔍 Self-hosted OCR vLLM contract (PR #7055). WP_MCP_AI_Self_Hosted_OCR_Client::ocr_images() emitted the SGLang dialect while every operator surface directs users to deploy vLLM — so the no-repeat-ngram processor was never engaged and long documents looped on coordinate tokens. Rewritten to the vLLM OpenAI-compatible shape (model = HF id; skip_special_tokens + ngram_size/window_size + DeepSeek's whitelist_token_ids under extra_body.vllm_xargs); base + CG Pro mirror byte-identical.
• 🤖 Dictation browser agent + FastConformer (PRs #7041, #7043–#7050). The feature drives a real browser over CDP (chromiumoxide) from dictated/typed instructions — a ReAct loop, a six-variant verdict model with real read-back, an origin-guarded safety gate + sensitive-field masking + async HITL Approve/Deny, and the brain model now correctly uses (never the shared cleanup/TTS model). A second local STT engine ( nemo_ctc) ships; an explicit master switch replaces the gate (the default used to silently disable polish); model download/install hardened ( moved out of the install dir, 5× staging-swap retry, install).

v1.2.5 — October 13, 2026

GTmetrix × WPCode Toolkit, Food & Beverage Phase 9 & the Hardened Dictation App

• 🚀 GTmetrix × WPCode performance toolkit (PR #7026, Proposal 068). +24 Pro tools — a 23-tool gtmetrix_* set (start/monitor/retest, report + Lighthouse-audit + resource-summary reads, browser/location/simulated-device listing, alert + page-tag + monitoring management, and generate_wpcode_snippet) plus the read-only list_wpcode_snippets on a shared WP_MCP_AI_Pro_WPCode_Snippet_Repository (extracted zero-behavior-change from create_wpcode_snippet, conditional_logic support). Deterministic CWV/grade/weight scoring with a 41-check standalone oracle, a credit-aware Action Scheduler poller + CPT snapshot store surviving GTmetrix's 1-month retention, a Basic-auth client with 429 backoff + sensitive-resource hard-blocks, and gtmetrix_install_wpcode_fix drafts-only/chat-restricted. Five schedule + two workflow presets, an assistant pack + wp mcp-ai pro gtmetrix seed-assistant, full 7-surface registration + regenerated coverage manifests. Deferred (plan §8): WP 7.1 second pass, live-key smoke test, proposals-README status.
• 🍽 Food & Beverage Phase 9 (PR #7032). +10 Pro tools — five transactional-table CPT backends (mcp_ai_fnb_sale|purchase|stock|waste|booking behind enable_fnb_native_storage, with idempotent upserts + before/after hooks) read by metrics/reports unchanged through a WP_MCP_AI_Fnb_Cpt_Reader; the ACT-tier fnb_import_table Sheet/CSV→CPT bridge (dry-run, idempotent); and nine fnb_pr_* purchase-request tools running the approval lifecycle on the QMS engine (preconditions via wp_mcp_ai_qms_state_preconditions, PO numbering PR-YYYYMM-###, release-signature relaxation). The four A1–A4 assistants ship as unified Blueprints; a new top-level F&B Management menu (CRM/PM pattern) with five CPT screens + a dashboard + settings link. Deferred: Phase 10 chat/social/booking wiring, reference-table CCT fields, Appendix A10.
• ⚙️ F&B admin menu + module-registry fix (PR #7029). tools/food-beverage/init.php was dead code — fnb was missing from the Pro Module Registry's conditional_toolkits/dir_map, so the admin menu never registered (tools still worked via the central map). A new F&B settings page + the CRM-style enable gate land; the 21 shipped tools now surface correctly. design-...-toolkit-creation case study updated to eleven registration surfaces.
• 🍱 F&B assistant-pack seeding + CSV guidance (PR #7033). The truncated WP_MCP_AI_Fnb_Assistant_Seeder completed (seed(), portability-engine load, image-tool add) so the one-click admin button and the CLI share identical semantics; CSV data-directory guidance + a read-only status row (configured/exists/is-directory/readable/writable).

v1.2.4 — October 12, 2026

MCP Quirk Hardening, Chart Recipes, Model Foundry Phase 1 & the Content Graph SPA Page

• 🛡 MCP client-quirk hardening (PR #7007, Proposal 066). Every advertised tools/list schema now carries a root type: object and hazardous schemas are skipped-with-reason instead of dropping the whole catalog (bracketed property names, >20 KB schemas, root combinators, >64-char slugs — the new WP_MCP_AI_Tool_Schema_Auditor); nvoos_get_profile attaches structuredContent whenever its outputSchema is advertised (Codex turns declared-outputSchema text-only results into errors); the registry fires wp_mcp_ai_mcp_tools_list_changed (once per request) backing listChanged; JetEngine MCP + MCP App discovery caches cap at the server ttlMs and invalidate on notifications/tools/list_changed; the CG-AI standalone mirror ports the hardening. Site Health direct test + debug field; 44 new tests on WP 6.9 + 7.1.
• 📈 nvoos-chart recipe rendering (PRs #7003, #7005). Fenced nvoos-chart JSON renders as real HTML/CSS charts on all three chat surfaces (no SVG/canvas/CDN) — 29 types (v1's bar/column/line/area/dot/donut/heatmap + v2's histogram, box, strip, stem, violin, pie, waffle, unit, diverging, lollipop, dumbbell, slope, bullet, pyramid, waterfall, candlestick, gantt, sparkline, radial, dial, race, grid); invalid fences degrade to escaped code blocks; sanitisation by construction (extracted before marked/DOMPurify, createElement + textContent); resource caps (40 labels / 12 series / 120 points / 240 cells); theme-adaptive, dark-mode-aware, prefers-reduced-motion; grouped-bar rendering fixed. +1 base tool create_chart_fence (server-side validator mirror) + the design-chart-recipes skill + byte-identical conformance fixtures across the three suites. Deferred (plan §12): race replay, SPA CSV copy, render_chart_preview REST, mermaid spike, a11y scan.
• 🧠 Model Foundry Phase 1 — Corpus Foundry (PR #7008, Proposal 067). +3 Pro tools — export_trajectory_corpus (harness traces → OpenAI tool-calling rows), export_preference_pairs (DPO rows, R4, min_margin skip), export_plugin_docs_corpus (docs-hub uploads or a symlink-safe validated dir → docs_v1 rows with per-document provenance) — behind the new deactivatable model_foundry Pro module + the ai_ml preset. The WP_MCP_AI_Corpus_Governance engine is consent fail-closed (_wp_mcp_ai_training_consent; caps → exact → fuzzy → opt-in semantic dedup → PII scrub → deterministic content-hash holdout split → R12 provenance → guarded sharded write — holdout rows never enter ; skip-never-truncate). Consent UI ships in Phase 3 ( until then); Phases 0/2–6 deferred in the implementation plan. skill + .

v1.2.3 — October 10, 2026

CORS Same-Origin Enforcement, Standalone SPA WordPress Login & REST Auth Fixes

• 🛡 CORS same-origin enforcement (PR #6986). WordPress core rest_send_cors_headers() (rest_pre_serve_request, priority 10) reflects any Origin header back with Access-Control-Allow-Credentials: true on every REST response — which silently overrode the Security → Network "Same Origin" setting, so a hardened site still echoed arbitrary origins. The new WP_MCP_AI_CORS_Guard (12th includes/security/ class) hooks priority 20 and, in site mode, replaces the reflected header with the configured policy: exact-allowlisted origins (site origin + the new cors_allowed_origins setting, one origin per line + the wp_mcp_ai_cors_allowed_origins filter) are echoed with credentials; everything else gets the site's own origin with credentials off; star mode keeps core's allow-all reflection. Enforcement covers the plugin's REST routes (/mcp-ai/v1 by default, extensible via wp_mcp_ai_cors_guard_route_prefixes); the MCP/OPTIONS/SSE/controller emitters share one resolve_allow_origin(). 20 new tests; 138 related REST/security tests pass.
• 🔐 Standalone SPA WordPress login (PR #6993, Proposal 064). A fourth auth mode for examples/nvoos-pro-spa-vite — WordPress login via an Application Password (Basic auth over REST): wp/v2/users/me?context=edit validation with a UTF-8-safe Basic header, and the real user + capabilities mounted into the runtime, so the deployed app (chat.nvoos.cloud) gets the full admin surface with real server-side capability enforcement instead of the bearer mode's client-side manage_options. The Basic header attaches only to requests targeting the configured site origin (never the media worker or third parties). Plugin-side gaps fixed by live verification: chat_transcripts_permissions_check() skips the nonce for Authorization-header requests (CSRF-safe by construction), and permissions_check()/permissions_check_assistant_list() gained Application Password branches (same capability gates, admin bypass + rate limiting intact). 39 PHPUnit tests; full live matrix verified.
• 🛰 OOS streaming CORS fixed (PR #6993). The OOS engine's SSE emitter (lib/core SseHandler) sent no CORS headers — every cross-origin browser chat stream on OOS-routed sites was blocked (pre-existing; bearer/guest modes too). WP_MCP_AI_CORS_Guard::emit_stream_cors_headers() fires from the WP adapter before ; stays framework-agnostic.