deemesh-hub 1.3.0

Bundles deemesh SDK 1.3.0; see the SDK release for what changed there - instantaneous power addresses, the Mitsubishi tool management table, new status codes -22 and -23, one breaking change (/machine/toolArea/toolGroupCount on Fanuc answers status -20 instead of 0 without the Tool Life Management option), and fixes including lathe Y-offset columns and Siemens alarm reads that never recovered after a dropped link.

The hub itself changed as well:

• GET /version tells you what you are talking to: {"status":0,"value":{"hub":"1.3.0","arch":"x64","sdk":"1.3.0"}}. It sits inside the IP whitelist; GET /health stays the bare, whitelist-exempt liveness probe it was.
• GET /help (also served at the root /) is a plain-text manual for programs and AI agents: where everything is, the command grammar, the status codes worth acting on, and a sane first conversation with a hub. Point an agent at it and it can drive the hub without the packaged documents.
• File explorer: select a program as the main program from the browser (confirmation first, result read back and shown as a modal so the view you are on does not change); the current main program of every channel shown in the header, with a check mark on that file in the tree (both rendered from data already fetched - no extra machine traffic); and a timeout field that applies to every read and write the explorer makes, since listings and transfers grow with file sizes. The header keeps a fixed two-row height, matched with the data model page.
• The dashboard status-code view carries the new -22 and -23.
• Alarm reads now survive dropped links. An SDK fix, noted here because hubs run unattended: on a link that drops periodically, every alarm address used to time out forever after the first drop until the hub was restarted. Verified against a link that cuts every 75 minutes - the reads recover on their own after each reconnection.

Notes

• Windows Firewall asks once on first run whether to allow the hub. Click Allow if other PCs will call it (it is not a virus warning). Details in docs/HUB_KO.md / HUB_EN.md section 1.1.
• The hub is designed for a trusted network inside the plant (IP whitelist + admin PIN, HTTPS available, no built-in user login). To expose it beyond that, put it behind an authenticating reverse proxy.
• Tested on a SINUMERIK 840D sl control on a test bench (Siemens), a FANUC Series 31i control on a test bench, a production machine and FANUC NC Guide with Series 30i and 0i projects, mill and lathe (Fanuc), and NC Trainer2 plus (Mitsubishi M800 series, lathe and mill).