Skip to content

Resolve generic stream types in graph metadata - #270

Draft
cboulay wants to merge 2 commits into
cboulay/sanitize-enum-leakfrom
cboulay/resolve-generic-stream-metadata
Draft

cboulay wants to merge 2 commits into
cboulay/sanitize-enum-leakfrom
cboulay/resolve-generic-stream-metadata

Conversation

@cboulay

@cboulay cboulay commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

Inherited generic stream declarations were advertised as ~MessageInType / ~MessageOutType, even when concrete subclasses specialize them to AxisArray. This prevented dashboard connections from passing declared-type validation.

Resolve explicit generic base arguments before emitting stream and dynamic-settings metadata. Shared stream declarations remain unchanged; unbound or ambiguous types remain unresolved.

Stacked on #267 (cboulay/sanitize-enum-leak). Draft #271 merges the JSON-schema settings branch on top of this PR so the stack can be tested and released from one tip.

Validation: 25 tests pass covering metadata resolution, graph execution and GraphContext sessions; verified AsArray and Flatten advertise AxisArray in the INTENT environment.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant