From b774a5a1fa1666542a8a6072eaaa9602a7d120ba Mon Sep 17 00:00:00 2001 From: wonhyo Date: Tue, 28 Jul 2026 12:52:49 +0900 Subject: [PATCH] Make the debugger visible before installation Show the real v0.2.0 synthetic workbench near the README introduction so prospective users can understand the route-to-evidence workflow before bootstrapping the project. Constraint: Keep generated screenshots out of Git while exposing only synthetic fixture data. Rejected: Commit the PNG to the repository | The repository policy excludes screenshots and generated QA artifacts. Confidence: high Scope-risk: narrow Directive: Update the demo only with synthetic fixtures and a versioned public asset. Tested: GitHub GFM rendering, public asset HTTP 200, SHA-256 match, and git diff --check. Not-tested: README rendering on non-GitHub Markdown hosts. --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 54a50de..5110826 100644 --- a/README.md +++ b/README.md @@ -21,6 +21,15 @@ remain stable compatibility identifiers in `v0.2.x`. It binds the UI/API to loopback HTTPS. It does not contact production services, databases, or external URLs, and it has no telemetry or export path. +## Demo + +[![code-debugger v0.2.0 showing Routes, an expanded orders execution graph, Flow Outline, and Evidence Inspector for the synthetic Nuxt and Django fixture](https://github.com/achieve0410/code-debugger/releases/download/v0.2.0/code-debugger-v0.2.0-demo.png)](https://github.com/achieve0410/code-debugger/releases/download/v0.2.0/code-debugger-v0.2.0-demo.png) + +*Actual `v0.2.0` workbench using only synthetic `fixtures/nuxt-django` data. +Select **Analyze**, choose `/orders`, and use **Expand all** to reveal the +frontend-to-Django flow. Select any node or edge to inspect its bounded evidence +on the right. Click the image for the full-size view.* + ## What it shows For the synthetic Nuxt/Django fixture, selecting `/orders` exposes a bounded