[Wittig18]

Summary

I replaced the empty BreakpointManager stub in apps/web/src/components/debug/BreakpointManager.tsx with a client component. I also rendered it on apps/web/src/app/debug/page.tsx. I couldn't run anything here, so none of it has been compiled, linted or run in the browser. The component keeps breakpoint state in memory using types that mirror the Rust Breakpoint and BreakpointCondition for the four kinds the issue lists: FunctionEntry, HostFunction, ContractCall and BudgetThreshold. The add form has a type selector and shows only the fields that type needs: contract address, function name or CPU instruction limit. It checks required fields and that the CPU limit is a positive integer. Each breakpoint in the list has an enable/disable switch, a hit count and a delete button. The styling uses the same slate and violet Tailwind classes as DecodeForm. There is no backend wiring, so hit counts always show 0 for now. The component also accepts optional breakpoints and onChange props so replay can hook in later.

Changed files

• apps/web/src/app/debug/page.tsx
• apps/web/src/components/debug/BreakpointManager.tsx

Test plan

The web app has no existing test setup, so I added no tests. CI should run the apps/web lint, type-check and build (next build). To check it by hand, open /debug, add one breakpoint of each type, toggle them, delete one, and confirm the validation errors appear for empty or invalid input.

This PR was created as a draft by the issue solver bot. It will remain a
draft until repository CI passes.

Closes #489

[mintlify]

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit c342efc.

Approve preview

[drips-wave]

@Wittig18 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[coderabbitai]

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codeZe-us]

Hi @Wittig18 is this PR ready for review?