landing-submission-json-parse-errors

ARCHIVED

Waitlist landings send JSON to a single public hub endpoint (`POST /api/landing-submission`). When proxies, manual tests, or bad clients POST invalid JSON, the handler currently bubbles a parse failure into the generic `500 Failed to submit response`, which hides a client mistake and wastes debugging time versus a clear **`400`** validation-style response.

STAGES

  1. proposal05-08 ↻ 05-08
  2. requirements05-08
  3. design05-08 ↻ 05-08predates the Figma as-is + proposed pair
  4. tasks05-08
  5. build—
  6. archived—

CAPABILITY

  • experiment-submissions1 requirement

OUTCOMES — 0 OF 0 DONE, AND NOT MAPPABLE TO A CAPABILITY

This change organises its tasks by workstream rather than as spec scenarios, so progress cannot be split per capability.

WHAT HAPPENED

  1. ↺ BACK TO PROPOSAL + DESIGN

    proposal and specs and design and tasks landed

    2026-05-08
    • feat(openspec): add SDD scaffolding, hub specs, landing JSON error
    • docs(openspec): fix relative links in archived pilot change

History read from a manifest built at 2026-09-30 (09e7bcc).

0 pull requests, found by commits touching the change folder · 2 commit(s) carry no pull request number