chart/app
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
..
analysis Keep the alert number out of the message and in the push body 2026-08-11 23:23:58 -05:00
api Number alerts, stamp them locally, and compact the zone list 2026-08-11 21:44:57 -05:00
bars Stop a zero-price tick and a late exchange bar corrupting the store 2026-08-10 17:10:24 -05:00
market Unify chart geometry and deepen 30m history 2026-08-11 04:08:02 -05:00
notify Implement M4 confluence alerts 2026-08-09 20:51:32 -05:00
__init__.py Implement M0 Yahoo market data and replay 2026-08-09 20:36:13 -05:00
config.py Number alerts, stamp them locally, and compact the zone list 2026-08-11 21:44:57 -05:00
runtime.py Keep the alert number out of the message and in the push body 2026-08-11 23:23:58 -05:00