MainSequence Desktop 0.4.17 preview

An MCP refresh survives a backend that is briefly unreachable. Connecting or disconnecting
an MCP re-reads the environment's saved connections and each one's tool catalog; when the
backend restarted during that refresh (a local Django development server reloads on every
code change), the remaining MCP was relabelled Unnamed MCP and its tools were dropped
until the next refresh. The pane now remembers the last name the backend resolved for each
connection and keeps it while the lookup is unavailable; the worker also labels a connection
with the release's own name (such as crm) when its repository cannot be read. A connection
whose catalog cannot be read keeps the tools registered by the previous refresh and is
named in a warning under the Tools list, with Refresh or Re-register tools reading
it again; a failed listing keeps the current environment's tools in place. A disconnected
MCP still loses its tools, and an environment change still denies them immediately.

Validation: 97 Node tests (two new pane tests covering the degraded refresh after a
disconnect and a failed listing, and the packaged-worker naming test extended with the
release-name fallback), ten native Desktop simulator tests, loader validation and
distribution checks on Desktop's bundled Code 2.1.304. Against the local
backend, whose container restarted every one to three minutes during the investigation,
the rebuilt worker labelled the saved MainSequenceCRMAPI connection crm ·
MainSequenceCRMAPI once the container answered again, where the listing taken during a
restart had carried no name at all. Bundles
devtools 0.2.8 unchanged. Update from the MainSequence marketplace and reload the plugin
in the Code chat. Node 22+ required.

Source revision: be118c3. Archive SHA-256: 149298296aabf31be0d82c31838577db44ffe73ace9f992f5502bb3a24a33490.