claude-plugin-wordpress-manager 2.13.0 → 2.14.1

package/docs/plans/2026-03-02-content-framework-architecture.md

@@ -38,12 +38,12 @@ source:
 
 # Target — dove pubblicare
 target:
-  site_id: opencactus          # id dal WP_SITES_CONFIG
+  site_id: mysite          # id dal WP_SITES_CONFIG
   content_type: post           # post | page
   status: draft                # draft | publish | future
   scheduled_date: null         # ISO 8601 se status=future
   categories: [blog, seo]
-  tags: [cactus-water, wellness]
+  tags: [premium-water, wellness]
 
 # Content Parameters — passati a wp-content per la creazione
 content:
@@ -86,8 +86,8 @@ Configurazione persistente per sito — brand voice, canali attivi, parametri di
 ```yaml
 ---
 # Site Configuration v1.0
-site_id: opencactus
-site_url: "https://opencactus.com"
+site_id: mysite
+site_url: "https://mysite.example.com"
 last_updated: "2026-03-02"
 
 # Brand Voice — alimentato da GenBrand output
@@ -97,7 +97,7 @@ brand:
   style_notes: |
     Stile divulgativo-scientifico. Evitare iperboli.
     Preferire dati concreti a claim generici.
-    Valorizzare il territorio siciliano.
+    Valorizzare il territorio.
 
 # Default Content Parameters
 defaults:
@@ -175,7 +175,7 @@ Questa skill orchestra il flusso brief → publish → distribute.
 ### 1.5 Flusso Operativo End-to-End
 
 ```
-Utente: "Genera un articolo sul cactus water per opencactus"
+Utente: "Genera un articolo sul sparkling water per mysite"
                 │
                 ▼
     GenCorpComm (content_marketing domain)
@@ -194,7 +194,7 @@ Utente: "Genera un articolo sul cactus water per opencactus"
     → legge brief → valida gates → crea post WP → distribuisce → archivia
                 │
                 ▼
-    Output: "Pubblicato: https://opencactus.com/cactus-water-benefici/
+    Output: "Pubblicato: https://mysite.example.com/premium-water-benefici/
              LinkedIn: schedulato in 2h
              Newsletter: campagna creata, pronta per invio"
 ```
@@ -214,8 +214,8 @@ Formato di scambio tra wp-analytics e GenSignal. Traduce metriche WP nel formato
 ```yaml
 ---
 # Signals Feed Schema v1.0
-feed_id: "FEED-opencactus-2026-03"
-site_id: opencactus
+feed_id: "FEED-mysite-2026-03"
+site_id: mysite
 generated: "2026-03-02T12:00:00Z"
 period: "2026-02-01..2026-02-28"
 source_tools:
@@ -232,7 +232,7 @@ source_tools:
 
 ```yaml
 events:
-  - entity_id: "Page:/cactus-water-benefici"
+  - entity_id: "Page:/premium-water-benefici"
     relation: pageviews
     value: 3240
     unit: count
@@ -240,9 +240,9 @@ events:
     delta_pct: +47        # variazione vs periodo precedente
     provenance:
       source_id: "ga4_top_pages"
-      site: opencactus
+      site: mysite
 
-  - entity_id: "Page:/cactus-water-benefici"
+  - entity_id: "Page:/premium-water-benefici"
     relation: avg_engagement_time
     value: 185
     unit: seconds
@@ -250,13 +250,13 @@ events:
     delta_pct: +12
     provenance:
       source_id: "ga4_report"
-      site: opencactus
+      site: mysite
 ```
 
 ## Search Signals
 
 ```yaml
-  - entity_id: "Keyword:acqua di cactus"
+  - entity_id: "Keyword:acqua premium"
     relation: search_impressions
     value: 8500
     unit: count
@@ -264,9 +264,9 @@ events:
     delta_pct: +120
     provenance:
       source_id: "gsc_query_analytics"
-      site: opencactus
+      site: mysite
 
-  - entity_id: "Keyword:acqua di cactus benefici"
+  - entity_id: "Keyword:acqua premium benefici"
     relation: search_ctr
     value: 4.2
     unit: percentage
@@ -274,7 +274,7 @@ events:
     delta_pct: -8
     provenance:
       source_id: "gsc_query_analytics"
-      site: opencactus
+      site: mysite
 ```
 
 ## Source Signals
