-- Custom outbound messages: a trigger, a template, and a transport.
--
-- Until now an outbound row was one of a handful of hard-coded emitters, each
-- with its own format and its own moment. This adds the general case: pick what
-- fires it, write what it says, and choose whether it leaves as a UDP datagram
-- or an HTTP request.
--
-- The HTTP half is what makes it useful for antenna switches — most of them are
-- driven by a URL like http://192.168.1.50/antenna?band=20m — and the band
-- change is the trigger they want, being rare by nature.
--
-- Empty on every existing row, which is what the hard-coded services expect.
ALTER TABLE integrations_udp ADD COLUMN trig      TEXT NOT NULL DEFAULT '';
ALTER TABLE integrations_udp ADD COLUMN template  TEXT NOT NULL DEFAULT '';
ALTER TABLE integrations_udp ADD COLUMN transport TEXT NOT NULL DEFAULT '';
ALTER TABLE integrations_udp ADD COLUMN url       TEXT NOT NULL DEFAULT '';
ALTER TABLE integrations_udp ADD COLUMN line_end  TEXT NOT NULL DEFAULT '';