docs(linkedin-studio): M0-15 — repoint remaining prose families + route ab-tests/plans

commands/report.md

@@ -27,7 +27,7 @@ For data format details and directory structure, see `assets/analytics/README.md
 First, verify that analytics data exists:
 
 ```bash
-ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/ 2>/dev/null | grep -E '\.json$' | head -10
+ls -1 ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/posts/ 2>/dev/null | grep -E '\.json$' | head -10
 ```
 
 If no JSON files exist, tell the user:
@@ -101,7 +101,7 @@ If the user chose monthly:
 "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/node_modules/.bin/tsx" "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" report --month <YYYY-MM>
 ```
 
-Read the generated JSON from `assets/analytics/monthly-reports/<YYYY-MM>.json`. Present the monthly summary with MoM comparison deltas, weekly breakdown, and top performers. Then jump to Step 7 for deep-dive options.
+Read the generated JSON from `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/monthly-reports/<YYYY-MM>.json`. Present the monthly summary with MoM comparison deltas, weekly breakdown, and top performers. Then jump to Step 7 for deep-dive options.
 
 ### Step 2c: Heatmap
 
@@ -127,14 +127,14 @@ Execute the report CLI command:
 ```
 
 The CLI will generate:
-- `assets/analytics/weekly-reports/YYYY-WXX.json` - Structured report data
+- `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/YYYY-WXX.json` - Structured report data
 
 ## Step 4: Read Generated Report Data
 
 Read the generated JSON report:
 
 ```bash
-cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/<YYYY-WXX>.json
+cat ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/<YYYY-WXX>.json
 ```
 
 The report contains:
@@ -195,7 +195,7 @@ After the initial trend data, automatically run trend analysis for the key metri
 
 Construct the 4-week table by reading available weekly report files:
 ```bash
-ls ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/*.json 2>/dev/null | sort | tail -4
+ls ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/*.json 2>/dev/null | sort | tail -4
 ```
 
 Read each file and extract the summary metrics to populate the table columns.
@@ -220,7 +220,7 @@ Automatically flag these conditions based on the report data and trend analysis:
 
 **Detect alerts by comparing current week data against baselines:**
 ```bash
-cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/baselines.json 2>/dev/null
+cat ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/baselines.json 2>/dev/null
 ```
 
 Compare current week's `aggregateMetrics` against baseline means and standard deviations. Flag any metric that is:
@@ -372,7 +372,7 @@ If user wants to analyze specific posts:
 Read the weekly post data directly:
 
 ```bash
-cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/<YYYY-WXX>.json | jq '.posts[] | select(.title | contains("search term"))'
+cat ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/posts/<YYYY-WXX>.json | jq '.posts[] | select(.title | contains("search term"))'
 ```
 
 Show detailed metrics for that post and suggest what made it perform well/poorly.
@@ -382,7 +382,7 @@ Show detailed metrics for that post and suggest what made it perform well/poorly
 **If report generation fails:**
 
 1. **Week not found**: No data imported for that week
-   - List available weeks: `ls ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/`
+   - List available weeks: `ls ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/posts/`
    - Suggest importing data for that week
 
 2. **No posts in week**: Week file exists but is empty
@@ -406,10 +406,10 @@ Read `~/.claude/linkedin-studio.local.md` and suggest:
 ## Reference Files
 
 Reports use data from:
-- `assets/analytics/posts/YYYY-WXX.json` - Raw weekly post data
-- `assets/analytics/weekly-reports/YYYY-WXX.json` - Computed report
-- `assets/analytics/baselines.json` - Statistical baselines for comparison
-- `assets/analytics/metadata.json` - Import history and tracking
+- `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/posts/YYYY-WXX.json` - Raw weekly post data
+- `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/YYYY-WXX.json` - Computed report
+- `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/baselines.json` - Statistical baselines for comparison
+- `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/metadata.json` - Import history and tracking
 
 ## Step 8b: Export Options
 
@@ -419,12 +419,12 @@ If the user chooses option 4 ("Export report as markdown file") from the deep di
 
 1. Read the JSON report data:
 ```bash
-cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/<YYYY-WXX>.json
+cat ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/<YYYY-WXX>.json
 ```
 
 2. Format the data using this template and write to file:
 
-Save to: `${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/YYYY-WXX-report.md`
+Save to: `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/YYYY-WXX-report.md`
 
 ```markdown
 # LinkedIn Performance Report — Week YYYY-WXX
@@ -476,13 +476,13 @@ Save to: `${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/YYYY-WXX-report.
 ```
 
 **Important notes:**
-- The `assets/analytics/` directory is gitignored — exported reports contain personal analytics data and should not be committed
+- The `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/` directory is gitignored — exported reports contain personal analytics data and should not be committed
 - Use the `-report.md` suffix to distinguish from the JSON data files (e.g., `2026-W05-report.md` vs `2026-W05.json`)
 - Include all sections: metrics, trends, alerts, top performers, and recommendations for a complete standalone document
 
 After saving, confirm to the user:
 ```
-Report exported to: assets/analytics/weekly-reports/YYYY-WXX-report.md
+Report exported to: ${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/analytics/weekly-reports/YYYY-WXX-report.md
 
 Note: This file is in your gitignored analytics directory — it won't be committed to the repository.
 ```