feat(app-feedback): mock UI for the feedback pipeline: every issue and how far the pipeline has taken it - #4639
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
⏭️ Performance benchmarks were skippedPerf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to To run them on this PR, do any of the following, then push a commit (or re-run CI):
|
bf87954 to
337c191
Compare
Binary size checks passed✅ 7 passed
Generated by |
…d how far the pipeline has taken it typescript2/app-feedback, a Next 15 app on app-beps's stack and theme tokens. Mock data only (src/lib/mock-data.ts); the types mirror models.baml (Issue, IssueStatus) and handle_issue.baml (HandleOutcome) so real data is a data-source change later. - / : stat tiles (open, agent running, draft PRs, needs a human, landed), status / subsystem / difficulty filters, search, list and board views. Every row carries a pipeline strip: one segment per stage (triaged, organized, gauged, design pass, fix pass, gate, PR), colored done / running / failed / pending. - /issues/[id]: description, repros, resolution plan, design doc, comments, the pipeline timeline, and the last handle_issue run (outcome, turns, time, gate steps, PR).
typescript2/app-feedback, a Next 15 app on app-beps's stack and theme
tokens. Mock data only (src/lib/mock-data.ts); the types mirror
models.baml (Issue, IssueStatus) and handle_issue.baml (HandleOutcome)
so real data is a data-source change later.
landed), status / subsystem / difficulty filters, search, list and
board views. Every row carries a pipeline strip: one segment per
stage (triaged, organized, gauged, design pass, fix pass, gate, PR),
colored done / running / failed / pending.
comments, the pipeline timeline, and the last handle_issue run
(outcome, turns, time, gate steps, PR).
Stack (bottom to top)
//#headersVerified:
tsc --noEmit,eslint,next build(15 static pages).