feat(landing): consolidate use-case demo into unified trace view#226
Conversation
Merge separate Skills and Memory cards into a single agent card with an inline trace that shows skill calls and memory operations in order. Replace the flat use-case tab row with a scope-grouped layout (Personal / Organizations / Public) so visitors can place themselves without scanning twelve unrelated labels. Each of the twelve use cases now carries its own trace sequence in use-case-showcases.ts, and the post-trace summary block shows the actual MCP server and network allowlist from the skill config instead of a static "Skills used" pill list.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 824c9764a9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| label={activeUseCase.runtime.responseLabel} | ||
| text={activeUseCase.runtime.response} |
There was a problem hiding this comment.
This new ResponseBlock reads activeUseCase.runtime.responseLabel and activeUseCase.runtime.response, but the runtime payload built in use-case-showcases.ts only defines request/steps/outcome (plus the newly added trace), so both values are undefined for every use case. In practice this ships an empty response panel across the demo pages, which undercuts the new unified trace experience; either add responseLabel/response to each runtime entry or derive the block from existing fields before rendering.
Useful? React with 👍 / 👎.
1 participant
Summary
["github"]from the generated agent config) with the actual MCP server and network allowlist from the skill configTest plan
cd packages/landing && bun run buildpasses/for/<use-case>/pages render the trace + MCP + allowlist block (verified via Playwright)