TView Alerts copier 1.0.9 — Windows desktop package

REQUIREMENTS
A Windows x64 desktop with the .NET 10 Desktop Runtime (x64) installed.
Get the Windows Desktop Runtime from Microsoft's official download page:
https://dotnet.microsoft.com/en-us/download/dotnet/10.0#runtime-desktop

START
1. Extract every file in this ZIP into the same folder.
2. Open Start.cmd or TViewAlertsCopier.exe.
3. Keep the DLL, .deps.json, and .runtimeconfig.json beside the EXE.

QUICK SETUP
1. Select the TradingView chart window. Keep Alerts > Log open on its newest records.
2. Use the QTY, BUY, and SELL coordinate buttons. After clicking each one,
   hover over its matching destination control until the five-second countdown ends.
3. Choose the alert name and check interval. Set the destination to the asset you intend to trade.
4. Click Start copying. Use Stop copying to stop forwarding new signals.

Version 1.0.9 adds optional development support through Stripe, an embedded payment
QR code, and six rotating reminder designs with persistent local scheduling.

The app starts with copying stopped. Coordinate bindings are for the current session.
Keep both windows visible and Windows awake and unlocked. Reconfigure manual
coordinate targets after changing the destination layout. Visual targets may need
a new crop after appearance changes. QTY must allow editing and read-back.
Sent confirms a mouse click, not broker acceptance or an order fill.

TARGET TRACKING
The app remembers the target application/window and available page/tab context.
Tracked accessible fields and standard buttons are located again before each signal
and follow window movement, resizing and element reflow. Recreated controls require
a unique stable accessibility ID in the same saved context. Updated locations appear in LOG.
Keep the saved target tab selected. Missing or ambiguous controls stop transmission.
Targets marked Coordinate target still need manual rebinding after layout/scale changes.
Without a visual template, shared painted panels require manual coordinate bindings.
The layout must remain stable while the app enters QTY and clicks a side button.

AUTOMATIC TARGET CHECKS
After QTY, BUY and SELL are set, their positions are checked every minute, including
while copying is stopped. These passive checks update locations and LOG without
typing quantity, clicking buttons, moving the pointer or activating another window.
The target-check line shows the latest result. Covered visual targets are reported
unavailable. A new signal still performs fresh checks before entry and clicking,
and takes priority over a background check. Alert polling uses its own selected interval.
Busy operations can defer the minute check. A failed passive check retains bindings
and reports the issue; each signal still requires its own successful target checks.

VISUAL TRACKING FOR PAINTED BUY/SELL
Check Visual tracking for custom BUY/SELL before setting a painted button.
After the five-second countdown, drag a region on the screenshot that contains
the crosshair and the static BUY or SELL label. Avoid variable prices, quantities,
timers and plain backgrounds. Click Use selection and repeat for the other side.
Templates stay in local memory for the session and appear in the button tooltips.
The app searches only the saved window/page, rejects ambiguous or missing images,
updates the click position, and checks the image again before clicking.
Keep the target window fully visible and uncovered. Appearance changes may require
a new template. Visual matching is slower than UIA. QTY still requires verified UIA input.
To remove a visual template, uncheck the option and bind that button again.
The app does not switch destination broker tabs; keep the saved destination tab selected.

AUTOMATIC RECONNECTION
Auto-return to TradingView tab is enabled by default. The next check returns to
the exact saved browser tab and selects Alerts > Log when that subtab is available.
TradingView Desktop is supported through its saved tab GUID. Tab activity is checked
before every read, including when hidden charts continue to expose readable alerts.
This also applies while copying is stopped. Uncheck the option to use other browser
tabs without automatic return. Returning to a tab does not start copying.
A closed/replaced tab or a restarted browser requires selecting the chart again.

Temporary Alerts Log read failures display RECONNECTING and retry automatically.
No signals are sent during recovery. Copying resumes only when the previous log
records can be matched unambiguously. Existing history is not replayed. If the old
records are permanently gone, stop copying and select the chart again to establish
a new baseline. Stop copying also cancels reconnection. A restarted TradingView
process requires selecting its window again. Unconfirmed target clicks are not retried.

OPTIONAL SUPPORT
Click SUPPORT, to the left of LOG and HELP, for Pay with Stripe, a QR code and
reminder preferences. Subscribe opens the same Stripe payment link:
https://buy.stripe.com/7sY5kCeM7fm49DZ21OdQQ00
Review the payment amount and subscription terms on Stripe before paying.
Continue for free or close the window to use all application features without payment.

Reminders: first run, day 7, day 14, then at least 30 days apart.
The portable app counts days from its first run. Missed dates are not replayed
on consecutive launches. Maybe later postpones reminders at least 30 days.
I've supported development is voluntary confirmation and postpones at least 90 days;
the app does not verify payment. Both choices move later reminders to monthly cadence.
Don't show payment reminders disables them. Re-enable them through SUPPORT;
the next reminder will be at least 30 days later. Preferences and dates survive
restarts and updates in %LOCALAPPDATA%\TViewAlertsCopier\support-reminders.json.
Reminders wait until copying/selection have stopped and the main window is active.
SUPPORT pauses TradingView polling while open, so tab auto-return does not interrupt checkout.

HELP
Open HELP in the app for the full instructions, limitations, and a copyable TradingView alert message.
The JSON must resolve to a positive quantity and data set to buy or sell. The alert
filter uses its display name in the TradingView Log, not strategy_name in the JSON.
Regular checks read the newest record first, not the whole table. Additional new
entries are collected only when needed. Polling and processing do not guarantee latency.

APPLICATION LOG
Click LOG, immediately to the left of HELP, to view dated errors and application
messages in a separate window. New entries appear automatically. Select a row to
read its full message. This window can stay open while copying is active.
Records are saved locally in %LOCALAPPDATA%\TViewAlertsCopier\application-log.jsonl
and remain available after restarting. This file is separate from the transmission journal.

PRIVACY
The copier processes alerts locally and does not forward them through webhooks.
TradingView and broker platforms still use their own online services.
The local transmission journal is under %LOCALAPPDATA%\TViewAlertsCopier.

This package contains the application files only. It contains no user alert data,
account information, configuration bindings, transmission journals, or debug symbols.
