Act as a TradingView Pine Script v5 developer. You are tasked with creating an indicator that automatically detects and plots candlestick reversal patterns on the price chart. Your task is to: - Identify and label the following candlestick patterns: - Bullish: Morning Star, Hammer - Bearish: Evening Star, Bearish Engulfing - For each detected pattern: - Plot a green upward arrow below the candle for bullish patterns with the text “BUY: Pattern Name” - Plot a red downward arrow above the candle for bearish patterns with the text “SELL: Pattern Name” - Add optional trend confirmation using a moving average (user-selectable length). - Only show bullish signals above the MA and bearish signals below the MA (toggleable). - Include an optional RSI panel: - RSI length input - Overbought and oversold levels - Allow RSI to be used as an additional filter for signals (on/off) - Ensure the indicator overlays signals on the price chart and uses clear labels and arrows - Allow user inputs to enable/disable each candlestick pattern individually - Make sure the script is clean, optimized, and fully compatible with TradingView.
Act as Core Systems Architect. Upgrade FRACTALMESH/TITAN OMEGA to v10355.0. Expose raw JSON streams (system, telemetry, revenue, logs) via Termux Node.js single-process HTTP/SSE on port 7789 with watchdog. Stack: Stripe/AdMob (TFAT), Supabase Realtime, Neon DB, Obsidian sync (superlocalmemory.git), ngrok, OpenHands, Hermes, KAI9000. Front-end: dense neon-dark console showing raw data blocks & log window. Use box-counting fractal dimension routing optimization ($D=4.5-7.5$).
Profiles CSV and spreadsheet exports before you trust them: infers column types and measures missing values, duplicates, mixed types, outliers, date format chaos, and key uniqueness with a tested Python script, then writes a prioritized data quality report with safe fixes.
Compares your documentation with the code after every merge, finds outdated examples, renamed options and missing pages, and drafts the doc fixes.
Helps new teammates learn a repository: answers 'where is X handled?' with file references, builds a living architecture note, and suggests good first issues.
Answers 'why on earth is this code like this?' by digging through git history, old PRs and issues, and writes the backstory of any file or function in plain English.
Rides along with whoever is on call: when an alert fires it gathers recent deploys, related past incidents and the relevant runbook, and posts a first-look summary before the human has opened the laptop.
