Skip to content

feat(app-feedback): mock UI for the feedback pipeline: every issue and how far the pipeline has taken it - #4639

Draft
ATX24 wants to merge 1 commit into
baml/feedback-part-3d-evalsfrom
baml/feedback-part-3e-ui
Draft

feat(app-feedback): mock UI for the feedback pipeline: every issue and how far the pipeline has taken it#4639
ATX24 wants to merge 1 commit into
baml/feedback-part-3d-evalsfrom
baml/feedback-part-3e-ui

Conversation

@ATX24

@ATX24 ATX24 commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

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).

Stack (bottom to top)

  1. feat(atb2): sandbox for handle_issue: worktree lifecycle, allowlisted env, repro pre-check on canary #4634 sandbox
  2. feat(atb2): the gate: fmt, clippy, changed-crate tests, nextest, insta, the baml corpus; judged by exit code #4635 the gate
  3. feat(atb2): handle_issue: a design pass, then a fix pass in the sandbox; PR body; outcome; agents run on Fable #4636 handle_issue
  4. feat(atb2): handle_issue evals; run_tests.sh picks a pipeline stage; //# headers for the playground graph #4637 evals, run_tests.sh, //# headers
  5. feat(app-feedback): mock UI for the feedback pipeline: every issue and how far the pipeline has taken it #4639 app-feedback mock UI (this PR; independent of the BAML code, stacked so it lands after it)

Verified: tsc --noEmit, eslint, next build (15 static pages).

…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).
@vercel

vercel Bot commented Aug 31, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
beps Ready Ready Preview Aug 31, 2026 4:12am
promptfiddle2 Ready Ready Preview Aug 31, 2026 4:12am

Request Review

@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

⏭️ Performance benchmarks were skipped

Perf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to canary/main.

To run them on this PR, do any of the following, then push a commit (or re-run CI):

  • Add RUN_CODSPEED=1 to the PR description, or
  • Include run-perf or /perf in the PR title or any commit message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant