• Changes included in version 0.2.0.

New features

• Replace the long-post screen with a recoverable staged workflow UI that offers Standard, Pro and Pro + internet profiles, optional automatic images, live per-stage progress, retry and cross-page resume controls, automatic SEO handoff, and draft or scheduled publication.
• Complete persistent long-post orchestration by advancing image generation, SEO metadata and publication as separate saved operations after article sections, with media placement receipts and publication deferred until the article is complete.
• Add a persistent long-post workflow service that snapshots generation context, advances research, planning and individual structured sections with replay-safe step IDs, prevents concurrent requests and rebuilds draft content from completed HTML and image-slot blocks without duplicate appends.
• Add a shared SEO service that estimates and generates metadata through the structured long-post API, avoids charges when no supported provider is active, and rollback-safely writes titles, descriptions and focus keywords to Yoast SEO and Rank Math.
• Allow the complete 50,000-character structured business profile to reach relevant requests and expand the long-post prompt to 100,000 characters for full reference articles, with coordinated validation and longer request timeouts.
• Replace the single long business description with a translatable ten-section profile capped at 50,000 characters, including detailed modal guidance, aggregate client/server validation and legacy-value migration.
• Compile a bounded tool-specific business context for writing, landing, image, metadata and context-aware translation requests while preserving the short translation description.
• Raise the image metadata batch limit to 48, load 24 attachments per page, and support Shift-click range selection in the media picker.
• Add the pom_ai_transcribe_audio AJAX bridge so prompt dictation completes: it verifies the nonce, requires edit_posts or upload_files, validates duration, size and real audio type, and forwards the recording to the account transcription service.
• Add the pom_ai_dictation_max_file_size and pom_ai_dictation_allowed_mime_types filters, mirroring the account limits locally so oversized or unsupported recordings fail before upload.
• Warn in the POM AI MCP settings panel when pretty permalinks are not configured, because the discovery and OAuth endpoints are rewrite rules that return 404 while the MCP endpoint keeps answering.
• Report permalinks_enabled from the MCP status endpoint so clients and health checks can detect the same condition.

Fixed

• Require settings and per-post capabilities at the remaining profile and legacy long-post write boundaries, and keep the new character-limit paths functional when PHP's optional mbstring extension is unavailable.
• Preserve image-generation receipts on both the article and imported attachment so a failed article-meta write can recover without purchasing the same image again, reject trashed workflow drafts, and normalize AJAX error status metadata.
• Validate editable image attachments before improvement or background removal, remove local hard-coded source-image overrides, keep provider failures private, and make image credit estimates include the same profile context and style as execution.
• Enforce the aggregate 50,000-character business-profile limit even on partial settings submissions by including the stored values of omitted profile sections.
• Enforce the same five-minute scheduling lead time in the long-post interface and server-side workflow validation, and explain the WP-Cron dependency before users schedule publication.
• Process image metadata batches sequentially with real per-image progress, isolated failures, and paced requests so large selections do not overwhelm the account WAF.
• Route shared license validation through the account server configured by POM_AI_API_DOMAIN and narrowly accept its self-signed certificate in local environments so locally issued keys work with local POM AI services.
• Send dictated audio base64-encoded in a form-encoded body instead of a multipart upload. Signed POM AI requests are verified over the exact request body, and PHP leaves the raw input stream empty for multipart/form-data, so a multipart recording could never satisfy the account signature check.
• Stop wp_update_post and wp_update_page unpublishing content. The shared payload builder applied its draft default on updates as well as creations, so updating a published post or page without an explicit status argument silently moved it to draft. The default now applies only when creating.
• State the replace-by-default behavior in the wp_add_post_terms tool description. MCP clients read tool descriptions to decide how to call a tool, and the previous wording did not say that the call removes every existing term of that taxonomy unless append is true.
• Stop wp_update_option disabling autoload on the options it writes. It passed false as the autoload argument, which rewrites the autoload column, so updating the site title, tagline, posts per page or date formats removed them from the autoloaded set and added a query per option on every request.
• Resolve the pom://theme/templates/{archive,single,feed} MCP resources against POM Theme's numbered documentation directories. The lookup only checked docs/templates/, while the theme ships the references in docs/08-templates/, so all three resources silently served a two-line fallback stub instead of the theme's merge-tag documentation.

Changed

• Centralize Gemini image generation, credit estimation and validated WordPress media imports in a shared service used by the existing image tools and ready for long-post workflows.
• Keep the landing-page generator dormant by removing it from tool settings and preventing its menus and AJAX actions from registering while preserving the implementation for a future restoration.

Documentation

• Explain that scheduled long posts require a working WP-Cron or server cron runner and may remain queued when scheduled tasks are delayed.
• Document the current long-post profiles, first-step estimate, persistent progress and recovery, automatic image and SEO stages, cost shape, and scheduled-publication behavior.
• Document structured profile setup, tool-specific context selection, privacy, translation limitations, image guidance and input-cost behavior.
• Document sequential image metadata processing, Shift-click selection, 24-item picker pages, and the new 48-image batch limit.
• Add the documentation manifest that defines article order for POM Docs Sync.
• Give every POM AI documentation directory, article, and asset a globally unique product-scoped name and update all internal links.
• Enforce numbered documentation topics with no root Markdown files and complete index pages for every topic directory.
• Rewrite the 22-mcp-resources through 26-help chapters as distinct, code-verified guides to MCP resources, prompt recipes, boundaries, developer contracts, and troubleshooting.
• Reorganize and expand public AI and MCP documentation under numbered POM Docs Sync terms.
• Clarify that public documentation must be reader-focused and exclude internal operational material.
• Standardize numbered screenshot placeholders for public Markdown documentation.
• Rewrite the 01-start-here chapter as distinct, code-verified articles covering the product model, requirements, installation, interface locations, a first task, the setup checklist, transmitted data, review obligations, and updates and support.
• Rewrite the 02-license-and-domains chapter as distinct, task-oriented articles covering license activation, single-site and multisite scopes, subsite service licenses, the network update license, shared-subscription use, domain authorization and limits, domain removal, key rotation, and license error codes.
• Correct the documented settings path to Settings > POM AI and replace the internal request-signing description in the licensing chapter index with reader-facing licensing guidance.
• Rewrite the 03-credits chapter as distinct articles covering the credit unit, what does and does not consume credits, estimates and confirmation, balances, insufficient-credit errors, batch consumption order, subscription and top-up sources, expiration, usage history, charge review, and plan sizing.
• Rewrite the 04-writing-tools chapter around the four real writing tools, documenting the long-form outline-then-sections flow, the editable landing and site-wide plans, and the paragraph assistant's three content-creation modes.
• Rewrite the 05-translation chapter for the Polylang-based workflow, including the per-post buttons, the bulk analyze-and-translate screen, placeholder-based formatting preservation, and the untranslated-excerpt limitation.
• Rewrite the 06-image-tools chapter, documenting the reference-image numbering, the 24-image metadata batch limit, and that replacing an original rewrites site-wide references and permanently deletes the source attachment.
• Rewrite the 08-prompts chapter, documenting prompt-template append behavior, the six template contexts and their aliases, and the MCP prompts published by the server.
• Rename 05-translation/pom-translate-integration.md to polylang-integration.md because the translation tool integrates with Polylang, not POM Translate.
• Rewrite the 07-dictation-and-transcription chapter to cover the dictation control, browser permissions, transcription limits, credit cost, audio privacy and troubleshooting.
• Rewrite the 09-mcp-start-here chapter with the connection path, the four-check security model (scopes, WordPress capabilities, write gates, input schemas), the capability map, and reference pages for the MCP, status, discovery and OAuth endpoints.
• Record that MCP API key authentication is permanently read-only, that all four write gates default to closed, and that MCP operations consume no POM AI credits.
• Correct the README claim that a configured service user enables MCP API key writes. API key auth carries the fixed scopes mcp:read and wp:content:read, so no write tool can run under it; the service user only widens what it may read.
• Document the MCP write rate ceiling in the README and in the settings field description: writes use the configured read limit or 20, whichever is lower, and OAuth registration and token requests are fixed at 5 per minute.
• Rewrite the 10-mcp-workflows chapter as task sequences built on the read-check-validate-write-verify shape, covering content, media, taxonomies, comments, menus, options, POM Theme settings and templates, POM Cache, and the WooCommerce catalog, variations and coupons.
• Record the MCP option write allowlist (blogname, blogdescription, posts_per_page, date_format, time_format), the remote media limits (10 MB, no redirects, no private hosts, raster images only), and that product deletion is not exposed while variation and coupon deletion are.
• Rewrite the 11-mcp-authoring-tools chapter as a reference for the seven read-only authoring tools, covering their two scope groups, the normalized shortcode attribute schema, the discouraged-shortcode replacements, merge tag syntax including the %%…%% attribute form, and the error and warning taxonomy of both validators.
• Rewrite the 12-mcp-wordpress-content-tools chapter as a reference for the thirteen post and page tools, covering the public-post-type restriction, the read capability asymmetry between published and unpublished items, listings omitting content, the 1–100 per_page clamp, and the dry-run shapes.
• Rewrite the 13-mcp-wordpress-media-tools chapter as a reference for the eight media tools, covering the upload_files requirement on reads, the double extension-and-content validation on uploads, the four constraints on remote URL fetching, that omitting media_id removes a featured image, and that attachment deletion is permanent on sites without MEDIA_TRASH.
• Rewrite the 14-mcp-wordpress-taxonomy-tools chapter as a reference for the eleven taxonomy tools, covering the replace-by-default assignment behavior, that term reads need no WordPress capability while term meta needs manage_categories, that term listings return no total, that term listings expose no hierarchy, and the credential-name guard on meta keys.
• Correct three tool names that did not exist in the 22-mcp-resources and 24-mcp-boundaries chapters: pom_theme_get_setting to pom_theme_get_settings_values, wp_set_featured_media to wp_set_featured_image, and pom_cache_clear to pom_cache_clear_site_cache.
• Correct the WooCommerce boundary note, which listed product categories among the covered tools. Categories are a replace-by-default field on the product create and update tools; no tool lists, creates or renames a product category.
• Rewrite the 18-mcp-woocommerce-coupon-tools chapter as a reference for the seven coupon tools, covering the edit_shop_coupons capability that differs from the product tools while the scope and write gate are shared, that only eight coupon fields are writable through MCP so minimum spend and per-user limits are unreachable, that the listing omits date_expires so expiry cannot be audited from it, that trashed coupons keep their codes reserved, that wc_delete_coupon's dry run does not verify the coupon exists, and that wc_empty_coupon_trash purges permanently in batches of 100.
• Rewrite the 19-mcp-pom-theme-setting-tools chapter as a reference for the thirteen setting, CSS and asset tools, covering that reads need edit_theme_options while writes need manage_options, that pom_theme_get_status is the only tool registered when POM Theme is unavailable, that the writable-field allowlist contains two fields by default plus dynamic CPT layout fields, that JavaScript writes are refused unconditionally, that CSS validation blocks only PHP and </style> so invalid CSS is stored, and that the batch tool's own dry_run overwrites each entry's.
• Rewrite the 20-mcp-pom-theme-template-tools chapter as a reference for the seven template tools, covering the archive/single/feed split, that templates render nothing until assigned, that template markup is genuinely validated against the per-type merge tag catalog, that deleting a template leaves its assignment dangling, that a cpt_single assignment reports success without changing anything when no POM Theme post type row matches, and that pom_theme_configure_content_model is not atomic so a later-stage failure leaves earlier stages written.
• Rewrite the 21-mcp-pom-cache-tools chapter for the two cache tools, documenting that cache clearing is behind no write gate, that both tools are registered even when POM Cache is absent, that include_json defaults to true, that deleted is true when either purge succeeds so html_deleted must be read separately, and that the cache statistics are reset regardless of the purge outcome.
• Rewrite the 17-mcp-woocommerce-product-tools chapter as a reference for the sixteen catalog tools, covering the shared manage_woocommerce/edit_products permission model and the catalog write gate, that price is computed and only regular_price and sale_price are writable, that product listings return no total and cap at 100 while wc_get_store_stats supplies the counts, that no tool deletes a product, that categories and the product attribute set both replace rather than append, that variation listings omit stock, that wc_get_product_variations returns an empty list for a missing or non-variable product, that wc_batch_update_variations is a non-atomic loop whose per-entry dry_run overrides the batch-level one and which silently skips entries without an id, and that no tool can add terms to an attribute.
• Rewrite the 16-mcp-wordpress-site-and-menu-tools chapter as a reference for the twelve site, menu and SEO tools, covering the three different permission models, the read and write option allowlists, the recursive redaction in plugin settings reads, that menu item deletion is permanent and orphans children, and that the SEO tools write Yoast and Rank Math keys without detecting which plugin is active.
• Rewrite the 15-mcp-wordpress-comment-and-meta-tools chapter as a reference for the seven comment tools and three post meta tools, covering the moderate_comments requirement on comment reads, the edit_post requirement on meta reads, how the four moderation actions differ in reversibility and spam-filter feedback, that created comments are attributed to the acting user, and that post meta has no revision history.

Build

• Synchronize the recursive POM Knowledge Markdown tree to wp-content/docs/pom-knowledge during local release builds while excluding hidden and non-Markdown files.
• Update POM Framework so managed file reads are cached per request and OPcache remains an optional acceleration layer.

• Changes included in version 0.1.1.

Breaking changes

• Replaced the legacy public/private API key pair with the single POM AI product license key; legacy keys are no longer sent or accepted.

New features

• Added mandatory per-site POM AI licenses on multisite: each subsite (including third-party sites) must explicitly authorize its domain with a license whose account supplies the credits; plugin updates keep using the network license managed from the main site.
• Added the network-aware missing/invalid license admin notice and subscription cost info on the License tab.
• Added the shared POM Framework license field (save, masked display, revalidate, unlink) to the AI settings License tab.
• Sent X-POM-License-Key and X-POM-Domain headers on every account API request.

Fixed

• Updated license guidance to list the canonical Single, Agency, and Unlimited POM AI plans.
• Added an always-visible multisite subsite license message explaining the main-site activation and network-license requirements for automatic updates.
• Stopped recommending or generating the retired listings shortcode and aligned POM authoring guidance with web_listings and its faceted-search mode.
• Prevented duplicate monthly subscription credit batches from stacking in account balances.

Security

• Signed every POM AI request with timestamp, nonce, exact-body HMAC, and the shared product license key, and moved fallback updates exclusively to licensed v2 tokens with SHA-256 verification.

