Skip to content

PeerInfo uses kind/version instead of spec's name/version (§6.2) #148

@nficano

Description

@nficano

Category: spec-conformance Severity: major
Location: src/Messages/Session/PeerInfo.php:17-49
Spec: ARCP v1.1 §6.2

What

Spec §6.2 examples show client: {name, version} and runtime: {name, version}. SDK serialises kind/version. Conformant peers will not find the name field.

Evidence

    public function __construct(
        public string $kind,
        public string $version,
        public ?string $fingerprint = null,
        public ?string $principal = null,
        public ?string $trustLevel = null,
    ) {
        ...
    public function toArray(): array
    {
        $out = [
            'kind' => $this->kind,
            'version' => $this->version,
        ];

Proposed fix

Rename kind to name (or add it alongside) so the wire field is name.

Acceptance criteria

  • client/runtime payloads carry a name field per spec example.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions