Fewer desk errors: clean first-try outputs, budgets that fit the job, stop distances stated up front

What changed for people using Bellwether

• The desk stops tripping over itself. On the day reports from 10–⁠11 September, roughly seven in ten portfolio-manager and researcher sessions had their first structured answer rejected and had to retry, a handful of Critic sessions ran out of budget before finishing, and three buys were refused for stops set too tight. This release fixes the causes: sessions get a budget sized to the job they are about to do (inside the role cap and the day's reservation, never above), the desk accepts a first answer that is right but wrapped oddly (and keeps the model's original attempt on file), and the minimum stop distance is shown to the portfolio manager as a number from the same rule the Executor enforces, so proposals arrive already compliant. Measured live on the pinned models: first-try structured answers went from 0 of 20 valid to 20 of 20, budget-error sessions 0, too-tight stops 0, Quant reports 27 of 27 valid.
• Quieter alerts. "Not enough budget left for this session" is now a single deduplicated notice with plain wording, not a repeated critical alert.
• Readiness knows about desk errors. The readiness report gains a "desk error sessions in the last day" check, so a bad day shows up as red instead of being discovered in a transcript.
• Help and console copy: the Guidance article now explains that the rule reading for a saved note arrives from the desk a few seconds after you save; an example in the Guidance panel and help was replaced with a neutral one.