Changed

• Removed the unused account-side development copy so POM Standard remains the only account.pom.es POM AI implementation.

Documentation

• Required complete production-facing documentation maintenance and the canonical access-denying .htaccess in repository agent guidance.
• Replaced the completed client migration runbook with a permanent licensing, multisite, and verification reference, corrected setup/FAQ guidance, and removed placeholder links.
• Documented the client/account ownership boundary and direct migration to the shared single-license protocol.
• Standardized pending and historical release notes under the current categorized changelog format.
• Updated the release procedure to require dated changelog headings.

Build

• Centralized plugin documentation under wp-content/docs/pom-ai during local release builds and excluded the docs tree from ZIP artifacts.
• Sourced manifest release notes from versioned changelog sections and rejected invalid changelog structures during builds.
• Accepted mandatory ISO release dates in versioned changelog headings when generating manifests.
• Pruned repository metadata from Composer dependencies before packaging production ZIPs.

Internal

• Deleted the local pom_ai_api_keys option automatically after the new license validates, leaving a non-secret migration marker.
• Standardized incremental changelog maintenance and required CHANGELOG.md in release packages.

• Changes included in version 0.1.

Internal

• Established the existing release baseline before adoption of the incremental changelog workflow.

The entries below reconstruct unversioned or previously undocumented development before this repository adopted incremental release notes. Each active month consolidates its non-merge Git commits; merge-only, version-number-only, and internal tracking-only commits are omitted.

2026-06

New features

• Images: replaced references when replacing images.

Fixed

• Ai Translate: set Polylang language before translated terms. Set translated posts/products to the destination Polylang language before assigning translated taxonomy terms, so Polylang filters resolve categories in the target language.
• Framework: import framework classes consistently.
• Tinymce: open AI modal from separate editors.
• Releases: hardened private release publishing.

Security

• Security: POM Framework - Harden settings AJAX and dependency toolchain.

Changed

• Mcp: removed legacy iconpicker reference.
• Framework: POM Framework - Rename Pomatio Framework.

2026-05

New features

• Ai Mcp: added integrated MCP server.
• Added POM Cache tools to MCP for cache management.
• Ai Mcp: added MCP server settings to configuration and update access control.
• Mcp: added authoring context resources and validation.
• Mcp: improved MCP resources and prompts.

