|
|
||
|---|---|---|
| .. | ||
| account | ||
| control | ||
| negotiation | ||
| README.md | ||
| manifest.json | ||
README.md
Protocol v1 Conformance Fixtures
These fixtures define stable protocol examples for all implementations.
manifest.json lists each fixture suite. Consumers must reject unknown fixture format versions.
Each case has a unique name, an operation, an input, and an expected result.
An accepted case can include value. Consumers must compare that value after normalization.
A rejected case does not define an implementation-specific error message.
All identifiers, timestamps, keys, and tokens are synthetic. Do not add production data.
Fixture files must remain valid JSON. Do not use comments or language-specific numeric values.
Operations
parseControlFramevalidates one Control frame.selectProtocolVersionselects the highest common protocol version.selectCapabilitiesselects supported capabilities in supported-list order.acceptNegotiatedCapabilitiesvalidates the Server capability selection.parseDeviceRegistrationRequestvalidates an account or owned-role registration request.parseHostRegistrationCodeRequestvalidates a Host registration-code request.parseDeviceRefreshRequestvalidates a device token refresh request.parseDeviceTokenPairvalidates device access and refresh credentials.parseBrowserAuthorizationExchangeRequestvalidates a Browser credential exchange request.parseBrowserAuthorizationExchangeResponsevalidates Browser device credentials and account data.parseRpcErrorPayloadvalidates one Remote RPC error payload.encodeControlFrameWithLimitsvalidates and encodes a Control frame with negotiated limits.decodeControlFrameWithLimitsdecodes a Control frame with negotiated limits.
selected: null represents no common protocol version.
An omitted negotiated field represents a legacy Server without a capability list.