Extend runtime response validation to the remaining typed response shapes

[zeshi-du]

Follow-up to #266 (merged), which established the validation policy (looseObject + openWireLiteral + evidence-based nullish/optional — see the merge comment there) and wired it into the 7 run-path shapes.

Remaining work: bring the other typed response shapes onto the same schema layer incrementally — CliTest, CliTestCode, CliCreateTestResponse, CliProject, MeResponse (schema already stubbed as ME_IDENTITY_SCHEMA, currently unwired), UsageResponse, CliFailureSummary, and the rest of the as T casts in src/lib/http.ts helpers.

Guidelines:

• Follow feat(http): validate API responses at runtime with valibot instead of blind casts #266's policy exactly; no fail-closed on fields the server may legitimately add or omit.
• One PR per coherent group of shapes is fine (reads vs writes vs account surfaces) — no need for a single mega-PR.
• Each schema needs the same fixture-evidence discipline feat(http): validate API responses at runtime with valibot instead of blind casts #266 used (cite the test fixture that proves a field is optional vs nullable).

Good structured task for anyone who wants it — comment /assign to claim.

[Davidson3556]

/assign

[testsprite-hob]

Assigned to @Davidson3556. Thanks for taking this on. (2 more slots available.)

Your open assigned issues (1/3):
(none)