claude-plugin-wordpress-manager 2.13.0 → 2.14.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "wordpress-manager",
-  "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.",
+  "version": "2.14.1",
+  "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 46 skills, 12 agents, and security hooks. v2.14.1 adds Editorial Kanban Dashboard and Context Snippet (Step 0) in content skills.",
   "author": {
     "name": "vinmor",
     "email": "morreale.v@gmail.com"
@@ -42,7 +42,10 @@
     "content-pipeline",
     "editorial-calendar",
     "signals-intelligence",
-    "structured-data"
+    "structured-data",
+    "dashboard",
+    "kanban",
+    "context-snippet"
   ],
   "mcpServers": "./.mcp.json"
 }

package/CHANGELOG.md

@@ -2,6 +2,65 @@
 
 All notable changes to the WordPress Manager plugin for Claude Code.
 
+## [2.14.1] — 2026-03-02
+
+### Added — Context Snippet (Step 0)
+
+Contesto editoriale automatico nelle content skill. Ogni invocazione di `wp-content-pipeline` o `wp-editorial-planner` mostra 3-5 righe di stato operativo prima di iniziare il workflow — "ecco cosa sto per toccare".
+
+**Step 0: CONTEXT nelle skill**
+- `wp-content-pipeline/SKILL.md` — Step 0 con pipeline slice: mostra brief attivi con status
+- `wp-editorial-planner/SKILL.md` — Step 0 con calendar slice: mostra prossima scadenza
+- Workflow aggiornato: `CONTEXT → SCAN → CONFIG → ...` e `CONTEXT → PLAN → BRIEF → ...`
+- Step 0 è informational-only: non blocca mai il workflow, gestisce file mancanti gracefully
+
+**CLI snippet in `context-scanner.mjs`**
+- Nuovo entry point: `node scripts/context-scanner.mjs --snippet --site=mysite [--slice=pipeline|calendar|signals]`
+- `renderContextSnippet()` enhanced: nuovo parametro `activeBriefs` per pipeline slice
+- Output su stderr (coerente con pattern MCP server)
+
+**Design document**
+- `docs/plans/2026-03-02-context-snippet-design.md` — architettura, formato, vincoli
+
+---
+
+## [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)
@@ -13,7 +72,7 @@ Il Content Framework introduce un'architettura a 3 fasi che collega signal intel
 - 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 (opencactus + altri)
+- Supporto multi-sito (mysite + altri)
 - Distribuzione automatica su Buffer + Mailchimp dopo pubblicazione
 
 **Phase 2: Content Intelligence**
@@ -30,8 +89,8 @@ Il Content Framework introduce un'architettura a 3 fasi che collega signal intel
 - Integrazione cross-phase: signals-feed → topic suggestions → calendar → brief → WP post
 - SYNC bidirezionale: status WordPress → aggiornamento calendario
 
-**E2E Test su opencactus.com**
-- PLAN: anomalia signals-feed (acqua di cactus +120%) → topic assignment ✅
+**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 ✅
@@ -48,7 +107,7 @@ Il Content Framework introduce un'architettura a 3 fasi che collega signal intel
 - 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 opencactus
+- Report: 48 read passed, 26 write passed, 0 failed su mysite
 
 ### Stats
 
@@ -74,7 +133,7 @@ Il Content Framework introduce un'architettura a 3 fasi che collega signal intel
 - 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)
@@ -97,7 +156,7 @@ Il Content Framework introduce un'architettura a 3 fasi che collega signal intel
 - 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/                                 # 45 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)
@@ -2182,8 +2182,8 @@ Il menu guida attraverso 4 step:
 ┌  WP REST Bridge — Validation Runner v1.2.0
 │
 ◆  Seleziona il sito target
