[enkerewpo]

A package manifest listed its capabilities by contract id only. Which transport each one is served over (MCP, gRPC, ROS 2) was decided in code and only visible in Atlas after boot, so the package catalog, Robonix Hub and anyone writing a client had to read the code or start the package to find out.

Manifest format (manifestVersion stays 1; older rbnx ignores the field):

capabilities:
  - name: robonix/service/voiceprint/identify
    transport: grpc
  - name: robonix/service/voiceprint/list
    transport: [grpc, mcp]     # one contract served over several transports

Checks:

• When the manifest is read: an unknown or duplicate transport, a repeated contract, or a transport the contract's mode cannot use (streams are gRPC only; topic_in/topic_out are gRPC or ROS 2) is an error. A missing transport is a warning while packages migrate.
• During boot: rbnx compares the (contract, transport) pairs each provider registers in Atlas with the manifest, for package-managed and Soma-managed packages. Registered but not declared, registered without a declared transport, and declared but not registered once the provider is ACTIVE are each warned about once. None of these fail the start. The shared lifecycle driver the framework adds on its own is not reported.

The 18 manifests in this repository now declare what their code registers. Tests cover parsing, the mode check and the comparison, including one against a real Atlas service. The book's packaging spec is updated in syswonder/robonix-book.