Raylux 0.25.0: client licence metering and the alarm notification core

Client licence metering, the groundwork for alarm notification, and the licence format settled for good.

The licence format is final

The signed format now carries everything the commercial model needs, in one change rather than three — three separate format changes would have been three chances to miss the window. No licence had ever been issued, which is the only reason this was free to do.

Scripting, user-defined types, named queries and OPC UA became core capability at this release rather than paid options.

Client licence metering

The unit is a session, not a connection, and that was the whole problem. One operator screen opens several connections — the screen itself, each alarm table on it, and a shared background one. Counting connections would have charged one operator two seats for a screen with an alarm table and three for a screen with two: a per-screen, unpredictable price on the number a customer was sold.

• An established session is never cut off mid-use, and an older client that does not identify itself is admitted and never metered, so no gateway starts turning operators away after an upgrade.
• Ships with session administration: see who is connected, on which client, with which project open, and end a session.

Alarm notification groundwork

The roster, escalation policy, configuration and pipeline engine all landed. Nothing sends yet — there is no delivery method, so the service is deliberately not started rather than logging a failure on every alarm.

Fixes

• Lens opened a console window on every launch — the worst application in the product to get that wrong on, since a stray console on a kiosk panel is both visible to the operator and a route out to the desktop.
• The Studio and Lens setups showed two wizards in sequence.
• "New project from template" was empty on every installation ever shipped, because the templates were placed where the gateway does not look for them.