-│  ● opencactus (https://opencactus.com)
-│  ○ bioinagro (https://www.bioinagro.it)
+│  ● mysite (https://mysite.example.com)
+│  ○ othersite (https://othersite.example.com)
 └
 ◆  Cosa vuoi validare?
 │  ○ Solo read tool
@@ -2200,13 +2200,13 @@ Per automazione, CI, o uso da Claude Code si usano i flag:
 
 ```bash
 # Selezionare sito specifico
-node scripts/run-validation.mjs --site=opencactus
+node scripts/run-validation.mjs --site=mysite
 
 # Test solo read tool
-node scripts/run-validation.mjs --site=opencactus --module=unified-content
+node scripts/run-validation.mjs --site=mysite --module=unified-content
 
 # Test write CRUD sequences
-node scripts/run-validation.mjs --site=opencactus --test-writes
+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

package/docs/VALIDATION.md

@@ -1,7 +1,7 @@
 # WP REST Bridge — Validation Report
 
 > Generated: 2026-03-01T21:15:22.960Z  
-> Active site: `opencactus`  
+> Active site: `mysite`  
 > Tools registered: 148 | On server: 135  
 > Runner: v1.2.0
 
@@ -10,7 +10,7 @@
 | Service | Status | Note |
 |---------|--------|------|
 | wordpress_core | OK |  |
-| woocommerce | NO | Error listing products: WooCommerce not configured for site "opencactus". Add wc_consumer_key and wc... |
+| woocommerce | NO | Error listing products: WooCommerce not configured for site "mysite". Add wc_consumer_key and wc... |
 | multisite | NO | Error listing sites: Site is not configured as multisite. Set is_multisite: true in WP_SITES_CONFIG. |
 | mailchimp | NO | Mailchimp not configured. Add mailchimp_api_key to WP_SITES_CONFIG. |
 | buffer | NO | Buffer not configured. Add buffer_access_token to WP_SITES_CONFIG. |
@@ -338,4 +338,4 @@
 
 ## Changelog
 
-- 2026-03-01T21:15:22.960Z — Run on `opencactus`: passed=22, failed=0, error=0, not_configured=64, skipped_write=59, skipped=3, untested=0
+- 2026-03-01T21:15:22.960Z — Run on `mysite`: passed=22, failed=0, error=0, not_configured=64, skipped_write=59, skipped=3, untested=0

package/docs/guides/wp-ecommerce.md

@@ -128,11 +128,11 @@ npx wp-env run cli wp wc tool run install_pages --user=1
 ```bash
 # Prodotto semplice
 npx wp-env run cli wp wc product create \
-  --name="Acqua di Cactus Poco Dolce" \
+  --name="Acqua Premium Light Blend" \
   --type=simple \
   --regular_price=3.50 \
-  --description="Bevanda naturale a base di acqua di cactus siciliano. Zero calorie." \
-  --short_description="Cactus water naturale, zero calorie" \
+  --description="Bevanda naturale premium a zero calorie. Zero calorie." \
+  --short_description="Premium sparkling water, zero calorie" \
   --categories='[{"id": 1}]' \
   --manage_stock=true \
   --stock_quantity=100 \
@@ -141,7 +141,7 @@ npx wp-env run cli wp wc product create \
 
 # Prodotto variabile (creare prima il prodotto padre, poi le varianti)
 npx wp-env run cli wp wc product create \
-  --name="T-Shirt DolceZero" \
+  --name="T-Shirt AcmeBrand" \
   --type=variable \
   --description="T-shirt ufficiale del brand" \
   --attributes='[{"name":"Taglia","options":["S","M","L","XL"],"variation":true,"visible":true}]' \

package/docs/plans/2026-03-01-tier3-wcop-implementation.md

@@ -904,7 +904,7 @@ gh release create v2.6.0 --title "v2.6.0 — AI Content Optimization (Tier 3 WCO
 ### Task 24: Update Memory
 
 **Files:**
-- Modify: `/home/vinmor/.claude/projects/-home-vinmor/memory/wordpress-manager.md`
+- Modify: `/home/user/.claude/projects/-home-vinmor/memory/wordpress-manager.md`
 
 **Step 1: Update memory file**
 

package/docs/plans/2026-03-01-tier4-5-implementation.md

@@ -1755,7 +1755,7 @@ Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>"
 ### Task 22: Update memory file
 
 **Files:**
-- Modify: `/home/vinmor/.claude/projects/-home-vinmor/memory/wordpress-manager.md`
+- Modify: `/home/user/.claude/projects/-home-vinmor/memory/wordpress-manager.md`
 
 **Step 1: Update all sections**