🎨 Palette: Add concrete example tooltips to financial parameter inputs

[aarjava]

💡 What:
Added help tooltips to various statistical and financial parameter inputs in the src/dashboard.py Streamlit application.

The following inputs now have tooltips with concrete examples:

• Factor Beta Window: "Lookback window for factor beta estimation (e.g., 63 days = ~3 months)."
• Regime Vol Window: "Lookback window for historical volatility (e.g., 21 days = ~1 month)."
• ADV Participation %: "Max percentage of average daily volume allowed per trade (e.g., 0.10 = 10%)."
• High Volatility Quantile: "Threshold for 'High' volatility regime. E.g., 0.80 means the top 20% most volatile days are classified as High Volatility."
• Transaction Cost (bps): "Trading friction in basis points. 10 bps = 0.10%."
• Max Drawdown Alert: "Triggers an alert if drawdown exceeds this threshold (e.g., -0.2 = -20%)."
• Volatility Alert (ann.): "Triggers an alert if annualized volatility exceeds this threshold (e.g., 0.35 = 35%)."
• Beta Alert: "Triggers an alert if portfolio beta to benchmark exceeds this threshold."
• Days-to-Liquidate Alert: "Triggers an alert if estimated days to liquidate the portfolio exceeds this value."

Also created .Jules/palette.md to journal the learning that inputs involving statistical/financial parameters require concrete examples for clarity.

🎯 Why:
Parameters like "basis points" or "quantiles" can be opaque or easily misinterpreted (e.g., entering 0.1 for 10 bps instead of 10). By providing concrete examples directly in the UI where the user makes the input, we reduce cognitive load, prevent input errors, and make the application more accessible to users with varying levels of financial domain expertise.

📸 Before/After:
(See attached screenshot from verification step demonstrating the tooltip on hover).

♿ Accessibility:
Improves cognitive accessibility by providing immediate, contextual help text without requiring the user to seek external documentation. Streamlit's native help tooltips are also standard and screen-reader friendly compared to custom implementations.

---

PR created automatically by Jules for task 6219316027630247623 started by @aarjava

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.