= 0.4.85 (2026-11-14) =
* Auto-discover active and inactive TaxoCommerce plugins using WordPress get_plugins and local ZIP filenames, deduplicate built-in suppliers and register new Accounting/Customers cards without Core updates. Keep native WordPress install and activation screens (WordPress.org-compatible). Issue #2669.

= 0.4.84 (2026-11-13) =
* Fix WordPress.org release packaging to use the confirmed official taxocommerce-core slug, main PHP filename, text domain and five gettext catalogs. Remove obsolete long-slug packaging transformation, ensure the published ZIP contains the same Core code validated in staging, and add regression checks. Issue #2625.

= 0.4.83 (2026-11-13) =
* Address WordPress.org manual-review findings: delegate extension installation/activation/deactivation to WordPress native plugin administration while retaining discovery and authenticated download of local ZIP packages; remove Core's custom upload/installer and obsolete handlers. Make JSON output-buffer cleanup unconditional, separate read-only country GET from validated POST, replace dynamic CSS with static rules, prefix Core anomaly filters, and remove installation-specific post-slug exceptions. Retain native Code Check rules without suppressing remaining warnings. Issue #2625.

= 0.4.82 (2026-11-13) =
* Group native Core Code Check results by severity: red confirmed errors, amber review warnings, green files without findings, grey unchecked files. Show source location, rule and recommended review action. JSON adds classified_findings while keeping existing results and summary unchanged. No external checker or functional code changes. Issue #2623.

= 0.4.81 (2026-11-13) =
* Core Code Check now reports the actual number of findings and rule types, displays all captured evidence and shows Review Required instead of an apparent pass when PHP succeeds but WordPress/security findings exist. JSON gains a consistent summary, without invoking any external plugin. Incomplete or truncated scans never pass. Issue #2621.

= 0.4.80 (2026-11-13) =
* Extend Core's own PHP/WordPress/security Code Check with local, token-based WordPress.org manual-review criteria, source lines, PHP sessions and SQL indicators. No Plugin Check dependency or network requests. Preserve CPU batches and JSON export; regression tests cover reported source locations and distinguish contextual warnings from confirmed failures. Issue #2619.
* Fix false duplicate-symbol reports after interpolated PHP strings; retain official Plugin Check status as not executed.

= 0.4.79 (2026-11-13) =
* Keep the exact Core dashboard header and version history on both Autocheck subtabs. Place independent Functionality Check and Code Check below the persistent navigation; retain bounded code analysis and JSON downloads. No changes to the review findings or store data.

= 0.4.78 (2026-11-11) =
* Fix local Plugin Check on existing stores: Core in taxocommerce-core/ uses its matching native gettext domain and five bundled catalogs. Build the public WordPress.org distribution from the same sources with its assigned long folder, entrypoint, gettext domain and catalogs, strictly checking both packages. Issue #2565.

= 0.4.77 (2026-11-11) =
* Align gettext calls, plugin header, five bundled locale catalogs and WordPress.org ZIP folder with the assigned plugin slug; preserve existing admin URLs and data. Issue #2560.

= 0.4.76 (2026-11-11) =
* Concise WordPress.org readme with coherent version metadata and changelogs. Runtime features and catalog data are unchanged. Issue #2557.

= 0.4.75 (2026-11-11) =
* Added complete read-only JSON download for Core > Content > Anomalies, preserving the separate editorial report.

= 0.4.74 (2026-11-10) =
* Three-zone admin header: unique local Description and static link on left, wider collapsed CHANGELOG.md in center, version/date on right; no duplicate panel. Issue #2521.

= 0.4.73 (2026-11-10) =
* Hide only Action Scheduler's past-due admin notice through its public filter, without changing scheduled tasks or other notices. Issue #2510.

= 0.4.72 (2026-11-10) =
* Admin subtitle uses bundled Description metadata; static Plugin URI and local version history retained. Issue #2494.

= 0.4.71 (2026-11-10) =
* Static local Description and Plugin URI replace Core developer excerpt requests and button; preserve link, local history and legacy uninstall cache cleanup. Issue #2494.

= 0.4.70 (2026-11-10) =
* Optional official developer excerpt requires explicit administrator action; no automatic external requests. Preserve resilient last verified excerpt and local Description from #2489. Readme discloses destination and data sent. Issue #2491.

= 0.4.68 (2026-11-09) =
* WordPress.org pre-review changes: enqueue Core admin styles, use native `wp_handle_upload()` for extension ZIPs, preserve manual extension controls; request slug `taxocommerce-core`. Issue #2481.

