Repository navigation
v0.2.0-rc.3
Pre-releaseAda MCP Server 0.2.0-rc.3
RC3 separates the installed skill/plugin entry from the exact Ada MCP runtime
it uses. This remains a Linux/AMD64 Debian Trixie Docker pilot with the same
pinned SDK/ALS and support boundaries. Python/MCP metadata uses 0.2.0rc3;
distribution metadata uses 0.2.0-rc.3. Actual published release assets establish
availability; this source document alone does not.
- Keep a compatible full/local or lightweight entry installed while selecting
another exact verified runtime/binding. Entry package version is independent
of the active server version; compatible updates require no plugin upload. - Require integer workflow contract 1 in authenticated release/runtime metadata.
Missing or unknown contracts need a compatible entry update before activation. - Inspect private pinned selection before using fallback acquisition. Explicit
activation uses no-clobber writes or expected-old-state backups and preserves
the old runtime/image/binding for rollback. Validate record ownership/type/size
on the same opened descriptor that supplies its bytes; reject unchecked swaps. - Return structured invalid results for malformed nested OCI binding metadata
while preserving the active pair. Keep source-only helper validation and
immutable image/source pins. - Retain files and their locator for later sessions. A custom selection path
is not automatically remembered; supply it again or explicitly retain it
through a supported host setting. Report session-only use where unavailable.
Public RC1/RC2 bytes remain immutable legacy baselines. RC2's entry has no
selection support and needs one initial entry update to gain it; its existing
update checker can still announce newer published releases. See the
first-install guide
and approved update/rollback procedure
for actual asset-digest verification, initial setup and activation.
A separate manual post-publication consumer check exercises the public RC2
runtime's actual notice of RC3 through MCP initialization/project results and
a fresh explicit check. Its real evidence must be inspected after publication;
unit fixtures do not establish that outcome. It does not install the target
or mutate a private Cloud plugin. See the
release procedure.
The support matrix
still limits semantic/tool acceptance. Compiler/tests remain separate. Actual
macOS, native Codex/Claude/OpenCode lifecycle and another account's Cloud import
remain development work. Preserve the original MIT and component notices under
licensing.