Module server_capabilities 

GET /v1/capabilities — runtime discovery of what this lean-ctx instance supports, so any client (any language) can branch on real features instead of trial calls. The HTTP route lives in http_server; the payload builder lives here so it stays compiled (and drift-tested) without the http-server feature.

Contract: docs/contracts/capabilities-contract-v1.md. The set of TOP_LEVEL_KEYS is the stable contract surface and is bound to that doc by tests/capabilities_contract_up_to_date.rs.

Not to be confused with crate::core::capabilities, which models RBAC permissions (fs:read, …). This module describes server capabilities.

Constants

COMMUNITY_ALWAYS_ON_FEATURES

Always-on Community capabilities. They are explicit Trust Core product records rather than capabilities inferred to be free because they are local.

COMMUNITY_OPTIONAL_FEATURES

Community capabilities gated only by compilation.

TOP_LEVEL_KEYS

Stable, documented top-level keys of the capabilities document.

Functions

capabilities_value

Build the capabilities document for this running instance.