Fixed

• Ai Mcp: default OAuth DCR scopes for ChatGPT.
• Mcp: improved styling and layout of OAuth consent screen.
• Ai Mcp: accept missing OAuth resource from Codex.
• Account: aggregate domain allowances across active subscriptions.

Security

• Pom Form: updated pom-form reference and improve CSS class sanitization.

Documentation

• Updated AGENTS.md file.

2026-04

New features

• Implemented field persistence logic in Pomatio Framework to manage transient UI state.
• Pom Ai: migrated AI tools to GPT-5.4 and Gemini 3.1 image preview.
• Pom Translate: added translator notes to machine translation prompts.
• Merge Tags: pomatio Framework - Add robust nested merge tag parsing.
• Pom Form: added bulk open and close controls to repeaters.

Fixed

• Pom Ai: kept subscription credits active during delayed renewals.
• Pom Ai: reuse shared Responses parser for image metadata generation.
• Wines: improved local wine search matching.
• Openai: raise GPT-5 output token ceiling.
• Pom Form: contain CodeMirror horizontal overflow.

Security

• Pom Form: pomatio Framework - Apply WordPress file permissions to generated settings.

2026-03

New features

• Added prompt template manager. Added new reference images and per-image prompt for image improver tool.
• Added bulk wine creation feature from images and enhance AI wine filling functionality.
• Enhanced error handling and add detailed information for bulk wine creation process.
• Enhanced image processing by adding output directory handling and creating named temporary files.
• Added output format handling for image processing and enhance resizing functionality.
• Pom Ai: bg remover auto dimensions in target size.
• Improved AI fetching with AI.

Changed

• Pomatio Framework updated.

Documentation

• AGENTS.md update.

2026-02

Fixed

• Extract domain from url on domain adding on POM AI account.
• POM AI credits not being granted on subscription.
• POM AI Status detection was brittle (could return inactive even with a real subscription).

Changed

• Updated: improved plugin dashboard widget.
• Updated: Pomatio Framework.

Build

• Updated: Pomatio Framework and other vendor dependencies.

2026-01

New features

• Enhanced font management features in Pomatio Framework.
• AI: used gpt-5.2 for build-page generators.
• Enhanced AI text generation with improved AJAX handling and response extraction.
• Updated default word counts and add guidelines for content structure in prompt templates.

Fixed

• Improved shortcode handling and translation response validation in helpers.
• Ensured safe word count handling in createRepeaterItem function.
• Translate: handle WP_Error and chunk Google requests.
• Defer settings loading to init and improve settings definition handling.

Changed

• Refactored AI image generation and improvement prompts.

Build

• Composer updated.

2025-12

Fixed

• Handle product translation requests.
• Aligned woo term translations and short excerpts.

Build

• Composer updated, fixed product translating.
• Composer updated.

2025-11

New features

• Added google gemini image helper.
• Added Gemini image generation php function.
• Pom Account: used gemini for image generation.
• Image Tools: added support for expanded aspect ratios.
• Added images for radio tiles, removed post writer tool.
• Track AI credits with expiring batches.
• Surface credit breakdown in account dashboard.
• Landing Generator: stream section builds with progress.
• Admin: enhanced dashboard banner.
• Added plugin updater.

Fixed

• API: propagate remote errors.
• Propagate API failures to ajax handlers.
• Preserved prompt formatting.
• Hardened AI translate entity cloning.
• Improved WooCommerce translation coverage.
• Validate credit inputs and harden dashboard output.
• Prevented duplicated long post actions.
• Clamp long post word count.
• Hardened landing generator defaults and errors.
• Hardened image and translation helpers.
• Normalize generated image payloads.
• Respected table prefix for domain limits.
• Used max_completion_tokens for chat models.
• Pom Account: used standard text domain.
• Delay background removal deletion.
• Enforce image metadata limits and preserve fields.
• CSS fix.
• Settings: derive locale-based language labels.
• Persist landing generator AI context.
• Exclude vendor and node_modules from cs-fix.
• Honored top-up credits for standard orders.
• Process credits on all orders.

Changed

• Updated credits rates per tool.
• Improved image generator tools.
• Improved pom-account.
• Stop storing blog id in credit tables.
• Ignore /var folder and remove it from repo tracking.
• TinyMCE tool improvements.
• Dashboard improvements.
• Landing generator improvements.
• Improved my account endpoint.
• Improved translation prompt.