= 0.4.62 (2026-11-08) =
* Complete Core gettext catalogs for Spanish, English, French, German and Dutch (791 translatable messages per locale, plus gettext header); no remaining empty translations for currently extracted strings.
* Preserve native WordPress/WooCommerce contents, role and menu APIs, and fixed HTML search attributes. Add regression checks for translated interface labels.
* Translation QA and WordPress Plugin Check required before staging and Focazul deployment. Issue #2062.

= 0.4.61 (2026-11-07) =
* Mantiene el rótulo del menú padre TaxoCommerce Core frente a alteraciones de otros módulos; sin modificar enlaces ni permisos. Issue #2351.

= 0.4.60 (2026-11-07) =
* Core shows all 19 current family plugins, including absent/inactive Tasks, without installing anything automatically.
* WordPress activation-state detection, card actions and translated description preserved; issue #2340.

= 0.4.59 (2026-11-07) =
* Cabecera del administrador: título, versión y fecha de publicación, sin duplicar titulares. Issue #2336.

HISTORIAL LEGADO — TAXOCOMMERCE CORE

TaxoCommerce SEO monolítico, versiones previas a la división modular.
Los números aquí corresponden al MONOLITO, no al plugin independiente.
Fuente: https://github.com/distribuidordeherramientases-wq/seo-taxonomy/blob/staging/CHANGELOG.md
La sección 2.0.0 marcada «Próxima versión» en la fuente no se considera publicación.

ORIGEN Y TRANSICIÓN
* Historical source: the TaxoCommerce SEO monolith through 2.4.1 maintained the SEO architecture, category/product relationships, taxonomy and the original WordPress administration; these are not Core standalone versions.
* The 2.2.x legacy work included the vocabulary bridge, canonical semantic labels and the product/category relationship model.
* During 2.3.x the monolith organised clusters, primary and secondary hubs, landing pages, menus and associated WooCommerce categories/products.
* Core became the administrative and integration point for independent TaxoCommerce extensions, preserving the existing data contracts rather than migrating every service into Core.
* Later standalone work refined the Extensions panel, nested menu navigation, WordPress.org compliance and internal Auto Test. Individual learning, images and feeds remain owned by their respective modules.
* The international storefront uses explicit country-based pages, templates and navigation; the Core layer retains role/menu selection while Templates owns frontend rendering.

CAMBIOS DEL MONOLITO (TEXTO VERIFICADO)

## [2.4.0] - 2026-10-13
Etapa del plugin central:
[Resumen ejecutivo del ciclo 2.4.0] - **Modularización:** inicio de la separación del monolito en TaxoCommerce Core y extensiones de Import-Export, Imágenes y System Check; diseño de Vocabulary y FAQs como módulos diferenciados.

## [2.3.10] - 2026-10-06
Etapa del plugin central:
- Ojeador 0.10.0 añade la pestaña **Novedades**, un radar externo que usa **Clusters + Hubs primarios** como frontera comercial para descubrir categorías, subfamilias y tecnologías que todavía no están representadas en el catálogo.

## [2.3.5]- 2026-09-17
Etapa del plugin central:
[Arquitectura comercial y contenido] - Nuevas recomendaciones de arquitectura para **Clusters, Hubs primarios y Hubs secundarios**.
[Arquitectura comercial y contenido] - Mejoras de las plantillas para incorporar señales y recomendaciones de marketing.
[Arquitectura comercial y contenido] - Ajustes de frontend y helpers de plantillas para mantener coherencia entre STAGING y producción.
[Arquitectura comercial y contenido] - Actualización de informes cuya validación de relaciones entre posts y categorías había quedado obsoleta.

# \[1.5.0\]
Etapa del plugin central:
[Auditoría y validación] -   Validación de Clusters, Hubs Primarios, Hubs Secundarios y Categorías.

# \[1.4.0\]
Etapa del plugin central:
[Arquitectura SEO] -   Implantación de la estructura basada en Clusters.
[Arquitectura SEO] -   Incorporación de Hubs Primarios.
[Arquitectura SEO] -   Incorporación de Hubs Secundarios.
[Arquitectura SEO] -   Relaciones semánticas entre niveles.
[Arquitectura SEO] -   Gestión independiente de nodos SEO.
[Arquitectura SEO] -   Generación de páginas estructurales.

# \[1.3.0\]
Etapa del plugin central:
[Clasificación] -   Gestión de taxonomía SEO independiente.

DIVISIÓN EN PLUGINS AUTÓNOMOS
El cierre ordinario del monolito está documentado en la versión 2.4.1 (25/10/2026).
Las versiones independientes y sus cambios posteriores se registran en CHANGELOG.md.
Véase docs/PLUGIN-HISTORY-SOURCES.md para referencias a los cambios y PR.