@@ -288,20 +288,20 @@ events:
     delta_pct: +85
     provenance:
       source_id: "ga4_traffic_sources"
-      site: opencactus
+      site: mysite
 ```
 
 ## Performance Signals
 
 ```yaml
-  - entity_id: "Site:opencactus"
+  - entity_id: "Site:mysite"
     relation: lcp
     value: 2.1
     unit: seconds
     ts: "2026-02-28T23:59:59Z"
     provenance:
       source_id: "cwv_crux_origin"
-      site: opencactus
+      site: mysite
 ```
 
 # Anomalies & Patterns
@@ -310,9 +310,9 @@ Sezione che Claude popola dopo aver analizzato i delta:
 
 | Entity | Metric | Delta | Pattern Match | Action |
 |--------|--------|-------|---------------|--------|
-| Keyword:acqua di cactus | impressions | +120% | Search Intent Shift | Investigate: content cluster opportunity |
+| Keyword:acqua premium | impressions | +120% | Search Intent Shift | Investigate: content cluster opportunity |
 | Source:linkedin | referrals | +85% | Early-Adopter Surge | Scale: increase LinkedIn posting frequency |
-| Page:/cactus-water-benefici | CTR | -8% | Hype→Utility Crossover | Optimize: refresh meta description, test titles |
+| Page:/premium-water-benefici | CTR | -8% | Hype→Utility Crossover | Optimize: refresh meta description, test titles |
 ```
 
 **Dove vive**: `.content-state/signals-feed.md` (sovrascritta ad ogni generazione)
@@ -342,7 +342,7 @@ Step 7: GENERATE SIGNAL FEED
 ### 2.4 Flusso Intelligence Loop
 
 ```
-Utente: "analizza performance opencactus ultimo mese e genera segnali"
+Utente: "analizza performance mysite ultimo mese e genera segnali"
                 │
                 ▼
     wp-analytics (skill estesa)
@@ -352,7 +352,7 @@ Utente: "analizza performance opencactus ultimo mese e genera segnali"
                 │
                 ▼
     Claude presenta: "3 anomalie rilevate:
-     1. 'acqua di cactus' impressions +120% → Search Intent Shift
+     1. 'acqua premium' impressions +120% → Search Intent Shift
      2. LinkedIn referrals +85% → Early-Adopter Surge
      3. CTR -8% su pagina top → possibile title fatigue"
                 │
@@ -392,7 +392,7 @@ Pianificare contenuti nel tempo con un file `.state.md` che funge da calendario
 ---
 # Editorial Calendar Schema v1.0
 calendar_id: "CAL-2026-03"
-site_id: opencactus
+site_id: mysite
 period: "2026-03-01..2026-03-31"
 created: "2026-02-28"
 last_updated: "2026-03-02"
@@ -402,9 +402,9 @@ status: active                 # active | archived
 goals:
   posts_target: 8
   posts_published: 2
-  focus_topics: [cactus-water, sustainability, wellness]
+  focus_topics: [premium-water, sustainability, wellness]
   seo_targets:
-    - keyword: "acqua di cactus"
+    - keyword: "acqua premium"
       target_position: top-5
     - keyword: "bevanda zero calorie naturale"
       target_position: top-10
@@ -416,15 +416,15 @@ goals:
 
 | Data | Titolo | Tipo | Status | Brief ID | Post ID | Canali |
 |------|--------|------|--------|----------|---------|--------|
-| Mar 4 | Acqua di cactus: 5 benefici scientifici | post | published | BRF-2026-001 | 1234 | linkedin, newsletter |
-| Mar 6 | Come il fico d'India diventa bevanda | post | published | BRF-2026-002 | 1235 | linkedin, twitter |
+| Mar 4 | Acqua premium: 5 benefici scientifici | post | published | BRF-2026-001 | 1234 | linkedin, newsletter |
+| Mar 6 | Come il frutto mediterraneo diventa bevanda | post | published | BRF-2026-002 | 1235 | linkedin, twitter |
 
 ## Settimana 2 (8-14 Mar)
 
 | Data | Titolo | Tipo | Status | Brief ID | Post ID | Canali |
 |------|--------|------|--------|----------|---------|--------|
 | Mar 11 | Zero calorie, tutto gusto: la scienza | post | ready | BRF-2026-003 | — | linkedin, newsletter |
-| Mar 13 | Sicilia e sostenibilità: la filiera | post | draft | BRF-2026-004 | — | linkedin |
+| Mar 13 | Mediterraneo e sostenibilità: la filiera | post | draft | BRF-2026-004 | — | linkedin |
 
 ## Settimana 3 (15-21 Mar)
 
@@ -521,8 +521,8 @@ Orchestra la pianificazione editoriale e la conversione piano → brief → post
 
 ```
 .content-state/
-├─ opencactus.config.md           # Fase 1: config sito
-├─ bioinagro.config.md            # config per altro sito
+├─ mysite.config.md           # Fase 1: config sito
+├─ othersite.config.md            # config per altro sito
 ├─ signals-feed.md                # Fase 2: ultimo feed segnali
 ├─ 2026-03-editorial.state.md     # Fase 3: calendario corrente
 ├─ 2026-02-editorial.state.md     # calendario precedente (archived)
@@ -577,7 +577,7 @@ Zero file `.ts` aggiunti. Tutte le operazioni usano i 148 MCP tool esistenti orc
 - [x] `site.config.md` schema definito e documentato
 - [x] `wp-content-pipeline` skill creata con workflow completo
 - [x] Flusso end-to-end testato: brief.md → WP post (distribuzione LinkedIn skipped — wp-rest-bridge non connesso, tool AIWU usato per WP)
-- [x] Supporto multi-sito (opencactus + almeno un altro)
+- [x] Supporto multi-sito (mysite + almeno un altro)
 
 ### Fase 2: Content Intelligence
 

package/docs/plans/2026-03-02-content-framework-strategic-reflections.md

@@ -86,7 +86,7 @@ Invece di codice applicativo, usiamo **file Markdown strutturati come strato di
 |------|----------|-------|---------|
 | **Schema** | `.schema.md` | Template strutturato con frontmatter YAML, definisce la struttura | `content-brief.schema.md` |
 | **Instance** | `.state.md` | Stato corrente di un'istanza attiva, aggiornato tra sessioni | `2026-03-editorial.state.md` |
-| **Config** | `.config.md` | Parametri di tuning per un sito, brand, o workflow | `opencactus.config.md` |
+| **Config** | `.config.md` | Parametri di tuning per un sito, brand, o workflow | `mysite.config.md` |
 
 ### Perché Funziona
 

package/docs/plans/2026-03-02-content-intelligence-phase2.md

@@ -120,7 +120,7 @@ The schema must include these sections:
 - Phase 3 bridge: The Anomalies & Patterns table feeds `wp-editorial-planner` for topic suggestions when creating calendar entries.
 - Overwrite semantics: `signals-feed.md` is overwritten each time Step 7 runs. Previous feeds are not archived (they represent point-in-time snapshots). The `comparison_period` field preserves the baseline reference.
 
-**I. Example feed** — A complete, realistic example for opencactus with:
+**I. Example feed** — A complete, realistic example for mysite with:
 - 2-3 Traffic Signals (page-level)
 - 2 Search Signals (keyword-level)
 - 1 Source Signal
