CYGURU INDICATOR v3.3 — INSTALLATION AND VALIDATION

Complete Pine source: CyGuru_Indicator_v3_3.pine (not a patch).
Revised from the supplied CyGuru v3.2 RC1 source.

1. Keep the old script as a backup. Paste the complete new file into a new
   INDICATOR in Pine Editor. Save and Add to chart. Standard OANDA:XAUUSD 15m.
2. Compile in TradingView. This release has not yet been compiled or backtested
   there. Report any compiler error before enabling it for live decisions.
3. JSON lifecycle alerts are enabled by default. Stop the previous CyGuru/
   66 Gold Signals alert only when ready to replace it; leave other engines alone.
4. Create ONE alert for CyGuru Indicator: Any alert() function call.
   Use the signal webhook URL from your existing signal alert (NOT the candles
   webhook). Keep JSON generated by the script; do not paste a manual message.
5. Recreate the alert after changing source, settings, symbol or timeframe.
   TradingView alerts use a saved snapshot. Historical signals are not replayed.

WHAT CHANGED
- Same structure, sweeps, CHoCH, trend and pullback candidate rules.
- Default experimental selection: quality >=75/100, TP1 reward/risk >=1,
  stop distance 0.25–2 ATR, signal candle range <=2 ATR,
  entry within 1 ATR of execution EMA.
- Last confirmed 1H close/EMA20/EMA50 and EMA20 slope must align.
- Three complete bars between accepted signals; one unresolved setup at a time.
  Defaults are research choices, not optimized or proven profitable parameters.
- Independent tracker sends SIGNAL, FILL, TARGET, STOP, STOP_AFTER_TARGET and
  WINDOW_END. It continues tracking older accepted signals when overlap is enabled.
- One lifecycle update per origin per chart candle; same-bar outcomes take
  precedence over a separate FILL event. Each event keeps frozen original levels.
- Retains the supplied ordered one-minute OHLC audit and original stop after TP1.
- Website now accepts these lifecycle events under the existing CyGuru identity.
  No secrets belong in Pine. No old outcomes are manufactured or overwritten.

STATUS MEANING
PENDING ENTRY: setup proposed, no subsequent modeled entry touch yet.
ACTIVE: modeled entry touch reported; TP1/TP2 may already have been reached.
SUCCESS: TP1 was reached before SL after modeled entry. This is NOT net profit.
FAILED: modeled entry was followed by SL before TP1.
CLOSED: modeled lifecycle ended (SL, TP3, deadline or unfilled cancellation).
UNVERIFIED: no decided TP1/SL result, timeout, missing origin or conflicting updates.
A gap beyond the pending stop cancels unfilled and does not count as a loss.
An unfilled setup expires on the first bar after four eligible pending bars.
A filled setup times out after 64 bars from its fill, using the existing audit rule.
The signal candle itself never fills its own newly generated proposal.

WHY OLD SUCCESS=0 WAS INCONCLUSIVE
The supplied v3.2 JSON sent entry_proposed only; it did not transmit outcome
updates. Unverified proposals are not demonstrated losses. Their history remains
unverified. Do not compare their zero verified wins with the new measured stream.

VALIDATE BEFORE CLAIMING AN IMPROVEMENT
Use identical provider, date range, history and nominal execution assumptions.
Compare repaired baseline with filtered profile. Baseline: execution filter OFF,
confirmed 1H OFF, cooldown 0, One unresolved setup OFF. Keep adaptive settings equal.
Enable Performance Dashboard to inspect signals, fills, TP1, SL and timeouts.
Record unfilled/timeout rates and sample counts, not just TP1 hit rate. Filters
change the adaptive learning population; the comparison is between full profiles.
Separate development and untouched test periods, then forward-test on new data.
For net expectancy, drawdown and position risk, use a strategy backtest with
broker-appropriate spread, commission, slippage and position sizing. This is an
indicator; its nominal dashboard is not a portfolio or broker execution backtest.
OHLC intrabar ordering is inferred, not observed tick execution. Profitability,
lower risk and better results have not been established.

Official Pine references:
https://www.tradingview.com/pine-script-docs/concepts/alerts/
https://www.tradingview.com/pine-script-docs/concepts/other-timeframes-and-data/