From the #3696 review: the legacy Run-it accessory is suppressed by a single boolean ("some run proposal will render"), not per-suite. A turn that creates 3+ suites, where a given suite's run_eval_suite proposal falls past MAX_PROPOSAL_BLOCKS=5, leaves that suite created and linked but with no way to run it from Slack.
Fix options: match proposals to suites (proposal target → suiteId) and suppress the accessory per-suite, or have the server guarantee run proposals for created suites always fit under the cap (order them first).
Files: slack-app/listeners/views/proposal-builder.js (rendersRunProposal), slack-app/listeners/events/run-and-reply.js:145.
🤖 Generated with Claude Code
From the #3696 review: the legacy Run-it accessory is suppressed by a single boolean ("some run proposal will render"), not per-suite. A turn that creates 3+ suites, where a given suite's run_eval_suite proposal falls past MAX_PROPOSAL_BLOCKS=5, leaves that suite created and linked but with no way to run it from Slack.
Fix options: match proposals to suites (proposal target → suiteId) and suppress the accessory per-suite, or have the server guarantee run proposals for created suites always fit under the cap (order them first).
Files: slack-app/listeners/views/proposal-builder.js (rendersRunProposal), slack-app/listeners/events/run-and-reply.js:145.
🤖 Generated with Claude Code