claude-plugin-wordpress-manager 2.12.2 → 2.14.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "wordpress-manager",
-  "version": "2.6.0",
-  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (111 tools incl. WooCommerce + Multisite + Webhooks + Mailchimp + Buffer + SendGrid + Google Search Console), and WordPress.com MCP (hosted sites) with 12 specialized agents, 36 skills, and security hooks. Includes AI content optimization (headline scoring, readability, SEO scoring, content triage), Google Search Console integration (keyword tracking, indexing, SEO feedback), social/email distribution (Mailchimp, Buffer, SendGrid), programmatic SEO, content-commerce attribution, multi-language network, fleet monitoring, content repurposing, webhook propagation, site monitoring, CI/CD pipeline automation, WordPress Multisite network management, WooCommerce store management, local dev environment support, development, testing, security, i18n, accessibility, headless, and operations.",
+  "version": "2.13.0",
+  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP, WP REST API bridge (148 tools incl. WooCommerce, Multisite, Mailchimp, Buffer, SendGrid, GSC, GA4, Plausible, CWV, Slack, Workflows, LinkedIn, Twitter, Schema), and WordPress.com MCP with 45 skills, 12 agents, and security hooks. v2.13.0 adds Content Framework: 3-phase pipeline from signals intelligence to editorial calendar to WordPress publishing.",
   "author": {
     "name": "vinmor",
     "email": "morreale.v@gmail.com"
@@ -37,7 +37,12 @@
     "seo-feedback",
     "content-optimization",
     "readability",
-    "headline-scoring"
+    "headline-scoring",
+    "content-framework",
+    "content-pipeline",
+    "editorial-calendar",
+    "signals-intelligence",
+    "structured-data"
   ],
   "mcpServers": "./.mcp.json"
 }

package/CHANGELOG.md

@@ -2,6 +2,98 @@
 
 All notable changes to the WordPress Manager plugin for Claude Code.
 
+## [2.14.0] — 2026-03-02
+
+### Added — Editorial Kanban Dashboard
+
+Dashboard HTML statico generato on-demand dai file `.content-state/`. Zero dipendenze esterne, zero network call, zero framework — un singolo file HTML self-contained apribile nel browser.
+
+**Skill `wp-dashboard`**
+- Nuova skill con trigger in italiano e inglese ("mostra dashboard", "show editorial status", "apri kanban")
+- Workflow 4-step: sito target → mese → generazione → report
+- Guida visuale integrata: come leggere colonne, card, signals, progress bar
+- Tabella "Next Actions by Observation" che collega osservazioni visive ad azioni specifiche
+
+**Script `context-scanner.mjs` (modulo condiviso)**
+- Parser YAML frontmatter manuale (zero dipendenze npm) per `.content-state/` files
+- Parser tabelle Markdown editoriali con risoluzione date
+- `scanContentState()` — lettura aggregata di config, calendario, brief attivi/archiviati, signals
+- `aggregateMetrics()` — metriche pipeline: colonne, progress, fill rate, next deadline, channel usage
+- `renderContextSnippet()` — stub terminale per Fase B (context injection nelle skill esistenti)
+
+**Script `dashboard-renderer.mjs` (CLI + HTML)**
+- Template HTML Kanban con 5 colonne: Planned → Draft → Ready → Scheduled → Published
+- Card colorate per status con date, titoli, brief ID, WP post ID, badge canali
+- Progress bar con rapporto pubblicati/target
+- Signals strip con anomalie e delta percentuali
+- CSS Grid responsivo, stampa-friendly, ~14 KB output
+- CLI: `--site=X`, `--month=YYYY-MM`, `--output=path`, `--no-open`
+- Auto-detect sito se configurazione unica
+- Apertura browser cross-platform (Linux/macOS/Windows)
+- npm script: `npm run dashboard -- --site=mysite`
+
+**Verificato con dati reali mysite.example.com**
+- 8 entry calendario (3 planned, 1 draft, 2 ready, 2 published)
+- 3 anomalie signals (+120%, +85%, +47%)
+- Output 13.7 KB, tutte le sezioni presenti
+
+---
+
+## [2.13.0] — 2026-03-02
+
+### Added — Content Framework (3 Phases)
+
+Il Content Framework introduce un'architettura a 3 fasi che collega signal intelligence, content pipeline e editorial calendar. Zero nuovi MCP tool TypeScript — l'intera orchestrazione vive nel CLI via skill + file Markdown strutturati.
+
+**Phase 1: Content Pipeline Engine**
+- Nuova skill `wp-content-pipeline` con workflow 5-step: `RECEIVE → PREPARE → PUBLISH → DISTRIBUTE → ARCHIVE`
+- Schema `content-brief.schema.md` — formato di scambio tra Gen* skill e WordPress
+- Schema `site-config.schema.md` — configurazione per-sito (cadenza, canali, defaults)
+- Directory `.content-state/` con pipeline-active/archive per gestione brief
+- Supporto multi-sito (mysite + altri)
+- Distribuzione automatica su Buffer + Mailchimp dopo pubblicazione
+
+**Phase 2: Content Intelligence**
+- Estesa skill `wp-analytics` con Step 7 (signal feed generation)
+- Schema `signals-feed.schema.md` — compatibile con GenSignal NormalizedEvent
+- Delta calculation: confronto metriche con periodo precedente
+- Riconoscimento automatico pattern GenSignal (Search Intent Shift, Early-Adopter Surge, Price-Floor Inversion)
+- Pipeline: analytics → signals-feed.md → insight azionabili
+
+**Phase 3: Editorial Calendar**
+- Nuova skill `wp-editorial-planner` con workflow 4-step: `PLAN → BRIEF → SCHEDULE → SYNC`
+- Schema `editorial.schema.md` — calendario mensile con tabelle settimanali (7 colonne)
+- Lifecycle entry: `planned → draft → ready → scheduled → published`
+- Integrazione cross-phase: signals-feed → topic suggestions → calendar → brief → WP post
+- SYNC bidirezionale: status WordPress → aggiornamento calendario
+
+**E2E Test su mysite.example.com**
+- PLAN: anomalia signals-feed (acqua premium +120%) → topic assignment ✅
+- BRIEF: calendar entry → BRF-2026-005.brief.md con contenuto completo ✅
+- SCHEDULE: brief → WP post via AIWU ✅ (con limitazione `post_date` documentata)
+- SYNC: lettura status WP e verifica calendario ✅
+- Cleanup: test posts eliminati ✅
+
+**Known Limitation — AIWU MCP**
+- `wp_create_post` / `wp_update_post` non supportano `post_date`
+- `status: future` non funziona via AIWU (auto-publish)
+- Workaround: usare wp-rest-bridge `create_content` che supporta `date`
+
+### Added — Validation Runner v1.2.0
+
+- Sistema di validazione automatica per tutti i 148 MCP tool
+- Test CRUD per 26 write tool con sequenze automatiche a 2 tier
+- Modalità interattiva CLI con `@clack/prompts` (selezione sito, tipo validazione, filtro modulo)
+- Flag `--site=X` per selezione sito in batch mode
+- Report: 48 read passed, 26 write passed, 0 failed su mysite
+
+### Stats
+
+- Skills: 43 → **45** (+wp-content-pipeline, +wp-editorial-planner)
+- Reference schemas: +4 (content-brief, site-config, signals-feed, editorial)
+- Architecture doc: `docs/plans/2026-03-02-content-framework-architecture.md`
+- GUIDE.md: +3 sezioni (17.4 Content Pipeline, 17.5 Content Intelligence, 17.6 Editorial Calendar)
+
 ## [2.12.2] — 2026-03-01
 
 ### Fixed — Structured Data Tools Rewrite
@@ -19,7 +111,7 @@ All notable changes to the WordPress Manager plugin for Claude Code.
 - Now finds ALL JSON-LD scripts on a page (not just the first)
 - Reports per-schema issues with type labels
 
-### Validated end-to-end on opencactus.com
+### Validated end-to-end on mysite.example.com
 - sd_inject Article on post 2348: ✅
 - sd_list_schemas finds injected schema: ✅
 - sd_validate on live URL: ✅ (2 schemas detected)
@@ -42,7 +134,7 @@ All notable changes to the WordPress Manager plugin for Claude Code.
 - Corrected tool count from 145 to 148 across GUIDE.md and package.json
 - WordPress core: Plugins 6 (not 5), Users 6 (not 5), Media 5 (not 4), +Search (1)
 
-### Validated end-to-end on opencactus.com
+### Validated end-to-end on mysite.example.com
 - `get_active_site`, `list_content`, `sd_validate` (markup + URL), `sd_list_schemas`
 - GSC, Mailchimp tools return correct "not configured" errors
 

package/agents/wp-accessibility-auditor.md

@@ -6,7 +6,7 @@ description: |
 
   <example>
   Context: User wants to check their WordPress theme for accessibility compliance.
-  user: "Run an accessibility audit on my opencactus.com site"
+  user: "Run an accessibility audit on my mysite.example.com site"
   assistant: "I'll use the wp-accessibility-auditor agent to perform a WCAG 2.2 AA compliance audit."
   <commentary>Accessibility audits require automated scanning, code review, and manual testing guidance.</commentary>
   </example>

package/agents/wp-content-strategist.md

@@ -6,7 +6,7 @@ description: |
 
   <example>
   Context: User wants to create a new blog post with SEO optimization.
-  user: "Create a blog post about cactus water benefits for opencactus.com"
+  user: "Create a blog post about sparkling water benefits for mysite.example.com"
   assistant: "I'll use the wp-content-strategist agent to draft and publish the post with SEO optimization."
   <commentary>Content creation with SEO awareness requires specialized content workflow.</commentary>
   </example>
@@ -20,7 +20,7 @@ description: |
 
   <example>
   Context: User needs to manage taxonomies and organize content.
-  user: "Create product categories for the DolceZero line"
+  user: "Create product categories for the AcmeBrand line"
   assistant: "I'll use the wp-content-strategist agent to set up the taxonomy structure."
   <commentary>Taxonomy design impacts content architecture and SEO.</commentary>
   </example>

package/agents/wp-deployment-engineer.md

@@ -6,7 +6,7 @@ description: |
 
   <example>
   Context: User wants to deploy a custom plugin to their Hostinger-hosted WordPress site.
-  user: "Deploy the bioeconomy modal plugin to opencactus.com"
+  user: "Deploy the bioeconomy modal plugin to mysite.example.com"
   assistant: "I'll use the wp-deployment-engineer agent to handle the deployment."
   <commentary>Plugin deployment to Hostinger requires specialized deployment workflow.</commentary>
   </example>

package/agents/wp-distribution-manager.md

@@ -128,4 +128,4 @@ After each distribution operation, provide:
 
 ## Context
 
-Working directory: `/home/vinmor/.claude/plugins/local/wordpress-manager`
+Working directory: `/home/user/.claude/plugins/local/wordpress-manager`

package/agents/wp-monitoring-agent.md

@@ -6,7 +6,7 @@ description: |
 
   <example>
   Context: User wants to set up monitoring for their WordPress site.
-  user: "Set up monitoring for my opencactus.com site"
+  user: "Set up monitoring for my mysite.example.com site"
   assistant: "I'll use the wp-monitoring-agent to establish a monitoring baseline and configure health checks."
   <commentary>Monitoring setup requires running detection, establishing baselines, and configuring checks.</commentary>
   </example>

package/agents/wp-performance-optimizer.md

@@ -6,7 +6,7 @@ description: |
 
   <example>
   Context: User's WordPress site is loading slowly.
-  user: "My opencactus.com site is really slow, can you help?"
+  user: "My mysite.example.com site is really slow, can you help?"
   assistant: "I'll use the wp-performance-optimizer agent to diagnose performance bottlenecks."
   <commentary>Performance diagnosis requires checking plugins, hosting, caching, and content delivery.</commentary>
   </example>

package/agents/wp-security-auditor.md

@@ -6,7 +6,7 @@ description: |
 
   <example>
   Context: User wants a security audit of their WordPress site.
-  user: "Run a security check on opencactus.com"
+  user: "Run a security check on mysite.example.com"
   assistant: "I'll use the wp-security-auditor agent to perform a comprehensive security audit."
   <commentary>Security audits require checking plugins, users, hosting config, and known vulnerabilities.</commentary>
   </example>

