Add live AI agent workflow discovery demo - #53
Merged
Conversation
Adds /discover.html, a page that fetches the real Traverse capability registry client-side and composes a workflow from whatever's actually published right now (no fixtures). Graph is rendered with AntV G6: Goal -> Traverse system (AI Agent/MCP/Runtime, grouped in one combo) -> capability chain -> Result, with a live idle/running/completed execution-state simulation and human-readable capability names. Also fixes .claude/launch.json, which was pointing at `serve dist/` (stale build output) instead of the Astro dev server. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/discover.htmlpage: fetches the real, live Traverse capability registry (registry.traverse-framework.com/catalog.json) client-side and composes a workflow from whatever's actually published right now — no fixtures, no precomputed data.Goal → Traverse system (AI Agent / MCP / Runtime, grouped in one combo) → capability chain → Result, with dashed (discovery) vs. solid (data flow) edges and a live idle → running → completed execution-state simulation, matching the three-state pattern from the UMA chapter-13 reference app..claude/launch.json, which was pointing atserve dist/(stale build output) instead of the actual Astro dev server.Test plan
npm run buildpasses clean, page included in generated sitemap🤖 Generated with Claude Code