@@ -259,10 +259,10 @@ For each data point from Step 7.1, create a NormalizedEvent:
 ```
 
 **Entity ID mapping rules:**
-- GA4 top pages: `Page:{page_path}` (e.g., `Page:/cactus-water-benefici`)
+- GA4 top pages: `Page:{page_path}` (e.g., `Page:/premium-water-benefici`)
 - GA4 traffic sources: `Source:{source_name}` (e.g., `Source:linkedin`)
-- GA4 site aggregates: `Site:{site_id}` (e.g., `Site:opencactus`)
-- GSC keywords: `Keyword:{query}` (e.g., `Keyword:acqua di cactus`)
+- GA4 site aggregates: `Site:{site_id}` (e.g., `Site:mysite`)
+- GSC keywords: `Keyword:{query}` (e.g., `Keyword:acqua premium`)
 - CWV metrics: `Site:{site_id}` with relation = metric name (e.g., `lcp`)
 
 **Relation mapping rules:**
@@ -396,7 +396,7 @@ Crossover. Writes .content-state/signals-feed.md."
 
 Create `.content-state/signals-feed.md` with:
 
-- Frontmatter targeting opencactus, period: 2026-02-01..2026-02-28, comparison_period: 2026-01-01..2026-01-31
+- Frontmatter targeting mysite, period: 2026-02-01..2026-02-28, comparison_period: 2026-01-01..2026-01-31
 - source_tools: `[ga4_top_pages, ga4_traffic_sources, ga4_report, gsc_query_analytics]`
 - anomaly_threshold: 30
 - status: generated
@@ -404,27 +404,27 @@ Create `.content-state/signals-feed.md` with:
 Events section with realistic data:
 
 **Traffic Signals (3 events):**
-- `Page:/benefici-acqua-cactus-idratazione-naturale-sicilia` — pageviews: 3240, delta: +47%
-- `Page:/benefici-acqua-cactus-idratazione-naturale-sicilia` — avg_engagement_time: 185s, delta: +12%
+- `Page:/benefici-acqua-premium-idratazione-naturale` — pageviews: 3240, delta: +47%
+- `Page:/benefici-acqua-premium-idratazione-naturale` — avg_engagement_time: 185s, delta: +12%
 - `Page:/prodotti` — pageviews: 1850, delta: +8%
 
 **Search Signals (2 events):**
-- `Keyword:acqua di cactus` — search_impressions: 8500, delta: +120%
-- `Keyword:acqua di cactus benefici` — search_ctr: 4.2%, delta: -8%
+- `Keyword:acqua premium` — search_impressions: 8500, delta: +120%
+- `Keyword:acqua premium benefici` — search_ctr: 4.2%, delta: -8%
 
 **Source Signals (1 event):**
 - `Source:linkedin` — referral_sessions: 420, delta: +85%
 
 **Performance Signals (1 event):**
-- `Site:opencactus` — lcp: 2.1s, no delta (first CWV measurement)
+- `Site:mysite` — lcp: 2.1s, no delta (first CWV measurement)
 
 **Anomalies & Patterns table (3 rows):**
 
 | Entity | Metric | Delta | Pattern Match | Action |
 |--------|--------|-------|---------------|--------|
-| Keyword:acqua di cactus | search_impressions | +120% | Search Intent Shift | Investigate: content cluster opportunity |
+| Keyword:acqua premium | search_impressions | +120% | Search Intent Shift | Investigate: content cluster opportunity |
 | Source:linkedin | referral_sessions | +85% | Early-Adopter Surge | Scale: increase LinkedIn posting frequency |
-| Page:/benefici-acqua-cactus-idratazione-naturale-sicilia | pageviews | +47% | Unclassified anomaly | Review: investigate cause of +47% change in pageviews |
+| Page:/benefici-acqua-premium-idratazione-naturale | pageviews | +47% | Unclassified anomaly | Review: investigate cause of +47% change in pageviews |
 
 This feed serves as the integration test artifact. The wp-analytics Step 7 will produce files in this exact format.
 
@@ -432,7 +432,7 @@ This feed serves as the integration test artifact. The wp-analytics Step 7 will
 
 Run: `head -15 .content-state/signals-feed.md`
 
-Expected: valid YAML frontmatter with `feed_id: FEED-opencactus-2026-02` and `status: generated`.
+Expected: valid YAML frontmatter with `feed_id: FEED-mysite-2026-02` and `status: generated`.
 
 **Step 3: No commit** — this file is gitignored (instance data). It lives locally for testing.
 

package/docs/plans/2026-03-02-content-pipeline-phase1.md

@@ -94,7 +94,7 @@ The schema must include these sections:
   - `seo` block: `focus_keyword`, `meta_description`, `schema_type`, `internal_links`
   - `gates` block: `seo_score_min`, `readability_min`, `require_review`
 - **Status lifecycle**: `draft → ready → published → archived`
-- **Example brief** with realistic values for opencactus
+- **Example brief** with realistic values for mysite
 - **Validation rules**: which fields are required vs optional, default values
 
 Content body goes after the frontmatter `---` separator as standard Markdown.
@@ -137,18 +137,18 @@ The schema must include:
   - `seo` block: `default_schema`, `min_score`, `auto_internal_links`
   - `cadence` block: `posts_per_week`, `preferred_days[]`, `publish_time`
 - **Body section**: free-form notes for Claude context
-- **Example config** for opencactus site
+- **Example config** for mysite site
 - **Integration notes**: how GenBrand output maps to `brand` block, how WP_SITES_CONFIG maps to `site_id`
 
 **Step 2: Create an example instance file**
 
-Create `.content-state/opencactus.config.md` with realistic values for the opencactus site. This serves as both documentation and working config.
+Create `.content-state/mysite.config.md` with realistic values for the mysite site. This serves as both documentation and working config.
 
-Note: this file is gitignored (site-specific), but we create it as a template. Copy the example from the schema reference, filling in opencactus-specific values.
+Note: this file is gitignored (site-specific), but we create it as a template. Copy the example from the schema reference, filling in mysite-specific values.
 
 **Step 3: Verify both files**
 
-Run: `ls -la skills/wp-content-pipeline/references/site-config-schema.md .content-state/opencactus.config.md`
+Run: `ls -la skills/wp-content-pipeline/references/site-config-schema.md .content-state/mysite.config.md`
 
 Expected: both files exist.
 
@@ -162,7 +162,7 @@ Defines {site_id}.config.md structure for brand voice, distribution
 channels, SEO defaults, and content cadence per WordPress site."
 ```
 
