fix: exclude Playwright tests from CI and add live test result links

- Exclude Playwright tests from vitest.config.ci.ts (they require a running
  viewer and installed browser binaries not available in CI)
- Add live test result links to README, docs homepage, CI/CD guide, and
  viewer getting-started page pointing to
  https://dotnetprofessional.github.io/LiveDoc/

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: dotnetprofessional

README.md

@@ -7,7 +7,7 @@
 
 A **Living Documentation** platform that brings Gherkin-style BDD syntax to modern testing frameworks, enabling executable specifications that serve as living documentation.
 
-📖 **[Full Documentation →](https://livedoc.swedevtools.com/)**
+📖 **[Full Documentation →](https://livedoc.swedevtools.com/)** · 🔬 **[Live Test Results →](https://dotnetprofessional.github.io/LiveDoc/)**
 
 ## Packages
 
@@ -81,7 +81,7 @@ public class CalculatorTests : FeatureTest
 - ✨ **Gherkin Syntax** — Write tests using Given/When/Then
 - 📊 **Data Tables & Scenario Outlines** — Data-driven testing
 - 🎯 **Tag Filtering** — Include/exclude tests by tags
-- 🖥️ **[Live Viewer](https://livedoc.swedevtools.com/viewer/learn/getting-started)** — Real-time web UI for test results
+- 🖥️ **[Live Viewer](https://livedoc.swedevtools.com/viewer/learn/getting-started)** — Real-time web UI for test results ([see a live example](https://dotnetprofessional.github.io/LiveDoc/vitest/))
 - 📋 **Beautiful Output** — Formatted, colored test results in your terminal
 
 ## License

docs/docs/index.mdx

@@ -194,6 +194,36 @@ This works with any AI coding tool — **GitHub Copilot**, **Cursor**, **Claude
 
 ---
 
+## See It Live
+
+Want to see what LiveDoc produces? These reports are generated automatically by our CI pipeline on every commit:
+
+<div className="sdk-grid">
+
+<a className="sdk-card sdk-card--ts" href="https://dotnetprofessional.github.io/LiveDoc/vitest/" target="_blank" rel="noopener">
+
+### Vitest Test Results
+
+Browse the full LiveDoc Vitest test suite — features, specifications, and scenarios with pass/fail status, data tables, and step details.
+
+**View Vitest Report →**
+
+</a>
+
+<a className="sdk-card sdk-card--dotnet" href="https://dotnetprofessional.github.io/LiveDoc/xunit/" target="_blank" rel="noopener">
+
+### xUnit Test Results
+
+Browse the LiveDoc xUnit test suite — BDD features, journey tests, and .NET specifications.
+
+**View xUnit Report →**
+
+</a>
+
+</div>
+
+---
+
 ## Choose Your SDK
 
 <div className="sdk-grid">

docs/docs/viewer/learn/getting-started.mdx

@@ -174,6 +174,11 @@ graph LR
 - **Connect** via `LiveDocSpecReporter` (auto-discovers the viewer) or `LiveDocViewerReporter` (explicit URL)
 - **Run tests** and watch results stream into the browser
 
+:::tip See it live
+Want to see what the viewer looks like with real test data? Browse LiveDoc's own published test results:
+**[Vitest →](https://dotnetprofessional.github.io/LiveDoc/vitest/)** · **[xUnit →](https://dotnetprofessional.github.io/LiveDoc/xunit/)**
+:::
+
 ---
 
 ## Next Steps

docs/docs/vitest/guides/ci-cd.mdx

@@ -253,6 +253,17 @@ livedoc-tests:
 
 ---
 
+## Live Example
+
+LiveDoc's own CI pipeline produces static HTML reports on every commit. See the results:
+
+- **[Vitest Report →](https://dotnetprofessional.github.io/LiveDoc/vitest/)** — the LiveDoc Vitest test suite
+- **[xUnit Report →](https://dotnetprofessional.github.io/LiveDoc/xunit/)** — the LiveDoc xUnit test suite
+
+These are generated using exactly the pipeline described above — JSON export, static HTML conversion, and GitHub Pages deployment.
+
+---
+
 ## Troubleshooting
 
 | Problem | Cause | Solution |

packages/vitest/vitest.config.ci.ts

@@ -9,6 +9,7 @@ export default defineConfig({
     globals: true,
     environment: 'node',
     include: ['_src/test/**/*.Spec.ts'],
+    exclude: ['_src/test/Playwright/**'],  // Playwright tests need a running viewer + browsers — run locally or in dedicated e2e job
     setupFiles: ['./_src/app/setup.ts'],
     pool: 'forks',
     fileParallelism: false,