What happened
Provide a verified synthetic snapshot with source(seed:string)->middle:integer and sink(middle:string)->result:string, targeting sink with {seed:'x'}. The exported browserLocalPlan returns one incompatible source->sink proposal; a matching-string control returns one valid proposal.
Expected behavior
Required property names and declared JSON types must both match. Apply the same rule to starting-fact value types, predecessor selection, and generated field mappings. The planner remains an untrusted proposer.
Reproduction and environment
Reproduced against upstream 38e3c40af7b5df4bd177fe917fd968bf5b15d096 with the actual compiled Web package, Node v25.2.1, macOS arm64. Transport and persistent state use only disposable synthetic fixtures. The unchanged package's existing npm test suite passes. No live provider, production storage, or browser UI claim.
Governing Spec
1277-browser-local-workflow-composition v0.1.0 FR-002/FR-004; 068-public-platform-embedder-packages v1.0.0; supporting Spec 113 FR-002. This is a correction to existing supported behavior, not a proposal for deferred features or an immutable spec edit.
Proposed contribution
I am taking this bounded fix in a separate fix/planner-types topic branch. I will add a failing regression first, implement the smallest spec-aligned correction, run the complete Web package suite/build and an isolated review, and submit a draft with exact results and remaining gates. Please flag any overlapping work.
My contributor account cannot apply the repository's agent ownership label or access Project 1; please attach the appropriate agent label/project item for coordination. No severity label or maintainer approval is being asserted.
What happened
Provide a verified synthetic snapshot with source(seed:string)->middle:integer and sink(middle:string)->result:string, targeting sink with {seed:'x'}. The exported browserLocalPlan returns one incompatible source->sink proposal; a matching-string control returns one valid proposal.
Expected behavior
Required property names and declared JSON types must both match. Apply the same rule to starting-fact value types, predecessor selection, and generated field mappings. The planner remains an untrusted proposer.
Reproduction and environment
Reproduced against upstream
38e3c40af7b5df4bd177fe917fd968bf5b15d096with the actual compiled Web package, Node v25.2.1, macOS arm64. Transport and persistent state use only disposable synthetic fixtures. The unchanged package's existingnpm testsuite passes. No live provider, production storage, or browser UI claim.Governing Spec
1277-browser-local-workflow-composition v0.1.0 FR-002/FR-004; 068-public-platform-embedder-packages v1.0.0; supporting Spec 113 FR-002. This is a correction to existing supported behavior, not a proposal for deferred features or an immutable spec edit.
Proposed contribution
I am taking this bounded fix in a separate
fix/planner-typestopic branch. I will add a failing regression first, implement the smallest spec-aligned correction, run the complete Web package suite/build and an isolated review, and submit a draft with exact results and remaining gates. Please flag any overlapping work.My contributor account cannot apply the repository's agent ownership label or access Project 1; please attach the appropriate agent label/project item for coordination. No severity label or maintainer approval is being asserted.