package/agents/wp-site-manager.md

@@ -6,21 +6,21 @@ description: |
 
   <example>
   Context: User wants to check the status of their WordPress site.
-  user: "What's the status of my opencactus.com site?"
+  user: "What's the status of my mysite.example.com site?"
   assistant: "I'll use the wp-site-manager agent to check your site status."
   <commentary>Site status check requires coordinating multiple API calls.</commentary>
   </example>
 
   <example>
   Context: User wants to manage content across multiple WordPress sites.
-  user: "List all draft posts on opencactus"
+  user: "List all draft posts on mysite"
   assistant: "I'll use the wp-site-manager agent to query your WordPress content."
   <commentary>Content management operations should go through this agent.</commentary>
   </example>
 
   <example>
   Context: User needs to switch between WordPress sites.
-  user: "Switch to my bioinagro site and list plugins"
+  user: "Switch to my othersite site and list plugins"
   assistant: "I'll use the wp-site-manager agent to handle multi-site operations."
   <commentary>Multi-site coordination is a core capability of this agent.</commentary>
   </example>

package/commands/wp-setup.md

@@ -16,8 +16,8 @@ Add and configure a new WordPress site for management through Claude Code.
 
 ### Step 1: Gather Site Information
 Ask the user for:
-- **Site URL**: The WordPress site's base URL (e.g., `https://opencactus.com`)
-- **Site ID**: A short identifier for multi-site switching (e.g., `opencactus`)
+- **Site URL**: The WordPress site's base URL (e.g., `https://mysite.example.com`)
+- **Site ID**: A short identifier for multi-site switching (e.g., `mysite`)
 - **Admin username**: WordPress admin email or username
 - **Application password**: Generated from WordPress Admin → Users → Profile → Application Passwords
 - **Hosting provider**: Hostinger / other (determines available tools)

package/docs/GUIDE.md

@@ -130,7 +130,7 @@ wordpress-manager/                          # v2.12.2
 |   +-- wp-distribution-manager.md              # Multi-channel distribution + LinkedIn + Twitter/X (v2.10.0)
 +-- commands/                               # 5 slash commands
 |   +-- wp-status.md / wp-deploy.md / wp-audit.md / wp-backup.md / wp-setup.md
-+-- skills/                                 # 43 skill totali
++-- skills/                                 # 46 skill totali
 |   +-- [OPERATIVE - 5 skill]
 |   +-- wp-deploy/                              # Procedure deploy
 |   +-- wp-audit/                               # Checklist audit
@@ -346,7 +346,7 @@ WordPress Manager comprende richieste in linguaggio naturale. Ecco come formular
 
 | Cosa vuoi fare | Come chiederlo |
 |----------------|----------------|
-| Controllare lo stato | "Come sta il mio sito?" / "Status di opencactus" |
+| Controllare lo stato | "Come sta il mio sito?" / "Status di mysite" |
 | Creare un post | "Crea un post su..." / "Scrivi un articolo su..." |
 | Deploy un plugin | "Deploya il plugin X" / "Pusha il tema in produzione" |
 | Audit sicurezza | "Fai un audit di sicurezza" / "Controlla la sicurezza del sito" |
@@ -356,7 +356,7 @@ WordPress Manager comprende richieste in linguaggio naturale. Ecco come formular
 | Ripristinare un backup | "Ripristina il backup" / "Restore dal backup di ieri" |
 | Migrare un sito | "Migra il sito su Hostinger" / "Trasferisci il sito" |
 | Aggiungere un nuovo sito | "Configura un nuovo sito WordPress" |
-| Cambiare sito attivo | "Passa al sito bioinagro" / "Switch a opencactus" |
+| Cambiare sito attivo | "Passa al sito othersite" / "Switch a mysite" |
 | Eseguire test | "Esegui i test" / "Lancia Playwright" / "Testa il plugin" |
 | Hardening sicurezza | "Metti in sicurezza il sito" / "Hardening" |
 | Audit accessibilita | "Controlla l'accessibilita" / "WCAG audit" |
