Improve daily-experiment-report readability with progressive disclosure, quick stats, and visual status cues

.github/workflows/daily-experiment-report.md

@@ -358,6 +358,28 @@ plt.close()
 After saving each chart, upload it using the `upload_asset` safe-output tool and store the returned
 asset URLs — they will be embedded in the discussion body.
 
+## Step 5.5 — Build `min_samples` Progress Bars
+
+Add a helper to render per-variant progress toward `min_samples` using fixed-width Unicode bars:
+
+```python
+def render_progress_bar(current, target, width=10):
+    if target <= 0:
+        return "░" * width + f" {current}/{target} (N/A)"
+    ratio = max(0.0, min(1.0, current / target))
+    filled = int(round(ratio * width))
+    bar = "█" * filled + "░" * (width - filled)
+    return f"{bar} {current}/{target} ({ratio*100:.0f}%)"
+```
+
+Use this helper in the per-experiment sample-size table:
+
+```
+███████░░░ 15/20 (75%)
+██████████ 20/20 (100%)
+██░░░░░░░░ 5/20 (25%)
+```
+
 ## Step 6 — Render ASCII Comparison Table
 
 For each experiment, produce an ASCII table inside a fenced code block:
@@ -417,6 +439,11 @@ Use h3 (`###`) or lower for all headers in your report. Never use h1 (`#`) or h2
 
 Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to improve readability and reduce scrolling. Keep critical summaries and key metrics always visible.
 
+Use visual cues consistently:
+- Use emojis strategically (for example: `📊` charts, `✅` success, `⚠️` warnings, `❌` failures)
+- Use status badges for readiness (`🟢 READY`, `🟡 COLLECTING`, `🔴 FAILED`)
+- Bold final recommendations and wrap variant names in inline code
+
 Suggested structure:
 - Brief summary (always visible)
 - Key metrics or highlights (always visible)
@@ -429,21 +456,42 @@ Suggested structure:
 [1–2 sentence executive summary: N experiments analysed across M workflows,
  K reached significance (p < 0.05), list recommendations at a glance.]
 
+### ⚡ Quick Stats
+
+| Metric | Value |
+|--------|-------|
+| Active experiments | N |
+| Ready for analysis | R |
+| Statistically significant (p < 0.05) | K |
+| Recommendations | ✅ PROMOTE: P · 🟡 EXTEND: E · ❌ ABANDON: A |
+
 ---
 
 #### `<experiment_name>` · `<workflow_basename>`
 
+> **Status**: 🟢 READY / 🟡 COLLECTING / 🔴 FAILED
 > **Variants**: `<v1>` vs `<v2>` · **Window**: last 30 runs · **Analysed**: N runs with artifacts
-> **min_samples**: <min_samples> per variant
+> **min_samples**: <min_samples> per variant · **Significance**: p = <p-value>
 
 <hypothesis if declared>
 
-![Success Rate Chart](<ASSET_URL_success_rate>)
+<details>
+<summary><b>📈 View Detailed Statistics</b></summary>
+
+**Sample Sizes & Progress**
+| Variant | Runs | Progress |
+|---------|------|----------|
+| `<control>` | n | ██████░░░░ n/<min_samples> (##%) |
+| `<variant_B>` | n | ███░░░░░░░ n/<min_samples> (##%) |
 
-![Duration Chart](<ASSET_URL_duration>)
+![📊 Success Rate Chart](<ASSET_URL_success_rate>)
+
+![⏱️ Duration Chart](<ASSET_URL_duration>)
 
 <ASCII comparison table from Step 6 inside a ``` code block>
 
+</details>
+
 **Recommendation: PROMOTE / EXTEND / ABANDON** — <one sentence rationale>
 
 ---
@@ -452,10 +500,15 @@ Suggested structure:
 
 ### 📊 Summary
 
+<details>
+<summary><b>View Full Experiments Table</b></summary>
+
 | Experiment | Workflow | Control | Best variant | p-value | Guardrails | Recommendation |
 |-----------|---------|---------|-------------|---------|-----------|----------------|
 | ... | ... | ... | ... | ... | PASS/FAIL | ... |
 
+</details>
+
 > Analysis window: last 30 runs per workflow · Significance threshold: p < 0.05 (two-tailed)
 > Run: [${{ github.run_id }}](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }})
 ```