MainSequence Desktop 0.4.18 preview

A connected MCP's names now live with its saved connection. Until 0.4.17 the saved record
held only the release UID and endpoint, because the release detail read when connecting
carries neither a name nor a repository; every listing then asked the backend twice (the
release directory, then the repository branch) to label the row, and a backend that was
restarting during a refresh showed Unnamed MCP. devtools 0.3.1 reads the release's
name and its repository's name once, when the MCP is connected, and stores them in
mcp-connections.json as name, display_name and code_repository_branch_uid. A
listing shows them without a backend request, and a connection saved by an earlier
version is completed by the first listing that can read its names. A name that cannot be
read is left out and never makes a working MCP unavailable. The Add MCP search still
labels its rows live, from the repository branch each row names.

Validation: 97 Node tests (the packaged-worker MCP test covers stored names, listing
without a backend request, the one-time completion of an old record, and denied directory
or branch reads), ten native Desktop simulator tests, loader validation and distribution
checks on Desktop's bundled Code 2.1.304. Against the local backend, the saved
MainSequenceCRMAPI connection that 0.4.17 had left without a name was completed by the
first listing (5.6 s) and listed from the file afterwards (46 ms, no backend request);
its tool catalog and the Add MCP search carried the same labels. Bundles devtools 0.3.1.
Update from the MainSequence marketplace and reload the plugin in the Code chat. Node 22+
required.

Source revision: 27314db. Archive SHA-256: 6458f9784f0847f2195db11e405392f1f8d84ae8024d7e0c19a6749319da9d8d.