chart/app/analysis
Chris Amow 07f7befc08 Keep the alert number out of the message and in the push body
Producing a real alert to check the wiring showed #47 twice in one Events row:
once as the badge the browser draws from the `number` field, and again at the
start of the message, because the number had been prefixed onto the shared
string.

ntfy carries plain text and has nowhere else to put a number or a timestamp, so
those belong in a push body built for it. The browser already receives `number`
and `at` as fields and formats its own local time, so its message stays clean.
Alert now carries both: `message` for a screen, `push` for a phone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 23:23:58 -05:00
..
__init__.py Implement M3 projected daily moving averages 2026-08-09 20:44:11 -05:00
alerts.py Keep the alert number out of the message and in the push body 2026-08-11 23:23:58 -05:00
bar_space.py Price trendlines across bars, add one-shot alerts, collapse layers, drop 1h MAs 2026-08-10 04:15:05 -05:00
confluence.py Price trendlines across bars, add one-shot alerts, collapse layers, drop 1h MAs 2026-08-10 04:15:05 -05:00
horizontals.py Add prior-day levels and session VWAP; fix alert repetition they exposed 2026-08-10 00:36:21 -05:00
indicators.py Implement M3 projected daily moving averages 2026-08-09 20:44:11 -05:00
levels.py Price trendlines across bars, add one-shot alerts, collapse layers, drop 1h MAs 2026-08-10 04:15:05 -05:00
manual_lines.py symbol improvements 2026-08-11 19:51:39 -05:00
moving_averages.py Implement M3 projected daily moving averages 2026-08-09 20:44:11 -05:00
vwap.py Add prior-day levels and session VWAP; fix alert repetition they exposed 2026-08-10 00:36:21 -05:00