Surface guarded refusals for autonomous triggers

[wsr3005]

Summary

• classify budget, rate-limit, and security-quarantine refusals on TurnResult
• deliver concise, idempotent budget and rate-limit notices for automated poll surfaces
• keep security-quarantine details silent for autonomous turns and redacted across Slack refusal paths
• preserve existing error-notice behavior without double-delivering guarded refusals

Verification

• affected tests: 218 passed
• npm run typecheck
• ESLint and Oxlint on affected files
• Prettier and git diff --check
• synthetic rendering of the automated notices; no live Slack workspace was used

Screenshot

The screenshot uses synthetic data. Security-quarantine details remain silent for autonomous turns.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[wsr3005]

This head is mergeable and has completed fresh local affected validation, typecheck, lint, formatting, and independent review. GitHub still shows the fork workflow as awaiting maintainer approval with no jobs started. When convenient, could a maintainer approve the workflow run?

[time-attack]

Thanks for this, @wsr3005 — and sorry for the slow response.

We're closing this PR. Per CONTRIBUTING.md, since coding agents write most of the underlying code now, we'd rather receive feature ideas as a short human-written note in adrs/ — informal is great, just the idea in your own words — and bugs as a plain issue. If we're aligned we're happy to burn our own tokens on the implementation, and we'll credit you as co-author.

We don't want your idea to get lost, so we've captured it in #727 to triage on our side. Please feel free to open an adrs/ note if you feel strongly about the approach. Appreciate you engaging with the repo!