-Note: `.content-state/opencactus.config.md` is gitignored, so only the schema is committed.
+Note: `.content-state/mysite.config.md` is gitignored, so only the schema is committed.
 
 ---
 
@@ -308,14 +308,14 @@ PUBLISH → DISTRIBUTE → UPDATE → ARCHIVE."
 **Step 1: Write a realistic test brief**
 
 Create `.content-state/pipeline-active/BRF-2026-001.brief.md` with:
-- Frontmatter targeting opencactus, content_type: post, status: draft
+- Frontmatter targeting mysite, content_type: post, status: draft
 - Source: `manual` (not from Gen* — for testing without Gen* dependency)
-- A short (~200 word) article about cactus water benefits
+- A short (~200 word) article about sparkling water benefits
 - Distribution: linkedin only (minimal for testing)
 - SEO: focus keyword set, schema_type: Article
 - Gates: require_review: true (so pipeline stops for confirmation)
 
-This brief serves as the integration test artifact. The pipeline skill will read it, present it to user, and (on approval) publish to opencactus.
+This brief serves as the integration test artifact. The pipeline skill will read it, present it to user, and (on approval) publish to mysite.
 
 **Step 2: Verify brief parses correctly**
 
@@ -342,7 +342,7 @@ In the architecture doc:
   - [x] `site.config.md` schema definito e documentato
   - [x] `wp-content-pipeline` skill creata con workflow completo
   - [ ] Flusso end-to-end testato: brief.md → WP post → distribuzione social
-  - [x] Supporto multi-sito (opencactus + almeno un altro)
+  - [x] Supporto multi-sito (mysite + almeno un altro)
   ```
 
 Note: "Flusso end-to-end testato" left unchecked — that requires a live WP test which is a separate manual validation step.

package/docs/plans/2026-03-02-context-snippet-design.md

@@ -0,0 +1,232 @@
+# Context Snippet — Design Document (Fase B)
+
+**Data**: 2026-03-02
+**Versione**: 1.0.0
+**Stato**: Implementazione
+**Prerequisito**: [Dashboard Strategy](2026-03-02-dashboard-strategy.md) (Fase A completata in v2.14.0)
+**Deriva da**: Dashboard Strategy, sezione 6 — Fase B
+
+---
+
+## 1. Obiettivo
+
+Ogni content skill stampa automaticamente 3-5 righe di contesto editoriale operativo **prima** di iniziare il proprio workflow. Questo "Step 0" fornisce a Claude e all'operatore umano una fotografia istantanea dello stato corrente senza richiedere un'azione esplicita (come invocare `wp-dashboard`).
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    LIVELLO 2: CONTESTO OPERATIVO            │
+│                                                             │
+│  Step 0 inline nelle content skill                          │
+│  Output: testo terminale (3-5 righe)                        │
+│  Trigger: automatico, ogni invocazione skill                │
+│  Contenuto: solo lo slice rilevante per la skill attiva     │
+│                                                             │
+│  "Ecco cosa sto per toccare"                                │
+└─────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## 2. Architettura
+
+### 2.1 Componenti
+
+```
+scripts/context-scanner.mjs
+  ├── scanContentState()       ← legge .content-state/ (già esistente)
+  ├── aggregateMetrics()       ← calcola metriche (già esistente)
+  ├── renderContextSnippet()   ← formatta 3-5 righe terminal (già esistente)
+  └── CLI: --snippet --site=X  ← NUOVO: entry point per invocazione da skill
+
+skills/wp-content-pipeline/SKILL.md
+  └── Step 0: CONTEXT          ← NUOVO: istruzioni per Claude
+
+skills/wp-editorial-planner/SKILL.md
+  └── Step 0: CONTEXT          ← NUOVO: istruzioni per Claude
+```
+
+### 2.2 Flusso di Esecuzione
+
+```
+Utente invoca skill
+  → Claude legge SKILL.md
+    → Step 0: CONTEXT
+      → Claude legge .content-state/{site_id}.config.md
+      → Claude legge .content-state/{YYYY-MM}-editorial.state.md
+      → Claude legge .content-state/pipeline-active/*.brief.md
+      → Claude formatta e stampa snippet (3-5 righe)
+    → Step 1+: workflow normale della skill
+```
+
+### 2.3 Due Modalità di Rendering
+
+| Modalità | Quando | Come |
+|----------|--------|------|
+| **Claude-native** | Sempre (Step 0 nelle skill) | Claude legge i file direttamente e formatta il testo seguendo le istruzioni SKILL.md |
+| **Script CLI** | Opzionale, per automazione | `node scripts/context-scanner.mjs --snippet --site=mysite` |
+
+La modalità Claude-native è il default. La modalità CLI serve come backup e per uso in script/automazione.
+
+---
+
+## 3. Formato Snippet
+
+### 3.1 Formato Base (tutte le skill)
+
+```
+── Editorial Context ──────────────────────
+  mysite.example.com | 2026-03-01 → 2026-03-31
+  Pipeline: 2 draft → 1 ready → 0 scheduled
+  Posts: 3/12 pubblicati
+───────────────────────────────────────────
+```
+
+### 3.2 Slice: Pipeline (wp-content-pipeline)
+
+Aggiunge dettaglio sui brief attivi:
+
+```
+── Editorial Context ──────────────────────
+  mysite.example.com | 2026-03-01 → 2026-03-31
+  Pipeline: 2 draft → 1 ready → 0 scheduled
+  Briefs: BRF-2026-005 (ready), BRF-2026-006 (draft)
+  Posts: 3/12 pubblicati
+───────────────────────────────────────────
+```
+
+### 3.3 Slice: Calendar (wp-editorial-planner)
+
+Aggiunge prossima scadenza:
+
+```
+── Editorial Context ──────────────────────
+  mysite.example.com | 2026-03-01 → 2026-03-31
+  Pipeline: 2 draft → 1 ready → 0 scheduled
+  Next: Mar 18 — "Acqua Premium: La Rivoluzione..."
+  Posts: 3/12 pubblicati
+───────────────────────────────────────────
+```
+
+### 3.4 Slice: Signals (future — wp-analytics)
+
+Aggiunge anomalie rilevanti:
+
+```
+── Editorial Context ──────────────────────
+  mysite.example.com | 2026-03-01 → 2026-03-31
+  Pipeline: 2 draft → 1 ready → 0 scheduled
+  Signals: 3 anomalie | Top: /blog/benefici +45%
+  Posts: 3/12 pubblicati
+───────────────────────────────────────────
+```
+
+---
+
+## 4. Step 0 nelle Skill
+
+### 4.1 Template Step 0
+
+Ogni content skill riceve un blocco Step 0 identico nella struttura, con `sliceType` diverso:
+
+```markdown
+## Step 0: CONTEXT
+
+**What it does:** Provides editorial context before the main workflow begins.
+
+**Trigger:** Automatic — run this step at every skill invocation, before Step 1.
+
+**Procedure:**
+1. Determine the active site from user context or ask the user
+2. Read `.content-state/{site_id}.config.md` for site URL
+3. Read the most recent `.content-state/*-editorial.state.md`
+4. Count entries by status (planned, draft, ready, scheduled, published)
+5. Read `.content-state/pipeline-active/*.brief.md` for active brief IDs and statuses
+6. Display the context snippet
+
+**Format:**
+[specific to slice type]
+
+**If files are missing:**
+- If no config file exists → skip snippet, report "No site config found"
+- If no editorial calendar exists → show partial snippet with "no calendar"
+- If no active briefs → show "0 active briefs"
+- Never stop the workflow because of missing context — Step 0 is informational only
+```
+
+### 4.2 Differenze per Skill
+
+| Skill | sliceType | Riga Extra |
+|-------|-----------|------------|
+| `wp-content-pipeline` | `pipeline` | Lista brief attivi con status |
+| `wp-editorial-planner` | `calendar` | Prossima scadenza (data + titolo troncato) |
+| Future: `wp-analytics` | `signals` | Anomalie top dal signals-feed |
+
+---
+
+## 5. CLI Entry Point
+
+### 5.1 Aggiunta a context-scanner.mjs
+
+```javascript
+// CLI entry point (when run directly, not imported)
+if (process.argv[1] && process.argv[1].endsWith('context-scanner.mjs')) {
+  const args = process.argv.slice(2);
+  if (args.includes('--snippet')) {
+    // Parse --site=X and --slice=Y
+    // Run scanContentState + aggregateMetrics + renderContextSnippet
+    // Output to stderr (consistent with MCP server logging pattern)
+  }
+}
+```
+
+### 5.2 Interfaccia CLI
+
+```
+node scripts/context-scanner.mjs --snippet --site=mysite [--slice=pipeline|calendar|signals] [--month=2026-03]
+```
+
+| Flag | Required | Default | Description |
+|------|----------|---------|-------------|
+| `--snippet` | Yes | — | Attiva modalità snippet (senza questo flag, il modulo è solo libreria) |
+| `--site` | Yes | — | Site ID per il contesto |
+| `--slice` | No | `pipeline` | Tipo di slice: `pipeline`, `calendar`, `signals` |
+| `--month` | No | Mese corrente | Mese del calendario editoriale |
+
+---
+
+## 6. Vincoli
+
+| Vincolo | Valore | Motivazione |
+|---------|--------|-------------|
+| Overhead < 500ms | Sì | Step 0 non deve rallentare la skill |
+| Informational only | Sì | Step 0 non blocca mai il workflow |
+| No nuovi file .content-state/ | Sì | Step 0 legge, non scrive |
+| Stesso formato di renderContextSnippet() | Sì | Consistenza tra modalità |
+
+---
+
+## 7. Deliverable
+
+| File | Azione | Descrizione |
+|------|--------|-------------|
+| `scripts/context-scanner.mjs` | Modifica | Aggiunta CLI `--snippet` + rimozione label "stub" |
+| `skills/wp-content-pipeline/SKILL.md` | Modifica | Aggiunta Step 0: CONTEXT (pipeline slice) |
+| `skills/wp-editorial-planner/SKILL.md` | Modifica | Aggiunta Step 0: CONTEXT (calendar slice) |
+| `docs/plans/2026-03-02-context-snippet-design.md` | Nuovo | Questo documento |
+| `package.json` | Modifica | Bump `v2.14.0` → `v2.14.1` |
+| `CHANGELOG.md` | Modifica | Entry per context snippet |
+
+---
+
+## 8. Catena Documentale
+
+```
+docs/plans/2026-03-02-dashboard-strategy.md
+  ├── docs/plans/2026-03-02-dashboard-kanban-design.md        (Fase A — completata)
+  │     └── docs/plans/2026-03-02-dashboard-kanban-implementation.md
+  └── docs/plans/2026-03-02-context-snippet-design.md         ← QUESTO DOCUMENTO (Fase B)
+```
+
+---
+
+*Design document per Fase B del sistema dashboard — context snippet inline nelle content skill.*