TICK — TRADING — V2.9 live test checklist + paste/setup + validation plan

Context

• Active lane: trading
• HQ outcome (today): Finalize and ship Indicator V2.9 (files + paste instructions) and complete the execution checklist so it’s ready for live chart testing tomorrow.

This artifact is NOT trading advice and contains NO signals. It’s a QA + execution-truth checklist to reduce mistakes when you paste/test on TradingView.

A) Paste / Install (repeatable, no surprises)

1. Open Pine Editor

• TradingView → Chart → Pine Editor.

2. Create new indicator script

• New → Indicator.
• Paste the full V2.9 code.
• Save as: ENVO — UI Clarity — V2.9 (or your canonical name).

3. Compile clean

• Ensure there are 0 errors.
• If warnings exist, record them (don’t ignore silently).

4. Add to chart

• Add to chart.
• Confirm it renders (HUD, labels, tables, etc.).

5. Baseline settings (defaults)

• Confirm-on-close: ON by default.
• Session filters: set to your intended sessions; ensure timezone is correct.
• Any higher-timeframe inputs: confirm they reference the intended TF and do not repaint.

Deliverable expectation: after this step, you can remove/re-add the indicator and it comes back identical with saved defaults.

B) Non-repaint / execution-truth validation

Goal: verify the script only changes state on confirmed bars (or your declared rules), and that labels/alerts match what you see.

Checklist:

• All request.security calls (if any) have lookahead OFF.
• Any intra-bar computations are either:
  • explicitly allowed and labeled as such, OR
  • gated behind bar close confirmation.
• Any persistent variables (var) reset rules are correct across sessions and symbols.

Replay test protocol (15 min):

• Pick 1 symbol, 1 timeframe.
• Turn Replay on.
• Step bar-by-bar for ~200 bars.
• Confirm:
  • The reason codes / pass-block reasons do not change retroactively after the bar closes.
  • Counters increment only when the event is actually confirmed.

Record findings:

• What changed unexpectedly?
• Was it a repaint issue or a logic issue?

C) Alerts: payload + guardrails (automation-ready)

You’re verifying structure, not trading performance.

Checklist:

• Every alert condition has a unique, stable name.
• JSON payload (if used) is valid JSON (no trailing commas; quotes correct).
• Include fields (minimum):
  • version, symbol, timeframe, event, ts, barIndex, confirmState, reasons[].
• Ensure any cooldown / max trades/day logic is clearly separated from signal logic.

Test:

• Trigger an alert in replay.
• Copy the raw alert text.
• Validate it with a JSON validator.

D) Visual QA (HUD / labels / tables)

Checklist:

• HUD doesn’t overlap price on common resolutions (laptop + ultrawide).
• Colors are readable on dark + light backgrounds.
• Labels don’t spam (rate limit or only on events).
• Win/Loss counters: confirm definition (what counts as win/loss) is documented in-script or in a tooltip.

E) Tomorrow’s live chart test (no execution)

Goal: prove reliability on a live updating chart (without placing orders).

Protocol:

1. Load 3 symbols you care about.
2. Load 2 timeframes each (e.g., 5m + 15m).
3. Keep chart open for 60–90 minutes.
4. Log:

• CPU/lag issues
• alert spam
• label clutter
• unexpected state changes

Outcome definition:

• Ready = stable, non-repainting (per declared rules), alerts structured, UI readable.

NEXT (if issues found):

• Create a punchlist with exact reproduction steps + screenshots.