Seen on production: POST /api/v1/start with body {bad answers 422 invalid_name ("name is 1-40 characters…"), which sends an agent hunting for a field it did send; no invalid_json code exists anywhere in src.
Done when
Files I expect to change: src/http/ (the body reader), src/contract/, test/
Risks: changing a status for clients that matched on 422; keep the shape
Suggested brief: scout or torque. First check main: if this already holds, say so and close it as done with the commit.
Seen on production: POST /api/v1/start with body
{badanswers 422invalid_name("name is 1-40 characters…"), which sends an agent hunting for a field it did send; noinvalid_jsoncode exists anywhere in src.Done when
Files I expect to change: src/http/ (the body reader), src/contract/, test/
Risks: changing a status for clients that matched on 422; keep the shape
Suggested brief: scout or torque. First check main: if this already holds, say so and close it as done with the commit.