From 664f23e7fe82b185d425ca94fd924e4fdc742f8e Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Sat, 11 Apr 2026 18:11:52 +0200 Subject: [PATCH] Keep dashboard screenshot visible on npm package README The dashboard image link used a repo-relative path, which does not resolve on package renderers that only see published files. Switch to the raw GitHub URL so the same dashboard screenshot is always visible in README views tied to the package page. Constraint: Preserve the existing dashboard screenshot asset without changing visual content Rejected: Add docs/images to npm package files list | increases published artifact size for a docs-only need Confidence: high Scope-risk: narrow Reversibility: clean Directive: Prefer absolute GitHub raw links for README-only media that is not part of published package files Tested: npm test (47/47) Not-tested: External third-party README mirror caching behavior --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cca9332..3dbc079 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ confusing ownership. `musafety` adds strict guardrails so parallel agent work stays safe and predictable. -![Multi-agent dashboard example](docs/images/dashboard-multi-agent.png) +![Multi-agent dashboard example](https://raw.githubusercontent.com/recodeecom/multiagent-safety/main/docs/images/dashboard-multi-agent.png) The dashboard above is the exact kind of parallel workflow this tool is built for.