Owner Connection Id Records Parity
completetasks7/7owner-connection-id-records-parity
openspec/changes/owner-connection-id-records-parity/View on GitHub →
Artifacts
Official change artifacts tracked under openspec/.
Proposal
Owner-agent REST callers can discover connectionid values from /v1/streams, but the polyfill owner read path still requires connectorid on stream record reads. This makes the public REST contract weaker than MCP and weaker than the advertised connection_id query shape.
Design
The reference read surface has two adjacent routes with different purposes:
Tasks (7/7)
Spec Deltas (1)
Affected capabilities
Capability specs this change proposes to modify.