@@ -557,7 +557,7 @@ Il plugin include **12 agenti** organizzati per area di competenza. Alcuni agent
 - Switching tra siti multipli
 - Coordinamento tra tool Hostinger e WP REST Bridge
 
-**Esempio attivazione**: "Come sta il mio sito?", "Passa al sito opencactus", "Elenca tutti i siti configurati"
+**Esempio attivazione**: "Come sta il mio sito?", "Passa al sito mysite", "Elenca tutti i siti configurati"
 
 ---
 
@@ -982,7 +982,7 @@ wp-block-development: guida creazione blocco
 ```
 
 ```
-Utente: "Deploya il plugin su opencactus"
+Utente: "Deploya il plugin su mysite"
   |
 wordpress-router: TASK = operativo
   |
@@ -1373,7 +1373,7 @@ Questi hook eseguono script bash per validazioni tecniche:
 Per un'operazione di import WordPress, la catena e:
 
 ```
-Utente: "Importa il backup su opencactus"
+Utente: "Importa il backup su mysite"
   |
 Hook #6 (backup-reminder.sh) -> Stampa reminder backup
   |
@@ -1536,26 +1536,26 @@ Aggiungi piu siti a `WP_SITES_CONFIG`:
 ```bash
 export WP_SITES_CONFIG='[
   {
-    "id": "opencactus",
-    "url": "https://opencactus.com",
-    "username": "admin@opencactus.com",
+    "id": "mysite",
+    "url": "https://mysite.example.com",
+    "username": "admin@mysite.example.com",
     "password": "xxxx xxxx xxxx xxxx"
   },
   {
-    "id": "bioinagro",
-    "url": "https://bioinagro.com",
-    "username": "admin@bioinagro.com",
+    "id": "othersite",
+    "url": "https://othersite.example.com",
+    "username": "admin@othersite.example.com",
     "password": "yyyy yyyy yyyy yyyy"
   }
 ]'
-export WP_DEFAULT_SITE="opencactus"
+export WP_DEFAULT_SITE="mysite"
 ```
 
 ### Cambio Sito
 
 ```
-"Passa al sito bioinagro"
-"Switch to opencactus"
+"Passa al sito othersite"
+"Switch to mysite"
 "Elenca i siti configurati"
 ```
 
@@ -1578,7 +1578,7 @@ Il wp-site-manager agent determina automaticamente quale set di tool usare:
 ### Scenario 1: Check-up Mattutino del Sito
 
 ```
-Tu: "Come sta opencactus oggi?"
+Tu: "Come sta mysite oggi?"
 
 Claude:
 - Controlla raggiungibilita (HTTP 200)
@@ -1592,7 +1592,7 @@ Claude:
 ### Scenario 2: Pubblicare un Articolo Ottimizzato SEO
 
 ```
-Tu: "Scrivi e pubblica un articolo sulla bioeconomia del fico d'India in Sicilia"
+Tu: "Scrivi e pubblica un articolo sulla bioeconomia del frutto mediterraneo in Mediterraneo"
 
 Claude (attiva wp-content-strategist + skill wp-content):
 1. Propone struttura (H1, H2, H3)
@@ -1764,7 +1764,7 @@ Claude (attiva wp-cicd-engineer + skill wp-cicd):
 ### Scenario 14: Monitoring Continuo del Sito
 
 ```
-Tu: "Configura il monitoring completo per opencactus.com"
+Tu: "Configura il monitoring completo per mysite.example.com"
 
 Claude (attiva wp-monitoring-agent + skill wp-monitoring):
 1. Detection con monitoring_inspect.mjs (rileva setup esistente)
@@ -2014,7 +2014,7 @@ Claude (attiva wp-distribution-manager + skill wp-linkedin):
 ### Scenario 30: Thread Twitter/X dal Blog
 
 ```
-Tu: "Crea un thread Twitter dal mio ultimo articolo sul fico d'India"
+Tu: "Crea un thread Twitter dal mio ultimo articolo sul frutto mediterraneo"
 
 Claude (attiva wp-distribution-manager + skill wp-twitter):
 1. Detection con twitter_inspect.mjs (OAuth tokens configurati?)
@@ -2029,10 +2029,10 @@ Claude (attiva wp-distribution-manager + skill wp-twitter):
 ### Scenario 31: Generare Contenuto AI da Zero
 
 ```
-Tu: "Scrivi un articolo sui benefici dell'acqua di cactus per l'idratazione"
+Tu: "Scrivi un articolo sui benefici dell'acqua premium per l'idratazione"
 
 Claude (attiva wp-content-strategist + skill wp-content-generation):
-1. Brief: topic = acqua di cactus, audience = consumatori health-conscious, goal = informare, 1200-1500 parole
+1. Brief: topic = acqua premium, audience = consumatori health-conscious, goal = informare, 1200-1500 parole
 2. Keyword research: se GSC disponibile, gsc_query_analytics per keyword correlate; altrimenti suggerisce keyword semantiche
 3. Outline: pattern "Standard Article" — intro + 4 H2 (benefici, scienza, vs alternative, come usare) + conclusione
 4. Draft: scrive contenuto calibrato sulla voce del sito (analizza ultimi 5 post per tono)
@@ -2159,6 +2159,130 @@ File:           644 (rw-r--r--)
 wp-config.php:  440 (r--r-----)
 ```
 
+### 14.8 Validation Runner — Test Automatizzati dei Tool MCP
+
+Il **Validation Runner** (`scripts/run-validation.mjs`) verifica il corretto funzionamento di tutti i 148 tool MCP registrati. Supporta due modalita di utilizzo: **interattiva** (menu guidato) e **batch** (flag CLI per automazione/CI).
+
+#### Modalita Interattiva
+
+Lanciando lo script senza flag si attiva un menu guidato con `@clack/prompts`:
+
+```bash
+node scripts/run-validation.mjs
+```
+
+Il menu guida attraverso 4 step:
+
+1. **Selezione sito target** — lista automatica dai siti in `WP_SITES_CONFIG`
+2. **Tipo di validazione** — read tool, write tool per tier, o validazione completa
+3. **Filtro modulo** (opzionale) — per testare un singolo modulo (es. `unified-content`)
+4. **Conferma** — riepilogo e conferma prima dell'esecuzione
+
+```
+┌  WP REST Bridge — Validation Runner v1.2.0
+│
+◆  Seleziona il sito target
+│  ● mysite (https://mysite.example.com)
+│  ○ othersite (https://othersite.example.com)
+└
+◆  Cosa vuoi validare?
+│  ○ Solo read tool
+│  ○ Solo write tool (Tier 1 — CRUD base)
+│  ○ Solo write tool (Tier 2 — con dipendenze)
+│  ○ Solo write tool (tutti i tier)
+│  ○ Tutto (read + write)
+└
+```
+
+#### Modalita Batch (CLI)
+
+Per automazione, CI, o uso da Claude Code si usano i flag:
+
+```bash
+# Selezionare sito specifico
+node scripts/run-validation.mjs --site=mysite
+
+# Test solo read tool
+node scripts/run-validation.mjs --site=mysite --module=unified-content
+
+# Test write CRUD sequences
+node scripts/run-validation.mjs --site=mysite --test-writes
+
+# Solo Tier 1 (content, term, comment, user)
+node scripts/run-validation.mjs --test-writes --tier=1
+
+# Solo Tier 2 (media, plugin, assign_terms)
+node scripts/run-validation.mjs --test-writes --tier=2
+
+# Regolare il delay tra le chiamate
+node scripts/run-validation.mjs --delay=200
+```
+
+**Flag disponibili**:
+
+| Flag | Descrizione |
+|------|-------------|
+| `--site=ID` | Seleziona il sito target (switch automatico via MCP) |
+| `--module=NOME` | Filtra per modulo (es. `unified-content`, `gsc`, `wc-products`) |
+| `--test-writes` | Esegue sequenze CRUD: create > verify > update > verify > delete |
+| `--tier=N` | Filtra le write sequences per tier (1, 2, o 3) |
+| `--include-writes` | Include write tool nel test read (senza sequenze CRUD) |
+| `--delay=MS` | Millisecondi di attesa tra le chiamate (default: 100) |
+| `--timeout=MS` | Timeout per singola chiamata (default: 10000) |
+
+**Regola duale**: senza flag → interattivo. Con almeno un flag → batch mode.
+
+#### Write Test Tiers
+
+| Tier | Sequenze | Descrizione |
+|------|----------|-------------|
+| **1** | content, term, comment, user | CRUD base, entita standalone |
+| **2** | media, plugin, assign_terms | CRUD con dipendenze tra entita |
+| **3** | switch_site | Operazioni speciali (cambio sito e ritorno) |
+
+Ogni sequenza esegue il ciclo completo **create → verify → update → verify → delete** con cleanup automatico in caso di errore.
+
+#### Output: Tre Livelli di Dettaglio
+
+I risultati vengono generati in tre formati complementari:
+
+1. **Console (stderr)** — log in tempo reale durante l'esecuzione, ideale per monitorare il progresso:
+   ```
+   [validation] Write sequences to run: content(T1), term(T1), user(T1)
+   [validation]   ── Sequence: content (Tier 1) ──
+   [validation]     → extracted id=2451
+   [validation]     [+] create:create_content (488ms)
+   [validation]     [+] verify:get_content (341ms)
+   ```
+
+2. **Markdown** (`docs/VALIDATION.md`) — report tabellare per consultazione rapida, con status per ogni tool, servizio e modulo.
+
+3. **Dashboard HTML** (`docs/validation/dashboard.html`) — interfaccia grafica interattiva con:
+   - Grafici riassuntivi (passed/failed/skipped)
+   - Dettaglio per modulo e servizio
+   - Tempo di risposta per ogni tool
+   - Filtri e ricerca
+
+   > **Importante**: La dashboard carica `results.json` via `fetch()`, quindi richiede un server HTTP. Non funziona con il protocollo `file://`.
+
+   ```bash
+   # Avviare un server locale per la dashboard
+   cd docs/validation && python3 -m http.server 8111
+
+   # Poi aprire nel browser
+   # http://localhost:8111/dashboard.html
+   ```
+
+#### File Generati
+
+| File | Formato | Descrizione |
+|------|---------|-------------|
+| `docs/validation/results.json` | JSON | Dati strutturati, merge incrementale tra run |
+| `docs/VALIDATION.md` | Markdown | Report leggibile, rigenerato ad ogni run |
+| `docs/validation/dashboard.html` | HTML | Dashboard interattiva (richiede HTTP server) |
+
+I risultati sono **incrementali**: un run su un singolo modulo (`--module=X`) aggiorna solo quel modulo in `results.json`, preservando i risultati precedenti degli altri.
+
 ---
 
 ## 15. Troubleshooting
@@ -2363,6 +2487,121 @@ bash ~/.claude/plugins/local/wordpress-manager/scripts/validate-wp-operation.sh
 
 ---
 
+## 17. Content Framework
+
+The Content Framework connects Gen* ecosystem skills (GenCorpComm, GenMarketing, GenSignal) to WordPress publishing through structured Markdown files.
+
+### 17.1 Architecture
+
+The framework uses three types of MD files as configuration layer:
+
+| Type | Suffix | Purpose | Location |
+|------|--------|---------|----------|
+| Schema | `.schema.md` | Template definition | `skills/wp-content-pipeline/references/` |
+| Config | `.config.md` | Site-specific settings | `.content-state/{site_id}.config.md` |
+| Brief | `.brief.md` | Content instance | `.content-state/pipeline-active/` |
+
+### 17.2 Content Pipeline (Phase 1)
+
+**Skill**: `wp-content-pipeline`
+
+The pipeline orchestrates: `SCAN → CONFIG → VALIDATE → PUBLISH → DISTRIBUTE → UPDATE → ARCHIVE`
+
+**Creating a brief**:
+1. Generate content (via GenCorpComm or manually)
+2. Save as `.content-state/pipeline-active/BRF-YYYY-NNN.brief.md`
+3. Set frontmatter: site_id, title, categories, channels, SEO params
+4. Set `status: ready` when content is finalized
+
+**Publishing a brief**:
+1. Invoke `wp-content-pipeline` skill
+2. Pipeline reads all `status: ready` briefs
+3. Validates quality gates
+4. Creates WP post → distributes to channels → archives brief
+
+**Site configuration**:
+- One `.content-state/{site_id}.config.md` per managed site
+- Defines brand voice, default categories, active channels, SEO settings
+- Brief values override config defaults
+
+### 17.3 Directory Structure
+
+```
+.content-state/
+├── {site_id}.config.md          # site configuration
+├── pipeline-active/             # briefs in progress
+│   └── BRF-YYYY-NNN.brief.md
+└── pipeline-archive/            # completed briefs
+    └── BRF-YYYY-NNN.brief.md
+```
+
+### 17.4 Integration with Gen* Skills
+
+| Gen* Skill | Produces | Pipeline Consumes |
+|------------|----------|-------------------|
+| GenCorpComm | Multi-format content | Body + metadata → brief.md |
+| GenMarketing | Content calendar | Topics + dates → brief.md |
+| GenBrand | Brand voice | Tone + style → config.md |
+| GenSignal | Market signals | Topics → editorial planning (Phase 2) |
+
+### 17.5 Content Intelligence (Phase 2)
+
+**Skill**: `wp-analytics` (extended with Step 7: Signal Feed Generation)
+
+The intelligence layer creates a feedback loop: analytics data → structured signals → actionable insights.
+
+**Generating a signals feed**:
+1. Run `wp-analytics` signal feed generation for a site
+2. Step 7 collects data from GA4, GSC, Plausible, CWV tools
+3. Calculates delta % vs previous period
+4. Maps metrics to GenSignal NormalizedEvent format
+5. Identifies anomalies (±30% threshold by default)
+6. Matches 3 GenSignal patterns automatically
+7. Writes `.content-state/signals-feed.md`
+
+**Detectable patterns**:
+
+| Pattern | Detection Source | Trigger |
+|---------|-----------------|---------|
+| Search Intent Shift | GSC queries | CTR ≥ +20% with stable position |
+| Early-Adopter Surge | GA4 traffic sources | Single source ≥ +50% vs site < +20% |
+| Hype→Utility Crossover | GA4 page metrics | Engagement ≥ +15% with bounce ≤ -10% |
+
+**Acting on signals**:
+- "Approfondisci con GenSignal" → Full SignalCard with scoring and next_actions
+- "Crea brief dai segnali" → Auto-generate content briefs in pipeline-active/
+- Signals feed topic suggestions → Editorial calendar (Phase 3)
+
+**Signal feed file**: `.content-state/signals-feed.md` (overwritten each generation)
+
+### 17.6 Editorial Calendar (Phase 3)
+
+**Skill**: `wp-editorial-planner`
+
+The editorial planner manages monthly content calendars as `.state.md` files, bridging strategic planning to tactical execution.
+
+**Workflow**: `PLAN → BRIEF → SCHEDULE → SYNC`
+
+| Step | Action | Input | Output |
+|------|--------|-------|--------|
+| PLAN | Create monthly calendar | site config + signals feed | `{YYYY-MM}-editorial.state.md` |
+| BRIEF | Convert entries to briefs | calendar entries | `pipeline-active/BRF-*.brief.md` |
+| SCHEDULE | Create WP future posts | ready briefs | WordPress posts with `status: future` |
+| SYNC | Update calendar from WP | WordPress post status | Updated calendar entries |
+
+**Calendar structure**:
+- One `.content-state/{YYYY-MM}-editorial.state.md` per month
+- YAML frontmatter: monthly goals, posts target, focus topics, SEO targets
+- Markdown tables: one per week with columns Data, Titolo, Tipo, Status, Brief ID, Post ID, Canali
+
+**Entry lifecycle**: `planned → draft → ready → scheduled → published`
+
+**Cross-phase integration**:
+- Phase 2 signals → topic suggestions for `[da assegnare]` entries
+- Calendar entries → Phase 1 briefs → WordPress publishing pipeline
+
+---
+
 *Guida v2.12.2 — WordPress Manager Plugin per Claude Code*
 *Ultimo aggiornamento: 2026-03-01*
 *WCOP Score: 8.8/10 (Tier 4+5 complete)*