Documentation

• Document credit usage for pom account apis.
• Improved AGENTS.md.

Build

• Added releases workflows and scripts.
• Updated memory limit for composer stan command.
• Fixed composer cs errors.
• Composer updated.

Internal

• Added qa composer scripts.
• Stabilized phpstan.
• Added cs-fix command.

2025-10

New features

• Added remove bg tool.
• Added placeholder imagery to AI tool selection tiles.
• Added shared character limit handling to AI prompts.
• Added pom-pomstandard folder.
• Handle additional dictation audio MIME types.
• Expand allowed MIME types for audio transcription.
• Added reusable dictation component for admin prompts.
• Added voice dictation.
• Added direct generation option across AI tools.
• Added logging for AI credit consumption.
• Added usage logs table to account view.
• Account: auto-manage single-domain credits.

Fixed

• Fixed tile radio selection state in media tools.
• Fixed transcription request to send audio file data.
• Ensured credit renewals and account ux.

Security

• Enforce capabilities on ajax handlers.
• Changed permissions to edit_posts for getting credits.

Changed

• Updated pom-form.
• Moved wp core notices to an empty h1 for tidier look in wp admin.
• Moved each tool under corresponding submenus in wp admin.
• Refactored AI image generator admin UI.
• Removed modal from image generate tool.
• Refactored AI media tools to inline forms.
• Used tile layout for radio groups in image tools.
• Improved metadata row layout.
• Refine media picker layout and pagination.
• Removed unused previous page controls from image pickers.
• Used WP color picker for background selection.
• Refactored landing and long post tools to inline forms.
• Adjust progress display for structured tools.
• Deleted transcribe audio tool.
• Persist remaining credits across tools.
• Automate long post writer flow.
• Handle Safari dictation audio uploads.
• Improved audio mime detection for dictation uploads.
• Log credit movements for domain management.

Documentation

• Added AGENTS.md file.

Styles

• Improved styles.

Build

• Refactored AI texts generator to inline workflow.

2025-09

New features

• Updated pom-framework, added requires_initialization to false on main settings.

Changed

• Updated Pomatio Framework.
• Updated pom-form.

2025-08

New features

• Long posts writer tool for POM AI created.

Changed

• Updated translations.

Styles

• Moved bottom bar css to fenomenus.

2025-07

New features

• Added TODOs.
• Wines from image now allow to paste from Excel.
• New image improver tool.
• Added tool images and descriptions.

Changed

• Image generator now uses modern models.
• Applied maintenance updates to admin settings.
• Updated POM form.
• Updated settings.
• Improved UI.
• Moved AI wines from image to POM Restaurant Menus plugin.

Styles

• Minor admin CSS changes.

2025-06

New features

• Allowed editors to access AI tools.
• Added .gitignore.

Fixed

• Fixed translate with AI.
• Small fix for translating posts.

Changed

• Updated Pomatio Framework.

Styles

• Improved translate with AI styles.

2025-05

Changed

• Updated Pomatio Framework.
• Improvements to wine searcher.

2025-04

New features

• Added structured outputs for text generator.
• Added structured outputs for landing page generator.

Changed

• Updated POM AI API calls to account.pom.es.
• Improved text generator.
• The landing page generator now also designs.
• Translate with AI moved to POM AI plugin.

2024-10

New features

• Added appspec.yml file.
• Changed endpoints to work on production env, added transcibing AI tool.
• Improved text generator tool, added wines from image tool.

Fixed

• Temp debugging commit.
• POM AI debugging.

Changed

• Replaced local api endpoints by real production endpoints.
• Changed calculate credits API call from GET to POST.
• Changed calculate credits API call from POST to GET.

2024-09

New features

• New helpers: pom_ai_deduct_credits, pom_ai_get_site_credits, pom_ai_add_credits_to_site.
• Added image generator and image metadata generator.

Fixed

• Fixed modal for image generator module after image is generated.

Changed

• Translated admin menu links.
• Now all the prompts are generated with the Pomatio API.
• Now the api keys are stored as options in the site.

Documentation

• Added README.md.

Styles

• Unified repeated css in a shared css file, changed api keys to headers instead of body.

Internal

• Initial commit with base features.