fix(service): restore Zod 4 query coercion - #1256
Conversation
|
[PHASE: RESEARCH] Issue #1250 was read first and re-baselined against current
Run record: |
|
[PHASE: PLAN] The implementation plan is locked under milestone ruling D6; no local formal PLAN-EVAL is launched. The decisive test sends Evaluation remains composed through draft→ready augment, OpenHands, and the orchestrator pre-merge gate. Run record: |
|
[PHASE: IMPL] Commit Evidence
Acceptance precisionThe implementation directly proves numeric coercion and the non-typed HTTP/docs-shaped regression. The live issue's broader fresh-seeded-project and MCP-execution wording is not overstated: #1204's tools inspect schemas and emit curl templates but do not execute service operations. The generated schema + existing read-tool suite are recorded as supporting evidence for orchestrator review. NextTransition to ready-for-review / |
Summary
Correct the oRPC smart-coercion adapter used by
@netscript/serviceso scaffolded Zod-4 contracts accept numeric query/path parameters sent as HTTP strings. The regression generates the OpenAPI parameter and issues the Scalar/docs-shapedGET /issues/board?cycleId=1request, asserting the handler receives numeric1.Scope
packages/service· Archetype 4 + service overlaySlices
cf773ec38b29105addb29105addValidation
cycleId: 1cycleIdis a numeric query parameterpackages/servicetest task: 87 passed, 0 failedmilestone-run.md(orchestrator waiver)Harness
.llm/runs/fix-onboarding-quickwin-1250--1250/Drift / Debt
deno.lockmodification; it is excluded.packages/servicefolder-role and Scalar asset debt is unchanged.Definition of Done
Acceptance evidence